I at 100% sure, the answer is NO, it just on a flat or curve surface. all eye manipulation, even with this text I make an illusion. you only can see it, you can't smell it, can't feel it, can't hear it and you would know that I'm so dumb
if want to accurate, just fly with real aircraft.
As local shop's run out of popcorn, I've nothing left to chew on,
so thought I'd throw out some ideas, just to
N.B. Originally written in August, (not updated).
I've not looked, but guessing all probably covered on other fora.
re: FSX - MS resuming responsibility - My previous post -
Given MS have FS-New in the wings,
I wouldn't expect MS to update any aspects of FSX.
I doubt they'd recode FSX for DX12 on W7.
Think it's likely just maintaining product availability/activation for FSX-SE.
FSX's 'Real World Weather' still isn't working.
Maybe once FS-New public testing commences ?
FS-New - Product Name -
Although the community is widely calling it 'Flight Simulator 2020',
'Windows 10' == Windows as a service.
A device may not be able to receive updates if the device hardware is incompatible, lacks current drivers or otherwise outside of the OEM period.
Not all features in an update will work on the devices.
A device also needs to have the latest update to remain supported.
Similarly 'Flight Simulator' might be a 'forever' product name,
with a continuous rolling development programme, (with ongoing new feature availability, being hardware-related).
32bit v 64bit -
FS-New to be available on Xbox One and Windows 10.
- Xbox - Specific about minimum hardware.
- PC - Only specifies OS W10, but not hardware. PC W10 - Available in both 32 and 64 bit.
Mentioned as developer.
Might have been selected for their previous collaborations,
including possibly for having implemented Kinect/HoloLens controls,
and also for user-avatar generation.
Aside - All aircraft's registrations displaying AS-MGS#
AS-MGS14 may have been destroyed, and the registration re-assigned
as it appears on at least 2 different aircraft.
______________________________________________________________ EXPECTATIONS - Personal -
Technologies as utilised in, or enhanced over, MS-FLIGHT's implementations.
File Structure/Implementation -
Virtualised 'Asset Locator' file system.
Abstracted 'Content' from 'Data About Content'.
e.g. SceneryObjects -
Single model, with multiple 'livery' textures.
Instance based textures.
Some instantly applied changes without full reload of all flight data.
Collision Detection -
All surfaces hardened.
Language - Coding -
Lua - As common coding language across the platform -
animations, gauges, missions, achievements/rewards, interface conditionals.
User - Familiarisation/Learning/Training/Etc. -
Entirely optional scenario-based.
Structured Career progression.
Hopefully with additional queryable meta-data.
UN LOCODE 'functions' (a string identifiying infrastructure present)
i.e. port/rail terminal/road terminal/airport/etc.
Latest version UN/LOCODE 201 9-1, (July 2019),
has identifiers for 111,523 locations worldwide, (cities/towns/villages)
'Jobs Board' -
Hopefully improved destination runway checking/discrimination than present in MS-FLIGHT.
Airport meta-tag LOCODE would enhance 'Job' description possibilities.
e.g. Transport passengers to cruise-ship.
Career mode -
Hopefully extended beyond MS-FLIGHT's capabilities.
Pilot Records -
Similar level of detail/attainment to MS-FLIGHT.
Hopefully with better sorting/filtering.
As per previous FS versions -
There were features present in alpha-versions,
that were turned off in RTM.
e.g. FSX alphas had -
- Cloud shadows
- Hardened 3D waves
Wouldn't expect everything to be OOBE available on day 1.
Skinned animated characters for - User, copilot, missions, multiplayer, etc.
? Walkabout ?
Present in cockpit.
Actively participate hands-on during checklists, (hooks existed in FLIGHT's aircraft models)
AI Traffic - Aircraft -
ROUTED - Follow airways, versus currently great-circled, (hooks existed in FLIGHT's propdefs).
Enhanced as per MS-FLIGHT, (sub-metre detailed).
I'd considered FSX 1km area coverage to be 'Legacy' supporting,
with 'Vector' as being intended FSX default for addons.
______________________________________________________________ WISHLIST - Personal -
Large/massive objects -
- To be visible beyond ~20 statute miles.
- e.g. Oilrigs to be visible at greater distance, than their helideck's windsocks.
Viewport - @ Zoom-levels lower than 100% -
Culling - Of any object should not occur.
Clipping - Of scenery objects should not occur.
Viewport - Cockpit -
Culling of any object/effect should not occur until
any object's origin is at least 20metres behind the user-aircraft model's origin.
______________________________________________________________ Early released pics/videos -
Visually stunning & massive improvement.
Pics were stated as 'In-Game', (or in one instance, 'In Hangar'),
i.e. Not modeling-program renders.
A few comments on, just covering matters I've not seen mentioned here - Titles below, as per original pic's filename. N.B. In some cases I'm being overly critical, given dev-status of originals.
Model/texture artifacting displaying at cloud edge overlaps.
Possibly a cloud impostor model is missing its texture, (at one-o-clock).
European Parliament Building - Bridges immediately N & W of, respectively over canal & river, display as if transparent.
CockpitDR400_3 - KittyHawk_E3_001 -
Both pics display AS IF camera can display user-controlled 'depth of field'.
i.e. Focus on what user's looking at.
Swell/Wave sets -
Origin directionally inappropriate -
- As if through island.
- Not radiating from inlet.
Suppress, or posssibly orient via overlay ?
Video - Pair of TBM-Socata aircraft over inlet/islands -
Wingtip landing light effects - With distance display at diff wing positions .
Cliff section photoscenery displays possible cloud remnants.
Water on slopes -
- Lake - RH far side
- River -
As if waterclass offset from terrrain mesh.
Trees - Corduroy effect, // diagonal lines of, crossing contours.
Relative to camera position, 3 off circular ?buttons?, (? or are they air vents ?)
appear to be ODDLY ORIENTED, show ?wrong?/lower edges.
Terrain LOD'ing -
Nearby view - 'Digital Surface Model' covered by autogen.
Distant view - POSSIBLY 'Digital Terrain Model' for canopy cover.
In retrospect, can't think what specifically prompted that thought. ;-)
Maybe wishful thinking.
Swell/Wave sets -
Inappropriate for lake.
Orientations & alignments -
- Effect 'contours' coastline, rather than origin based.
- Overly large for short fetch.