Aries

Nothing changed after last patch... Any fixes on this?

same here... black cursor in ST... ...MT was great but from last update i get like 23 fps in it versus normal 90/45 ASW framerates in ST 7800x3d, 64gb, 7900xtx, Quest 2 over Virtual Desktop...

Never... underestimate an F/A-10C...

No no no... you just don't get it... Everybody... wants... an AC-130 multicrew & Balkans map... for... me...

Thanks on this info... I just upgraded to 7800x3D & 7900XTX and was having a lot of questionmarks cause this "beast" was behaving like the old 10600K/3090Ti next to it... "Screenshot" is from 2D usage. not VR...

Does ASW work as intended?

Nice "medium" spec bro... (pre-last gen AMD fastest CPU & GPU)... I switched recently to 7900XTX from 3080 and boy oh boy does it look nice on max Virtual Desktop streaming quality with Quest 2, and keeps up the necessary 36FPS for ASW to run the damn thing smooth (even on a mediocre 10600KF)...

What you rumbling about YoYo? Do your homework before posting such negative info...

Seems like it went into this last OpenBeta version... although not mentioned in changelog... I got definitively better moving vehicle distinction from background on IR Mavericks seeker picture in Viper...

Yes... this... TGP WHOT/BHOT hardly usable to spot armor... and also IR Mavericks...

What is the status on this? Using IR Mavericks on Viper is a pain... targets simply are not hot or distinguishable from the surroundings... Also TGP WHOT/BHOT don't seem to pop up targets at all (armor, tanks)... In old A-10C times this worked really nice... then targets would somehow be a little jiggly against the background... it was a little cheat mode but worked... Am I doing something wrong?

Nothing special... just like always... Start VD Streamer on PC, start Virtual Desktop in Quest 2 headset... wait for connection and then use Launch game from green tray icon and point to MT DCS.EXE... I updated Quest 2 & VD Streamer to latest versions also... don't know if that affects anything...

It finally works as intended (as before MT) after last OpenBeta Patch - 2.8.3.38090

So we will actually never again be able to run Virtual Desktop on MT version in Oculus API? I mean WTF?!?!? This can't be the answer... Implementing what you asked for (--force_OculusVR) is such a reasonable path/solution...

Is there a way to launch MT with Virtual Desktop through Oculus API in the latest patch? Anyone tried?