Exiting IL-2 window in VR

[TheWarsimmer]

Sometimes when I get into a dogfight all of my controls and commands will suddenly become unresponsive. Joystick, throttle, escape key... it all stops working until I exit the game via oculus. I can still look around in VR in the cockpit until it inevitably crashes into the ground.

 

It usually happens when I am looking hard over my shoulder in multiplayer, and it reminds me of when you exit a program window by accident, but I play in fullscreen mode on the mirrored desktop.

 

Does this happen to anyone else?

[dburne]

Are you somehow manipulating the mouse and clicking outside of the VR image on the desktop?

[Gomoto]

fullscreen checked in the options?

Edited December 12, 2019 by Gomoto

[TheWarsimmer]

Yeah that's about the only thing I could think of... that I'm somehow exiting the window. But full-screen is checked in the options and I am not using the mouse when it happens. It must be something on my end if it doesn't happen to anyone else.

 

EDIT: Just happened again in multiplayer. It almost always occurs in a hard maneuver like a loop, while looking over my shoulder. I'll just stay in the loop and no commands work at all until I force the exit via Oculus. If anyone has any experience with this, I'd appreciate the help. Has happened the last 3 times I've played online.

Edited December 13, 2019 by TheWarsimmer

[Sully--]

I occasionally have this problem and using the mouse to click on the IL2 window fixes it. Give that a try. It seems other apps/windows are gaining focus in Windows, which I suspect is the problem. 

 

-Sully 

[MAJ_Balapan]

Same problem in the exactly same situations you described (hard turning and looking behind seat) happened to me and my vr mate multiple times before. I also could see pointer on the desktop, but could not get it into game window.

I haven't had this hapenning to me for several patches/updates now, I thought that maybe it was fixed in one of the patches. 

Edited December 18, 2019 by =LwS=Balapan

[=SFG=capt_nasties]

I have encountered this and had a buddy have it twice in a couple of hours...its a thing

[squidboi]

This exact behaviour still happening in 2020 on various VR hmd

[dburne]

Has never happened to me so far, with Rift or Rift S.

Very odd...

 

@squidboi

I see your posting in multiple threads on this, why don't you try listing your system specs, which VR Headset, the settings you run for it , along with your game settings?
Might help in giving others a clue on things to maybe suggest.  Unless of course you are not wanting any assistance.

Edited June 22, 2020 by dburne

[squidboi]

This is happening on Vive but I polled people in discord and immediately i had multiple people saying it has happened to them on other headsets, HOTAS, etc... so seems to be something that is not specific to one HMD or hardware.

[Dutch2]

On 6/23/2020 at 7:10 PM, squidboi said:

This is happening on Vive but I polled people in discord and immediately i had multiple people saying it has happened to them on other headsets, HOTAS, etc... so seems to be something that is not specific to one HMD or hardware.

 

As what @dburne already did wrote down, any reason why keeping this so secret?  

[squidboi]

On 6/28/2020 at 5:02 AM, Dutch2 said:

 

As what @dburne already did wrote down, any reason why keeping this so secret?  

 

I told you what HMD I'm using. It should be enough. This happens on variety of settings for many users across many HMD. No secret. Guess I'll troubleshoot among ourselves then.

[Hoots]

8 minutes ago, squidboi said:

 

I told you what HMD I'm using. It should be enough. This happens on variety of settings for many users across many HMD. No secret. Guess I'll troubleshoot among ourselves then.

 

Wow. To help you solve this tricky technical problem I am going to give you one piece of high level information and say it's happening across many users with no back up of that data at all. A developer's dream customer.

[dburne]

2 hours ago, squidboi said:

 

I told you what HMD I'm using. It should be enough. This happens on variety of settings for many users across many HMD. No secret. Guess I'll troubleshoot among ourselves then.

 

OK.