Jump to content

chroma_aus

Members
  • Posts

    12
  • Joined

  • Last visited

Everything posted by chroma_aus

  1. This is a long-standing issue I've had with the Mirage, and it seems to have gotten worse over time. Particularly in the cockpit, the shimmer is significantly worse than any other module, to the point that I have trouble reading anything without a bit of zoom. Some of the weapons (in particular the S530) look almost cell-shaded with how strongly the edges are aliased. There seems to be a bit of a performance hit in the F1 cockpit as well. It's a real shame because the Mirage might be my favourite aircraft to fly, but the visuals are just such a mess compared to literally everything else. I know a lot of people have experienced the same thing, and a lot of people haven't, so here's the question - has anyone managed to fix it? Some particular setting that reduces the shimmer to a bearable level? I'm running at 1080p with an RX 5700XT. Textures on High, MSAA x2, Anisotropic filtering x16, no sharpening or upscaling. DCS inherently has a bit of shimmer, but these settings look good for every other module, so I'm hoping to finally get the Mirage F1 working too.
  2. Userbase alienation aside, devs should always strive to keep vendor choice available. I switched to AMD last generation after years of Nvidia, simply because their cards were no longer making sense at the price point. Locking the community into RTX (or any other vendor for that matter) when there are open alternatives available would be shortsighted and quite possibly detrimental to the community in future, when it comes time for upgrades.
  3. Just disable them if it bothers you. Insert the line "no_easter_eggs = true" in autoexec.cfg.
  4. I had the same issue, turned out to be GIMP's dds exporter. Export the file as something else (png or psd) and use Nvidia's texture tools exporter to convert to dds.
  5. Just over 10GB for me (download size, not installation size). Update sizes usually depend on how many modules/maps you have installed.
  6. Mirage 2000 and JF-17 have it. There's no humidity simulation in DCS right now so they occur every time you go transonic, just like all the other vapour effects.
  7. Does anyone know whether canopy reflections are planned for the Mirage F1? Right now there's just a sort of matte grey sheen when you look at it side-on, and I couldn't find anything mentioning whether that'll be the final implementation. Just looks a little out-of-place compared to how polished the rest of the cockpit is.
  8. Allocation =/= usage. DCS is designed to allocate as much memory as it can to itself, which can appear as usage in Task Manager. It doesn't necessarily mean it's using all of it, just that it's holding it reserved - this is why lots of people can have good performance with <64GB, and still see enormous memory usage the moment they upgrade. Even when you do have usage higher than 32 gigs (possible in the case of users like yourself), a lot of the data DCS stores is not high priority, like unloaded terrain, and you won't see performance suffer even if it's streamed occasionally from an SSD pagefile. With that and the price of DDR5 in mind, 64 gigs just doesn't make much sense in my opinion.
  9. Go for 32 gigs in 16x2, you can always upgrade later if needed. Right now, DCS's major memory-related bottleneck is VRAM, and while it'll allocate everything you give it memory-wise, not all of it actually gets utilised and so the performance improvement with more memory will be minimal.
  10. The Conquest server has a similar concept and was great to play on while it had a population. It was just about the only place where Mirages and Flankers could be employed to their full potential, so hopefully Tempest succeeds and retains its playerbase long-term.
  11. Because nearly all the multiplayer servers run Open Beta, and always have. ED's probably just adding that now to cut down on the daily masses of people asking why they can't see anything on the connection list. There's also no reason not to run Open Beta, since Stable is just an older version of OB with no changes made. Both versions are essentially as buggy as one another, with the exception that OB gets fixes first.
×
×
  • Create New...