[Standardized Camera Reference Point ]New way to set default camera position: by entering the sitting height/eye height in cm/ft·inch

Yes indeed, I just never thought of it for VR and this works too!

The Numbers are in feet and degrees. To the left and the rear are minus, to the front and right are plus.

Just trying to find you again in the forum ( it seems to be not straight forward, at least not for me).

I was searching for you because of your suggested settings
in the cameras.cfg file.
I did it today and I was surprised how dramatically the realism of flying improved in the C172 (from an already incredible realism).
EXCELLENT !!!
For the Airbus I’ll change the settings too, of course !!
How did you know ? From studying the documentation of the SDK?
Can you tell me how to comment in the camera file ?
Would you mind to make available more camera.0 settings
for the InitialXyz variable for more planes ?

Hope you can convince ASOBO.

Thanks a lot !!
bye walter

Because I used to design aicraft and FDEs for all sims up to MSFS

Put a ; at the end of the data section.

Sure (the numbers in the parentheses are the pitch values)

208______0.02, 0.6, 1.0 (-10)
A320_____0, 0.77, -2.25 (-7.5)
747______0.13, 1.05, 4.79 (-10)
787______0.09, -1.71, 31.15 (-15)
C152_____0.05, 0.14, -0.8 (-10)
C172_____0.03, 0.11, 0.1 (-10)
CAP10___-0.275, 0.2, 0.6 (-5)
CJ4______0.05, 0.47, 8.72 (-12.5)
DA40_____0, 0.11, -0.9 (-7.5)
DA62_____-0.05, 0.35, 0.40 (-7.5)
DR400____0, 0.2, -0.1 (-10)
DV20_____0.03, 0.14, -0.55 (-10)
Extra______0, -0.04, 0.5 (0)
King Air ___-0.01, -0.2, 0.57 (-7.5)
Longitude__0, 0.65, 10.82 (-12.5)
Pitts_______0, 0.02, 1.55 (0)
Savage Cub_0, 0.15, 2 (-10)
TBM_______0.05, 0.19, -0.9 (-12.5)

Bernt

5 Likes

Hi Bernt, thank’s a lot !
The view over the nose of the airbus is phenominal.
I trust YOU, that you made it as real as possible.
The TBM was like the one I used for myself before.
Of course I’ll try the other assignments too.

It must have cost you a fortune of time tinkering out all the best values
for a perfect fit.
I use a 21:9 34’’ screen for the sim. Maybe for other screen formats
the feeling might be different.

Thanks for the hint with the semi-colon.

Wish you very much success for your new project !
(listened to the forum “Buschtrommel”)
And stay here with us pedestrians !!
bye , walter

Unfortunately changing the PBH value when using VR is causing a major problem I’ve been documenting here:

[BUG] FS2020 using 2D cockpit camera in VR - wrong horizontal plane rotation (ex: FBW A320, SALTY 747, SDK SAMPLE)

PBH values other than 0 in VR wouldn’t make sense IMO.

@PZL104

Well this is exactly what the topic I’ve linked above is about!

  1. Very few vendors are providing a specific PilotVR camera

  2. Many who are providing a specific PilotVR camera are still using a PBH value (most often a copy/paste of the camera #0)

  3. The game is using PBH value even if you’re in VR.

If the game wouldn’t be using the PBH value, eventually, vendors wouldn’t be required to pay attention to this for their VR customers. Even the SDK sample is setting the wrong example to me in using a PBH value for the PilotVR camera.

Unfortunately the game is still using some of the 3D camera logic even in VR. You can see this in exterior view when the camera position, which is actually your head, is moving up and down and sideways with the aircraft (nausea inducing), like it does in 3D, and also: [BUG/FEATURE] FS2020 is breaking the VR golden rule: don’t move the camera, the user is

I don’t know what to think of these bugs but I believe these bugs just went through unnoticed during the game QA prior release, because as soon as you’re using FS2020 in VR and loading say the FBW A320, everyone should notice immediately something is wrong with the PBH (the whole ground is slanted more than 6 degrees beneath you). And just going outside and taxiing a little, everyone should also notice immediately something is wrong with the camera moving around with every bump on the road. 5 minutes of this treatment and you remove your headset and go :face_vomiting:

1 Like

It is, but it’s still very limited close to the aircraft. I once almost ran over a pushback truck because you can’t see anything close to the aircraft.

It’s a matter of minutes if you know how it should be.

I assume that the zoom setting is even more important. I’m always using 0.33 because it’s the setting which produces the correct sense of speed on my 16:9 monitor and my viewing distance.

No projects. I stopped developing pretty soon after the MSFS announcement.

1 Like

Hi Bernt,
was very pleased to get your mail today !
Fortunately you did not have a run over. Hopefully now the airbus has video cameras at his four corners installed?

It’s “a matter of minutes” - , yes.
But it may take a day or more to tinker out the best settings for only one plane.
( If we would not have to restart the sim after every change in a config file one would write a short Python program, which would make it easier)
So again, thanks !! You saved me/us a lot of time and frustration .
The ZOOM setting:
“I assume that the zoom setting is even more important. I’m always using 0.33 because it’s the setting which produces the correct sense of speed…”
That’s the solution for me, – I had the vague feeling that the approach seemed so fast now, after using the new settings ! I thought it was a delusion.
Thank you for your hint, that we pobably have to shift the ZOOM too.
Yet, as already said, using your cameras.cfg settings, gives me an until now unexperienced level of reality with the planes a tried out, especially the Cessna 172, 152, Airbus…
Only now I like to fly Cessnas and the Airbus !

Bernt, I know, I plague you once again:
In which file folder do we find the zoom variable ?

Maybe, the standard settings are preferred by non pilots or not so experienced ones for take off or landing, because they tend to aim over the spinner or some reference point on the cowling, and do not take a far away reference point to aim at. This pilot deficiency
may not have an outcome as pronounced as in the realistic settings.
Bernt, thanks again !
Bye, walter

1 Like

No cameras and I don’t think that there are any which are covering the nosewheel area in other aircraft.
You simply have to be very careful and cautious! Pushback/startup are situations which are prone to serious acciddents.

You don’t need to restart the sim when you are doing changes in the camera.cfg file.
Run the sim in dev mode, and after a change simply reload the aircraft.

The zoom setting is in the MSFS cameras menu.

best regards

Bernt

1 Like

Bernt, thanks again.

bye, walter

1 Like

“Run the sim in dev mode, and after a change simply reload the aircraft”.
Tried it out. Great time saver.
Tried out other settings today: together with your zoom factor your setting gave the optimum result (also for my 21:9 monitor), at least for the C172 I was tinkering about.
Just came back with these settings from a flight into the twilight of Iceland, - phantastic mood, clouds, hues, … like real .
Thanks, bye, walter
Have to fly once more !!!

1 Like

Is there a way to change this via the Community folder (overriding the default settings) or is it necessary to change the the cameras.cfg file in the “Official” foder?

Thanks, this is great stuff :slight_smile:

I’m using the camera.cfg files in the official folder since this is where all default aircraft are stored.

Cool, thanks.

I think I’m doing something wrong though as the changes seem to have no effect.

I changed the camera.0 settings in the default Cessna 172 and it still loads and recenters in the same spot as always.

I’ll have to have a better look into it tomorrow

1 Like

These are the values which need to be changed in the individual aircraft camera.cfg files.
e.g. for the 152 (the values after the ; are the original values which I keep as reference.

[CAMERADEFINITION.0]
InitialXyz = 0.05, 0.14, -0.8 ; 0.049951, 0.09, -0.821195
InitialPbh = -10, 0, 0

Yeah, those are the ones in using.
Strange.
Do you have to reload the whole sim BTW or can you reload the aircraft with the developer aircraft chooser?

Thanks

Hrm… I don’t remember a ; and more values after the initial three numbers… Did I miss something silly?

I’m adding the ; and the original values manually to the file as a reference so that I can keep track of the changes.
No need to do that, but that’s one of the important things you learn quickly when you start playing with the files.

I’ve also made a separate folder where I keep the modified camera files, because sometimes a SU or WU updates the camera.cfg as well.