FS9 is a flight simulator. FSX is just a video game... !!!?
Posted: 11 Mar 2015, 16:41
Here's what I discovered about FS9 and FSX in a highly detailed tutorial by Tom Gibson (of FS Aviator fame). Please don't take my word for it. This is all found in Tom Gibson's "Propliner Tutorial 2008", available on his website. Feel free to draw your own conclusions, but it does mean that all those who have staunchly stuck to flying in FS9 have actually been using the BEST flight simulator affordablle. And those who have migrated to FSX have embraced but a video game... And there's more about this than I can copy and paste here. Since I only discovered this recently, I'm sharing this here merely to bring it to your attention. Otherwise, most of you will probably never know about this eye-opening tutorial and how good a flight simulator FS9 truly is...
FS9 is a flight simulator by default. FSX is just a video game by default. It delivers false scenery placement by design and by default. It requires substantial modification by users before it is safe to use FSX as a flight simulator. Those who cannot be bothered to convert FSX from video game to flight simulator should avoid using FSX...
......Gross errors are present in all default FSX Cockpit Views (CV = 2D panel), and most third party CVs for use in FSX, probably because those who wrote the code did not understand how to control scenery placement; or even that they were responsible for placing it.
In FSX every aircraft and every start up flight must specify the correct ZOOM to place the scenery at its true LAT/LON. Every producer of every *aeroplane* converted or created for use in FSX is individually and personally responsible for placing the scenery in FSX! This design error has caused massive problems for FSX users because many / most third party FSX producers have not understood how FSX works and have failed to impose the required scenery projection code.
.....FSX cannot read ZOOM commands from a panel.cfg. FSX *requires* the producer of the *aircraft* to control scenery placement, aircraft by aircraft! Created or converted!
The vast majority of aircraft released or converted for use in FSX lack the code necessary to place the scenery correctly within FSX. Most have nothing more than random values. Consequently those who have used FSX have been subjected to random scenery placement, random displayed mesh height, randomised climb paths and randomised glideslopes! FSX cannot deliver flight simulation without substantial effort by users to fix all the aircraft they use. If you hope to achieve flight simulation and cannot be bothered to fix FSX then you should avoid it.
....Cockpit View design is all about the harmonisation of the two overlaid Microsoft windows on the screen. Many 'panel designers' still have no idea what they are supposed to be doing or how to do it. Many 2D panels are functionally useless because the panel designer in FS9 and the aircraft designer in FSX only bothered to design and encode the front window on the screen and could not be bothered to control the perspective, placement and parallax of the projected scenery in the window behind it at all.
Those who only pretend to fly aeroplanes in MSFS never notice that the mesh and scenery have false perspective, false placement, false parallax, false glidepaths, false eyelines, and false mesh heights.
*Even when they are obviously correct in the Virtual Cockpit View, but entirely different when the 2D panel is in use*
If you hope to achieve flight simulation you must personally take responsibility for fixing or discarding all the broken cockpit environments that you have purchased, or that you have downloaded as freeware. Using this tutorial with randomly projected scenery at the wrong LAT/LON displayed with random parallax and random perspective is a waste of time. You must make time to fix what is broken or avoid what is broken in both FS9 and in FSX. Using broken flight simulator files is potentially dangerous, especially for real aircrew, or anyone who may become a pilot later. You may fail to understand that the scenery is misplaced and develop dangerous patterns of behaviour based on that false placement. Many of you do. These issues are explained and illustrated in greater detail within the simulation control interface tutorials available from http://www.calclassic.com/tutorials.
In this updated Propliner Tutorial I have included two screen shots to demonstrate the display errors which are present by default within FSX. Now is the time to study FSXcv.jpg and FSXvc.jpg which demonstrate exactly how FSX distorts perspective, scenery placement and mesh height. This destroys the necessary relationship between time and distance and destroys the necessary relationship between where the gauges correctly show the scenery is in azimuth and elevation and where it is being projected in the rear window of the simulation. The example chosen is the FSX default Baron. The default Baron CV has uncorrected FS9 scenery projection variables. The ridge line is displayed several miles closer than it really is.
Now let’s turn that gross error of distance and climb slope around and think what it means for the approach case. During the approach the time and distance to go to the runway is much longer than it is displayed to be. FSX CV users see a zoomed ‘picture’ which causes them to descend far too soon or at a VSI which is excessive. Things that are 8 miles, and perhaps four minutes away, may be displayed as less than six miles and less than three minutes away. That may be ‘entertaining’ in a children’s video game, but it is useless for flight simulation.
*Using misprojected scenery is the worst mistake anyone interested in flight simulation can make.*
Attempts to use this tutorial with broken or randomly encoded simulation control interfaces are doomed to failure.
Not even real aircrew can learn how to use a flight simulator when scenery projection is just random and grossly wrong. If you allow yourself to fly with grossly misplaced scenery you will never be able to judge distance or glideslope or climb slope during flight simulation. You will never be able to judge when to descend or what VSI is required.
Both screen shots are from the FSX default Baron at the same departure threshold using the values encoded by Microsoft. In the cockpit view screen shot the zoom is 1.0 because Microsoft failed to encode the required FSX Pythagorean compliant ZOOM value. In FSX cockpit view we are given false cues. The runway is displayed as much shorter than real life and with false perspective cues to match that deception, the ridge line is falsely displayed much closer than real life and the mesh is falsely rendered to match that deception.
That alone would make FSX a product for those interested in flight simulation to avoid. However there are also errors in its VC views. Again the *aircraft* producer has to project the scenery from VC view using code in the aircraft.cfg. In many cases the producers and converters of FSX aircraft have failed to understand their responsibility and have failed to provide the necessary scenery projection code. Many aircraft said to be compatible with FSX will display in FSX, but they are not FSX compliant. The necessary scenery projection code is randomised or has never been converted from the values used by FS9.
It is important to understand that last point. This is not just a problem of huge errors in one FSX viewing mode and smaller errors in the other. Because scenery placement is coded by the *aircraft* creator in FSX most third party aircraft makers (and converters) have guessed and coded random values for the FSX scenery projection variables because the aircraft maker/converter never understood they were responsible for projecting the scenery correctly in FSX. Many have just made LAT/LON projection numbers up at random and they are all different.
Both viewing modes in FSX have errors. Both cause false scenery display according to what an individual aircraft designer randomly decided to encode. Not only do two viewing modes in a single aeroplane have entirely different scenery placement in FSX, each different aircraft in FSX has randomly different scenery placement and randomly different ways of displaying a 3 degree glidepath.
A flight simulator is not a variety of video game. Any simulator must be programmed to replicate reality. The rules of the simulation must be the laws of the real universe. In a simulator time and distance must match. In a flight simulator scenery placement must be real. In a flight simulator the azimuth and elevation of scenery as indicated by the gauges must match where the scenery is projected in the rear window of the simulation. None of those things is true in FSX until and unless the ZOOM has been encoded correctly by the *Aircraft Designer*.
........Real pilots need the distance shown on the DME to match where the scenery is. Real pilots need the glidepath observed through the windscreen to be three degrees when the ILS says it is three degrees. Real pilots need the climb gradient to the next ridge line to be real.
So do we!
Think hard about whether you will remember to fix every aeroplane you have ever acquired, or ever will acquire for use in FSX. If you doubt that you will remember or bother to fix every broken aeroplane in FSX you should avoid using FSX altogether. There are fewer 2D panels with gross errors in FS9 because it is not broken by default, but the same warning applies to those produced by third parties.
REALISM IS MORE THAN REALISTIC FLIGHT DYNAMICS.
In a perfect world all the files available for purchase and download would be free from gross errors. Real life is not like that. In order to experience flight simulation you must be vigilant. You must police the files you use. This tutorial is useless to anyone who does not bother.
FS9 VC mode always imposes realistic scenery perspective and placement. With a realistic eyepoint FS9 VC mode imposes realistic parallax and a fully functional field of view. Only eyepoint is coded by third parties and may need correction in FS9 VC.
FS9 is a flight simulator by default. FSX is just a video game by default. It delivers false scenery placement by design and by default. It requires substantial modification by users before it is safe to use FSX as a flight simulator. Those who cannot be bothered to convert FSX from video game to flight simulator should avoid using FSX...
......Gross errors are present in all default FSX Cockpit Views (CV = 2D panel), and most third party CVs for use in FSX, probably because those who wrote the code did not understand how to control scenery placement; or even that they were responsible for placing it.
In FSX every aircraft and every start up flight must specify the correct ZOOM to place the scenery at its true LAT/LON. Every producer of every *aeroplane* converted or created for use in FSX is individually and personally responsible for placing the scenery in FSX! This design error has caused massive problems for FSX users because many / most third party FSX producers have not understood how FSX works and have failed to impose the required scenery projection code.
.....FSX cannot read ZOOM commands from a panel.cfg. FSX *requires* the producer of the *aircraft* to control scenery placement, aircraft by aircraft! Created or converted!
The vast majority of aircraft released or converted for use in FSX lack the code necessary to place the scenery correctly within FSX. Most have nothing more than random values. Consequently those who have used FSX have been subjected to random scenery placement, random displayed mesh height, randomised climb paths and randomised glideslopes! FSX cannot deliver flight simulation without substantial effort by users to fix all the aircraft they use. If you hope to achieve flight simulation and cannot be bothered to fix FSX then you should avoid it.
....Cockpit View design is all about the harmonisation of the two overlaid Microsoft windows on the screen. Many 'panel designers' still have no idea what they are supposed to be doing or how to do it. Many 2D panels are functionally useless because the panel designer in FS9 and the aircraft designer in FSX only bothered to design and encode the front window on the screen and could not be bothered to control the perspective, placement and parallax of the projected scenery in the window behind it at all.
Those who only pretend to fly aeroplanes in MSFS never notice that the mesh and scenery have false perspective, false placement, false parallax, false glidepaths, false eyelines, and false mesh heights.
*Even when they are obviously correct in the Virtual Cockpit View, but entirely different when the 2D panel is in use*
If you hope to achieve flight simulation you must personally take responsibility for fixing or discarding all the broken cockpit environments that you have purchased, or that you have downloaded as freeware. Using this tutorial with randomly projected scenery at the wrong LAT/LON displayed with random parallax and random perspective is a waste of time. You must make time to fix what is broken or avoid what is broken in both FS9 and in FSX. Using broken flight simulator files is potentially dangerous, especially for real aircrew, or anyone who may become a pilot later. You may fail to understand that the scenery is misplaced and develop dangerous patterns of behaviour based on that false placement. Many of you do. These issues are explained and illustrated in greater detail within the simulation control interface tutorials available from http://www.calclassic.com/tutorials.
In this updated Propliner Tutorial I have included two screen shots to demonstrate the display errors which are present by default within FSX. Now is the time to study FSXcv.jpg and FSXvc.jpg which demonstrate exactly how FSX distorts perspective, scenery placement and mesh height. This destroys the necessary relationship between time and distance and destroys the necessary relationship between where the gauges correctly show the scenery is in azimuth and elevation and where it is being projected in the rear window of the simulation. The example chosen is the FSX default Baron. The default Baron CV has uncorrected FS9 scenery projection variables. The ridge line is displayed several miles closer than it really is.
Now let’s turn that gross error of distance and climb slope around and think what it means for the approach case. During the approach the time and distance to go to the runway is much longer than it is displayed to be. FSX CV users see a zoomed ‘picture’ which causes them to descend far too soon or at a VSI which is excessive. Things that are 8 miles, and perhaps four minutes away, may be displayed as less than six miles and less than three minutes away. That may be ‘entertaining’ in a children’s video game, but it is useless for flight simulation.
*Using misprojected scenery is the worst mistake anyone interested in flight simulation can make.*
Attempts to use this tutorial with broken or randomly encoded simulation control interfaces are doomed to failure.
Not even real aircrew can learn how to use a flight simulator when scenery projection is just random and grossly wrong. If you allow yourself to fly with grossly misplaced scenery you will never be able to judge distance or glideslope or climb slope during flight simulation. You will never be able to judge when to descend or what VSI is required.
Both screen shots are from the FSX default Baron at the same departure threshold using the values encoded by Microsoft. In the cockpit view screen shot the zoom is 1.0 because Microsoft failed to encode the required FSX Pythagorean compliant ZOOM value. In FSX cockpit view we are given false cues. The runway is displayed as much shorter than real life and with false perspective cues to match that deception, the ridge line is falsely displayed much closer than real life and the mesh is falsely rendered to match that deception.
That alone would make FSX a product for those interested in flight simulation to avoid. However there are also errors in its VC views. Again the *aircraft* producer has to project the scenery from VC view using code in the aircraft.cfg. In many cases the producers and converters of FSX aircraft have failed to understand their responsibility and have failed to provide the necessary scenery projection code. Many aircraft said to be compatible with FSX will display in FSX, but they are not FSX compliant. The necessary scenery projection code is randomised or has never been converted from the values used by FS9.
It is important to understand that last point. This is not just a problem of huge errors in one FSX viewing mode and smaller errors in the other. Because scenery placement is coded by the *aircraft* creator in FSX most third party aircraft makers (and converters) have guessed and coded random values for the FSX scenery projection variables because the aircraft maker/converter never understood they were responsible for projecting the scenery correctly in FSX. Many have just made LAT/LON projection numbers up at random and they are all different.
Both viewing modes in FSX have errors. Both cause false scenery display according to what an individual aircraft designer randomly decided to encode. Not only do two viewing modes in a single aeroplane have entirely different scenery placement in FSX, each different aircraft in FSX has randomly different scenery placement and randomly different ways of displaying a 3 degree glidepath.
A flight simulator is not a variety of video game. Any simulator must be programmed to replicate reality. The rules of the simulation must be the laws of the real universe. In a simulator time and distance must match. In a flight simulator scenery placement must be real. In a flight simulator the azimuth and elevation of scenery as indicated by the gauges must match where the scenery is projected in the rear window of the simulation. None of those things is true in FSX until and unless the ZOOM has been encoded correctly by the *Aircraft Designer*.
........Real pilots need the distance shown on the DME to match where the scenery is. Real pilots need the glidepath observed through the windscreen to be three degrees when the ILS says it is three degrees. Real pilots need the climb gradient to the next ridge line to be real.
So do we!
Think hard about whether you will remember to fix every aeroplane you have ever acquired, or ever will acquire for use in FSX. If you doubt that you will remember or bother to fix every broken aeroplane in FSX you should avoid using FSX altogether. There are fewer 2D panels with gross errors in FS9 because it is not broken by default, but the same warning applies to those produced by third parties.
REALISM IS MORE THAN REALISTIC FLIGHT DYNAMICS.
In a perfect world all the files available for purchase and download would be free from gross errors. Real life is not like that. In order to experience flight simulation you must be vigilant. You must police the files you use. This tutorial is useless to anyone who does not bother.
FS9 VC mode always imposes realistic scenery perspective and placement. With a realistic eyepoint FS9 VC mode imposes realistic parallax and a fully functional field of view. Only eyepoint is coded by third parties and may need correction in FS9 VC.
-Woog