Thomas_LOLW

Yeah, but it seems to be connected to the same setting in DCS. When I switch off "wake turbulence", it apparently also disables the burble and the ground effect on the carrier.

It took me some time but meanwhile I manage to land despite burble effect on wire 2-4 in 95% of all cases. I still get C ratings, but I do not care, since I use the Bankler mission for training and get 65-70 points in most cases. Therefore I think the effect is ok and can be handled with some exercise and training, but the LSO ratings need improvement.

no stupid question at all...it is a virtual squadron. Yeah...I don't know why we make our lives harder...it is just established routine I guess...as a newbie I did not question it when I joined.

...I manually downloaded the 64 bit dll file (https://znix.xyz/OpenComposite/download.php?arch=x64&branch=openxr) and pasted it into the DCS bin folder, overwriting the old file. Since then - no more issues with OpenXR on DCS servers

I think this settings is only relevant for the Windows Mixed Reality Home Screen...correct me if I am wrong.

...Same here - same error on certain MP servers. Unfortunately also on our squadron server - but interestingly, not always, on some missions it works without hassles. I have now switched to an older version of OpenComposite, which seems to help so far. Cheers, Thomas

I fly with the Reverb G2 and Nvidia RTX 3080, FPS goes down to 30 on the SC at night (motion reprojection on), but it is still very enjoyable, since you do not have fast movements on the carrier deck anyway...you are supposed to taxi very slowly, especially at night. As soon as I reach the cat, fps goes up to usual 45 fps. I guess even with the RTX 4090 you will not get native 90 fps in DCS VR, you may crank up some graphic settings, but you will stay at 45 fps...

in our squadron, we always fly 30° angled approach. So, after the inbound call, just add 30° to the radial given by AI Marshal, put it into the HSI and fly towards the SC TACAN on that radial until you are 15 nm away from the carrier. Then enter the final bearing and arc to that final bearing. Works fine for us!

I wonder if meanwhile someone has upgraded from a 3080 to a 3090 and can share his/here experience? I am running DCS on a 3080 in VR just fine, but I need to lower the ground textures on the Syria map. Prices for a 3090 are quite reasonable at the moment, and it seems that waiting for the ridiculously expensive 40xx cards makes no sense, at least in DCS where we do not have raytracing etc. Thanks folks!

according to HP, the resolution is 2160 x 2160 (per eye)

First of all, many thanks to Nikoel for creating this post and and keeping it updated, I am sure it took (and still takes) a lot of time. Everything worked fine for me, without any hassles. However, I noticed that the performance with my new Reverb GT2 is worse than with my old Oculus Quest 2 (running with Oculus software). With the Quest 2, I had stable 45 frames (AWS turned on), with the Reverb, frames drop down to 30 quite often - using the same DCS settings of course. Seems that Quest is doing a better job with the VR drivers, since the screen resolution between the 2 headsets is not so much different. I wonder if some else here has the same experience? Cheers, Thomas

...Do I still need a Steam Account for downloading the WMR software, or can I get it somewhere else? I have Windows 11 and it seems it is not installed by default... Thanks, Thomas

It seems you can also switch between Mode C (reporting altitude as well) and non-Mode C.

Thanks guys! our squadron uses 4 digit codes, so I guess I have to use a different mode.

I have recently joined a virtual squadron which uses Lot ATC. The tower controller assigns transponder codes before take off, but I am not sure how to enter them in the DCS Hornet. Has anyone experience with this? I know it is possible to use SRS for this purpose, but I would prefer to do it in the Hornet cockpit. Many thanks, Thomas

...I flew the F-14 yesterday and the AP does work as described in the update report from Heatblur (vertical velocity needs to be within +/- 200 fpm). However, you should be either well below Mach 1 or above, if you are close to sonic speed, the vertical velocity gets crazy (don't know if that is a bug or intended).

I played around with different settings to get rid of the stutters, and the outcome was quite surprising... I am running a medium ranged system with a GTX 1070 and 4 core CPU overclocked to 4.6 GHz. Still I prefer to run DCS in 4K on my 55 inch TV screen since I love the immersion it gives. I have always been running DCS (and X-Plane 11) at 30 Hz, since constant 60 Hz is not achievable with decent graphic settings, and 30 Hz - if you get used to it - is working mostly really well with any flight simulation (of course not with action games..). Using a GSYNC Monitor is not an option when you have Track IR. So, I ended with the following settings: - Windows Game Mode: off - Full screen optimization: disabled for the .exe file - VSYNC and full screen mode: disabled in DCS - NVIDIA inspector settings: VSYNC with 1/2 refresh rate enabled (the TV runs at 60 Hz) - RTSS: frame rate locked to 29.98 - UHD colors activated on the TV (my TV does not have HDR, unfortunately) Within DCS, I have set all settings to HIGH. Wenn I start my flight, I press "ALT + ENTER" to get into full screen mode, and from now on I have a really good performance, no stutters, excellent look and feel...even on the Supercarrier which did not work really well before I made these changes. Again, 30 Hz refresh rate is not for everyone, but believe me, you get used to it after a couple of hours. The investments needed to get solid 60 Hz is not worth for me at the moment (crazy prices for decent graphic cards...) Thomas