Thanks to Martin and Curt for your answers. That helped a lot :) I will
post about my progress on the forums.
Maxime
Martin Spott wrote:
Hi Maxime,
Maxime Guillaud wrote:
Following the tutorial from the wiki
(http://wiki.flightgear.org/index.php/Using_the_Custom_Scenery_TerraGear_Toolse
Curtis Olson wrote:
> On Mon, Jun 8, 2009 at 2:04 PM, Martin Spott wrote:
>> James Turner wrote:
>>
>> > Is there an accepted way to store an absolute time (as opposed to an
>> > interval or delta) in the property tree? [...]
>> FlightGear's "official" time seems to be seconds since midnight
The mapping of land use/cover types to specific textures is defined in the
materials.xml file. In the past we often would map several similar types of
land cover to a single texture to keep texture memory usage under control
and in some situations because we didn't have a specific texture created
Hi Maxime,
Maxime Guillaud wrote:
> Following the tutorial from the wiki
> (http://wiki.flightgear.org/index.php/Using_the_Custom_Scenery_TerraGear_Toolset),
>
> I was able to generate some scenery successfully. However, when I load
> it into FG, it looks like many of the land use data types
On Mon, Jun 8, 2009 at 2:04 PM, Martin Spott wrote:
> Hi James,
>
> James Turner wrote:
>
> > Is there an accepted way to store an absolute time (as opposed to an
> > interval or delta) in the property tree? The obvious way (to me)
> > would seem to be using a double to store seconds since the Un
Hello,
Following my recent uncovering of detailed landcover information for
France (see
http://www.flightgear.org/forums/viewtopic.php?f=5&t=5105&sid=c3a960f7f3ee2f652973410a6d06ce9b),
I proceeded to generate custom scenery integrating this data.
Following the tutorial from the wiki
(http://
Hi James,
James Turner wrote:
> Is there an accepted way to store an absolute time (as opposed to an
> interval or delta) in the property tree? The obvious way (to me)
> would seem to be using a double to store seconds since the Unix epoch,
> but it's not exactly human-readable. Of course
diff -u -r1.4 adi.xml
--- Aircraft/f16/Models/adi.xml 7 Jun 2009 08:25:53 - 1.4
+++ Aircraft/f16/Models/adi.xml 8 Jun 2009 18:30:04 -
@@ -403,7 +403,7 @@
- glide-slop-index
+ glide-slope-index
material
controls/lighting/instruments-norm
--alex--
--
| I belie
Another of those simple-but-awkward questions:
Is there an accepted way to store an absolute time (as opposed to an
interval or delta) in the property tree? The obvious way (to me)
would seem to be using a double to store seconds since the Unix epoch,
but it's not exactly human-readable. Of
On 5 Jun 2009, at 19:52, James Turner wrote:
> I want this for the route-manager dialog, but I can imagine similar
> concepts being useful in the other places in the GUI - for example
> the 'position on ground' dialog could have the runway and parking
> position fields replaced with menus,
On 6 Jun 2009, at 08:46, Melchior FRANZ wrote:
> This would really be the best approach. It could then also be used to
> live-enable/disable (grey out) widgets, or to change their color while
> the dialog is open, etc. I'll work on that in the near future and try
> to keep PLIB'isms away as far a
11 matches
Mail list logo
