matze140

Hi, i recently had a crash due to accidently typing a "." in the UFC scratchpad and then pasting it into the Radio Frequency Line Line. It is reproducable all the time. Someone else experiencing the same? OR_Ser_Trainingsmap_Syria_Mittag_V1_4-20240317-140946.trk dcs.log-20240317-131724.zip

For me, enabling HT on Intel CPU (13900K) solved most of the stuttering and inconsistent frametimes. I disabled it last year when there was the general advise to deactivate it. Today i gave it a try and it works. Maybe someone else can give it a try?!

I got this spikes in VR on a 4090…unstable 90 fps (refresh rate of Crystal). Only when there is a huge headroom on GPU the frametimes are a flatline. On 72Hz mode it is slightly better. Dropping LOT Switch factor to 0.1 makes it also better…so maybe its a bottleneck in loading things to the VRAM. My rig is a 13900k build with 64GB of ram…so I can’t imagine it’s related to a raw Hardware Problem. After restarting DCS several times I suddenly got one perfectly smooth session. but after a PC restart ist back to the stuttery mess.

Yes. Received the reservation number this morning.

That’s absolutely true. Before DFR availible I also run with pimax play at 0.75 what is something in your region. The picture was much better than the Reverb G2 although it has nearly the same render resolution.

At what resolution are you playing then?

To be exactly, as soon as you „set the exact resolution“, you are underscaling the Headset. 5100X4300 is the native resolution of the Crystal. I know there is a lot of confusion about that, cause people on steam VR stated the 100% as a wrong resolution, but this is the correct number. Be in mind it has to over render because of Distortion Profile. As soon as you are touching the resolution override function you are wasting picture quality.

I think i found the issue! It’s the HDR-Effect/ general brightness applied slightly different for each eye, because of the difference in 3D room position. It may be realistic in real life and also in terms of rendering, but IRL we are not limited by 8 Bit colors. It would be better to couple the brightness level of both eyes. Don’t know difficult this may be. @BIGNEWY Maybe the Dev-Team could have a look at this?

But the World scale is only applied to the cockpit/GUI. The world scale in general can’t be adjusted or did I miss s.th.?

C:\Users\<YOUR PROFILE>\AppData\Local\Quad-Views-Foveated

The problem is in fact the TallyMouse tool. It makes „,“ instead of „.“! Only Dots work. I got this Problem a few hours ago and solved it by rewrite the Settings file which is created by the Tool!

I just think most of the people dont see it because night time flights are not so common for the majority. Maybe it’s the same thing as the super carrier wires only rendered in one eye when they were out of their resting position. Meanwhile this was fixed. But yes. Its very annoying for me. Feels like your eyes are broken. You loose every stereoscopic vision of the clouds when rendered different in both eyes. I will ask some guys in my sqaudron to test this on their rig.

I have the same issue. Different colouration of clouds in night time/ low light level between left and right eye. The problem are the dark areas that are barely visible. Its like color banding differently for each eye. In ST the problem does not exist. Maybe there is a slight deviation in gamma or something else for left and right eye in MT VR. like the already fixed shadow problem at night in VR. Maybe a developer could have a look at this.

Pi-Tool RR 0,75. DCS: medium/high. Flat ground shadows, MSAA Off, Clouds Standard, OpenXR Toolkit: RR UNTOUCHED, Foveated rendering custom setup. 90+ FPS 90% of the time. Some 80-90 FPS the rest of the time. I dont mind the missing MSAA because the resolution is so high and the image so clear. In 0,75 RR its so much clearer than my old Reverb G2.

I had the same behaviour everytime i pull too much Gs. In F2 view, you see the horizontal and vertical stabs osszilating a bit even if there are no control inputs. Maybe a sort of damage model, but it is not described anywhere.