Viewpoint dropping suddently when looking at the comm panel

[Mazhurg]

Anyone else encounters this:

Quire often when coming in to a station looking at the left menu panel to select comms (to dock) my view will drop down to the middle of my chest (clipping the chest), requiring a view reset.

Thing is, it does not happen when merely looking left, selecting destinations or going through the other tabs.

If I'm the only one, then there might be something not quite right in my config (although the OR works fine in all other tried apps), if others encounter this then I'll bug it.

I can live with it, but it's quite annoying, especially when requesting docking close to the station at speed.

 

[Adam Lusardi]

Join the club I've had that problem from day 1, thought it was bad camera placement etc. but it happens quite often. So much now I have F12 bound to an alt fire button, but occasionally I reset automatically when looking at the left panel especially in combat then it really goes wrong

 

[Pate]

Yep, for me the viewpoint either drops or rises almost every other time when going to System Map via the left menu panel. I have a Voice Attack command "Center" to reset the orientation, and need to use it pretty often (every 5 minutes or so) when playing. The 1.2 patch did not seem to make any change to this problem.

 

[CMDR Holycow]

Yep. Every once and a while my head is sticking out from my nipples. Looking to the sides doesnt seem to do it for me. Sometimes it just "pops" that way coming out of a jump.. sometimes after taking off from a landing pad... I have seen it happen many times where I specifically notice that I wasn't moving my head really at all... It's ok, I have "reset" set in voice attack just for that Happens to me once every 2 or 3 nights playing. Not very often, but has happened a dozen or more times.

 

[Mazhurg]

The thing is knowing that there are some pretty big changes coming both from the video drivers (AMD) and OVR (OR drivers) that will require FD to "reconfigure" the OR mode, and knowing that the DK2 is really a development prototype, I wonder if it is worthwhile to nag FD on this subject at this time versus letting them work on the next iteration of the VR interface as I am sure they and OVR are probably actively coordinating currently.

I mean, it's a win-win as OVR get to showcase E (best game on OR for now) and FD gets more sales.

 

[CMDR Holycow]

The thing is knowing that there are some pretty big changes coming both from the video drivers (AMD) and OVR (OR drivers) that will require FD to "reconfigure" the OR mode, and knowing that the DK2 is really a development prototype, I wonder if it is worthwhile to nag FD on this subject at this time versus letting them work on the next iteration of the VR interface as I am sure they and OVR are probably actively coordinating currently.

I mean, it's a win-win as OVR get to showcase E (best game on OR for now) and FD gets more sales.

It would be a waste of time for them to change anything before CV1. I wouldn't count on it. As long as we keep getting the same overall experience for now... im pretty satisfied, myself. Once the CV1 comes out, they will actually have something to tweak and optimize for.

 

[CMDR Saari]

It would be a waste of time for them to change anything before CV1. I wouldn't count on it. As long as we keep getting the same overall experience for now... im pretty satisfied, myself. Once the CV1 comes out, they will actually have something to tweak and optimize for.

I think you're probably correct about this. I'm content for them to leave things the way they are now until CV1... unless the next SDK breaks something of course. I also hope that DK2 will still be compatible even after CV1 release so I can hold off on a purchase if I need to depending on the release window.

To address the OP though: I have the same or very similar issue. It doesn't sound like mine happens as often as you though - once an hour or so I get the chesthead jump. Hmm, chesthead might be a side-effect of onionhead use

This issue has been brought up at Oculus where someone collected data about it straight from the head tracking software:

https://forums.oculus.com/viewtopic.php?t=19614

The only advise I can offer is to make sure you have Oculus Position Reset bound to a handy button (right analogue stick click on my 360 pad).