VORPX latest verison hooks into Falcon BMS
-
Alright, I think I have figured out the main source of VORPX CTDs for me. It seems tied to mouse movement, mostly due to position/movement of the cursor outside of the smaller (1024x768) OG Falcon UI screen when windowed. I will also get crashes if I am moving the mouse around during entry to/exit from 3d even if it seems the mouse is within the UI boundaries.
More things to try:
- Full screened UI to see if the mouse cursor is more kept in the UI
- Change to g_bEnableExclusiveMouseCapture 0 to see if slipping the mouse off the 3d window causes the CTD (this does seem to be what is possibly making the 3d environment be more stable)
- Lots of mouse clicking inside the 3d cockpit just because I haven’t done this yet
- Even though it isn’t recommended, alt-tab out to click on something else in another program since you can get away with it occasionally on monitors
This also may not bode well for PointCtrl in BMS, which I’m still a believer in it being the best VR cockpit interface.
To avoid bumping a lot of threads, it looks like most of you were playing in a similar thread started by @philip40912 about crashes too. I will though eventually post this in the BMS in VR mega thread after some more testing.
-
@snake122
Thanks for your testing.
My suffering experience is the same, mostly crash when committing into 3D which makes playing BMS nearly impossible.
Looking very forward to your testing result. -
@philip40912 if it is crashing before you get to the loading screen (F-16 with progress bar), try carefully clicking on the commit icon and not moving the mouse as you do it and especially after clicking and don’t move it again until you get into the 3d world. This seems to have success for me. I’m going to turn down the DPI of my mouse or finally make the transition to my trackball.
-
@snake122
Do you mean when ready, click TAKEOFF and then try not to select RAMP/TAXIWAY/RUNWAY as the movement of mouse cursor would potentially trigger the crash? -
@philip40912 Yes, but even from the time your mouse cursor in the UI changes from F-16 to parachute man in the UI I have tried to not move the mouse. So far in my testing, I have let it be whatever I left it at last with the start type selection when I figured out it seemed ties to mouse movement. I’ll add that to the list of stuff to test.
EDIT: it does seem selecting the start type is fine to click.
-
@snake122
I change to g_bEnableExclusiveMouseCapture 0
Set full screened UI - crash even more often directly in UI - very strange & unsual.
Set it back to windowed or borderless - problem solved!! Was working great with almost successful entering into 3D without crash every time.But not sure why after a few days, now the crashes start again and all happens in UI.
The crash before this solution mostly happened when committing into 3D before the loading page.Now the crash happens in the UI when clicking comms / tactical engagement etc…
If i could make it to loading page, it is almost guaranteed successful entry into 3D without crash.
But the crashing scenario now seems different than before.
I try switching between windowed / borderless / full screen but having constant crash in UI.
Very frustrating indeed - was thinking eventually got a solution but another whole new problem seems appear again, crashing in the UI instead of commiting into 3D. -
@Snake122
Guess the crashing in UI problem seems “mouse movement, mostly due to position/movement of the cursor outside of the smaller (1024x768) OG Falcon UI screen when windowed” due to using VORPX / VR headset which has extended the FOV in the VR headset. -
@philip40912 yeah, now I’m not even 100% it’s tied to the mouse/borderless/windowed. It is frustrating since it’s very stable in 3d. I’ll let you know if I come across anything.
-
@snake122 Thanks!! Hope to figure out what the problem is & get a solution. Indeed once enter the 3D it becomes very stable. Problem all occurs in UI.
-
@snake122 Just for your info, now the crashes nearly happens almost 100% in UI. Can’t even make it to 3D…the moment i click comms it crashes. Situation seems different & have no idea why all of a sudden problem seems happen in a totally different scenario. It was crashing almost 100% the moment when i wanted to commit into 3D & all stable in UI. Now it’s almost crashing almost 100% in UI but will not crash in 3D.
-
@snake122 said in VORPX latest verison hooks into Falcon BMS:
This also may not bode well for PointCtrl in BMS, which I’m still a believer in it being the best VR cockpit interface.
I would expect that ones BMS gets native VR support that shouldn’t be an issue. I agree though PointCTRL is the way to go for cockpit manipulation in VR.
-
@philip40912 said in VORPX latest verison hooks into Falcon BMS:
@snake122 Just for your info, now the crashes nearly happens almost 100% in UI. Can’t even make it to 3D…the moment i click comms it crashes. Situation seems different & have no idea why all of a sudden problem seems happen in a totally different scenario. It was crashing almost 100% the moment when i wanted to commit into 3D & all stable in UI. Now it’s almost crashing almost 100% in UI but will not crash in 3D.
Yeah, it still seems to be tied to the mouse but still not necessarily 100% sure. I have found it seems more stable if I move the mouse to the BMS UI window during the splash screen and once the actual UI pops up I wait 3 seconds and the same with each click that would bring up a different UI section. I haven’t tested the comms screen at all because for me it’s nowhere stable enough to bother with MP yet. Entering the loadout screen usually causes a crash for me too. As I mentioned, there doesn’t seem to be any issues with the selecting ramp/taxi/runway now that I have tested it more, it seems when we get about 2/3 through the load status bar, we are going to make it into 3d. Crash on exit seems to be reduced by specifically moving the mouse cursor up and left (into the 1024x768 UI window) before hitting escape and E but still not 100%.
-
@snake122 Thanks for your effort in trying. If we could manage to figure out what causes the crash in UI, it would be perfect & ultimate answer Hope to hear some great news from the community.
-
@snake122
I google and read some interesting comment about VORPX as follow
Would this maybe explain why the mouse may move outside of BMS UI boundary because when in VR in order to click comms / TE etc we need to look up“VorpX insists on converting head movement into mouse movement, which makes it fine for games that don’t natively support head tracking”
“VorpX can output mouse-emulation with head tracking as input”