[Flightgear-devel] Local Weather in 2.4
Hi All, I've had a short look at how ThorstenB has implemented Local Weather as a run-time loadable submodule, and for me it performs just fine, but in the Forum I had a few people reporting problems either with METAR mode or in general (unfortunately not with enough info so that I could diagnose anything). It'd be great if some people here could also test if the new structure works well or not and provide some feedback so that I can fix it if anything needs fixing. Also, the atmospheric light and haze model is a bit rough and untuned. Unfortunately, I'll have very little time during the next weeks to test-fly or tune anything, so if I could get some feedback about what situations look (most) unrealistic, that'd be helpful. Thanks in advance, * Thorsten -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Website update?
Curt - would it be possible for you to change the Developers link on the main FlightGear page? Can the CVS Resource and Source Code menu items be condensed down to a Portal link that points to this wiki link: http://wiki.flightgear.org/Portal:Developer ...or give me access and I'll do it. :D g. -- Proud owner of F-15C 80-0007 http://www.f15sim.com - The only one of its kind. http://www.simpits.org/geneb - The Me-109F/X Project Some people collect things for a hobby. Geeks collect hobbies. ScarletDME - The red hot Data Management Environment A Multi-Value database for the masses, not the classes. http://www.scarletdme.org - Get it _today_! Political correctness is a doctrine, fostered by a delusional, illogical minority, and rabidly promoted by an unscrupulous mainstream media, which holds forth the proposition that it is entirely possible to pick up a turd by the clean end. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Heads up: scenery download / built-in
On 21.06.2011 00:39, Vivian Meazza wrote: The bug which was stopping the built-in download running here was trivial - once we found it: a space in a directory name. Replaced with an underscore and it worked right out of the tin. The white-space issue is fixed for the new library now. It only applied to external svn. The same problem persists for original terrasync(.exe) - it'll be fixed there once the utility is adapted to use the library (after the release). Same is true for the trailing '/' issue. Fixed for the library now, persisting for terrasync(.exe) for now. Not quite - only the external mode was available. That turned out to be caused by a non-updated config.h file. Thanks to Fred for his help and guidance to solve that one. Indeed, thanks to Fred. It did work nicely for automake. I'm sorry that there were issues with the MSVC9 project (or cmake). But I'm depending on others helping me out here. And I truly hope we can have a common build system only one day - cmake maybe. In doing this I noticed that both the built in and external variants seem to be functionally similar. I can't even work out how or why the external variant works - but it does. FG finds, starts, and stops the external SVN program. Either ThostenB has been very clever, or it's just serendipity here. I hope it's the former. The code relies on finding svn on the system path. Same as terrasync(.exe) did - remember it's (almost) the same code. The latest update (yesterday) has an option to configure a full path to svn(.exe), which resolves the issue with systems where svn(.exe) isn't on the system path. Again, that's not available yet for the terrasyn(.exe) utility - it will be later (see above). And of course, the svn-library/svn-command-line options are functionally similar. 4. It is handy to be able to switch off/on scenery download at runtime, but here you only get about 5 of the 10 fps back. I see that once started the svn program remains loaded: this might be the cause. I don't see svn processes sticking. If a svn process is still present, then subversion is still active. The call to external svn is blocking - it's impossible that a svn process sticks when you've successfully disabled svn support (see status in GUI). You'll notice that hitting Apply/OK buttons briefly block the GUI when you disable terrasync: they block since the code waits for the final (blocking) svn operation to return/abort. And I can guarantee that there is no thread or anything running once terrasync is disabled. So, if you see any fps difference and terrasync is disabled, then that difference isn't caused by terrasync/svn. 5. The automatic refresh works well. There is an occasional grey-out. Disconcerting at first, but actually not a problem. This is a major advantage over Terrasync Yesterday, I have limited that feature for the current release to only affect cases where ocean tiles (missing scenery) are replaced by actual scenery. It removes the distracting effect for normal tiles, until we can handle the refresh smoothly (like when they are out of sight). It remains an advantage when missing scenery is replaced by actual data: better to have a brief gray-out and then see the tile with the destination airport, than to keep seeing a patch of ocean/missing scenery. 5. To use the built-in option requires 2 additional and quite large dependencies which will need updating etc from time to time. For those of us that build FG this is a bit of a pain. It's absolutely the same dependency that terrasync(.exe) has. If you haven't used/weren't interested in terrasync(.exe) so far - don't bother about the new feature. If you have used it, then FG can now be built with the same dependencies like terrasync(.exe) was. Again, nothing really changes. cmake/automake will make sure that the svn-library dependency is automatically disabled when the library isn't present (again, sorry, if you're using a fixed MSVC9 project - hopefully cmake will help you soon). Those running pre-built Windows/Mac binaries will be happy about using the svn-library (no separate svn utility to worry about) - especially since a svn command-line utility isn't common for most normal Win/Mac users/systems. I guess most Linux distros have a svn utility pre-installed by default. And those building FG themselves (again, many Linux users I guess) have the option to use external svn. 6. Both the internal and external variants seem to be using the external svn.exe. No way. Built-in svn uses the library and doesn't depend on any external svn(.exe). If you saw svn(.exe) being called, then built-in support was disabled (either since the feature wasn't compiled into FG or since the use-built-in-svn property was false). To make such things more obvious, there's a new status message when svn starts now: it'll tell whether internal or external support is selected/used. Pull yesterday's simgear. Do we require Windows users to have
Re: [Flightgear-devel] Heads up: scenery download / built-in terrasync
On Mon, Jun 13, 2011 at 8:50 PM, ThorstenB wrote: Hi, the final GUI bits for a new feature are now in fgdata - the last feature addition for the 2.4 release from my part... You can download/update scenery directly from FlightGear now (main menu: Environment = Scenery). Credit for the idea goes to James - bugs are mine ;-). Great work guys. I really, really, like this feature. From a completely new user perspective, this is almost perfect. The problem is that /sim/terrasync/scenery-dir isn't set by default, so a new user has to A) Set FG_SCENERY to something sensible, in the correct order B) Find some way to set up /sim/terrasync/scenery-dir C) Use the fine GUI we've just created. Of course, A and B can be well handled by launchers, but it would be fantastic if there was no dependency. I _think_ we default $FG_SCENERY to $FG_HOME/Scenery. Could we default it to $FG_HOME/TerraSync:$FG_HOME/Scenery, and then set /sim/terrasync/scenery-dir=$FG_HOME/TerraSync? (Note that this would mean scenery-dir supporting $FG_HOME) That way a completely new user without any launcher would be able to use this fine feature straight out of the box. It would also allow me to vastly simplify the instructions for downloading scenery in the manual. -Stuart -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim Functions for Propwash and Downwash [was: Clarification on YASim input]
On Tue, Jun 21, 2011 at 12:47 AM, Hal V. Engel wrote: I just added this to the P-51D this morning. I have this setup so that the propwash affects Roll_moment_due_to_rudder Cldr, Pitch_moment_due_to_flaps Cmflap, Delta_Lift_due_to_flaps dCLflap, Lift_due_to_Elevator_Deflection CLde, Pitch_moment_due_to_gear Cmgear, Pitch_moment_due_to_elevator Cmde and Pitch_moment_due_to_alpha_horiz_tail Cmht. It had a significant impact on low speed high power handling. The rudder has authority much earlier during take off and the tail lifts in a very natural way during the take off run. Over all these changes made take offs easier and more natural feeling. This also made it less likely to ground loop during the engine runup. This is an easy enhancement to do and it appears to improve ground handling and take off significantly. I have these changes checked in to my fgdata GIT clone if anyone wants to try them. I've had a quick flight with the updated FDM, and it certainly makes take-off a lot easier with pedals. I even managed to stay on the runway during the take-off roll, despite not having flown the aircraft for a couple of weeks. I'd suggest that this is a sufficiently small bug fix to be allowed in the upcoming release, as it makes such a difference to the flyability of what I assuming is going to be included as one of the default aircraft. BTW - I've actually sat in this particular P51D - Gunfighter. It was at a fly-in in Texas, and for a $5 donation you could sit in the aircraft and get your photo taken. Unfortunately I was there on business and didn't have a camera, so all I've got is a polaroid. -Stuart -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Heads up: scenery download / built-interrasync
With Yesterday in the command window I got Cannot start scenery download. No local cache directory defined. The new SVN system did not work Today, with the new GIT the Flightgear program crashes. Here is a stack trace: msvcr90.dll!_crt_debugger_hook(int _Reserved=0) Line 65C msvcr90.dll!_invoke_watson(const wchar_t * pszExpression=0x, const wchar_t * pszFunction=0x, const wchar_t * pszFile=0x, unsigned int nLine=0, unsigned int pReserved=0) Line 230 + 0x7 bytes C++ msvcr90.dll!_invalid_parameter_noinfo() Line 125 + 0xc bytes C++ msvcp90.dll!std::basic_stringchar,std::char_traitschar,std::allocatorchar::operator[](unsigned int _Off=4294967295) Line 1583C++ fgfs.exe!stripPath(std::basic_stringchar,std::char_traitschar,std::allocatorchar path=) Line 107 + 0x2e bytes C++ fgfs.exe!simgear::SGTerraSync::SvnThread::setLocalDir(std::basic_stringchar,std::char_traitschar,std::allocatorchar dir=) Line 147 + 0x4dbytesC++ fgfs.exe!simgear::SGTerraSync::reinit() Line 665 C++ fgfs.exe!simgear::SGTerraSync::init() Line 647 C++ fgfs.exe!SGSubsystemGroup::init() Line 152 + 0x46 bytesC++ fgfs.exe!SGSubsystemMgr::init() Line 458 + 0x1b bytes C++ fgfs.exe!fgInitSubsystems() Line 1518 C++ fgfs.exe!fgIdleFunction() Line 501 + 0x5 bytes C++ fgfs.exe!fgOSMainLoop() Line 285 C++ fgfs.exe!fgMainInit(int argc=1, char * * argv=0x02734d28) Line 663 + 0x5bytes C++ fgfs.exe!main(int argc=1, char * * argv=0x02734d28) Line 243 + 0xd bytesC++fgfs.exe!__tmainCRTStartup() Line 586 + 0x17 bytes C kernel32.dll!7688d0e9() [Frames below may be incorrect and/or missing, no symbols loaded forkernel32.dll] ntdll.dll!76e816c3() ntdll.dll!76e81696()fgfs.exe!fgOptTraceRead(const char * arg=0xffc88b04) Line 889 + 0xb7bytes C++ c48300bf()Unfortunately FG will not link in Debug mode so I can't go any further.I am using the new 3rd party stuff fromftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/MSVC/fgfs-win32-VS90-3rdParty+OSG-20110618.zipAlan -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear development entered state feature-freeze until July, 17th 2011
I am also interested in this and since nobody replied yet I am starting the discussion by bringing up my personal experiences: OpenAL-Soft/libopenal: AFAIK at least version 1.11.753 is needed to have all features (like doppler), though older versions may work as well. plib: Version 1.8.6. Why and how to obtain it can be found here [1]. Pretty old but still up to date, as far as I know. OpenSceneGraph: My personal experience, which includes some testing of different versions, is that 2.9.10 works best here. At later versions the osgText-bug is fixed which causes FG to have a bug. The oldest version I've tested was 2.8.3 with which I got random seg faults in FG quite often. The latest stable release 2.8.5 was *not* tested, this would be an option. I am using system: Linux 2.6.39.1 #2 SMP x86_64 GNU/Linux Debian Stable/Squeeze ATI Technologies Inc RS880 [Radeon HD 4200] Driver: fglrx, mostly latest version, 11.6 atm (11.1/11.2 during testing, IIRC) [1] http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg21059.html Alex Sun, 19 Jun 2011 20:50:25 +0200 Jari Häkkinen j...@flygarna.se: Torsten Dreyer skrev 2011-06-17 21.47: Anticipating the release 2.4.0, we reached our first milestone today. The development streams for flightgear, simgear and fgdata on gitorious are now declared frozen. The above states quite clearly that testing is expected to be against the source repositories for fg source/data and simgear. There are many other 3rd party software dependencies whereof the most prominent are plib and osg. Which version of these packages should be used for 2.4.0 testing? -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear development entered state feature-freeze until July, 17th 2011
Yes OSG 2.9.10 works best if you can compile it. But on Debian sid/unstable I'm unable to compile it with gcc/g++ 4.6. So I'm using 2.9.15 right now with some font size issues. 2011/6/21 Alex D-HUND f...@beggabaur.de I am also interested in this and since nobody replied yet I am starting the discussion by bringing up my personal experiences: OpenAL-Soft/libopenal: AFAIK at least version 1.11.753 is needed to have all features (like doppler), though older versions may work as well. plib: Version 1.8.6. Why and how to obtain it can be found here [1]. Pretty old but still up to date, as far as I know. OpenSceneGraph: My personal experience, which includes some testing of different versions, is that 2.9.10 works best here. At later versions the osgText-bug is fixed which causes FG to have a bug. The oldest version I've tested was 2.8.3 with which I got random seg faults in FG quite often. The latest stable release 2.8.5 was *not* tested, this would be an option. I am using system: Linux 2.6.39.1 #2 SMP x86_64 GNU/Linux Debian Stable/Squeeze ATI Technologies Inc RS880 [Radeon HD 4200] Driver: fglrx, mostly latest version, 11.6 atm (11.1/11.2 during testing, IIRC) [1] http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg21059.html Alex Sun, 19 Jun 2011 20:50:25 +0200 Jari Häkkinen j...@flygarna.se: Torsten Dreyer skrev 2011-06-17 21.47: Anticipating the release 2.4.0, we reached our first milestone today. The development streams for flightgear, simgear and fgdata on gitorious are now declared frozen. The above states quite clearly that testing is expected to be against the source repositories for fg source/data and simgear. There are many other 3rd party software dependencies whereof the most prominent are plib and osg. Which version of these packages should be used for 2.4.0 testing? -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FlightGear development entered state feature-freeze until July, 17th 2011
Am Tue, 21 Jun 2011 23:42:41 +0200 schrieb Alex D-HUND f...@beggabaur.de: Oops, wrong link for the plib version. Should be: [1]http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg20793.html I am also interested in this and since nobody replied yet I am starting the discussion by bringing up my personal experiences: OpenAL-Soft/libopenal: AFAIK at least version 1.11.753 is needed to have all features (like doppler), though older versions may work as well. plib: Version 1.8.6. Why and how to obtain it can be found here [1]. Pretty old but still up to date, as far as I know. OpenSceneGraph: My personal experience, which includes some testing of different versions, is that 2.9.10 works best here. At later versions the osgText-bug is fixed which causes FG to have a bug. The oldest version I've tested was 2.8.3 with which I got random seg faults in FG quite often. The latest stable release 2.8.5 was *not* tested, this would be an option. I am using system: Linux 2.6.39.1 #2 SMP x86_64 GNU/Linux Debian Stable/Squeeze ATI Technologies Inc RS880 [Radeon HD 4200] Driver: fglrx, mostly latest version, 11.6 atm (11.1/11.2 during testing, IIRC) [1] http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg21059.html Alex Sun, 19 Jun 2011 20:50:25 +0200 Jari Häkkinen j...@flygarna.se: Torsten Dreyer skrev 2011-06-17 21.47: Anticipating the release 2.4.0, we reached our first milestone today. The development streams for flightgear, simgear and fgdata on gitorious are now declared frozen. The above states quite clearly that testing is expected to be against the source repositories for fg source/data and simgear. There are many other 3rd party software dependencies whereof the most prominent are plib and osg. Which version of these packages should be used for 2.4.0 testing? -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Heads up: scenery download / built-in
On Tue, 21 Jun 2011 21:00:39 +0200, ThorstenB wrote in message 4e00ea57.7060...@gmail.com: On 21.06.2011 00:39, Vivian Meazza wrote: The bug which was stopping the built-in download running here was trivial - once we found it: a space in a directory name. Replaced with an underscore and it worked right out of the tin. The white-space issue is fixed for the new library now. It only applied to external svn. ...and to this message. ;o) Please add a wee bit of vertical white-space in between your inline responses to e.g. Vivian above here, to help improve the readability of your own message. -- ..med vennlig hilsen = with Kind Regards from Arnt Karlsen ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] P-51D and SCR-522C merge request
I have just put in merge request 106 to merge P-51D and SCR-522C updates. These inlcude the VHF radio functionality and the propwash changes to the FDM. Hal -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
