Realism: Difference between revisions

Jump to navigation Jump to search
15 bytes added ,  6 March 2016
no edit summary
No edit summary
Line 23: Line 23:


<gallery mode="packed">
<gallery mode="packed">
File:Southwest04.jpg|
File:Southwest04.jpg
File:Kansas_Scenery_Two.jpg|
File:Kansas_Scenery_Two.jpg
</gallery>
</gallery>


Line 54: Line 54:
File:Moist air and haze seen from a Boeing 707 cockpit.png|Haze and dust particles with realistic blue color in distance
File:Moist air and haze seen from a Boeing 707 cockpit.png|Haze and dust particles with realistic blue color in distance
File:Morning flight.jpg|Few remaining clouds in morning sunlight, looks like it will be a nice flying day!
File:Morning flight.jpg|Few remaining clouds in morning sunlight, looks like it will be a nice flying day!
</gallery>


== Rendering ==
== Rendering ==
Line 64: Line 65:


<gallery mode="packed">
<gallery mode="packed">
File:Southwest09.jpg|
File:Southwest09.jpg
File:Water-sky01.jpg|
File:Water-sky01.jpg
File:Rayleigh_blue.jpg|
File:Rayleigh_blue.jpg
File:Tree02.jpg|
File:Tree02.jpg
</gallery>
</gallery>


Line 76: Line 77:


== Properties ==
== Properties ==
{{Stub}}
{{Stub|section=1}}
{{FGCquote
{{FGCquote
|1= I've started creating some properties under /sim/realism (mostly booleans for the moment), with the expectation that at some point we can create a GUI, and also use some Nasal to batch-configure the individual settings for different applications - flight trainer, game mode, kiosk, etc, etc. I'd be happy to add a /sim/realism/start-parked and /sim/realism/start-dark (though the latter involves aircraft designer help to hook the optional autostart functions of each aircraft). My concern is touching the dreaded position init code, which is already baroque and complex. There's also the question of guessing a parking position when we don't have parking stand data - eg picking a point some distance away from the runway centerline (runway width * 5, maybe?), level with the threshold - but like all heuristics, this one has problems.
|1= I've started creating some properties under /sim/realism (mostly booleans for the moment), with the expectation that at some point we can create a GUI, and also use some Nasal to batch-configure the individual settings for different applications - flight trainer, game mode, kiosk, etc, etc. I'd be happy to add a /sim/realism/start-parked and /sim/realism/start-dark (though the latter involves aircraft designer help to hook the optional autostart functions of each aircraft). My concern is touching the dreaded position init code, which is already baroque and complex. There's also the question of guessing a parking position when we don't have parking stand data - eg picking a point some distance away from the runway centerline (runway width * 5, maybe?), level with the threshold - but like all heuristics, this one has problems.

Navigation menu