Campaign Crash in VR 4.37.7
-
First crash in BMS 4.37.7. Korea Rolling Fire Using Quest 3 openxr.
Relevant dump and logs linked below.
https://1drv.ms/u/c/766bd780e0ffbdbf/EWuakzoJPBdEkyV2A6xHfe8BY4Qkmaofj4cpxhaFGNfJpA?e=9rWyK9Let me know if other details are needed
-
Thanks, Ill have a look asap.
-
Seifer asked me to take a look on it
It is a CTD on the FLCS code that did not change since…forever.Just to check before we go deep dive here:
- You did not change any airframe data?
- You are on an unmodded BMS?
- Can you please share with me your BMS config files?
Falcon BMS User.cfg
andFalcon BMS.cfg
-
Thanks for the quick response.
Nothing was changed in any data and no mods, vanilla BMS
Configs
https://1drv.ms/u/c/766bd780e0ffbdbf/EcUcTHKlrNBOmOAGVgdex5wBMguPADMF9wy3ba4RCMN-rw?e=B3LWu4 -
Some additional information. I flew the saved mission again without VR and no crash occurred. Not sure if it may be VR related but thought I’d pass it on.
-
@braulston is it a certain CTD with VR?
-
@Seifer Yes, I was in VR when the crash occurred.
-
But is it always a CTD in VR?
-
That’s the only CTD that I’ve had in VR, that said this is a new campaign under 4.37.7. Prior to this I flew a Balkans campaign in VR in 4.37.6 and never experienced one during the entirety of the campaign. I will try to fly another in VR later this evening or tomorrow and report back.
-
Flew again in same campaign with VR this time. No crashes occurred.
-
@Seifer I wanted to circle back on this to let you know that I’ve flown five more campaign missions in VR with no issues. So I don’t know if this is work the squeeze to chase at this point.