John Denker wrote:
> On 01/16/2011 02:23 PM, Martin Spott wrote:
>> John Denker wrote:
>>> FG is still using airport data that hasn't been updated since 2008.
>>
>> Depends on your particular definition of "FG". To be precise, the file
>> at:
>>
>> http://mapserver.flightgear.org/apt.dat.gz
On 01/16/2011 02:23 PM, Martin Spott wrote:
> John Denker wrote:
>
>> FG is still using airport data that hasn't been updated since 2008.
>
> Depends on your particular definition of "FG". To be precise, the file
> at:
>
> http://mapserver.flightgear.org/apt.dat.gz [1]
>
> contains 21
Unfortunately most of the users are not using or able to create individual
Terrain builds. If I could without taking computer courses I would, just to
make use of those 213 airfield updates! :) :)
…trying to be patient.
Peter :)
On Jan 16, 2011, at 4:23 PM, Martin Spott wrote:
> John Denker
Hi,
I have sent Martin an updated layout for KTPA. As is my understanding, thie
runways will be updated in the next world scenery build, unless I've done
something wrong.
Cheers
John
--
Protect Your Site and Customers
On 16 Jan 2011, at 21:05, Martin Spott wrote:
>> The solution as I think has been said is to figure out if there is a
>> way to get the name of the top level folder using Nasal, or to figure
>> out a way to use nasal within the scenery folder? You could always
>> try calling the nasal script fro
Hi,
I wrote a config file for the joystick "Thrustmaster T.Flight Hotas X" that
is not supported in the 2.0.0 nor in the git repository (see
http://gitorious.org/fg/fgdata/trees/master/Input/Joysticks/ThrustMaster). What
is the proper way to submit the .xml file for review/approval so that it can
John Denker wrote:
> FG is still using airport data that hasn't been updated since 2008.
Depends on your particular definition of "FG". To be precise, the file
at:
http://mapserver.flightgear.org/apt.dat.gz
contains 213 airfield updates (currently) which have been merged over
the time, which
On 01/16/2011 01:25 PM, Barry Fawthrop wrote:
> There was a news article on Magnetic North Change
> and How KTPA had to change from 90 to 80
>
> Are these changes being effected into FlightGear ???
No.
FG is still using airport data that hasn't been updated since 2008.
More than a few things
"J. Holden" wrote:
> The solution as I think has been said is to figure out if there is a
> way to get the name of the top level folder using Nasal, or to figure
> out a way to use nasal within the scenery folder? You could always
> try calling the nasal script from the xml (I have absolutely no
Barry Fawthrop wrote:
> There was a news article on Magnetic North Change
> and How KTPA had to change from 90 to 80
>
> Are these changes being effected into FlightGear ???
Depends on if anyone's submitting a modified layout.
Actually the runway directions are hardwired into our airfield lay
There was a news article on Magnetic North Change
and How KTPA had to change from 90 to 80
Are these changes being effected into FlightGear ???
--
Protect Your Site and Customers from Malware Attacks
Learn about vari
Hi Heiko
This isn't just a Terrasync problem as I have scenery files in multiple scenery
folders for testing purposes. So if the helipad was in my Scenery2/ folder, it
also wouldn't work...
The solution as I think has been said is to figure out if there is a way to get
the name of the top leve
> It won't work. Problem: to use the pads inside the
> Objects/e010n40/e011n47-folder I defined a line in the nasal-script like
> that: setprop ("models/LOWI/model/path",
> "Scenery/Objects/e010n40/e011n47/LOJO_helipad_libelle.xml");
>
> This path seems to be absolute.
> If you want to make this
Hi,
> On 16 Jan 2011, at 13:41, Martin Spott wrote:
>
> > I know we've already been talking about this topic but
> I don't remember
> > all the details. To me it looks like either a)
> the animation are
> > depending a little bit too much on textual path names
> or b) FlighGear
> > doesn't prov
On 16 Jan 2011, at 13:41, Martin Spott wrote:
> I know we've already been talking about this topic but I don't remember
> all the details. To me it looks like either a) the animation are
> depending a little bit too much on textual path names or b) FlighGear
> doesn't provide a reasonable variab
Hi Heiko,
Heiko Schulz wrote:
> terrasync
> -Scenery
> -Airports
> -Terrain
> -Models
> -Objects
Would be a little bit like saying "this car is red red" since
everything in TerraSync is directly related to Scenery ;-)
I know we've already been talking about this topic but
On 16 Jan 2011, at 10:56, fiers...@zonnet.nl wrote:
> When I saw this, I removed all sources for OSG and Simgear and restarted with
> a fresh git clone, but the error remains. I searched the forums and noticed
> someone else has the same problem with a completely freshly cloned git
> version.
Hi,
Still working on the moveable helipads together with Oliver Thurau I have still
problems to make the pads working for any scenery-folder like TerraSync,
Scenery or data/Scenery. It only works a specific one defined- not for all ones.
Looking for a solution I came to the question why it is l
Hi All,
I have been away for a couple of weeks, so perhaps I have missed
something. When I tried to compile a fresh git version using
download_and_compile.sh, I noticed there were some updates in OSG. It
seems simgear is not in sync (yet?), though, because I am getting the
following error:
19 matches
Mail list logo
