Jump to content

DCS MT VR not start after last update from META for OCULUS RIFT 1


Recommended Posts

Posted

Dear all,
My Oculus Rift 1 just come to update, and my  DCS MT VR does not start anymore. I have the splash screen and after few second, DCS is closed with no UI error message, and nothing in dcs.log, see below the last entry in dcs.log. Yesterday I had no isssue.
Without VR, the game run.

I don't know how remove the last update in Oculus Rift 1 :(, if anyone has an idea, it will be really appreciated.

2024-03-25 22:08:28.948 INFO    APP (Main): options.graphics =
{
	['AA'] = 'DLAA';
	['forestDetailsFactor'] = 1;
	['rainDroplets'] = true;
	['LensEffects'] = 0;
	['box_mouse_cursor'] = true;
	['anisotropy'] = 3;
	['water'] = 0;
	['motionBlurAmount'] = 1;
	['BlurFlatShadows'] = 0;
	['outputGamma'] = 2.5;
	['aspect'] = 1.7777777777778;
	['lights'] = 2;
	['LODmult'] = 1;
	['MSAA'] = 1;
	['messagesFontScale'] = 1;
	['width'] = 1920;
	['visibRange'] = 'High';
	['DLSS_PerfQuality'] = 1;
	['useDeferredShading'] = 1;
	['clutterMaxDistance'] = 400;
	['textures'] = 2;
	['cockpitGI'] = 1;
	['terrainTextures'] = 'max';
	['height'] = 1080;
	['multiMonitorSetup'] = '1camera';
	['shadows'] = 1;
	['defaultFOV'] = 78;
	['shadowTree'] = false;
	['chimneySmokeDensity'] = 5;
	['secondaryShadows'] = 0;
	['SSS'] = 0;
	['fullScreen'] = true;
	['preloadRadius'] = 100000;
	['scaleGui'] = 1;
	['Scaling'] = 0.66;
	['DOF'] = 0;
	['clouds'] = 1;
	['sceneryDetailsFactor'] = 1;
	['Upscaling'] = 'DLSS';
	['Sharpening'] = 0;
	['motionBlur'] = 0;
	['ColorGradingLUT'] = 0;
	['SSLR'] = 0;
	['effects'] = 3;
	['SSAO'] = 0;
	['maxFPS'] = 180;
	['sync'] = false;
	['heatBlr'] = 0;
	['forestDistanceFactor'] = 0.8;
	['flatTerrainShadows'] = 1;
	['civTraffic'] = '';
	['ScreenshotExt'] = 'jpg';
};

 

Aviate-navigate-communicate

Posted (edited)

Same issue, just updated as well and now I cannot launch the game. It crashes at the same point as yours. I'm on the Quest 3, the Oculus App version is 63.0.0.216.361

Edited by Cooper21
Posted (edited)

I have an Oculus Rift 1, firmware version 709/b1ae4f61ae and runtime version exe 63.0.216.361

Edited by irq11

Aviate-navigate-communicate

Posted (edited)

thanks Flappie for your answer, but I have still the same issue with force oculus command parameter 😞
Do you think there is a hope yet ? or we have to change our VR headset  ? in an other case, Who have to provide a fix ? ED or Meta, both ?

thanks by advance

Edited by irq11

Aviate-navigate-communicate

Posted
19 minutes ago, Flappie said:

Here's a thread about the issue:

 

And here's a possible workaround:

 

As others seem to be reporting as well, the workaround is no longer functional. A bit frustrated that they announced the issue has been fixed but the patch isn't 'scheduled'. Seems like a gamebreaking issue for lots of users would be a hotfix

Posted

DCS fatcat exes should do what Boeing exes did, QUIT.  Way to many customer complaints about this and they wont fix it until they want.  Get off your fat butts and fix this

  • Like 2

I-9 12900K, RTX 3090, 64 GB, 2TB SSD, Oculus Quest 2, Win 11, Winwing Orion F-16EX Stick, F-18 dual throttle, Thrustmaster TPR pedals.

Posted

I did these procedures and it works for me, in waiting official fix.

1st :

and then

 

Aviate-navigate-communicate

  • 2 weeks later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...