Re: [Flightgear-devel] Release 2.8.0 - closing release/2.8.0 branch
Do we have a volunteer (Thorsten?) to tag the branches as 2.8.0 to mark the official close of changes for 2.8.0(.0)? You might want to wait until you cut the release before laying down the tag... for 2.4.0 and 2.6.0, we set the tag version/2.x.0-final. I'll set the tag version/2.8.0-final on Thursday morning. Done. This marks our final state of the code for the 2.8.0 release. Please start building our distributables from this tag on the release/2.8.0 branch. Anything pushed to fg/sg/fgdata into the release/2.8.0 branch from how on will eventually go into a 2.8.0.x bugfix release. Thanks, Torsten -- 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
[Flightgear-devel] FlightGear 2.8.0 is out!
Hi, for the third time in a row, we were able to release a new version of FlightGear in time and following our Release Plan. After v2.4.0 exactly one year ago and v2.6.0 in February, FlightGear 2.8.0 has been released today! The Windows installers and the source and data tarballs are available through our website at flightgear.org and the mirrors are slowly catching the new version. The Mac version is still being worked on but we expect it to be ready soon. Thanks to everybody who has contributed to this new version, either by coding, bug reporting and fixing or other, probably invisible help. Please spread the word about our new product! Torsten -- 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
Re: [Flightgear-devel] FW: Compute ground elevation dynamically for STG format
Computing constant values at runtime is bad design and we should not do that. No matter if we notice a significant increase in load time now or not. The ground elevation at a specific point is well known at scenery generation time and that is where the vertical position of an object has to be computed. Not in the main loop at the moment of scenery loading where computing time is precious. I can think of one scenario where the information offset from ground aka AGL is necessary. This is when the scenery gets recreated and the ground elevation changes. In that case, objects may float above or sink into the ground with a fixed altitude. IMHO, our scenery database needs to know about that offset to create the correct altitude for an object in the scenery. I would not want to see _any_ object in the scenery with a position specified by AGL. If that feature helps scenery developers to _temporary_ place objects, may I suggest that this code is enclosed in #ifdef's and only enabled during compile time with a special CMAKE switch and never enabled for a release? Torsten -- 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
Re: [Flightgear-devel] Gear transit times
Am 30.08.2012 03:51, schrieb castle...@comcast.net: Hi, Is it possible to specify gear up and down transit times for each gear? In real airplanes the gear never ( well rarely, maybe ) sequence in perfect unison. In reviewing the xml files for the 737, I note there are transit times defined for each flap position, but the kinematics for the gear is only a single value for up or down based on gear selection state. Is this something in Nasal? or native code or something in JSBsim? I use the actuator in JSBsim to model the gear in the SenecaII, using the rate_limit property implement the transit time. The flightgear autopilot system has a so called noise-spike filter that can model transit times. The flightgear xml based autopilot system can run at FDM rate or at frame rate, btw. Using a autopilot tag in your aircraft's -set.xml adds the autopilot at fdm rate, using a property-rule runs the same config at frame rate. Torsten -- 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
Re: [Flightgear-devel] license
Looks like the dialog is GPL and the screenshot image is CC. Torsten-- 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
Re: [Flightgear-devel] fgdata trouble
Hi all, there is a WIKI page for this topic: http://wiki.flightgear.org/FlightGear_Git:_splitting_fgdata Many points have been discussed over and over some time ago. If there is something new that has developed over time, please add it to the wiki page before it gets lost on the mailing list. Torsten -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] FSWeekend 2012...
Am 06.11.2012 22:16, schrieb Durk Talsma: Yes, I also talked to Martin Crompton. James told me later on that you had been in touch with him. My action was rather spontaneous, so I asked him whether we could try to support Saitek products, without me knowing that you were also working on it. I hope we can join forces. I got their radiostack to try, and this looks like it's going to be a little more involved, since it may need its own USB driver. I'll try to send Martin just a quick note later tonight. You might want to check out the event input system, I have implemented some time ago. It's much more flexible than our joystick input system as it handles more events (relative axies e.g.) and is able to send events _to_ the device, too (switching LED's e.g.). Tat implemented this for the OSX, so it should be working there, too. The Windows implementation is still missing, unfortunately. Also, Melchior implemented raw HID communication using Nasal for the Thrustmaster Warthog, but limited to Linux use. If the Saitek devices don't use HID at all, things will become _very_ tricky and probably impossible to get them running cross platform. Torsten -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 3d clouds on multi-display systems (was Re: FSWeekend 2012...)
Am 08.11.2012 23:24, schrieb Stuart Buchanan: I'm confused. From my reading of Durk's post, 3D clouds would appear to work fine for a multi-display system out-of-the-box, but your comment here indicates that there is an issue that requires fixing by restricting the random seed. Hi Stuart, just one more note about multi-displays on a single machine: With our four cards driving eight displays at 1600x1200, the 3d clouds appear seamless across the individual displays and they work fine when clouds are scattered or few and you stay well clear of the clouds. When a cloud starts occupying a big part of one or more screens, there is a massive drop in frame rate, down to unusability. The same hardware runs smooth with 60fps (synced to vblank) in any situation with just a single display. Torsten -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Next FlightGear release (Feb. 17 2013)
Hi, in just about one month from now we are entering another round of the release process, starting with the four weeks feature freeze period. This is probably a good time to check in all the great and fancy new features that still hide in your local branches. I'd also like to see JSBSim synced before December, 17th. How should we call our new baby? Is it 3.0.0 or is it 2.10.0? This is a carry-over from our last release and gets answered along with: Is Rembrandt production ready? I'd also like to use the remaining four weeks to walk through the Lessons Learned section of our Release Plan (http://wiki.flightgear.org/index.php/Release_Plan#Lessons_learned) Somebody was kind enough to add a few points worth thinking about: 1. A lack of stress testing. We have a four weeks testing period with release binaries publically available, so I am not sure how to improve that. Do we need more testers? Do we need more time? 2. Lack of graceful feature scaling. Is this really something we can solve in the release process? 3. Change of the NOAA METAR url Also, this is more a bug or feature request than an issue with the release process 4. broken OSX downloads Yes - we need to improve the OSX builds. Does Jenkins provide stable binaries or do we still need a manual build provided by James or Tat? 5. Irritation caused by code signing Probably same as 4.? 6. GLSL errors Probably just a special case of 1. 7. Missing files in the Windows build Probably just a special case of 1. 8. Write the changelog ASAP Yes - That can easily start right now. As it is just a simple wiki page, please contribute to http://wiki.flightgear.org/Changelog_3.0.0 9. Lifting the code freeze for certain new features. As a clarification: We do not enter a code freeze but a feature freeze. Code changes are welcome after December 17th as long as it is guaranteed (not just unlikely) that they do not introduce any side effects and become a release blocker. It is the sole responsibility of the commiter to decide if that is the case or not. Every new feature that didn't make it into the respository by the deadline may probably easily wait for another four weeks to get commited. Remember: most aircraft are not affected by the feature freeze and aircraft developers quickly adopt and use new features as they become available. 10. Updating the wiki w.r.t. hardware recommendations Yes - this is a task for everybody. Last, but not least: Will we be able to create release binaries for our three major platforms automatically and probably release candidates for them on a regular schedule (e.g. once a week) from the same code base using the same pre-release version number? Thanks for reading that awfully long post ;-) Torsten -- Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Next FlightGear release (Feb. 17 2013)
All in all, for my part it seems rather a 2.10 than a 3.0 - some of the things which I'd like to see in 3.0 are done, but the majority isn't yet. This is probably true. To get to the 3.0 goal sometime in the near future, it's probably a good idea to create a backlog of open items in the wiki and link the release plan document to that. As usual, we don't have to be perfect for a new major release number. But the new features being the reason for the new major number should work reasonably correct. I can't tell if that's the case for Rembrandt as I didn't have the time for any tests over the last 12 month or so. I'll leave this discussion open until the feature freeze on Dec., 17th to come to a decision by that date. Another decision to make is the set of aircraft to be packed into the base package. My sugestion is to keep the current set if this is going to be a 2.10 release and to reduce to just the c172 if we roll out 3.0. Greetings, Torsten -- Keep yourself connected to Go Parallel: DESIGN Expert tips on starting your parallel project right. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Real-Time Radio Propagation, Was: Sqlite location
Hi, let me chime in here with a personal note, hoping it's not offending anybody. Although I like having accurate and detailed computation of our real-world simulation, I'm not really a friend of the radio propagation code with the level of detail given. Please let me explain why that is the case: The radio stations used for aviation purpose certainly follow the same physical laws as any other radio station does. However, their performance have to adhere to some specific rules, mostly set up by the ICAO. Service volumes is on of these rules, a straight ILS final track is another etc. If real life's environment disturbes the performance of the radio stations, the operator has to work hard to override these environmental impacts. As we usually do not have any detailed information about how the radio station is set up (and I doubt, we will ever get those), it's close to impossible to correctly model radio probagation of a specific station. Adding envirionmental factors besides terrain and terrain cover and the factors of aircraft installations will result in a wide range of uncertainty, spoiling all the detailed computation of the radio signal propagation. As a pilot, I am usually just interested in the factor, if I am within the service volume of a radio station. If so, I'd expect a clear and correct indication, probably with the well-known system errors applied. If I am outside the service volume, the systems may show something, but I do not really care about what exactly an ILS indicator (as an example) is showing. From real life experience, I can say that barely two stations behave the same if you are outside their published range. Sidelobes of a localizer may appear at on site and may not at another site. False glideslopes appear here but do not show up somewhere else. It depends heavily on the local setup of the base equipment (and to some degree on aircraft installations). However, I have seen the shoreline effect of ADF stations deflection my ADF needle heavily and I have seen effects of nearby thunderstorms and lightning on the instruments. I'd love to see these effects modeled. That said, I think doing realtime radio signal propagations is much more that we need and much more than we want. At least unless we are multi-threading and have a spare CPU for those computations. This is certainly just my personal point of view. Greetings, Torsten -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim Piston Engine Idle
I'd be grateful for an update of the Dragonfly and the ogeL. The Dragonfly's configuration was a wild guess, and only very vaguely based on real numbers. ogeL's engine is by definition just fantasy ;-) Thanks, Torsten Am 08.12.2012 20:12, schrieb Ron Jensen: I took a quick look through the FGData Aircraft directory today and came up with a list of some 27 JSBSim piston engines that still seem to be using either the old aeromatic default values for idle manifold pressure (minmp) or suspiciously low values. As time permits this week I intend to take a deeper look at this list and adjust the minmp value as seems appropriate, if there are no objections. I know a couple of engines have different versions in other repositories (JSBSim or personal hangers) that are updated and just need to be copied into FGData. Ron Probably won't idle: Aerocar/Engines/Lycoming_O-290.xml: minmp unit=INHG 6.0 /minmp an2/Engine/ASH-62IR.xml: minmp unit=INHG 5.0 /minmp Boeing314/Engines/WrightGR-2600.xml: minmp unit=INHG 6.0 /minmp c150/Engines/eng_O-200.xml: minmp unit=INHG 6.0 /minmp c172r/Engines/engIO360C.xml: minmp unit=INHG 6.5 /minmp c182/Engines/engIO540AB1A5.xml: minmp unit=INHG 6.5 /minmp c182rg/Engines/engIO540AB1A5.xml:minmp unit=INHG 6.5 /minmp c310/Engines/engIO470D.xml: minmp unit=INHG 6.5 /minmp c310u3a/Engines/engIO470D.xml: minmp unit=INHG 6.5 /minmp dc2/Engines/R-1820-R52.xml: minmp unit=INHG 6.0 /minmp dc6/Engines/CB17.xml:minmp unit=INHG 6.0 /minmp dc6/Engines/eng_R-2800.xml: minmp unit=INHG 6.5 /minmp Dragonfly/Engines/Rotax582.xml: minmp unit=INHG 2.1 /minmp Dromader/Engine/engine_Asz-62IRM18.xml: minmp unit=INHG 5.0 /minmp fkdr1/Engines/Oberursel-UrII.xml:minmp unit=INHG 6.0 /minmp flash2a/Engines/503.xml: minmp unit=INHG 2.0 /minmp Lockheed1049/Engines/WrightCyclone-975C18CB1.xml: minmp unit=INHG 6.0 /minmp Lockheed1049h/Engines/WrightCyclone-972TC18DA3.xml: minmp unit=INHG 6.0 /minmp Lockheed1049h/Engines/WrightCyclone-975C18CB1.xml: minmp unit=INHG 6.0 /minmp Noratlas/Engines/Bristol-739.xml: minmp unit=INHG6.0 /minmp ogel/Engines/200hp-jsbsim-2.0.xml: minmp unit=INHG6.0 /minmp P-38-Lightning/Engines/Allison.xml: minmp unit=INHG6.0 /minmp p51d/Engines/Packard-V-1650-7.xml: minmp unit=INHG4.0 /minmp PBY-Catalina/Engines/PBY-6_engine-new.xml: minmp unit=INHG 6.0 /minmp Skyranger/Engines/rotax.xml:minmp unit=INHG6.0 /minmp Storch/Engines/Argus_As_10.xml: minmp unit=INHG6.0 /minmp Maybe: G-164/Engines/R-1340-AN1.xml:minmp unit=INHG 7.0 /minmp Good: A6M2/Engines/Sakae-Type12.xml: minmp unit=INHG 10.5 /minmp b29/Engines/eng_R3350.xml: minmp unit=INHG 12.0 /minmp c172p/Engines/eng_io320.xml: minmp unit=INHG 8.3 /minmp C684/Engines/6Pfi.xml: !--minmp unit=INHG 6.0 /minmp-- Cap10B/Engine/LycomingIO360B2F.xml: minmp unit=INHG 12.0 /minmp Cessna337/Engines/engine_IO360C.xml: minmp unit=INHG 15.0 /minmp ercoupe/Engines/c-75-12.xml: minmp unit=INHG 10.0 /minmp Nordstern/Engines/eng_Maybach_Mb_IVa.xml:minmp unit=INHG 9.0 /minmp SenecaII/Engines/tsio360eb.xml: minmp unit=INHG 10.0 /minmp Short_Empire/Engines/eng_PegasusXc.xml: minmp unit=INHG 10.0 /minmp Submarine_Scout/Engines/eng_RRhawk.xml: minmp unit=INHG 10.0 /minmp ZivkoEdge/Engines/io540.xml:minmp unit=INHG 10.0/minmp ZLT-NT/Engines/engIO360C.xml: minmp unit=INHG 10.0 /minmp -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Which navradio code is considered standard?
Am 22.11.2012 20:44, schrieb ThorstenB: On 22.11.2012 10:08, Adrian Musceac wrote: I've gone ahead and used the new radio code for navaids, but I have a question: which navradio code is considered standard? newnavradio or navradio? navradio is the current/old standard, newnavradio is the new module. Most aircraft use navradio, few newnavradio. I'm not sure if there is a plan to switch/replace the old radio at some point, and whether the new module was compatible with the old etc. But for now, both are there. TorstenD is the expert here. The plan was to replace navradio by newnavradio. Due to an unhandled exception in my real-life's main loop, I have never been able to finish the transition and I will most likely not be able to soon. So please consider navradio as standard. Please, don't add too much code to the old navradio.?xx files but try to encapsulate new functionality within own classes and files and make them as reusable as possible. Torsten -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Real-Time Radio Propagation
Hi replying to multiple posts here, I'll try to collect and answer to some arguments. First: I totally agree that our current nav/comm radio implementation is far from being realistic w.r.t. propagation of the radio signal close to or on the ground. This should be improved. I spent an hour or two reviewing your code and I still think your implementation should not be merged into the code base. Let me explain why. - Realism Your algorithm takes into account many factors responsible for radio probagation. Most of those factors are unknown in our data set and we have to use assumptions for their values. The less data we have and the more assumptions we have to use, the more unrealistic the algorithm's result become. My definition for realism is: Does the simulator compute the same value as I would expect in the same situation in real life? I strongly doubt the algorithm together with our limited set of data can provide this. In some cases, the used algorithm is plain wrong as we know by definition (ICAO rules) the propagation of the radio signal. - Performance The most important limiting factor for radio propagation on VHF and up is question line of sight or obscured by terrain. Your approach is to perform terrain samples along the line between the sender and receiver which is expensive. My idea for the newnavradio was to traverse the scenegraph along the straight line between sender and receiver and probe for ground intersection. This is basically the functionality as the probe for ground elevation, which could be reused. The difference of performance impact is dozens or even hundrets of scenegraph traversals compared to just one. - Landcover Landcover contributes only neglible compared to terrain obscucarion to the loss of signal strength. - Coding style * You copied parts of the terrain sampler from advanced weather. Better reuse existing code, probably modify so it suits both usecases. * Using long chains of if/else or switch/case makes code hard to read and is usually a good indication for a flaw in the software design. * I prefer named constants instead of numbers to imporve readability. Summary You obviously spent a lot of time implementing the itm algorithm as a subsystem and I feel sorry if it is discouraging for you or other potential contributers that I (and I am just speaking for myself) do not support this contribution. My apologies for not speaking up earlier. This implementation only adds a pseudo-realistic radio propagation simulation due to lack of real data at the cost of cpu intensive calculations and a complex new subsystem that has to be maintained over the time. The same pseude-realism could be achived by implementing an approximation for signal attenuation for line of sight and obscured propagation paths (probably as simple as distance-squared and distance-to-the-power-of-something). Neither your implementation nor my suggestion provides a realistic prediction of the radio signal quality, both are more or less approximations. It's the gain/pain ratio that differs significantly. Please forgive my my clear words - it's not my intention to offend anybody. Regards, Torsten Oh - one last thing: Committing code just because somebody spent much time writing it or not committing would be discouraging should never be a reason to do so. -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Real-Time Radio Propagation
Hi Adrian, you are doing an excellent job at marketing your product ;-) As I do not have the time to proof you wrong, you deserve the chance to proof me wrong! I'll shut up now and stop objecting against merging your code. I won't be able to merge it myself before we enter the feature freeze but probably someone with commit rights takes care of it. I hope I find some time to test the LOWI approach which had the chance to do in RL recently... (http://data.x-plane.com/Docs/LOWI.pdf) Thanks, Torsten -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Real-Time Radio Propagation
Am 13.12.2012 16:28, schrieb geneb: Um, no he's not. He just happens to be a contributor like the rest of us. :) There is no herder for the Free Range Cats that make up the FlightGear project. :) How disappointing ;-) Frankly, I think your addition to FlightGear is fantastic and a needed feature for the non-entertainment side of the house. If the gamers don't like the small frame rate hit, they can just turn it off. But being called a gamer, _that_ is discouraging! Greetings Torsten -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Performance
Hi everybody, I just had the chance to compile a recent git-pull on my old and battered linux-notebook workhorse and with great delight, I noticed that I can run FlightGear again with 26fps at KSFO. I had to strip down most eye candy shaders for the GeForce Go 7400 but 3D clouds render fine without a noticable drop in framerate, even if a cloud spawns the entire screen. That was much worse a few month ago when FlightGear barely ran on that old hardware. Whoever was involved in that magic - well done! Thanks for still supporting older and weaker hardware. Torsten -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Release Progress: Feature Freeze is active
Hi, just a short reminder: The feature freeze for the next release is active. For those who are not familiar with our release plan (http://wiki.flightgear.org/Release_Plan): No new features or major changes shall be pushed onto the development streams (neither source nor data). This period is for preparing the code for the release and make sure there are no major issues. It lasts for four weeks until creation of the release branches. It's a good idea for aircraft developers to adhere to this rule. However, aircraft in fgdata may be handled as an exception from the frozen state. Any change to aircraft may be pushed to the repository if it is guaranteed that this change does not affect any other aircraft or system and if no file outside the root directory of that specific aircraft is changed. Also, aircraft defined as part of the base package (e.g. the c172p) enter the frozen state and shall not undergo major changes in that period. This is a very special feature freeze, as we only have a few days left before everything changes on earth (http://en.wikipedia.org/wiki/2012_phenomenon). Please make sure we get all our bugs fixed by that date to have a clean start into the new aera. If for any reason there is no apocalypse on Friday, regular development will start again on January, 17th 2013. Greetings, Torsten -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Next FlightGear release (Feb. 17 2013): Version 2.10
I have just pushed the new version number 2.10 to simgear, flightgear and fgdata along with the tag version/2.10.0 for all three repos. Make sure you pull all three repositories to avoid a version conflict. After the creation of the release branches on Jan., 17th the version numbers will again increase to 2.11.0 on next/master. I did not touch the other projects at https://gitorious.org/fg/ There is probably a version number in getstart that has to be adjusted (Stuart?) I don't know, if fgmeta et.al. need some adjustment? Torsten -- LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] JSBSim Synch with FlightGear
Hi JSBSim and FlightGear lists, should we sync the latest JSBSim code into FlightGear for the next release, scheduled for February this year? If so, please do this very soon so there is some time to rule out any oddities before I create the release branches on January, 17th. Thanks, Torsten -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_123012 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim Synch with FlightGear
Am 13.01.2013 20:33, schrieb Stuart Buchanan: On Sun, Jan 6, 2013 at 11:35 AM, Torsten Dreye wrote: Hi JSBSim and FlightGear lists, should we sync the latest JSBSim code into FlightGear for the next release, scheduled for February this year? My vote is not to sync at this point. I'd consider a JSBSim sync to be similar to feature development, particularly given the possible impact on a large portion of the FG fleet. Perhaps if it was only a day or so after the feature freeze we might be flexible, but 4 days before the release branch is cut is too late IMO. Agreed. Unless there is no major bug fixed, we should merge soon after the branch day and just before the next feature freeze. I have just added this to the lessons learned of our release plan. Thanks, Torsten -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_123012 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim Synch with FlightGear
I had hoped that we could do this a couple of months ago, but not synching JSBSim with the latest FlightGear would be very, very unfortunate. I'm not sure when the last sync occurred (does anyone know?), but there have been a lot of new features and bug fixes. Development has been very active. FlightGear will be very much behind the curve relative to the current JSBSim state if we don't synch. I've been driving FlightGear as an external visuals application from JSBSim lately, but I'd prefer to run sims fully integrated. I've got another reason for it to be integrated, but I need to discuss that with Curt offline, first. Yes, i had hoped, too. However, as you mentioned, many new features have been developed and that violates our feature freeze rule, unfortunately. That rule has been introduced for exactly this situation: not to raise some last minute issues (to avoid bugs here). Sorry - but as we improve our plan with every release, this most likely will not happen again ;-) Torsten -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_123012 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] JSBSim Synch with FlightGear
Am 14.01.2013 03:57, schrieb Jon S. Berndt: Outerra will be more up to date than FlightGear with respect to JSBSim. It's hard to be the best all the times ;-) Torsten -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Heads up: release branch creation startet NOW
Hi all, today is the 17th of January and I am going to create the release branches now . Please stay clear of the active runway and don't push anything to FlightGear, SimGear and FGDATA on gitorious. I'll post a message when I'm done. Those, who are involved in the creation of release candidates on our supported platforms may start their wake-up procedure ;-) Thanks, Torsten -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Heads up: release branches are ready,
Am 17.01.2013 19:03, schrieb Torsten Dreyer: I'll post a message when I'm done. Done. Version 2.10.0 now lives on the release/2.10.0 branches on SimGear, FlightGear and FGDATA to be released around the 17th of February. SimGear and FlightGear next branches as well as FGDATA master branch are now on version 2.11.0. These branches are again open for regular development. Thank you all for adhering to our feature freeze policy. Curt, James, ThorstenB and Tat: Please create our first release candidate as soon as possible to give many users without source code compile expertise the chance to test our new version. Greetings, Torsten -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_122712 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Sync with JSBSim
Hi, I have just synced the latest and greatest JSBSim into FlightGear. I flew a quick pattern with the SenecaII (the only JSBSim aircraft, I have a rating for) and found no quirks. Please check, if everything is still working in more complex aircraft. Greetings, Torsten -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122912 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Ati viewport bug
Any chance to wrap this into something like
if( true == getprop(/sim/use-ati-hack) ) {
addTheEmptyPrerenderCamera();
} else {
doNothing();
}
Am 28.01.2013 18:56, schrieb James Turner:
http://code.google.com/p/flightgear-bugs/issues/detail?id=385
Is about a problem with the viewport behaving very oddly, in certain Ati
catalyst drivers.
A kind person has worked out a hack, which fixes the issue, or at least
avoids it. It add an empty, pre-render camera to the scene, which I assume
forces some state which otherwise gets skipped in the Ati drivers.
If anyone has any strong opinions about applying the hack to the 2.10 release
branch, let me know. I'm currently undecided - it *is* a hack, but it fixes a
real and long-standing bug, and the cost to everyone else should be zero.
Regards,
James
--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. ON SALE this month only -- learn more at:
http://p.sf.net/sfu/learnnow-d2d
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Updated Short Reference for 2.10.0
Done. Am 29.01.2013 22:55, schrieb Stuart Buchanan: Hi All, I've just pushed a small commit checking in new versions of the FG Short Reference, something I should have done with the updated Manual a while back. If someone could cherry-pick the commit into the release branch, that would be great. The commit is: 68ad1905c83e87171f14d63099dc546fbcfc27df Thanks, -Stuart -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release candidates
Didn't he say GiB? And CDs are an ancient technology... Thanks for building the RC. We need to get this automated some day. Or at least documented... (another one from famous last words: if you have to do it more than once, automate it. If you can't automate it, document it.) Torsten Am 29.01.2013 23:14, schrieb Curtis Olson: It does run on my Win 7 laptop with nvidia graphics hardware (and nvidia graphics drivers installed.) I will get it uploading ... 740Mb! So much for the CD distribution. :-) Didn't Bill Gates famously say 640Mb should be enough for anyone? Curt. On Tue, Jan 29, 2013 at 3:33 PM, Curtis Olson curtol...@flightgear.org mailto:curtol...@flightgear.org wrote: ... and it looks like the windows version crashes immediately when it tries to bring up the splash screen (based on --log-level=debug). This is on my windows XP test machine that ran v2.8 ok. Hmmm... fgfs.exe has encountered a problem and needs to close, we are sorry for the inconvenience. Console log (at debug log level) says... Initializing splash screen found path: blah blah splash.png Splash screen progress init Microsoft Corporation GDI Generic 1.1.0 A window is opened, but it's just the outline, nothing is drawn in it before the error/crash happens. Any ideas? Curt. On Tue, Jan 29, 2013 at 3:25 PM, Curtis Olson curtol...@flightgear.org mailto:curtol...@flightgear.org wrote: I've been working on the first windows release candidate this week. It's been going fairly well, but there are the usual packaging things to work through (and/or remember.) Curt. On Tue, Jan 29, 2013 at 2:54 PM, Gijs de Rooy wrote: Hi all, with just two more weeks to go till the release, we'd better get our release candidates published. Mac is available on Jenkins, but I couldn't find anything for Windows or other OS yet... I've opened the usual subforum on the forum today, so we can collect all reports in a single place. http://www.flightgear.org/forums/viewforum.php?f=68 Cheers, Gijs -- Master Visual Studio, SharePoint, SQL, ASP.NET http://ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net mailto:Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com http://www.atiak.com/ - http://aem.umn.edu/~uav/ http://www.flightgear.org http://www.flightgear.org/ - http://gallinazo.flightgear.org http://gallinazo.flightgear.org/ -- Curtis Olson: http://www.atiak.com http://www.atiak.com/ - http://aem.umn.edu/~uav/ http://www.flightgear.org http://www.flightgear.org/ - http://gallinazo.flightgear.org http://gallinazo.flightgear.org/ -- Curtis Olson: http://www.atiak.com http://www.atiak.com/ - http://aem.umn.edu/~uav/ http://www.flightgear.org http://www.flightgear.org/ - http://gallinazo.flightgear.org http://gallinazo.flightgear.org/ -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Final release checklist
Hi all unless we don't have any major release blockers, we are going to release version 2.10 during the next weekend. So, if there is anything still overlooked, please shout out now. Do we have the latest getstart.pdf compiled and picked into the release branch? Anything else to think about? Thanks, Torsten -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Release 2.10.0: Decision Altitude
Hi all, at one point during every ILS approach you reach the decision altitude with two options: continue approach or go around. Being the copilot on our approach into the 2.10 release, I'd call out minimum, approach lights in sight, continue! If no one shouts out loudly _NOW_, I'm going to tag the release branches tomorrow (Saturday) morning (Central European Time) and give the package managers the GO to build and distribute the bundles. That should give us a ready-to-download release just in time on Sunday the 17th. Greetings, Torsten -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: final tags for 2.10.0
Am 15.02.2013 16:16, schrieb Torsten Dreyer: If no one shouts out loudly _NOW_, I'm going to tag the release branches tomorrow (Saturday) morning (Central European Time) and give the package managers the GO to build and distribute the bundles. That should give us a ready-to-download release just in time on Sunday the 17th. Done. The tag version/2.10.0-final exists on fgdata, simgear and flightgear. Please start creating the tarballs, installers, binaries et.al. for the final FlightGear 2.10 release from that tag. FWIW, I have also merged the release/2.10.0 branch into the master branch on simgear and flightgear. Both had conflicts on a few files. I resolved these conflicts by checking out the files of the release branch (git checkout --theirs while sitting on master) and committing those versions. This has been documented in the merge commit. There is still one open item: To push the final pdf and html documentation to the mapserver site. I do not have write access, so may please somebody who knows how to do that and is able to do so take care of it? Torsten -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: Decision Altitude
Hy Yves Sorry, I do not understand your question. Could you clarify, please? Torsten Am 16.02.2013 00:17, schrieb ys: Hi Torsten What does mean no public answer in this list for this decision ? -Yves Am 15.02.2013 um 16:16 schrieb Torsten Dreyer tors...@t3r.de: Hi all, at one point during every ILS approach you reach the decision altitude with two options: continue approach or go around. Being the copilot on our approach into the 2.10 release, I'd call out minimum, approach lights in sight, continue! If no one shouts out loudly _NOW_, I'm going to tag the release branches tomorrow (Saturday) morning (Central European Time) and give the package managers the GO to build and distribute the bundles. That should give us a ready-to-download release just in time on Sunday the 17th. Greetings, Torsten -- Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Release 2.10.0: final tags for 2.10.0
To my knowledge, this is a fully automated task, which is croned at each update. So for the online stuff everything seems to be fine. The only thing I do not know is who is taking care to update the getstart.pdf files pushed into the installers and tarballs for the release. Ah, good news. I just love automated tasks ;-) Stuart took care of the getstart.pdf for this release, so I assume we are all set w.r.t. documentation this time. Thanks Torsten -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Low visibility issues
Am 28.02.2013 16:38, schrieb Curtis Olson: We've always been able to set the individual weather parameters, either through the built in weather dialog box, or by setting raw property values. Setting raw property values allows nasal script control over the weather (as I'm sure you well know) :-) but it also allows external control of the weather, for instance by some external gui tool, or by some tool that wants to setup equivalent visual conditions across multiple FlightGear PC's running in sync. And please don't forget, there are command line options like --visibility, --wind, --random-wind etc. All those options override the other weather-magic. It took me quite some time to make all this behave in a somewhat reasonable way with basic-weather and I'd love to keep all that functionality. Best, Torsten -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] reminder: entering feature freeze now
Hi everybody, for most of us, it's June, 17th which marks the day for the feature freeze period, lasting until July, 17th. Everybody is invited to walk through the lessons learned section of our release plan at http://wiki.flightgear.org/Release_plan the bugtracker at http://code.google.com/p/flightgear-bugs/ and contribute to the changelog for the next release at http://wiki.flightgear.org/Next_Changelog As of today, the set of new features should be complete. The usual question at this point is: What version number will we give to the new release? Are we ready for a 3.0 or is it 2.12? Regards, Torsten -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] reminder: entering feature freeze now
snip I apologize for missing the point. No need to apoligize at all. If anybody is annoying somebody, it's me with my scheduled emails about release deadlines, my requests for following a specific release procedure and for raising discussions about version numbers. Some time ago, we agreed on setting the version number for the next release after the feature freeze deadline and well before the branch date. That idea was brought up by ThorstenB and it's documented in the release plan, IIRC. Collecting the arguments from this discusson, I can see good points for a 3.0.0 release. Most convincing was Stuarts comparison against 2.0.0 and the progress we made since that version. My suggestion is, we dare to call the 2013 summer edition FlightGear 3.0.0 and we bump the version number later this week. I'll leave that discussion open for a few days and hope we can agree on the new number. Torsten -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] SimGear build fails
Hi, I'm failing to build SimGear on 64bit linux: EffectGeode.cxx:83:136: error: no matching function for call to ‘osg::Geometry::setVertexAttribArray(int, osg::Geometry::ArrayData)’ OSG is stable 3.0.1 from svn (same with OSG trunk) SimGear is git next from today Yes, I rm-rf'ed previous artefacts and started from scratch. Thanks, Torsten -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] SimGear build fails
Am 27.06.2013 09:58, schrieb James Turner: On 26 Jun 2013, at 23:05, Thomas Geymayer tom...@gmail.com mailto:tom...@gmail.com wrote: Thank you Alex! I've just commited your patch. Yes thank indeed Alex, it's a relief to know someone is keeping bleeding-edge OSG working, since the rate of change over there seems to be increasing (for the better) Thank you, guys! Torsten -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] reminder: entering feature freeze now
Am 26.06.2013 09:58, schrieb James Turner: Yep, works for me too. James Thanks, Stuart for finding a solution. I have just pushed the version number 2.12.0 to SG, FG and FGDATA. Torsten -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot filters
Post a diff or the modified files or a link to a tarball here and I'll have a look. Probably a good start for me to get back into the loop after almost two years of absence... Torsten Am 26.07.2013 21:11, schrieb Alan Teeder: I have added a washout/high-pass filter and an integrator to the XML autopilot. Also I have added aliases to the exponential filter so that it may be also called low-pass or lag and an alias to the noise-spike filter so that it can also be called rate-limit. README.digitalfilters is updated to match, as well as incorporating the undocumented derivative filter and mentioning the use of expressions. How should I submit these for review? Please don´t ask me to use git, as I am very good at screwing my own repos up and would not like to do the same to fgdata. Alan -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Autopilot filters
Hi Alan, thank you for your patch. I have a few, probably dumb questions: * Isn't the your new integrator filter the same as a pi-simple-controller with Kp=1 and no min/max clamping? * What would you think about extending the exponential filter to make it behave like a high-pass or low-pass like typelow-pass/type or typehigh-pass/type. That would not double existing code. * What is the purpose for adding alias names for existing filters? Cheers, Torsten Am 27.07.2013 10:27, schrieb Alan Teeder: *From:* Torsten Dreyer mailto:tors...@t3r.de *Sent:* Saturday, July 27, 2013 8:47 AM *To:* flightgear-devel@lists.sourceforge.net mailto:flightgear-devel@lists.sourceforge.net *Subject:* Re: [Flightgear-devel] Autopilot filters Post a diff or the modified files or a link to a tarball here and I'll have a look. Probably a good start for me to get back into the loop after almost two years of absence... Torsten Thanks Torsten. The files are zipped at http://v-twin.dynip.sapo.pt/alan/FG/digitalfilter.zip. (10kb) At some time I will need to add a means of initialising the Integral filter to a property. Alan -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] (no subject)
Hi Tomash the navradio code is far from being perfect and and least to attempts for improvements exist. Unfortunately, both have currently stalled due to several reasons. The first is in newnavradio which you can use by setting use-new-navradio type=boolfalse/use-new-navradio in your aircraft xml as does the SenecaII. Note: this is still an experimental feature and some instruments/aircraft might not be compatible with that implementation. I'll continue to work on this, once I find more time for fg hacking. The second is a very detailed radio signal propagation model that has not made its way into the repositories. I don't know what the state of this is. I hope this helps - Cheers Torsten Am 04.08.2013 19:20, schrieb Tomash Brechko: Hello! In file src/Instrumentation/navradio.cxx method FGNavRadio::adjustILSRange the code that narrows ILS-LOC beam is commented out since the end of 2004. Are there any reasons not to have directed localizer beams? Being able to tune to localizer just from anywhere is a bit unnatural. -- Tomash Brechko -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] (no subject)
Hi Michail, the navradio code uses the magnetic variation as stored in nav.dat for the VOR. The environmental magnetic variation is not used for the VOR. The installed offset between magnetic and true north of the signal emitted by the VOR is published in the local AIP, so yes: we have to adjust nav.dat from time to time. HTH, Torsten Am 05.08.2013 10:38, schrieb ?? : Let me ask my question here. In nav.dat file VORs have slave variation. As I understand, slave variation of VOR depends on magnetic variation at he location. Does Flightgear use this slave variation, or it computes magnetic variation on the fly? Do we need to track magnetic variation change every year and manually edit nav.dat for it? 2013/8/5 Torsten Dreyer tors...@t3r.de mailto:tors...@t3r.de Hi Tomash the navradio code is far from being perfect and and least to attempts for improvements exist. Unfortunately, both have currently stalled due to several reasons. The first is in newnavradio which you can use by setting use-new-navradio type=boolfalse/use-new-navradio in your aircraft xml as does the SenecaII. Note: this is still an experimental feature and some instruments/aircraft might not be compatible with that implementation. I'll continue to work on this, once I find more time for fg hacking. The second is a very detailed radio signal propagation model that has not made its way into the repositories. I don't know what the state of this is. I hope this helps - Cheers Torsten Am 04.08.2013 19:20, schrieb Tomash Brechko: Hello! In file src/Instrumentation/navradio.cxx method FGNavRadio::adjustILSRange the code that narrows ILS-LOC beam is commented out since the end of 2004. Are there any reasons not to have directed localizer beams? Being able to tune to localizer just from anywhere is a bit unnatural. -- Tomash Brechko -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net mailto:Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net mailto:Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] 2.12 is branched
Permission granted ;-) As everybody seems to be caught in some real life trouble, I can't see a better way to get the release out than delaying it for a while. Would two weeks be enough for everybody? That will get us to the weekend Aug, 31/Sep 1. Torsten Am 13.08.2013 16:56, schrieb Curtis Olson: We would need permission from Torsten D, our release manager, but I would also second Thorsten R's proposal to defer the 2.12 release by a week or two. I have been spread very thin this summer with my day job projects and will be out of town myself on the 16-18 of August. I think we should at minimum get the Mac and Windows build slaves going, generate release candidates for both platforms, and push those out in the wild for a week (and address any major issues that surface) before finalizing the actual release. I apologize for not being more out in front of this ... this has been the summer from hell (work-wise) for me. Regards, Curt. On Tue, Aug 13, 2013 at 7:24 AM, James Turner zakal...@mac.com mailto:zakal...@mac.com wrote: On 13 Aug 2013, at 12:58, Renk Thorsten thorsten.i.r...@jyu.fi mailto:thorsten.i.r...@jyu.fi wrote: On the risk of making myself really unpopular, but would now be a good time to defer the release? It seems James is caught in the middle of moving, Stuart indicated some other private things piling up, I have the maddest travelling schedule I've ever had in my life this fall, and I haven't seen a number of other folks around for a while, we don't have release candidates out which will have impacts on bugfixes, assuming there'd be anyone around capable of doing bugfixes,... It seems we've hit a fluctuation where pretty much everyone is occupied with something else at the moment (?) - if that's the case, should we still go ahead? That's possibly a fair suggestion. I am scheduled to get my new broadband connection up and running tomorrow (Wednesday) so the Mac build slave will be available at that time (with decent upstream bandwidth again). However my time is a bit fragmented and likely to remain so for a few weeks - I'm happy to merge patches or anything else anyone explicitly requests, but I'm not focused enough to start chasing other people to get things done :) Once the Mac build slave is back, the biggest obstacle to an RC is getting the Windows build slaves to behave; if anyone on Windows could look at the Jenkins logs and shed any light, it would help. Kind regards, James -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net mailto:Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Curtis Olson: http://www.atiak.com http://www.atiak.com/ - http://aem.umn.edu/~uav/ http://aem.umn.edu/%7Euav/ http://www.flightgear.org http://www.flightgear.org/ - http://gallinazo.flightgear.org http://gallinazo.flightgear.org/ -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] New release date for 2.12
Good news, indeed and kudos to Virgin Media! Curt and James, what would you think about publishing the release during the weekend Sept. 14./15.? Or would you prefer to stick to the 17th (a Tuesday)? Torsten Am 15.08.2013 09:21, schrieb James Turner: On 14 Aug 2013, at 21:57, Curtis Olson curtol...@flightgear.org mailto:curtol...@flightgear.org wrote: I think the main initial hurdle here is to get the Mac Windows releases sorted out on Jenkins (if they aren't already). We've done the code freeze and branch on schedule so we are mostly down to the mechanics and time of actually building and pushing the release out the door. The lovely folks at Virgin Media have my broadband up and running now, I plugged in the Mac slave and it's happy, and indeed a Mac release build has rolled off the production line smoothly. Now to see if it actually works - testing appreciated. Regards, James -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Heads up: A-10, B-52F, AN-2225 and MiG-15 and users of moving-average filter
Hi all, the implementation of the autopilot filter moving-average has changed. Actually, the previous implementation gave incorrect results and this bug has now been fixed in the next branch. A quick grep through the Aircraft folder came up with A-10, B-52F, AN-2225 and MiG-15 using the moving-average filter in their A/P config files. Please check, if those aircraft still work as expected. Greetings, Torsten -- Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
