Brief description of the issue:
Detail steps to reproduce the issue encountered:
Context
Aircraft vendors can add the following entry in the camera.cfg file in order to set a reference position in the cockpit in VR mode:
[CAMERADEFINITION.##]
Title="PilotVR"
InitialXyz= #.#, #.#, #.#
InitialPbh = #, #, #
However not all aircraft currently available, both freeware and payware, are adding this section and in this case, FS2020 is using the default entry which is the one using: Title ="Pilot"
Furthermore, not only not all vendors are using this specific camera definition yet, but some of the ones who do are just copy/pasting the same values as the one found in their Title="Pilot" camera definition.
Problem
In the case there is no specific Title="PilotVR" camera definition, FS2020 is using the the default pilot view.
The problem is that in VR mode, FS2020 is also using the InitialPbh values which are meant to set the initial view direction in 2D mode, but are in fact rotating the horizontal reference plane in VR.
This is very disorienting in VR and this is breaking the VR golden rule like described in this other bug topic:
Example: FBW A320
InitialXyz = -0.045, 0.77, -2.274
InitialPbh = -6.2, 0, 0
With the latest FBW A320 Dev Branch version, there is no PilotVR entry and when jumping into the aircraft, the InitialPbh setting makes the entire world slanted by 6 deg (upward in front, downward at the back).
Example: Salty 747
Just downloaded latest Salty 747 which is a nice mod and I applaud the effort.
They’ve also added a “PilotVR” camera, but… (scroll to the end)
Example: Asobo 787
They’ve also added a “PilotVR” camera, but… (scroll to the end)
Example: DA62 SDK Sample v1.7
Although the latest DA62 v1.7 included in the SDK samples has a PilotVR camera definition section, it is however also using a non-zero PBH…
[details = “MSFS SDK\Samples\DA62\PackageSources\SimObjects\Airplanes\DA62_SDK_AIRCRAFT\cameras.cfg”]
[CAMERADEFINITION.29]
Title=“PilotVR”
Guid=“{C51E9C69-F592-49D0-9665-AF3CB96AB096}”
UITitle=“TT:GAME.PANEL_CAMERA_PILOT_VFR”
Description=“”
Origin=“Virtual Cockpit”
Track=“None”
TargetCategory=“None”
ClipMode=“Normal”
SnapPbhAdjust=“Swivel”
PanPbhAdjust=“Swivel”
XyzAdjust=1
ShowAxis=“NO”
AllowZoom=1
InitialZoom=0.35
SmoothZoomTime=2
BoundingBoxRadius=0.1
ShowWeather=1
CycleHidden=0
CycleHideRadius=0
ShowPanel=0
MomentumEffect=1
ShowLensFlare=0
PanPbhReturn=0
SnapPbhReturn=0
InstancedBased=0
NoSortTitle=0
NodesToHide=“”
Transition=0
PitchPanRate=20
HeadingPanRate=60
PanAcceleratorTime=5
XYZRate=0.25
XYZAcceleratorTime=0
ZoomPanScalar=1
Category=“Cockpit”
SubCategory=“Pilot”
SubCategoryItem=“PilotVR”
InitialXyz= -0.075, 0.325, 0.4
InitialPbh= 0.5, 0, 0
[/details]
Solutions
Here are a few simple solutions
-
Unless there is a good reason for this which Asobo might document, the game should never use the
InitialPbhsetting in VR mode ever (i.e.if (isVR) { IntialPbh = {0,0,0};} ) -
Asobo should evangelize aircraft vendors to always provide a
Title="PilotVR"section, if there is a need for such section. A good starting point to me would be adding one such example in the official docs here: SDK Documentation (flightsimulator.com) and to provide an SDK sample which is correct.
Do you have any add-ons in your Community folder? If yes, please remove and retest before posting.
Are you using Developer Mode or made changes in it?
Provide Screenshot(s)/video(s) of the issue encountered:
PC specs for those who want to assist (if not entered in your profile)
Build Version # when you first started experiencing this issue:
Are you on the Steam or Microsoft Store version?
Did you submit this to Zendesk? If so, what is your ticket #?
n/a
I see they have started developing for VR controller interaction. However, again comparing to x-plane I prefer mouse interaction. With controllers there’s a lot of swapping between holding the yoke and the controller and it’s just not a very good solution. hand tracking would be better, maybe they include that as well. Unfortunately that won’t work on the G2.