[Flightgear-devel] cloud bug in pre3
Here's an interesting one: When flying thru a cloud layer, that layer either disappears or becomes a solid cloud bank, which is fine when the viewpoint is from the cockpit. However, if the viewpoint is from the tower, or perhaps by extension, from another plane in multi-player mode (I can't check this), this becomes undesirable behavior. The entire world around the viewpoint becomes either zero visability or clear, for as long as your plane is in that layer. Cirrus, overcast, broken = total fog Scattered, few = disappear/clear Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] pre3 bugs
I've noticed a few bugs to report, 1. when running flightgear, press [ESC] , then [TAB] (intending to move the cursor to the cancel button) instead the instrument settings dialog comes up. ok. But: I can not press the Close button or click in the text fields, instead I can only click on the exit window underneath. It looks like the who's on top also occurs elsewhere, but not the can't click close, or press [ESC]. Neither can I drag the instrument window away from covering the exit window. 2. Select Aircraft from list: looks like the list box is one line too large and overruns the top of it's border window. It's a pleasure to have the scroll bar work. :) 3. If I start fgfs with --aircraft=T38 I get the error: Fatal error: Failed to open file at /usr/local/share/FlightGear/data/Data/AI/refueling_demo.xml (received from SimGear XML Parser) I note this file (and directory) was removed from fgfs-base-pre3 but is still referenced in: src/AIModel/AIScenario.cxxlines 46-48 and the nonexistant directory is mentioned in: src/AIModel/AIFlightPlan.cxx lines 51, 113 4. In a list box (like in Select Aircraft), when single clicking on an entry, the text becomes unreadable. Perhaps the background was supposed to darken? Otherwise, very nice flight. I see several improvements were made over the summer. :) Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] compile error for pre3
Since Flightgear-0.9.9-pre2 compiled fine without any problems, I was surprised to see this: if g++ -DHAVE_CONFIG_H -I. -I. -I../../src/Include -I../.. -I../../src -I/usr/X11R6/include -I/usr/local/include -DPKGLIBDIR=\/usr/local/share/FlightGear\ -g -O2 -D_REENTRANT -MT fg_init.o -MD -MP -MF .deps/fg_init.Tpo -c -o fg_init.o fg_init.cxx; \ then mv -f .deps/fg_init.Tpo .deps/fg_init.Po; else rm -f .deps/fg_init.Tpo; exit 1; fi fg_init.cxx: In function `bool fgInitSubsystems()': fg_init.cxx:1581: error: `setRealtimeProperty' undeclared (first use this function) fg_init.cxx:1581: error: (Each undeclared identifier is reported only once for each function it appears in.) make[2]: *** [fg_init.o] Error 1 make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/FlightGear-0.9.9-pre3/src' make: *** [all-recursive] Error 1 where is setRealtimeProperty get declared? Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] compile error for pre3
I _knew_ it was something simple... I guess one prerequisite at http://www.flightgear.org/Downloads/source.shtml needs to be updated. Thanks Andy Stewart Andreason wrote: Since Flightgear-0.9.9-pre2 compiled fine without any problems, I was surprised to see this: fg_init.cxx:1581: error: `setRealtimeProperty' undeclared This is SimGear version skew. You need to use the properly matched version of SimGear, but are probably building against an older one still in your /usr/local. Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Runway lighting - What happened to the new terrain engine?
Paul Surgeon wrote: I don't see why we have to limit ourselves to *having* to have world coverage for the engine to be useful. Yes, could the 10x10 degree sections be a mixture of: most made with the terragear engine, and some made with other engines? Perhaps depending on complexity, population density, popularity... I think there is a mindset that one has to have all the scenery installed on hard disk which is a waste of space. How many people fly in all the countries of the world with FlightGear on a regular basis? Stuck with a modem, I'd rather have a big hard drive and ready made scenery. Yes, I'm sure there are plenty of users who are happy with the current scenery engine and one of the advantages it has is that there is no paging of huge textures while flying. This allows for high speed flights without any pausing and can also be run on older hardware or where CPU cycles are best used elsewhere like instrument updates or FDM's. Last time I tried a Mach 5 flight in FS2004 I ended up with blank/grey scenery tiles because it couldn't build and page the textures fast enough. :) For sub-sonic speeds and VFR flight an eye candy terrain engine would be very much appreciated. Yes, I agree. Could the scenery engine choose to load tiles at high ground speed, and then add the higher resolution texture engine at low speed? in the same way trees are only added when close enough to the ground. Or would this blending of 2 engines slow down the frame rate? Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
Jon Stockill wrote: Lee Elliott wrote: I was hoping to generate some 2048x2048 maps, to improve the roads railways and then intended to scale them down to a more usable size for use with Atlas. I'm just waiting for a bunch of 4096x4096 maps to generate before I feed them to mogrify. 2048x2048 still had a lot of breaks in - 4096x4096 while it still has gaps gives more of an impression of them being continuous lines. I'll probably scale them down to 1024x1024 and 256x256 when they're finished. I've just been having crazy ideas about using the objects database to do an obstructions overprint too :-) not so crazy an idea, for you are giving me ideas. The roads and rails do look much better, but at this resolution, the tile edges show up. Ooops, filled up my hard drive partition... These files are huge, 1-3Mb each at 2048x2048. but only 10% of that size in JPG Hey!, why can't Atlas read JPG files??? smoothed terrain would be an excellent place for JPG. Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Atlas release candidate
Jon Stockill wrote: One thing it is showing up is quite a few missing scenery tiles in the 0.9.8 scenery. I noticed the missing tiles last week, but found they were introduced a while back, as they are also in scenery-0.9.5, (at least the 3 I managed to download last year) I've almost got all the 0.9.8 scenery for the 48 states, and have been making a list of the errors. Curt, as I'm not on the terragear list, and the errors seem to be in the source data, please make a note of these. Am I correct in observing this is something we can't fix without getting the source data repaired? unfinished squares, hole in Scenery Terrain w082n23 w083n23 w087n41 w081n48 w073n49 w074n49 w075n49 square elevation errors w083n30 large diamond w079n34 large was not in 0.7.8 w094n41 medium square w106n30 large diamond w117n41 small was not in 0.7.8 w072n41 medium diamond shoreline blocks: w081n21 w082n21 w085n21 w080n42 Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] AirportList
Andrew Midosn wrote: On the other hand, if most people feel that it isn't necessary (you can change airports by using Position Aircraft (on ground) after all) then the select from list option should probably be removed. I think the goal of having a list of airports, is to provide a way for the casual user to search for 'Common Airport Name' to find the Airport ID. Loading the airport should be as simple as sending the ID to the subroutine for Position Aircraft. Just because we can 'less' or view the apt.dat.gz file, doesn't make the list unnecessary, keeping in mind the potential Target Audience. Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] fgrun improvements
Curtis L. Olson wrote: I can explain the bug to you. If you specify a lon/lat that lies on the *exact* border between two tiles (i.e. --lat=90 --lon=45) then at startup the ground intersection code can fail. This means that the scenery subsystem never returns a valid groud elevation. Oh. I didn't think of that possibility. Need to add 0.01 to the lat|lon if mod()== .00 to fix it. Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] v1.0 musings
Oliver C. wrote: FlightGear has gone a long way, but imo it is still far too early for a 1.0 production release. a way to switch the aircraft and airport when flightgear is running as basic features which are a must have in a 1.0 production release. I agree, and to be at startup or not, is probably a widely varying preference. but the other above mentioned features really need to get into 1.0. Oh! (smack) So the menus are Not Supposed to work (yet) Why didn't anybody just say so. Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] menu problems (was v1.0 musings)
Stewart Andreason wrote: Oh! (smack) So the menus are Not Supposed to work (yet) Pardon me, that wording was too general in an attempt to be funny. I Have been having trouble with... a few parts of the menu that I'm attempting to use most frequently. Specifically, File.Reset does not fully reset some of the time; after View.Replay, it resets to the beginning of the replay location after crashing, bo105 still is unflyable and Sometimes, c172 won't even return to the airport, or I may end up on the runway upside down, or started oriented upward with an initial velocity, thereby catapulted off the runway with the engine off Location.Airport on the ground is wonderful, but don't select this unless you're never crashed. I've had my attitude indicator on the panel get stuck 30 degrees off level, and Debug.Reload Panel doesn't reset it. Something else perhaps is... broken as a feature? Once again, Reset doesn't fix it. Autopilot.Settings Really Nice 'dialog box', but setting the boxes and numeric fields does not turn on the autopilot. neither does pressing ctrl-a,h,s,t... I finally found it turns on if I click on the AP button, in the c172 cockpit. I believe Melchoir said to take care of my aircraft, and, when I'm not trying to duplicate something ...um... interesting..., I do try! :D Just call me 'attention to detail' Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] aircraft required to start
It seems this aircraft is required to start FlightGear. fgfs WARNING: ssgLoadAC: Failed to open '/usr/local/share/FlightGear/data/Aircraft/pa28-161/Models/pa28-161.ac' for reading Abort Stewart ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] 0.9.8-pre2 bo105 bug
I'm really happy to see a helicopter in fg, and it is pretty nice too. :) Of course, it is harder to fly, or should I say, Land... than I thought. I've noticed a bug; if I crash :P and _replay_ (to watch from another angle) the model still shows the crashed version... flying. Happy hunting, Stewart -- Powered by Linux. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] 0.9.8 reset
Does the Reset option in the File menu work for anyone? After I fall, or bounce, down the side of a cliff at the edge of a runway, (like into a lake that shouldn't be there), I can never get the plane to reset, unless I Exit and Restart. Sometimes I return to the runway, sometimes I don't. But every time, the throttle stops responding to the joystick: Failed to untie property propulsion/c-thrust[0] Failed to untie property propulsion/engine[0]/reverser-angle The bouncing airplane nearly killed me with laughter last night, is the Cessna made of rubber? :) Stewart -- Powered by Linux. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] May I help with scenery?
Chris Metzler wrote: Robicd wrote: I'd love to know that it's not a complete waste of time insisting in using this OS, so ... Who is still maintaing world sceneries? Should I contact someone in order to coordinate the efforts? It depends on what you're really asking here. Curtis Olson builds and maintains the official terrain, and keeps the official ground scenery that's distributed with that terrain. At present, that ground scenery consists of randomly-used structures on certain terrain types (e.g. the trees in forests, the generic buildings used in urban areas, etc.), as well as the unique structures mostly developed by Frederic Bouvier in the default scenery area (the San Francisco Bay area). I Ah, so Curtis is solely responsible for the scenery. Would it be helpful to report on anomolies, or errors? Or is the scenery generator pretty much automated in combining topographic, tower, and roadway features? Stewart -- Powered by Linux. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] 0.9.8-pre2 bugs found
Have been testing pre2, have found a few bugs: 1st: from the command line, if I give --lat and --lon it will get locked into a loop, appearing to freeze after the splash screen. --log-level=debug shows this after Running Main Loop: Model iterations needed = 6, new remainder = 7505 interpolate(): lookup error, x to small = - interpolate(): lookup error, x to small = - Updating adjusted fog parameters. interpolate(): lookup error, x to small = -10339 FGTileMgr::update() State == Running no terrain intersection has no effect if I add either --altitude or --on-ground 2nd: pressing shift-numpad-1 crashes completely. Can be duplicated every time, also with no parameters given at command line. debug follows: Cockpit: code 1 status 0 User released key 49 with modifiers 2 terminate called after throwing an instance of 'std::string' Abort Exit codes: system=6 status=0 signal=6 The other 7 views on the numpad are ok. 3rd: From the menu, Location, Select Airport from List Clicking on any airport, and pressing Apply, only resets to starting location. Also, not a bug, but it would be nice to use the keyboard in the list, or type a letter to jump down the list. 4th: other warnings noted: Initializing OpenAL sound manager Adding subsystem fx ATC Display ATC Manager WARNING - INVALID type found in /usr/local/FlightGear/data/ATC/default.atis WARNING - INVALID type found in /usr/local/FlightGear/data/ATC/default.tower WARNING - INVALID type found in /usr/local/FlightGear/data/ATC/default.ground WARNING - INVALID type found in /usr/local/FlightGear/data/ATC/default.approach From file sounds sample = /usr/local/FlightGear/data/ATC/default.wav ... Reading properties for panel Cessna C172 Skyhawk IFR Panel Texture Aircraft/c172/Panels/Textures/panel-bg.rgb does not yet exist Created texture Aircraft/c172/Panels/Textures/panel-bg.rgb handle=155 Set background texture to Aircraft/c172/Panels/Textures/panel-bg.rgb [repeat for several C172 texture files] Otherwise, very impressive. It's getting harder to find faults. Stewart -- Powered by Linux. Virus and bug free, by design. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Scenery questions
At http://www.flightgear.org/Downloads/scenery.html I've noticed there are two colored boxes now for downloadable scenery, yellow and orange. Is one newer, or have more detailed objects? There are _fewer_ transmitter towers or cellular masts in 0.9.7 as there were in 0.9.5. While several were perhaps a little taller than in reality, i know several were valid, that are now gone. What happened? At 45*54.5N 119*30.0W thru 45*56.2N 119*19.2W the Columbia River is still filled with green land and trees, instead of water. Looks like an artifact, filled incorrectly downstream from a road/bridge. Is this an automatically generated landscape? If so, I imagine there is a database of corrections that must be generated and applied. Who's doing this? Thanks, Stewart -- Powered by Linux. Virus and bug free, by design. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
