Lange_666

The image on your 2D screen doesn't hurt VR performance. No worries about that.

Means you couldn't connect to the ED servers for authorization of your account (probably an issue on their side). The topline reads "Authorization is valid for 2d 23h 59h" which means you can play 3 days without being logged in. In general these connection problems are solved quickly.

We are on page 20 already. Just keep going.

It's in here (posted a few times):

That's because they don't read what's been posted here and from people (i don't mention their names but one of them is called YoYo), who post the same complaint over and over again. If they wouldn't do that, it would be just 5 pages and people wouldn't have to go through 19 pages of half crap to find out what the problem and or solutions are.

There's a button "Transfer to DCS". Once you have set your waypoints, revert to the plane's cockpit press the "Transfer to DCS" button. This will then transfer the waypoints into the plane's NAV system. You'll see The Way do its job, just like you would do it yourself manually.

Oculus App: Settings ---> General Tab ---> Scroll to the bottom If you reverted back to V62 you can now block the update by performing the steps below: Simply browse to C:\Program Files\Oculus (or where you installed your application) Rename folder \Staging to bak.Staging Rename folder \tmp to bak.tmp Create a new file called Staging (with no extension, just create a new txt file and remove the extension .txt, then confirm when Windows says the file my unusable) Create a new file called tmp (also, no extension) This blocks the update. When there is an update, you still get a notification that there is an update and that it is in progress but if you check it's queued and the update will be blocked. Just reverse the steps and restart the app to let the update go through.

Just start at page one and read a bit, it's posted a zillion times already.

No need to go the CMD road to rename the files, just use Explorer, select the file, choose rename and remove the extension. Then on the prompt that it might become unusable, just hit YES.

One thing that bugs me a bit in your video are the values in the upper right corner. FPS seems to be at 120 but if you look at the 2 you'll see another number behind it. Same goes for other values. Also, for a fixed FPS 60 the frametime should be 16.6ms. Yours reed 18.8ms (for 120FPS?) but also there is another number under it. Or is that due to the 2 extra monitors?

Do you let your FPS fluctuate or do you use a capped FPS? If using a fluctuating FPS, what if you set it to like 60 or 120 fixed (in the nVidia control panel)?

Does it happen when TrackIR is not running and you use the keyboard to look around?

I've never seen V-Sync/G-Sync cause a stutter like that.

Did you make an exception for the DCS folders (Saved Games and install folder) in your antivirus software?

This is how you can block an update: Also, when blocking is in place you may see the taskbar blink (or shift if centered) briefly every 5 minutes. This is NOT a Windows problem but Oculus VR Runtime service checking for an update even if Oculus main software isn't running. If you stop it, the blinking stops until the next reboot.

Works fine now.

Just out of curiosity I gave it a go also (but i don't use it normally) I'm having exact the same problem as Lipfert Compile Error:Identifier name expected in modules/ModDX++.tmh at line 60 Line 60 reads: define DX65 3064

That's because the PTC V63 went into release. Turning off PTC will now get you V63 instead of reverting to the V62 since that is not an option anymore. Blocking the update won't work since it can only revert now to V63. You're too late!

You can check that in the app:

I "guess" you need to remove V242 from the name of the TheWayV242 folder.

Means that the installer is now also on the latest version...

There's a problem with the latest Oculus software (v63) which causes DCS to crash. Using Virtual Desktop instead should be fine from what i read. If you are still on V62 of the Oculus app you can block it from updating this way:

Turbo mode set to ON in OpenXR is the cause for me. If i turn Turbo Mode OFF, DCS doesn't crash, in MT that is, ST is fine with Turbo Mode set to ON.

I only update to a new version if i read that there are no problems (because it ain't the first time they FU some stuff). The next thing i do after an update is blocking it again for the next one to come.

Those who use the block trick ( https://forum.dcs.world/topic/343717-latest-oculus-v63-ptc-build-crashing-dcs-when-used-on-oculus-link/?do=findComment&comment=5390021 ) may see their taskbar blink (shift if centered) briefly every few minutes. This is NOT a Windows problem but Oculus service checking for an update even if Oculus main software isn't running. @yoadknux: see link in here for blocking + your trick works as long as they don't update the installer to version v63.