Thunk Posted February 7, 2021 Posted February 7, 2021 Bug: When watching a track file using VR, the pointer in the Jester Wheel tracks the user's head movements. If the viewer inadvertently moves the pointer away from it's original selection before the selection event plays, then the Jester Wheel stays stuck on screen for the entire track file. The pointer continues to follow the viewer's head movements, but cannot be closed. Can I reproduce it 100%: Yes. 100%. every time. If not 100%, how often out of 10: 10/10 How to reproduce/ description: Step1: Fly a mission using VR. Issue commands to jester using the wheel. Step2: Watch the track file using VR Step 3: When the Jester Wheel appears, look away. Notice that the jester wheel reacts to your VR head movements, not the originally recorded selection. Look somewhere so that the pointer is not on a valid selection, or just on a different selection than the original selection. Step 4: Jester Wheel stays stuck in the middle of the screen, with the ICS hiss continuing in the headset, for the remainder of the track. You cannot close it. It blocks the view for the rest of the replay. Expected result: When viewing a track file with VR, head movements by the viewer do not move the jester wheel pointer. The jester selection(s) made during the mission are faithfully replayed. Actual Result: When viewing a track file with VR, the viewer's current head movements are accepted by the jester wheel, which overrides the recorded selections in the trk file. DCS Version: OpenBeta 2.5.6.60966 System Specs: CPU i7 6700 GPU GTX1080 32GB RAM SSD OS: Win10 Peripherals: Joystick: Thrustmaster Cougar Throttle: Thrustmaster Cougar Pedals: Thrustmaster RCS Others: Headtracker: Quest 2 Mission File: Any F-14 mission file can reproduce this Log: Track: I don't know how to capture a track file showing that user inputs during replaying a track file changes the behavior of the track file. Video/ Screenshots: Mods: no mods
Recommended Posts