Stuart Buchanan wrote:
> --- Melchior FRANZ wrote:
> > Maybe the changelog should be on the wiki for fixes/extensions?
>
> An excellent use of the wiki - done. I've merged the data and simgear logs
> together here along with the feedback I've seen so far:
>
> http://wiki.flightgear.org/flightgear
On 5/10/07, Stuart Buchanan wrote:
--- Melchior FRANZ wrote:
> Maybe the changelog should be on the wiki for fixes/extensions?
An excellent use of the wiki - done. I've merged the data and simgear logs
together here along with the feedback I've seen so far:
http://wiki.flightgear.org/flightge
--- Melchior FRANZ wrote:
> Maybe the changelog should be on the wiki for fixes/extensions?
An excellent use of the wiki - done. I've merged the data and simgear logs
together here along with the feedback I've seen so far:
http://wiki.flightgear.org/flightgear_wiki/index.php?title=Changes_since_0
* John Wojnaroski -- Thursday 10 May 2007:
> OK, here is the list of salient changes for the next release
Also:
- fixed a bug where deleted property nodes were falsely referenced
- added texture cache so that common textures are shared among
models and don't consume separate texture memory
Th
* John Wojnaroski -- Thursday 10 May 2007:
> OK, here is the list of salient changes for the next release of
> Simgear. If I've missed any please let us know
Sounds good. I'd just make some small changes:
> Redefined airport signage class to a more general class for all signs
> Sign emissive v
OK, here is the list of salient changes for the next release of
Simgear. If I've missed any please let us know
Redefined airport signage class to a more general class for all signs
Added new commands to create signs
More stringent header dependencies
Sign emissive values settable via material xm
6 matches
Mail list logo
