lemoen

I'm glad they got changed. I can see them in VR now!

The Tf-51 is free and can take-off and land in short distances on open fields. Also, it has CTLD support so you can cart around repair crates and SAMs / EW. It allows anyone to help with logistics even if they don't fly helos. While I agree the L-39 would be great on red, Blue's options are less stellar in this regard.

yeah now divide that by 2 to get where us VR users are.

1000 km /h = 1000 000m / h = 1 000 000 m / 3600s = 277m/s t = d / v = 3400 / 277 ~ 13s

It is not temperature related. Its more likely that there's a bug related to shader cache or something, maybe some objects are never cached and they are cached while in a mission and the stutters occur as they get created.

That doesn't work for VR but the mirror display on your main monitor will be antialiased I think.

We're all having this problem. Use 2xMSAA, lower your preload to 60000 or so. Seemed to help for me. Look in MSI Afterburner, your graphics VRAM is probably getting maxed out too (I know, I know)

Vulcan will free up the CPU, not the GPU, so I'm not holding my breath wrt using higher MSAA. VR users don't need a high quality algorithm (until we have high res displays), we just need something to smooth the worst of the jaggies. I use 2x and its OK but it would be nice to have something faster.

The builtin MSAA works fine but is slow as all hell. It would be nice if we had the option to use a lower quality but fast AA algorithm. Oculus recently added 8x MSAA support to their SDK, I wonder if ED will add this for Rift users. I guess not.

ED hasn't said anything so no use asking I guess. I'm one of the lucky ones with 32GB of RAM I bought before the prices went insane. Also, we are on a beta release, you should expect things to not work 100%, bugs come out when 1000s of people use software. 2.5 uses quite a lot of RAM, in a MP server like Blue Flag or 104th it can easily hit 16GB or more. So people are wondering if this is intended, the future or something else. That's all.

This is normal. Your card is probably not fast enough for 90 in-game so it tries the next factor of two of 90 (in this case half), if that doesn't work it'll try 22.5 and so on. I run basically at 45 max on my 1070 all the time. I use the ctrl+2 option but most of them just results in 45.

I have died in 2.5 in the Gazelle and have not seen this bug again.

2 cores at 100%, CPU at 50% (4 cores, no HT).

I see 50% utilisation max, besides for some transients over 50%, which I assume is loading or windows or something, on my i5 (4 cores). This along with people complaining about stutters, low GPU usage etc tells me nothing has changed.

We're never going back to 1.5.8. This is an issue with DCS, not Blue Flag and has been reported to ED by xcom and drexx (Dynamic DCS server)

If you're only getting 30fps in SP you'll be having pain in MP on big servers. I suggest you lower your graphics much more and try again. MSAA + DS is pretty slow right now, try switching off MSAA in-game and enable 2x in your AMD panel and see how that works for you. Also, lower shadows, view distance, texture quality, terrain quality. You only have 4GB of vram to work with so it is touch and go already.

It will be better for loading of assets, obviously. But all the unit AI / flight models / collision detection / line of sight calcs etc are done on that one thread and at the moment, a CPU with more cores isn't going to help those things.

This bug was fixed a while ago? Is it back?

Multiple effects going on. Suffice it to say, most of DCS is still running in those same 2 threads. These threads however, may jump from one core to another core so you'll see multiple cores being used. Some object loading and stuff may be done in parallel over all the cores though. Don't be fooled, DCS is still mostly the way it has been.

Nvidia anti-aliasing doesn't to anything for me. Is there a trick I'm missing? I'm suspecting a good dose of placebo around here. Graphs and screenshots or it didn't happen!

The Mig-21 has it too and it has it BAD. Most of the fuselage is missing, which is a pain because with the canopy open you should be able to look at the outside.

Its a DCS issue. Dynamic DCS has the same problem and xcom and drexx both reported it to ED already. Sent from my iPhone using Tapatalk

For ED Devs, I provide a link to my last Blue Flag Track, a screenshot of afterburner's perf graphs and a screenshot of my settings. The framerate and GPU usage was erratic. I hope this helps in some way. Let me know if I can provide more data. My system specs are: Windows 10, 32GB DDR4, i5-7600k@4.5GHz, GTX1070 8GB Edit: Running with Oculus Rift CV1, PD=1.3 https://www.dropbox.com/sh/7v511puz3mfp9fo/AABc0rmH4HOGoIRCyYTBY7K0a?dl=0

The M model's Vivienne FLIR mode is very very dark. Tried using it on Blue Flag (day mission) and I had to use the non-flir mode to hope to see anything. I haven't tried the viewer in other models.

Disable MSAA in game. Enable FXAA in nvidia panel. Enable deferred shading. lower gamma. Sent from my iPhone using Tapatalk