Default Cockpit Camera in VR is too close to panels | Quest 3

Bug Reporting Hub Virtual Reality (VR)
, , ,
1

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

2 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue:
When using the Asobo 787 in VR, camera view defaults to literally right in front of captain-side flight panels(As if my face was pressed against it). I have tried resetting view with shift key but the view stays where its at. If I move back in my chair to move away from instrumentation panels and press shift(Camera reset) it defaults to the faulty view again. I only have this issue in the 787, other airliners camera views in VR are properly centered and spaced. I should also note I do not experience the camera view issue in non-VR mode using the 787.

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
No mods are installed

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
Every single time I try to use the Asobo 787

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

1.Start flight at airport gate
2.Activate VR mode
3.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are currently plugged in, as well as your VR headset? Please name all of them as there could be a potential conflict.
None besides the VR headset
[PC Only] Are you using Developer Mode or have you made any changes to it?
No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?
PC

[PC Only] What GPU (Graphics Card) do you use?
4090

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]

:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?
•

Provide extra information to complete the original description of the issue:
•

If relevant, provide additional screenshots/video:
•

2

I’m finding this with stock aircraft, 3rd party devs seem to have got it right

1 Like
3

Actually depends on the airplane. On many it is super low. Some too far. And then adjusting has been made more difficult needing to use the shift key. Not optimized at all for VR.

4

as a side note, do be aware that you can set the keyboard keys to the MSFS 2020 defaults, which switch the seat controls back to the arrow keys as a workaround

1 Like
5

in general many aircraft has issues with Neutral VR position. It’s either too far back, off to the side, too low or high. I resorted to an Xbox Controller, and adjust my position. Added to that in a Motion rig with Motion compensation in VR, it gets even wilder. Pilot position is a new feature in 2024. spawn points are adjustable by devs.

6

I confirm that “bug”.

How I “fix” it - move slightly forward, center the VR view (shift-key or what you have assigned) and lean back or sit normal. It should be fine now.

7

Usually I already change the aircraft.cfg for my VR camera. I’m a real airbus first officer and all aircraft like fenix use left seat only for VR.

image
image398×245 4.6 KB

Here what I changed to Fenix.

So every time I press a ‘reset camera’ bottom in my joystick, I’m dead center in my seat. :white_check_mark:

2 Likes
9

Thank you for the bug report.

We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged