dontcsink

nullI think I bought it and installed it. Enabled 3D And I removed the gunsight And it just not shows up null

Thanks for the advice. I did some test and found that ASW is main reason making the render break. Closing it with ctrl+numpad1 temporarily solves the problem. I am a little conservative in terms of increasing graphics settings I didn't increase the Oculus software's resolution, I don't know if that resolution is handled by its onboard qualcomm chips or using PC's graphic card. For the pixel density I am still confused, I mean which pixel density has the final say. Oculus debug tool or DCS settings. I currently use DCS settings and set it to 1.1 nullnull

Hi Tepnox, thanks for the reply. I did more test and found that it is ASW that causes the problem. However it has two aspect 1. The ASW algoritm is indeed causing blue fragment of the screen to shatter 2.The oculus debug tool cannot really close the ASW, I have to use Ctrl+numpad1 to close it. (Confirmed solve) I searched the ASW problem of oculus on google, and found that it is a legacy problem that haven't been completely solved. Given how facebook performed during the metaverse bubble (and how Oculus did before the purchase), I think there won't be an offcial solution..

I still haven't figured out how to record quest 2's PC streaming video But I found a similar phenomenon. Different game but similar problem. When I look into the sky I see those crazy flashing lighter parallelogram flashing. I tried USB3 cable, I tried use Oculus debug tool like this, but none works. null This happens only in quest2's screen, not on my the PC's monitor. Looks like oculus should take more responsiblity since it is their device cannot render a smooth sky. But now I don't know who to blame with 100% certainty. If it is oculus and meta, I need to go to their forum to f*** them for creating such problems that hard to describe.

Forgive me for not knowing how to screenshot the Oculus display... But when I tried recently with Oculus quest 2 with VR. I'm using an 4070TI vs 5950X cpu, with ED's version of DCSW client, not steam. --------------------------------This is the Problem-------------------------------------------- 1. When I set the graphics settings in default VR preset, when I spawn in a F-14 and look up the sky, the blue sky shows a subtle color step with very noticeable flash, that really hurts my eye.. That's still the small problem. The big problem is... 2.The Oculus type-C port is very loose, it is very easy, for a fast rotation movement or very big tilt angle of my head to cause the USB link to break. And it directly went to Oculus home. 3.After I re-pluging the cable with force, abd use Oculus grip to navigate back to Oculus link. I can only see a black screen with 3 white round dots, although the sound is still there. I always need to quit and restart DCS to re-enter a VR session. This is very un-pleasant. ----------------------^^^^^^^^^^^^^^^^^^This is the Problem^^^^^^^^^^^^^^^^-------------------------- So how could I deal with this bunch of mess? Greedy Oculus does not allow PC USB-wire streaming without opening Oculus desktop app. And it takes a lot of time from navigating from Oculus VR home to Oculus desktop interface. Up to What portion can I blame Oculus and meta?

I find that only the landing setting functions of AI_A2A_Dispatcher is not working ERROR SCRIPTING (Main): Mission script error: [string "C:\Users\admin\AppData\Local\Temp\DCS\/~mis00006337.lua"]:141027: attempt to index local 'self' (a nil value) I find that in the MOOSE.lua, all the AI_A2G_Dispatcher landing functions is commeted out, so as take off functions. Hoever, only landing method setting gives me the "a nil value error" Here is my script. All the group names are okay, if I remove the setsquardronlanding method then the script is okay Detection_SetGroup_Red=SET_GROUP:New():FilterCoalitions("red"):FilterPrefixes({"Red_EWR","Red_AWACS"}):FilterStart() Detection_from_Red=DETECTION_AREAS:New(Detection_SetGroup_Red,20000) Red_A2A_Dispatcher=AI_A2A_DISPATCHER:New(Detection_from_Red) --Red_A2A_Dispatcher.SetSquadronLandingAtEngineShutdown() Red_A2A_Dispatcher:SetGciRadius(120000) Red_A2A_Dispatcher:SetSquadron("Maykop_Khanskaya",AIRBASE.Caucasus.Maykop_Khanskaya,{"Red_GCI"},12) Red_A2A_Dispatcher:SetSquadronGci( "Maykop_Khanskaya", 900, 1200 ) Red_A2A_Dispatcher:SetSquadronTakeoffFromParkingHot("Maykop_Khanskaya") How to deal with it?