Hello,
With GIT from today 03/29/2013 and jenkins build #1021 the issue is back again,
and it even seems worse than ever before!
Here the output of the console since 30min, FGFS is stuck in "Loading
Navigation datas":
Logging priority is debug
initializing cloud layers
Using initial window size: 960 x 720
Initializing splash screen
Enabling ATI viewport hack
Configuration State
======= ==============
aircraft-dir = "C:/Programme/FlightGear/fgdata2/Aircraft/ec135"
fghome-dir = "C:\Dokumente und Einstellungen\Heiko Schulz\Anwendungsdaten\flight
gear.org"
aircraft-dir = "C:/Programme/FlightGear/fgdata2/Aircraft/ec135"
aircraft-search-paths =
C:\Programme\FlightGear\MD-900
scenery-search-paths =
C:/Programme/FlightGear/terrasync
C:/Programme/FlightGear/terrasync/Terrain
C:/Programme/FlightGear/terrasync/Objects
Cannot find splash screen file 'Aircraft/ec135/splash.rgb'. Using default.
Splash screen progress init
NVIDIA Corporation
GeForce GTX 460/PCIe/SSE2
4.2.0
4.20 NVIDIA via Cg compiler
Splash screen progress loading-aircraft-list
Splash screen progress loading-nav-dat
NavCache at:Path "C:/Dokumente und Einstellungen/Heiko Schulz/Anwendungsdaten/fl
ightgear.org/navdata_2_11.cache"
NavCache: initial build required for Path "C:/Programme/FlightGear/fgdata2/Airpo
rts/apt.dat.gz"
NavCache: main cache rebuild required
NavCache at:Path "C:/Dokumente und Einstellungen/Heiko Schulz/Anwendungsdaten/fl
ightgear.org/navdata_2_11.cache"
will create tables
Data file version = 810
...
NavCache: initial build required for Path "C:/Programme/FlightGear/terrasync/Air
ports/Z/Y/C/ZYCC.ils.xml"
re-loaded ILS data for ZYCC
nav.dat load took:18513
What I write now is not to make anyone upset but might not be loved by
everyone, as I think I have to remind some things:
Would it be possible to test sensible things BEFORE they went into GIT? I think
in the past we tested cross-plattform sensible things before it went into GIT/
CVS.
Yes, I'm aware that GIT is the developement place, and with this a larger group
of people can be reached for testing.
Yes, I'm also aware that developing for cross-plattform is pretty challenging.
But Co-Developers depends on the latest developement steps if they want to make
it compatible with the next FlightGear release! It is pretty bad for
Co-developers when due such failures their own projects are delayed. Not every
developer has plenty of time everyday and week to wait until the problem has
been fixed.
I hoped that I could get my Project EC135 P2 into FGdata in the next weeks
since I spent about guessed 100 hrs into finetuning the fdm, but due this bug
I'm not be able to make further developement steps, especially regarding
tooltips and the new VSI, and so my little project will be delayed now for a
indefinitely time since I will probably very busy with studies again until
early summer.
Cheers
Heiko
------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete
for recognition, cash, and the chance to get your game on Steam.
$5K grand prize plus 10 genre and skill prizes. Submit your demo
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
