Re: [Flightgear-devel] Fwd: in air starts and all preset
James Turner wrote: My 'least bad' option is to save control state (from the -set.xml, or config, or command line) as part of the initial state, so that it's re-applied after the controls are reset. According to my understanding a safe assumption about defaults would mean to have the state of a fresh startup scenario replayed. More precisely this would mean to a) read 'static' aircraft configuration (from '*-set.xml' files), b) furtheron read stuff which had been written into '$HOME/.fgfs/', c) afterwards read the '$HOME/.fgfsrc' file and d) finally the given command line flags. At least this is what I'd expect as a user To achieve such state upon reset you could think of a) storing every parameter, which had been read from startup config ressources, into reserved space in memory as The Initial State or b) re-read the same set of config files and/or flags upon reset. I guess that b) would be rather ressource-intensive, and since storing a boiled down copy of the startup properties in memory might be rather cheap these days, I suspect it would be the way to go. Best regards, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: in air starts and all preset
On 2 Nov 2010, at 14:14, Martin Spott wrote: According to my understanding a safe assumption about defaults would mean to have the state of a fresh startup scenario replayed. More precisely this would mean to a) read 'static' aircraft configuration (from '*-set.xml' files), b) furtheron read stuff which had been written into '$HOME/.fgfs/', c) afterwards read the '$HOME/.fgfsrc' file and d) finally the given command line flags. At least this is what I'd expect as a user To achieve such state upon reset you could think of a) storing every parameter, which had been read from startup config ressources, into reserved space in memory as The Initial State or b) re-read the same set of config files and/or flags upon reset. I guess that b) would be rather ressource-intensive, and since storing a boiled down copy of the startup properties in memory might be rather cheap these days, I suspect it would be the way to go. Yeah, and indeed part of a) is already done - it's just a question of extending it to more properties / trees of properties. I can't think of any likely ways this could break existing aircraft or scripts - can you? James -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] pa24 and pitts changes committed
pa24-250 changes The light cone approach to landing lights has not worked for some time. I reverted to my original landing light emulation. Is someone working on light effects? pitts s1c changes 1. fixed typos in sound.xml 2. changes both wing incidence to 1.5 deg. and the horizontal stab incidence to 2 deg per the pitts s1c plan set posted at the Biplane Forum (www.biplaneforum.com). 3. softened both main gear compression and spring to make take-off and landing possible w/o banging the lower wing tips on the ground. The real Pitts is hard to land but not impossible. 4. animated main gear flex to match compression. I missed #1 and #2 in the commit message for the pitts. Dave P. -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Fgviewer multiple defines.
For a week or so now I have the following link error in Fgviewer (VC++ 2010) FlightGear.vcxproj - C:\FlightGear\flightgear\projects\VC100\Win32\Release\fgfs.exe -- Build started: Project: fgviewer, Configuration: Release Win32 -- fgviewer.cxx osgDB.lib(osgDB.dll) : error LNK2005: public: void __thiscall std::basic_ofstreamchar,struct std::char_traitschar ::`vbase destructor'(void) (??_d?$basic_ofstr...@du?$char_traits@d...@std@@@std@@QAEXXZ) already defined in SimGear.lib(props_io.obj) osgDB.lib(osgDB.dll) : error LNK2005: public: __thiscall std::basic_ofstreamchar,struct std::char_traitschar ::basic_ofstreamchar,struct std::char_traitschar (char const *,int,int) (??0?$basic_ofstr...@du?$char_traits@d...@std@@@std@@q...@pbdhh@Z) already defined in SimGear.lib(props_io.obj) C:\FlightGear\flightgear\projects\VC100\Win32\Release\fgviewer.exe : fatal error LNK1169: one or more multiply defined symbols found -- Build started: Project: fgjs, Configuration: Release Win32 -- ul.lib(ulClock.obj) : warning LNK4099: PDB 'vc90.pdb' was not found with 'ul.lib(ulClock.obj)' or at 'C:\FlightGear\flightgear\projects\VC100\Win32\Release\vc90.pdb'; linking object as if no debug info ul.lib(ulError.obj) : warning LNK4099: PDB 'vc90.pdb' was not found with 'ul.lib(ulError.obj)' or at 'C:\FlightGear\flightgear\projects\VC100\Win32\Release\vc90.pdb'; linking object as if no debug info fgjs.vcxproj - C:\FlightGear\flightgear\projects\VC100\Win32\Release\fgjs.exe My osg svn copy is about 2 weeks old Regards Alan -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fwd: in air starts and all preset
James Turner wrote: On 2 Nov 2010, at 14:14, Martin Spott wrote: According to my understanding a safe assumption about defaults would mean to have the state of a fresh startup scenario replayed. More precisely this would mean to a) read 'static' aircraft configuration (from '*-set.xml' files), b) furtheron read stuff which had been written into '$HOME/.fgfs/', c) afterwards read the '$HOME/.fgfsrc' file and d) finally the given command line flags. At least this is what I'd expect as a user To achieve such state upon reset you could think of a) storing every parameter, which had been read from startup config ressources, into reserved space in memory as The Initial State or b) re-read the same set of config files and/or flags upon reset. I guess that b) would be rather ressource-intensive, and since storing a boiled down copy of the startup properties in memory might be rather cheap these days, I suspect it would be the way to go. Yeah, and indeed part of a) is already done - it's just a question of extending it to more properties / trees of properties. I can't think of any likely ways this could break existing aircraft or scripts - can you? I don't - but I'm probably not the best candidate for being questioned about this flavour of details ;-) Even if it would, having a plausible, reasonably defined and thus reproducible mechanism for the long term is probably worth a lot more than an obviously imperfect hack just to meet the needs of a few scripts (if there were the demand for such thing). The startup-scenario is a well-defined state and therefore I can't imagine why its re-instantiation could be bad (TM). Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Continuous Integration (nightlies!)
Thanks to Gene, and some script hackery by me, we have a Mac 'nightly' (actually more often than that right now, but it may become a real nightly): http://flightgear.simpits.org:8080/job/FlightGear-next-mac/lastSuccessfulBuild/artifact/ Download, read the instructions, and fly! (Key info from the Readme - you need to have fgdata checked out, and this is only fgfs, no GUI launcher - it's aimed at testers and aircraft developers, not casual users) If this proves popular, we'll upload the binaries to a proper server, since the build server isn't ideally placed for that. (To help gauge the popularity, please let me know if you use these) Windows equivalent to follow 'soon'. Notes for Tat other Mac developers - this is an automake build, 32-bit Intel only, with static PLIB, OSG as dylibs and ALUT as a framework; all plugins, dylibs and frameworks are inside the bundle at default locations. It seems a bit slower than my Xcode build, possibly because the current compile flags for Mac automake don't specify any SSE options or vectorisation. I have only tested on 10.6, 10.5 should work, no idea about 10.4. Future work - include symbols via an .xSYM, so crash reports are useful. Regards, James -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Unexpected behaviour of FlightGear's material animation
Hi all, I have created some FlightGear scenery models that light up at night. I have followed the directions contained on the Howto: Illuminate faces page on the FlightGear wiki. My model's XML file contains the following: animation typematerial/type object-nameWalls/object-name condition greater-than property/sim/time/sun-angle-rad/property value1.70170/value /greater-than /condition emission red1/red green1/green blue1/blue /emission /animation Using FlightGear 1.9.1 on Ubuntu 10.04, this works -- except the lights don't turn off. The wiki says that the lights will turn off automatically when the condition is no longer true, but this did not work for me. To turn the lights off I needed to include the following: animation typematerial/type object-nameWalls/object-name condition not greater-than property/sim/time/sun-angle-rad/property value1.70170/value /greater-than /not /condition emission red0/red green0/green blue0/blue /emission /animation Can anyone confirm whether the behaviour works as described in the wiki? Should the lights automatically turn off, or is the wiki wrong and the second condition is required? Also, using FlightGear v2.0.0 on Ubuntu 10.04 (compiled on 1-Nov-2010 using the Download and Install script), the behaviour is different again: the lights are lit at all times. Has the behaviour changed for this version, is it still under development, or have I missed a change in the animation properties? Many thanks, Greg Hawkes -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Unexpected behaviour of FlightGear's material animation
http://code.google.com/p/flightgear-bugs/issues/detail?id=165#c4 -- Nokia and ATT present the 2010 Calling All Innovators-North America contest Create new apps games for the Nokia N8 for consumers in U.S. and Canada $10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store http://p.sf.net/sfu/nokia-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
