Severe Cockpit dragging in VR

[Talisman]

2 hours ago, SCG_Fenris_Wolf said:

 

You need to turn on your Lighthouse sensors and let it get recognized by them first.

 

They aren't tracking the headset, then this happens.

 

But you're lucky: Here is a very good video that will solve your problems! Credits to SweViver??

https://www.youtube.com/watch?v=4Ec0AKuS8ms

 

For how to install the Lighthouse, check https://support.steampowered.com/steamvr/HTC_Vive/

and this video https://www.youtube.com/watch?v=rv6nVPPDmEI

 

 

Here is some troubleshooting. The guy had to reinstall his SteamVR to properly let it recognize Vive Basestation (Lighthouse).  https://forum.pimaxvr.com/t/setting-up-with-one-base-station/12402/9

 

 

Thanks for responding, but perhaps you have not understood the problem of 'cockpit dragging' in VR as per the OP.  I have already seen and followed all the links you posted and my lighthouse is recognised by my Pimax 5k + and is tracking OK.

 

Unless I have misunderstood your post, what you have contributed appears not to address the problem highlighted by the OP.  But thanks for trying.

 

Happy landings,

 

Talisman

[fiddlinjim]

Fenris is totally correct, whenever you get a cockpit dragging issue resulting from moving your head, it is caused by the HMD losing sight of the sensor.

I changed the 5K+ HMD USB location port when this happened and to me and no more lost sensor problems. 

[SCG_Fenris_Wolf]

As fiddlinjim indicated, afaik it can be a partial loss. Check your room. Whatever you find, good luck Talisman, and let us know afterwards ??

 

P.S. The OP had a different problem than you described.

Edited June 7, 2019 by SCG_Fenris_Wolf

[Talisman]

Problem solved.  It was turning off the 'limit VR view' in the game settings that solved it.  Of course, I had tried this before but it had not helped before.  The reason it had not helped me before was because I did not realise that I had to shut down the game, the VR goggles and the lighthouse and start everything up again from scratch for the change I had made to take effect.  Now I realise the shut down and restart requirement, everything has started working as advertised and I am a very happy bunny :)) 

 

Thanks for all your help folks.

 

Happy landings,

 

Talisman

[SCG_Fenris_Wolf]

IL-2 played a late april's fools on you. Ah well, thanks for answering with your solution!

 

I have received the Pimax5k+ and am working out some proper settings now, including 3dmigoto zoom dialed in, etc.

[buster_dee]

New to VR and this discussion. It just happened to me with Reverb G2. Worked fine a couple of days ago; now I can't shake it off. Really tough when landing since you don't just lose ability to get better side view, you introduce parallax.

 

Update: relaunched game, then flew a Quick Mission before attempting a regular mission, and VR worked well in both. I wonder if some older missions are not properly set up for VR, needing another mission to goose it into full function. 

[firdimigdi]

10 hours ago, buster_dee said:

New to VR and this discussion. It just happened to me with Reverb G2. Worked fine a couple of days ago; now I can't shake it off. Really tough when landing since you don't just lose ability to get better side view, you introduce parallax.

 

Update: relaunched game, then flew a Quick Mission before attempting a regular mission, and VR worked well in both. I wonder if some older missions are not properly set up for VR, needing another mission to goose it into full function. 

 

Your headset had likely lost tracking in the first case and was ok in the second case; it can happen, make sure to adhere to the usual advises for maintaining tracking (clean headset cameras, adequate lighting, proper startup order of WMR/SteamVR, etc) - missions are not separately configured for VR or screen.

[buster_dee]

Thanks. It's probably because I had no lights on (stuck in TrackIR thinking). Can you point me to the proper startup order? Each app seems to want to be in charge.

[dburne]

23 minutes ago, buster_dee said:

Thanks. It's probably because I had no lights on (stuck in TrackIR thinking). Can you point me to the proper startup order? Each app seems to want to be in charge.

 

Launch Windows Mixed Reality for Steam VR and it should take care of the rest.

Then launch IL-2.

[buster_dee]

I seem to have this backwards. I thought Steam VR had a version compatible with WMR, not the other way around (that WMR had a version compatible with Steam). Even though it works most of the time (crashes aside), might be time to start over.

[dburne]

1 minute ago, buster_dee said:

I seem to have this backwards. I thought Steam VR had a version compatible with WMR, not the other way around (that WMR had a version compatible with Steam). Even though it works most of the time (crashes aside), might be time to start over.

 

Yes get Windows Mixed Reality for Steam VR from the Steam store. Then just use it to launch both WMR and Steam VR.

 

[buster_dee]

Got software sorted (and launching 'order'), but pit still glued to my head. I'm going to reread this thread.

[dburne]

3 minutes ago, buster_dee said:

Got software sorted (and launching 'order'), but pit still glued to my head. I'm going to reread this thread.

 

Assign "default VR View" to a button on your stick.

It acts to recenter the view.

 

Edit: If your saying the pit moves with your head then that is a tracking issue. Maybe poor lighting in room or something.

Edited December 3, 2021 by dburne

[buster_dee]

I can look around fine. But, if I lean, the cockpit moves in that direction, and I gain nothing in the attempt. I turned on room lights, but no change.

[Drum]

I had this trouble too, what worked for me was resetting my boundary's to sitting only, clear old settings and setup as sitting and make sure you have real light in the room, not through a window light.  ?

[dburne]

1 hour ago, buster_dee said:

I can look around fine. But, if I lean, the cockpit moves in that direction, and I gain nothing in the attempt. I turned on room lights, but no change.

 

I don't have mine hooked up at the moment but look in WMR for an option to reset your environment or something like that.

[buster_dee]

Yes dburne, the problem was WMR, which sorted when I set up boundary again (the seated/standing in-place option). Now, IL2 keeps 'centering me' to the right cockpit sill. At least I know the headset is not broken. Thanks so much for all suggestions. Will I remember it? That's another matter. As an aside, I still can't hit a barn or stay away from stalling or ground-looping, but VR is gorgeous--even with the G2's narrow FoV. In those winter maps, I feel like my first stop after landing should be to the Nissan Hut coal stove--debrief be damned.

Edited December 4, 2021 by buster_dee

[readyred1]

OK, the same problem I had with my G2. The following procedure:

Do this each time before starting IL2.

 

[dburne]

9 minutes ago, buster_dee said:

Yes dburne, the problem was WMR, which sorted when I set up boundary again (the seated/standing in-place option). Now, IL2 keeps 'centering me' to the right cockpit sill. At least I know the headset is not broken. Thanks so much for all suggestions. Will I remember it? That's another matter. As an aside, I still can't hit a barn or stay away from stalling or ground-looping, but VR is gorgeous--even with the G2's narrow FoV. In those winter maps, I feel like my first stop after landing should be to the Nissan Hut coal stove--debrief be damned.

 

Congrats and enjoy!

Be aware it can be quite addictive!!

[paul_leonard]

Go see this thread.  It's insane how many people run into this problem and think they are unique (no offence). Paul

 

It's about you not sort of auto-calibrating the headset by starting in WMR Cliff House first, then moving on to Steam and game. 

 

Weird issue - environment locked to head movement. Reverb 2

 

[spreckair]

I also had this problem this evening with my G2.  I was using it in a dark room and the cameras could not identify the room.  After turning on a light in the room, all was corrected.