Hi,
Just installed in Windows 7 64-bits the FlightGear
RC3.exe for a trial, and noted some minor things -
1. It will install over your previous version, in
my case 2.6 unless you watch and change the
install path from C:\Program Files\FlightGear\...
In my case I changed the install to
C:\Program Files\FlightGear-2.8
so the icon correctly uses -
C:\Program Files\FlightGear-2.8\bin\Win64\fgrun.exe
BUT fgrun retains the paths to the previous
2.6, like
C:\Program Files\FlightGear\bin\Win64\fgfs.exe
C:\Program Files\FlightGear\data
I had to manually change these...
Maybe it would be better installing to say
C:\Program Files\FlightGear\2.6\
\2.8\ etc?
And the fgrun path to the cache of persistent
data perhaps should also change... like -
C:\Users\user\AppData\Roaming\flightgear.org\fgrun\2.6\airports.txt
C:\Users\user\AppData\Roaming\flightgear.org\fgrun\2.8\airports.txt
And say fgrun26.prefs fgrun28.prefs, or something,
making it possible to have 2 or more versions active
at one time...
Like I suppose a few people now, I like to keep the last
working version, while I try the latest, especially
now they are arriving each 6 months...
And a big thank you to those making that happen ;=))
And I think the installer will setup a desktop icon
labeled 'FlightGear 2.6...' unless you manually change
it...
2. On loading the sopwithCamel-YASim... get a console
output error of -
... running Camel utilities
Nasal runtime error: props.setDoubleValue() with non-number
at C:/Program Files/FlightGear-2.8/data/Nasal/props.nas, line 30
called from: C:/Program
Files/FlightGear-2.8/data/Aircraft/sopwithCamel/Models/fuel.nas, line
280
called from: C:/Program
Files/FlightGear-2.8/data/Aircraft/sopwithCamel/Models/fuel.nas, line
249
called from: C:/Program
Files/FlightGear-2.8/data/Aircraft/sopwithCamel/Models/fuel.nas, line 78
But can not particularly see why - fuel.nas has
249: initDoubleProp(t, level-gal_us, 0); 'looks' ok.
Except in the initDoubleProp function, it sets -
node = arg[0]; prop = arg[1]; val = arg[2]; ok,
and then does -
if(node.getNode(prop) != nil) {
val = num(node.getNode(prop).getValue());
}
280: node.getNode(prop, 1).setDoubleValue(val);
Could it be the nasal num() functions returns a
non-number???
I think this problem has been around for quite
some time, like back before 2.6...
Will continue doing some more testing as time
permits...
HTH.
Regards,
Geoff.
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
