Crashing when launching F4 in VR.

[SemajW]

Hi Everyone, hope you're all well. I'm just wondering if anyone has experienced a similar issue to me, and if anyone is aware of what might be happening or how to fix it? When I go to load into an instant action with the F4, I load into a world of water and then freezes for around 15 seconds, and then crashes. I thought it might be a VR problem or similar, however I tried launching in my other aircraft and it launches no problem. So its narrowed down to just the F4. I've reinstalled it and messed around with settings but nothing has helped. I've tried uninstalling all mods, on both standard and MT versions, still no luck. I'm starting to think it may be a lack of hardware issue, but I don't see how it can be that much more demanding than anything else. My settings are set quite literally as low as possible, everything off and sliders all the way down. My specs are -

Ryzen 7 7800x3d

RTX 3070

32GB DDR5 5600mhz

Meta Quest 3 using Meta Quest Link

Any help would be much appreciated!

Thanks, James

[HB_Painter]

Hey thanks for the report! After uninstalling all mods did you try a repair? Otherwise please submit some logs so we can take a look

[SemajW]

Hi Painter, excuse my ignorance but how do you run a repair? I tried looking in the DCS folder, both install and saved games and couldn't see a repair application. Could I have some advice on where that might be? I'll also look for a crash report! Again, sorry for my lack of knowledge, not very savvy with all this stuff! Thanks, James

[Jokkr]

I'm having the same issue of game crashing upon hitting "fly" on any F4 mission in VR.

I did notice meta updated my software same morning before I experienced the issue.

Quest Pro headset, standard Meta utilities

 

Ryzen 5900 (12 core)

Nvidia 3900

32GB 

1TB+2TB nvme

Quest Pro

 

jokkr

Edited June 5, 2024 by Jokkr

[hornblower793]

Please could you upload your logfile following a crash so that we can have a look for clues to the cause

[diamond26]

Same problem here. F-4E suddenly stopped working in VR. DCS crashes every time I try to launch F-4E, either instant action or mission based.
VR headset is Quest Pro. Can't recall any recent change between Sunday and Monday when it stopped working.
In 2D it launches as before.

I have perfomed full repair and no mods are running.

any plane_VR_dcs_working.log F4E_2D_working_dcs.log F4E_VR_broken_dcs.log

Edited June 4, 2024 by diamond26
typo correction

[Cobra847]

6 minutes ago, diamond26 said:

Same problem here. F-4E suddenly stopped working in VR. DCS crashes every tim eI try to launch F-4E, either instant action or mission based.
VR headset is Quest Pro. Can't recall any recent change between Sunday and Monday when it stopped working.
In 2D it launches as before.

I have perfomed full repair and no mods are running.

any plane_VR_dcs_working.log 145.35 kB · 0 downloads F4E_2D_working_dcs.log 97.94 kB · 0 downloads F4E_VR_broken_dcs.log 173.11 kB · 0 downloads

 

And does this happen every time now?

 

[diamond26]

3 minutes ago, Cobra847 said:

And does this happen every time now?

 

Yes impossible to fly in VR anymore with F-4E

[Jokkr]

I have the same issue. Also on a Quest Pro,

F4 crashes upon hitting fly button. All other planes I have tried are OK'

I did notice problem starting just after a Meta (auto)  upgrade.

dcs.log

[YoYo]

No issue for me, I fly only VR (QP too) and F-4E works fine (I dont use Instant action, this part sametimes is buggy, just missions, trainings and editor). No issue with the others modules? Also check the version of firmware in the gogles and Meta Link App (if you are on the cable). Some drivers could have a problem (example my friend has v65 in gogle and he had a problem, but with whole DCS, after hitting fly = ctd).

Edited June 5, 2024 by YoYo

[diamond26]

The question is why only F-4E has the problem. I played numerous missions, after I discovered the F-4E issue, with other planes even heavy multiplayer and everything run as before.

@Cobra847 if you need more details please let me know. I really want to fly F-4E again!

[Jokkr]

tried the latest version uploaded this am. 

Still broken!!

dcs.log

Odd how all other aircraft i fly do not demonstrate this

 

jokkr

[diamond26]

dcs.log-20240605-172620.zip

[hornblower793]

Both seem to be crashing at the same point in loading so that might give Heatblur a clue

 

2024-06-05 17:26:20.220 INFO    EDCORE (Main): try to write dump information
2024-06-05 17:26:20.222 INFO    EDCORE (Main): # -------------- 20240605-172620 --------------
2024-06-05 17:26:20.223 INFO    EDCORE (Main): DCS/2.9.5.55918 (x86_64; MT; Windows NT 10.0.22621)
2024-06-05 17:26:20.223 INFO    EDCORE (Main): D:\DCS World OpenBeta\Mods\aircraft\F-4E\bin\F-4E-Avionics.dll
2024-06-05 17:26:20.223 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff967a64100 00:00000000
2024-06-05 17:26:20.224 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'Diamantis'
2024-06-05 17:26:20.224 INFO    EDCORE (Main): OS-Version: 10.0.22621 () 0x100-0x1
2024-06-05 17:26:20.224 INFO    EDCORE (Main): 0x00000000003b4100 (F-4E-Avionics): cockpit::F4EAvionics::DCSWeaponsInterface::FireWeaponInDCS + 0x1F2F0
2024-06-05 17:26:20.225 INFO    EDCORE (Main): 0x00000000003b417b (F-4E-Avionics): cockpit::F4EAvionics::DCSWeaponsInterface::FireWeaponInDCS + 0x1F36B
2024-06-05 17:26:20.225 INFO    EDCORE (Main): 0x0000000000439038 (F-4E-Avionics): cockpit::F4EAvionics::DCS_JesterDialog::PushQuestion + 0x5DB8
2024-06-05 17:26:20.225 INFO    EDCORE (Main): 0x0000000000218ede (CockpitBase): cockpit::avDevice_BasicTimer::NextEvent + 0x1E
2024-06-05 17:26:20.225 INFO    EDCORE (Main): 0x00000000000045ab (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3EB
2024-06-05 17:26:20.225 INFO    EDCORE (Main): 0x0000000000004bc2 (World): wSimCalendar::DoActionsUntil + 0x262
2024-06-05 17:26:20.225 INFO    EDCORE (Main): 0x00000000008c9109 (DCS): SW + 0x408079
2024-06-05 17:26:20.225 INFO    EDCORE (Main): 0x00000000008c8de1 (DCS): SW + 0x407D51
2024-06-05 17:26:20.225 INFO    EDCORE (Main): 0x00000000008ebc82 (DCS): SW + 0x42ABF2
2024-06-05 17:26:20.225 INFO    EDCORE (Main): 0x00000000008a8a34 (DCS): SW + 0x3E79A4
2024-06-05 17:26:20.225 INFO    EDCORE (Main): 0x00000000008aa163 (DCS): SW + 0x3E90D3
2024-06-05 17:26:20.226 INFO    EDCORE (Main): 0x00000000004a1c10 (DCS): (function-name not available) + 0x0
2024-06-05 17:26:20.226 INFO    EDCORE (Main): 0x000000000280d185 (DCS): AmdPowerXpressRequestHighPerformance + 0x13A3181
2024-06-05 17:26:20.226 INFO    EDCORE (Main): 0x0000000000cf5dde (DCS): SW + 0x834D4E
2024-06-05 17:26:20.226 INFO    EDCORE (Main): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D

 

2024-06-05 17:11:47.770 INFO    EDCORE (Main): # -------------- 20240605-171147 --------------
2024-06-05 17:11:47.772 INFO    EDCORE (Main): DCS/2.9.5.55918 (x86_64; MT; Windows NT 10.0.19045)
2024-06-05 17:11:47.774 INFO    EDCORE (Main): E:\SteamLibrary\steamapps\common\DCSWorld\Mods\aircraft\F-4E\bin\F-4E-Avionics.dll
2024-06-05 17:11:47.775 INFO    EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007fff14344100 00:00000000
2024-06-05 17:11:47.777 INFO    EDCORE (Main): SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'jrbob'
2024-06-05 17:11:47.779 INFO    EDCORE (Main): OS-Version: 10.0.19045 () 0x100-0x1
2024-06-05 17:11:47.782 INFO    EDCORE (Main): 0x00000000003b4100 (F-4E-Avionics): cockpit::F4EAvionics::DCSWeaponsInterface::FireWeaponInDCS + 0x1F2F0
2024-06-05 17:11:47.784 INFO    EDCORE (Main): 0x00000000003b417b (F-4E-Avionics): cockpit::F4EAvionics::DCSWeaponsInterface::FireWeaponInDCS + 0x1F36B
2024-06-05 17:11:47.784 INFO    EDCORE (Main): 0x0000000000431708 (F-4E-Avionics): cockpit::F4EAvionics::DCS_JesterWheel::SetMenuInfo + 0x4198
2024-06-05 17:11:47.784 INFO    EDCORE (Main): 0x0000000000218ede (CockpitBase): cockpit::avDevice_BasicTimer::NextEvent + 0x1E
2024-06-05 17:11:47.784 INFO    EDCORE (Main): 0x00000000000045ab (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x3EB
2024-06-05 17:11:47.784 INFO    EDCORE (Main): 0x0000000000004bc2 (World): wSimCalendar::DoActionsUntil + 0x262
2024-06-05 17:11:47.784 INFO    EDCORE (Main): 0x00000000008c9109 (DCS): SW + 0x408079
2024-06-05 17:11:47.784 INFO    EDCORE (Main): 0x00000000008c8de1 (DCS): SW + 0x407D51
2024-06-05 17:11:47.785 INFO    EDCORE (Main): 0x00000000008ebc82 (DCS): SW + 0x42ABF2
2024-06-05 17:11:47.785 INFO    EDCORE (Main): 0x00000000008a8a34 (DCS): SW + 0x3E79A4
2024-06-05 17:11:47.785 INFO    EDCORE (Main): 0x00000000008aa163 (DCS): SW + 0x3E90D3
2024-06-05 17:11:47.785 INFO    EDCORE (Main): 0x00000000004a1c10 (DCS): (function-name not available) + 0x0
2024-06-05 17:11:47.785 INFO    EDCORE (Main): 0x000000000280d185 (DCS): AmdPowerXpressRequestHighPerformance + 0x13A3181
2024-06-05 17:11:47.785 INFO    EDCORE (Main): 0x0000000000cf5dde (DCS): SW + 0x834D4E
2024-06-05 17:11:47.785 INFO    EDCORE (Main): 0x0000000000017344 (KERNEL32): BaseThreadInitThunk + 0x14
2024-06-05 17:11:48.312 INFO    EDCORE (Main): Minidump created.

 

[Jokkr]

dcs.20240605-193343crash log 6=5=2024.txtdcs.20240605-193343crash log 6=5=2024.txtdcs.20240605-193343crash log 6=5=2024.txt

[Jokkr]

dxdiag jokkPC.txt

[diamond26]

errors remains with ST - non OpenXR

[diamond26]

the problem solved the hard way. Renamed (so I can have important files available) DCS saved game folder and let DCS rebuild a new one. After that F-4E worked again. Now i have to bring back bindings and missions

 

[diamond26]

After an extensive trial and error activity, I ended up finding that the problem was a binding for the Bombing Table Toggle to my throttle. Why this one caused all this issue with VR and not in 2D, I can only guess because the Bombing Table appears in different position in VR

 

[Jokkr]

Hmmm, that’s interesting. Will a simple unbinding solve or do I need to rebuild ?

[diamond26]

2 minutes ago, Jokkr said:

Hmmm, that’s interesting. Will a simple unbinding solve or do I need to rebuild ?

if you have the same issue (meaning coming from bindings), I would suggest to rename your F-4 inputs folder and create a new one by importing one by one the joystick, throttle, rudders and see where the problem appears again. It maybe that the switch I used with my throttle (Virpil CM3) was causing the problem in combination with VR.

[Jokkr]

Excellent work Diamond. Started off by just discarding the binding, nothing else….

everything is working fine, woo woo 

btw, I’m also a virpil user, stick, throttle, 2x button boxes. Great stuff

rarely solved so easily

thanks bud

 

jokkr

 

 

 

Edited June 6, 2024 by Jokkr