Reaching for the stars: Difference between revisions

Jump to navigation Jump to search
(Created page with "{{Stub}} {{Template:Spaceflight}} == Background == {{FGCquote |1= The code I'm looking at is a few of the key parts of what needs to be adapted for landing on the moon! The...")
 
Line 10: Line 10:
   | title  = <nowiki>Re: Implementing moonlight (or not)</nowiki>
   | title  = <nowiki>Re: Implementing moonlight (or not)</nowiki>
   | author = <nowiki>bugman</nowiki>
   | author = <nowiki>bugman</nowiki>
  | date  = Dec 17th, 2015
  | added  = Dec 17th, 2015
  | script_version = 0.23
  }}
}}
== Prototyping ==
{{FGCquote
|1= Note that regardless of recent interest in supporting this, this is a really long-standing idea (just search the archives for "moon" or "mars" to see for yourelf).
In my opinion it would be a terrific idea to review the corresponding code and see if/what and how things could be adapted to become increasingly configurable - if breakage/backward compatibility should turn out to be problematic, we could introduce a dedicated subsystem - pretty much  based on the approach/features that Thorsten is using in [Earthview#|Earthview]]
The basic idea being to encapsulate a light source, and LOD nodes for different ranges/visibility and texture sheets, in conjunction with effects/shaders that are to be applied.
This would be in line with how many other features in FlightGear started out being hard-coded, were then moved to become property-configurable, and finally become fully instantiable/modifiable at run-time (AI traffic, models, Canvas, camera views)
|2= {{cite web
  | url    = http://forum.flightgear.org/viewtopic.php?p=269045#p269045
  | title  = <nowiki>Re: Implementing moonlight (or not)</nowiki>
  | author = <nowiki>Hooray</nowiki>
   | date  = Dec 17th, 2015
   | date  = Dec 17th, 2015
   | added  = Dec 17th, 2015
   | added  = Dec 17th, 2015

Navigation menu