Jump to content

Recommended Posts

Posted (edited)

Ugh guess I am going to have to uninstall and try and delete the reg entry. Amazing how deep this thing buries itself in one's system, it has me absolutely pulling my hair out. No idea why it worked fine for about 3 days then blammo with no easy way to get it back.

Edited by dburne

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted

I'm confused. No idea why it's causing a crash for you. TBH you don't *need* OXRTK so you could just disable it for the time being, given you'll likely be wanting to play with the patch later 😉

14900KS | Maximus Hero Z690 | ASUS 4090 TUF OC | 64GB DDR5 6600 | DCS on 2TB NVMe | WarBRD+Warthog Stick | CM3 | TM TPR's | Varjo Aero

Posted

Can you look to see what your \HKEY_CURRENT_USER\Software\OpenXR_Toolkit\DCS World registry setting looks like?  If the nuke worked, it should be virtually empty (2 or 3 settings tops).  If it is still full of settings, then it didn't reset properly.

Posted (edited)
6 minutes ago, zildac said:

I'm confused. No idea why it's causing a crash for you. TBH you don't *need* OXRTK so you could just disable it for the time being, given you'll likely be wanting to play with the patch later 😉

Ok finally got it  - whew!!!

Uninstalled OXRTK followed by deleting the Open XR Toolkit reg entry, has now gotten the Toolkit back working for me. At least now I know I will have to delete the reg entry if it happens again so much thanks!!

I have absolutely zero idea what I might could have done that caused this issue to start with. 

Edited by dburne
  • Like 1

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted
2 minutes ago, dburne said:

Ok finally got it  - whew!!!

Uninstalled OXRTK followed by deleting the Open XR Toolkit reg entry, has now gotten the Toolkit back working for me. At least now I know I will have to delete the reg entry if it happens again so much thanks!!

I have absolutely zero idea what I might could have done that caused this issue to start with. 

 

OK cool. Well, at least it's working now 👍 Just in time to try the MT patch when it hopefully drops today 😉

  • Like 1

14900KS | Maximus Hero Z690 | ASUS 4090 TUF OC | 64GB DDR5 6600 | DCS on 2TB NVMe | WarBRD+Warthog Stick | CM3 | TM TPR's | Varjo Aero

Posted
16 minutes ago, zildac said:

OK cool. Well, at least it's working now 👍 Just in time to try the MT patch when it hopefully drops today 😉

Yeah  now that would be nice!

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted
13 minutes ago, dburne said:

Yeah  now that would be nice!

 

  • Like 1

14900KS | Maximus Hero Z690 | ASUS 4090 TUF OC | 64GB DDR5 6600 | DCS on 2TB NVMe | WarBRD+Warthog Stick | CM3 | TM TPR's | Varjo Aero

Posted
3 minutes ago, zildac said:

 

Wohoo!

  • Like 1

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted
3 hours ago, dburne said:

Nuke option worked in safe mode - however when I take it out of safe mode I am right back to it crashing when launching DCS.

I suspect you might not have hit "Confirm?" when doing this. Because it would have deleted the registry key like you ended up doing later.

The issue you had was most likely conflicting settings somewhere between either the game and OpenXR Toolkit or Varjo and OpenXR Toolkit. This is an unfortunate consequence of multiple components contributing to a complex state.

The Safe mode + Restore Defaults is meant to address exactly that.

  • Like 1

I wasn't banned, but this account is mostly inactive and not monitored.

Posted
2 minutes ago, markturner1960 said:

DCS keeps us on our toes........😀

 

LOL ain't that the truth, just glad I got mine sorted this morning before the big update drop.

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted

@BIGnewy: the combination Quest 2, Open XR as active runteam, DCS steam edition, run from steam by selecting MT preview results in crash during startup:
# -------------- 20230310-170211 --------------
DCS/2.8.3.37556 (x86_64; MT; Windows NT 10.0.22621)
C:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin-mt\dx11backend.dll
# C0000005 ACCESS_VIOLATION at 00007ff90f8c7407 00:00000000
SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'xxxxx'
OS-Version: 10.0.22621 () 0x300-0x1
0x0000000000017407 (dx11backend): RenderAPI::DX11Renderer::setNewFrameBuffer + 0x37
0x0000000000016188 (dx11backend): RenderAPI::DX11Renderer::pushFrameBuffer + 0x68
0x000000000000bac0 (GraphicsCore): enlight::AtmosphereWrapper::precompute + 0x450
0x00000000000681db (GraphicsCore): render::CopyPass::doCopy + 0x14B
0x00000000000675b3 (GraphicsCore): render::CopyPass::operator= + 0x4A3
0x000000000004343f (GraphicsCore): render::BaseRenderingPass::execute + 0x1F
0x000000000003d9f0 (GraphicsCore): render::RenderGraph::~RenderGraph + 0x29B0
0x00000000000445f2 (GraphicsCore): render::RenderGraph::render + 0x292
0x0000000000116e35 (Visualizer): smSceneManager::regLua + 0x1005
0x0000000000103d09 (Visualizer): smCamera_Implement::getClipRegion + 0x16259
0x00000000000f3916 (Visualizer): smCamera_Implement::getClipRegion + 0x5E66
0x0000000000106a42 (Visualizer): smSceneManager::DestroySceneManager + 0x1542
0x0000000000031fa0 (edCore): ed::thread::_get_current_thread_id + 0xA0
0x0000000000029363 (ucrtbase): _recalloc + 0xA3
0x00000000000126bd (KERNEL32): BaseThreadInitThunk + 0x1D
---------------------

 

I does start when Oculus runtime is selected, but i see no improvement in frametime at all

Posted (edited)

Don, try to reinstall the wrapper again.  After the firmware update the wrapper needs to be reinstalled or it might not work properly.  If that still doesn't work then reset Varjo Aero to factory setting.

Edited by Supmua

PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti.

Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L

Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2

Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon)

VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/

Posted (edited)
1 hour ago, Supmua said:

Don, try to reinstall the wrapper again.  After the firmware update the wrapper needs to be reinstalled or it might not work properly.  If that still doesn't work then reset Varjo Aero to factory setting.

 

 

Your a little behind. 😉

Look a few posts up, have solved this already. Culprit was Open XR Toolkit, once I fully nuked it everything was fine again. I must have somehow got a setting changed in there that it did not like.

Thanks,

Edited by dburne
  • Like 1

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

  • Recently Browsing   0 members

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