Back to P3D... Wait, what happens?

[SleepyBridge6]

For a single session and after flying a lot on fs2020, I had to go back to P3D for a simple flight with the A2A C172.
First reaction while taxiing: the toe brakes work exactly as I expect. Breaking with one foot, I can accelerate a turn and it won’t stop the plane.
Then I took off. I right away thought that my controls were not calibrated the right way at all. I had to make ample movements to achieve what I want. Checked FSUIPC, native calibration in the sim… No, everything was correct. Second thought: what the heck this airplane flies slowly… But I was at my normal cruising speed (110 kts).

What does it mean? That fs2020 is far too sensitive on the controls. And I wonder if speeds and distances are ok. It’s as if there was a slight time acceleration in place.

How do you feel it on these points?

[YearlingDeer319]

A2A goes by the numbers and FS doesn’t.

End of.

[TaupeTerror3931]

I have to second that. Too bad it will be quite a while before the C172 gets rewritten for MS2020. Also, install the current FSIUPC7 beta. it’s working pretty well now. Not complete, but close.

[SleepyBridge6]

I get that and agree. But what I was mentioning is not for this plane in particular.
Generally speaking, FS is too sensitive on the controls and it seems to me that the plane fly “quicker than real”, if it makes sense…

[CptLucky8]

@SleepyBridge6

and it seems to me that the plane fly “quicker than real”, if it makes sense…

I’ve read another discussion about how stretching the view over 3 monitors is exacerbating distortions, and what you’re describing I’m pretty sure has been raised in the past prior release as far as I remember reading this somewhere, and it is an old problem with any Flight Simulator product.

Rewind back to FS9/FSX: I’ve always find the 3D projection wrong because it wasn’t based on recreating a virtual focal length, but in fitting a computer screen like any other Direct3D game which is applying a perspective transformation based on the window size, not based on a fixed focal length.

I’ve been looking back at my experience with X-Plane 11 in 2D then in VR and I think there might be a simple explanation in the end, which can be easily experimented:

• Use the simulator in a window filling 1/4 of your monitor.
• Stretch the window horizontally back and forth.

With X-Plane:

• Perspective projection doesn’t changes while resizing the window and the focal length (as with a camera lens) doesn’t change either so that relative sizes of objects is constant.
• The objects relative sizes don’t change with distance.
• The view keeps the horizontal FOV constant and you’ll change only vertical FOV (the vertical / horizontal ratio is getting smaller).

With P3D5:

• Perspective projection changes as if you’re changing camera lens focal length.
• The objects relative sizes change with their relative distance to the aircraft.
• The view zooms in our out

With FS2020:

• Perspective projection doesn’t change while resizing the window
• The objects relative sizes don’t change with distance.
• The view keeps the vertical FOV constant and you’ll change horizontal FOV.

Comparing all these:

• P3D5 is all wrong. It is distorting the objects depending on the window width/height ratio.

• X-Plane is right. There is no distortions whatsoever and you can calibrate the view so as to use the zoom, instead of the window width/height ratio, to simulate the focal length.

• FS2020 is right, but the problem is that with a fixed vertical FOV, it introduces distortions the wider the window.

IMHO, these distortions to the edges are most likely the root cause of the difference of perception to the aircraft speed, because it is a lot induced by peripheral vision cues, and because of the distortions, the objects are appearing moving faster to the edges than closer to the center.