Lee Dove

I found that binding both engine throttles to the same lever in fact solved all my ground and take-off issues. With split throttles it would randomly spin one way or the other. Levers on Hotas work fine so I wonder if it is a mossie thing.

I am having trouble finding the right settings to stop the cockpit interior including the floor looking way to bright. It is almost like external light is coming through the fuselage. Is there any specific setting that will reduce it? I have tried "cockpit illumination" and gamma but no luck.

No, everything works as before.

I think the problem here is that 2.9MT and the Occulus app fight for a single thread. I had massive problems until I changed to Virtual Desktop and all the problems got solved. I had no issues with ST implementation.

Hi, I can't go above 1.3 with a 4080 super and keep 72fps (Quest 3) so I would suggest that 1.7 is to much for a 4070. Just a 0.1 change seems to make a big difference.

I turned on frame generation (just got a 4080s) in the Nvidia graphics settings and got a big performance boost in DCS. In Windows 10 you seem to have to turn it on but it is on by default in win 11. https://www.tomshardware.com/how-to/enable-frame-generation-windows-10

Hi, Are you using the Occulus app? I could not get it to work most of the time on MT. I switched to Virtual Desktop and everything now works great on Quest 3. I think the Occulus app. fights with DCS for one of teh threads and ends up blocking it as I was getting 1 thread maxed out in MT .

Ok. I got this problem with MT while using Quest 2 and Occulus, ST was fine. When I got a Quest 3 I had problems with the Link disconnecting AND still had the MT problem. To solve the link issue I got Virtual Desktop, that solved both issues. It seems that there is a conflict between Occulus app and DCS MT when it come to thread usage . The VD setup is miles better in terms of quality and speed in both DCS and MSFS. Best thing I ever did. You do have to pay for VD and have a 5ghz wifi repeater. I use one of the powerline ones so not a big expense given the quality increase.

Which VR headset are you using. I had this issue with the Occulus app.

Is it the same with ST?

The quest will run without the occulus app , both 2 and 3 if you use Virtual Desktop. The only limitation is that it has to use a wireless link not the wired. I get better performance from VD wireless compared to Occulus wired Link. In fact when I got my Quest 3 I had issues with the Link which made me try VD. Best thing I ever did

I had this and the FPS counter was off screen when using VR. I had to start non VR and move the display box. try dragging the stats box to somewhere in the middle of the screen and toggle the display (1st press -> fps , 2nd press -> stats , 3rd = off)

The issues seems to have been with the Oculus App. I have moved to Virtual Desktop VR and now get great performance. I think the Occ. App and the DCS rendering thread are fighting for the same processor.

I think your problem is related to the Oculus app amd MT. I had no problems with the Occulus app in ST but endless issues in MT and had to reduce quality right down to get it to work. I have just installed Virtual Desktop and run wireless which with airlink was rubbish but works great. I have decided that the Occulus App when run with DCS MT overloads the CPU rendering thread.

If you select DLSS the DLAA is not relevant. I think DLSS uses DLAA anyway. The DLAA setting is if you want it without DLSS.

I reduced the PD down to 1.0 as per an earlier post. I was getting the same performance in ST and MT. Today after 1 mission I loaded and MT was down to 7-10 fps. I tried in ST and it was back to 45 fps. I will try with DSR disabled. Update: I disabled DSR and it seemed to help. I will keep track over the next few days.

This has now returned . Even with the reduce settings MT is 10 fps and ST 45 fps.

So you see it is ST but can't enable VR?

They changed the updater to start MT in 2.9. You can still start ST using the exe in the bin folder not calling the updater. I got caught out by this.

Thanks - I reduced the PD and now works. I can get the PD up to approx. 1.3 but above that the problem returns. Strange that I can run 1.8 and higher cloud settings in ST though. In ST I seem to be GPU/CPU bound with both working but in MT it is solid CPU bound and the GPU has plenty of capacity left. It would seem that FD have moved a lot of rendering load to a single thread and now overload it in MT. Probably gone a bit to far with the load redistribution.

DCS settings Nvidia settings

Which VR settings? Other files attached - Using a Quest 3 (had same problem with Quest 2) DxDiag.txt dcs.log

I had a problem in early 2.8 MT with running VR. It would become CPU bound and run at 5-6 fps. In ST it would run fine 60 FPS. I thought it had been fixed in later 2.8 patches but I am not sure as I used ST a lot of the time. In 2.9 (MT) I get the same problem - CPU bound in VR. In 2d I get 200+ fps and in VR I get 6. In ST 2.9 I get 90fps. Any ideas ?

I was doing some testing and was able to use (and get FPS improvement) in both the links I used to start 2.8. One calls the updater and used to be ST and the other direct to MT. Now to get ST I have to use the dcs.exe direct. This had me confused when people said DLSS was only available in MT and I seemed to get it in both (not the case). So does using the updater now start MT?

Hi, Occulus is OpenXR. So you use it automatically. I run it the same as you. I am having issues with very low frame rates and Main Thread blocking with MT in VR. MT in 2d works great and ST Vr and 2d are fine.