Matthew10_28 Posted April 15, 2018 Posted April 15, 2018 I've been messing with my real world cockpit to get it to line up with the in game dimensions. I've got a TMWH and MFD's so I've been measuring models and adjusting lots of things. I've been stepping outside the cockpit to get a better view from the side to see if components are at the proper station line relative to each other. Some how I haven't been able to move the eye point at all and I've been stuck just outside the right side of the cockpit and just in line with the dash. The commands don't work. Did I toggle something? Whats going on here?
dburne Posted April 15, 2018 Posted April 15, 2018 Have you tried using the VR-Recenter function in the UI layer of controls? I have assigned to a button on my HOTAS and is the first thing I do when getting into cockpit. Don B EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|
Matthew10_28 Posted April 17, 2018 Author Posted April 17, 2018 Have you tried using the VR-Recenter function in the UI layer of controls? I have assigned to a button on my HOTAS and is the first thing I do when getting into cockpit. Yep. That's the first thing I do as well. Oddly enough, that was always working in both the VR menu and the cockpit. (Even though it was recenterng me outside the cockpit). I just couldn't use the subject commands to move the pit to my centered eyepoint. I must have mashed the right buttons cause I got it working somehow. The only thing I can think of is that I've always had to hit esc after a mission loads, adjust controls, and then just click ok withoit actually doing anything. I have my left/right/scroll on modifiers on my hotas and they don't get recognized unless I do this. Why this may effect they keyboard commands I do not know. I may have skipped this step before trying to move the eyepoint as I do not think it was dependant on this hotas functions being fully recognized. If I'm able to recreate the non responsive condition, I'll try to pay attention to the sequence that fixes it.
Recommended Posts