TOViper

Major²: OpenXR Toolkit (I don't know what I would do without the Toolkit when flying in VR; without the tool DCS is just a messy-ugly-awful terrain stuttering thing) Often: Buddy Spike MP scenarios and COOP Server scenarios. Sometimes: SRS Rarely: A-4E Seldomly: VAICOM Pro That's it.

Hello Nineline, maybe tweaking this setting might help users to limit the draw distance in mirrors while the resolution setting for displays is set to 1024 or 1024 each frame, which should help a lot with performance if you consider increasing the number 2048 or higher values (I think its some kind of detail setting for such displays/mirrors)

Dear guys at ED, please make the far_clip setting work in section CameraMirrors, like that: CameraMirrors = { Low = { thisIsMirror = true; near_clip = 0.02; far_clip = 10000; Currently, DCS is not taking care of that setting for mirrors. Here are two screenshots: The scene in the normal view (1) doesn't show them correctly (caused by a far_clip setting of 30000), but the mirror (2) shows the rocks SW of Kobuleti. (1) (2) Thank you!! TOViper

Guys, I have flown only a few little hours on the newest update, so I have two questions: 1.) Is the performance (fps wise and running in 3D, not the menu) better than before for you? 2.) Have you removed all shaders (fxo's, meta2, NVidia shaders in case you use NVidia card) from your computer BEFORE running the newest DCS version? I am asking because I had no overheating issues due to fps limiting in VR (45 frames with ASW set to ON).

Will the EA release contain a manual with the most important items like checklists for all phases of flight/engagement?

Interesting ...

I did 2 tests today, and the result is the following: When flying in 20 ft AGL, and having Clutter & Grass ON, the fps value is ~120. When flying in 20 ft AGL, and having Clutter & Grass OFF, the fps value is ~170. When transitioning from 0 ft to 1200 ft, and having Clutter & Grass ON, the fps value changes more or less constantly from ~120 to ~180 (capped/limited by DCS), but I cannot see that "step function". I cannot reproduce that magic 900 feet bug, despite low altitudes is still a frame killer. I did my last tests months ago, and with another setup (now RTX 3080 instead of GTX 1080). I am wondering that Nineline didn't find any informaton in the bug tracker which marks that problem as "solved" or "ready for testing" or similar. Did it resolve by its own? Flying AH-64: Flying AJS37:

Hey Nineline, good morning! This topic contains also some little information about the 900 feet issue, but it doesn't show any new knowledge. After work I will try to produce a track file, and at the same time record it as MP4 to share it on YT.

Thanks and good hunting If you need someone to test something you may need, just call me!

Thank you for posting that information westr and Nineline for coming in on this! This is the thread, having already 15 pages of reports and discussions:

I have that issue as well, and IT IS disappointing, because other maps simply don't show that - as I call it - bug. Neiter RB nor ED have ever acknowledged it (not that I know), but instead they prefer to keep quiet about. Pfff.

Does anyone know how we could get access to the code? I could imagine merging the app into the www.viggen.training website, which is currently hosting the study-level based training for the Viggen only. There is still some webspace left ...

13 pages in A0 format at font size 8? Doesn't sound too bad Seriously, please ED do whatever you can to keep the modules alive. I was a little stunned - but OTOH happy - about the fact that the SA map is still in sale, because this map is also one of the most beautiful places to fly, despite I know its not used by many MP servers, which I find really really sad. I already lost the Hawk (no discussion about its low over-all quality), and TBH ... I would become really angry about losing SA map, therefore I keep my three thumbs pressed that this nasty story finally comes to a good end. Good luck guys!

Actually not! I wasn't aware that the RB15 is affected too. Should I add it?

Hey itsthatguy! Following your idea I added a note to the manual. null