Re: [Flightgear-devel] pthread error compiling simgear under ubuntu 11.10 (beta2)
success ! using cmake ended in a successful compilation :-D ok, now I will "cmake" fgfs too and send the new script to Thorsten. Thaank you ! -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] pthread error compiling simgear under ubuntu 11.10 (beta2)
On 27 Sep 2011, at 09:00, Francesco Angelo Brisa wrote: > ok, now I will "cmake" fgfs too and send the new script to Thorsten. > > Thaank you ! That's good news indeed! James -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] git
HiI've messed up weather in fgdata. How could i discard local changes and only get changes/original files? Git says to be up to date but weather is broken.Later I'll do my first upload. (groundnetworks.xml etc.) I do alike the wiki and after commit simply do a git push?Thanks Michael -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Atmospheric haze modelling
I've spent some time over the last days to add a model for an optically thick regime to the skydome scattering shader. I am rather happy with the model (as far as the skydome is concerned, it now renders visibilities down to 1000 m in a plausible way, the transition to the optically thin regime looks nice and you get spectacular sunsets - see http://www.flightgear.org/forums/viewtopic.php?f=47&t=11274&start=90#p137694 for some pictures). The problem is that making this really work means rethinking some concepts. What I have done so far is adding a layer of constant optical thickness from ground level up to some given altitude. That particular case has an analytic solution and hence computes rather fast - I think it's much faster to render an arbitrary density distribution as 10 subsequent layers of constant density each than to put the numerical integration in explicitly. What that means is that visibility is no longer a parameter which changes with your loaction - the visibility at the ground is tracked and determines in an essential way how the scene looks - even if you have 100 km horizontal visibility at your current position, what you see on the ground depends on the angle under which you view the ground haze layer and may be much less. On the other hand, this means that mountain ranges can stick out of the ground haze and be visible much further than the terrain just below. Ultimately, in this concept the notion of a single visibility determining everything is gone and instead you specify optical properties of the atmosphere in certain regions. It's probably obvious why this is tricky - the single visibility parameter currently governs many other things (scenery tile loading springs to mind, objects,...). It's also tricky but crucial to apply the same technique to the terrain, otherwise the horizon line never matches up. So, at this point, I thought I better start asking for some thoughts before finding myself in a difficult place. * Is this something we want to do at all (it's reasonably obvious that I want to do it, but I don't think I can develop this as a harmless addon mode)? * Is there a good way to implement this concept *without* causing too many problems for global weather or the default terrain rendering (for instance, right now, my version of skydome.vert and skydome.frag only run with global weather when some parameters are manually entered via property browser - not user-friendly... but in principle the parameters necessary could be computed from weather info), or is it acceptable that only non-shader rendering stays how it was, but shader-based rendering gets all changed? Or that global weather can't use the skydome shader any more? * Is there a way to implement this without altering every single terrain type/object/... shader and to put the equations for fading of objects with distance into one single place where they are easily updated? Some thoughts are very welcome at this point (possibly also some help in the implementation - I can derive the math quite alright, but to get GLSL to run for me takes an awful lot of time - I'm essentially learning by reverse engineering and trial and error). Cheers, * Thorsten -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] git
On Tue, Sep 27, 2011 at 4:00 AM, Michael Sgier wrote: > Hi > > I've messed up weather in fgdata. How could i discard local changes and > only get changes/original files? Git says to be up to date but weather is > broken. > > Later I'll do my first upload. (groundnetworks.xml etc.) I do alike the > wiki and after commit simply do a git push? > Hi Michael, If you know the specific file(s) that need to be returned to official git head version, then just run: git checkout file1 file2 file3 ... That (unceremoniously and without any confirmation) will discard your local changes to those named files. Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] git
if you just want to discard EVERYTHING back to the head version (make sure you are on the master branch) try this: git checkout -- . the full stop is part of the command, btw Alessandro. From: curtol...@gmail.com Date: Tue, 27 Sep 2011 10:25:56 -0500 To: flightgear-devel@lists.sourceforge.net Subject: Re: [Flightgear-devel] git On Tue, Sep 27, 2011 at 4:00 AM, Michael Sgier wrote: HiI've messed up weather in fgdata. How could i discard local changes and only get changes/original files? Git says to be up to date but weather is broken. Later I'll do my first upload. (groundnetworks.xml etc.) I do alike the wiki and after commit simply do a git push? Hi Michael, If you know the specific file(s) that need to be returned to official git head version, then just run: git checkout file1 file2 file3 ... That (unceremoniously and without any confirmation) will discard your local changes to those named files. Curt.-- Curtis Olson:http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Mon, 26 Sep 2011 13:04:02 -0500, Curtis wrote in message : > Updated to Beta02 -- with hopefully a bit better view management and > some more small gain tweaks (probably nothing anyone will notice.) ..tried to set camera target to some place on-shore with the camera operator click-to-point-to-orbit, on climb-out this is over-ridden to Carrier, just like on the Alphas. Beta02 is a step in the wrong direction, the drone climbs to ~800ft before diving into the drink. ..on resets, launch is uncommanded, one engine dies, and the drone drives and dives in to that side off the bow. ..incompatible with FG-1.9.1, unless we fix it. > I set the "tower" position to be the carrier deck target touch down > spot, and then set the manually controlled tower view to point > directly up the ideal approach path ... simulating a PLAT camera (if > I got my terminology right.) Essentially if the landing aircraft is > exactly on the right approach path it will be dead center of the > video screen. Any deviation shows up very clearly. > > Curt. > > > On Sun, Sep 25, 2011 at 10:04 AM, Arnt Karlsen wrote: > > > On Sat, 24 Sep 2011 17:10:29 -0500, Curtis wrote in message > > : > > > > > Hi Geoff (and Arnt, et. al.) > > > > > > I have another update to try. This one drives the roll angle by > > > manipulating the ailerons directly, rather than trying to modify > > > /controls/flight/SAS-roll. SAS-roll worked for me, and I was just > > > following the example of the existing f-14b dg-heading controller. > > > But driving /control/flight/aileron seems to work just as well for > > > me. If there is some sort of order of execution problem with > > > nasal or something conflicting with SAS-roll, perhaps this will > > > work better? I'd be interested in hearing if it helps if anyone > > > gets a chance to try it. > > > > ..roll is _much_ smoother, for Alpha05, copy your success on the > > elevators too. -- ..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. -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Tue, Sep 27, 2011 at 4:36 PM, Arnt Karlsen wrote: > ..tried to set camera target to some place on-shore with the camera > operator click-to-point-to-orbit, on climb-out this is over-ridden > to Carrier, Hi Arnt, There is some logic going on there to try to automatically guess what an operator is most likely to want or a user will find most interesting to look at. I won't claim this handles every situation, but in the short term why not get airborne, climb out and then find the spot you want to look at? This is intended to be a demonstration of a few different uav concepts implemented in FlightGear. > just like on the Alphas. Beta02 is a step in the wrong > direction, the drone climbs to ~800ft before diving into the drink. > A couple things: I haven't tested with the Nimitz -- sorry, can't vouch for what might or might not work there. I've only flown with the Vinson. It's basically a problem that I lack infinite time. Is this still on your tablet pc that gets 2-3 fps. Honestly, this demo will never work with frame rates that low, sorry. What version of FlightGear are you flying? I'm testing with v2.4 and git here, again I don't have infinite time to test on earlier versions. Again sorry about that. ..on resets, launch is uncommanded, one engine dies, The only time I've see the f-14b engine flame out has been due to lack of fuel? You might try calling the fuel truck over and topping you off if you have problems with your engine not running. > and the drone > drives and dives in to that side off the bow. > > ..incompatible with FG-1.9.1, unless we fix it. > Yeah, sorry, there's a limit to the number of combinations of versions and scenarios I can test and try to support. This was developed for the v2.4 release so going forward you can ding me for not being backwards compatible with v2.4, but it's hard to ask for something developed today to be compatible with 2 1/2 year old release of our code. Anyway, I appreciate you trying it and sorry it didn't work out. I think if I try to put together another demo like this, perhaps it will be base on a heavier than air balloon ... Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Tuesday 27 September 2011 15:53:26 Curtis Olson wrote: > a heavier than air balloon ... Would that be a Led Zeppelin? :) Ron -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Any alpha testers with a bit of extra time on their hands?
On Tue, Sep 27, 2011 at 9:47 PM, Ron Jensen wrote: > On Tuesday 27 September 2011 15:53:26 Curtis Olson wrote: > > > a heavier than air balloon ... > > Would that be a Led Zeppelin? > That's more clever than what I was thinking. :-) Open-humor. Curt. -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] No geomtry rendered, please help!
Greetings, i have strange behavior in "FG 2.4.0 release-final" git tag complied with MSVS2008. The compiled exe appears to be operational since embeded application dialogs and camera control with mouse work , but fgfs show neither any geometry nor any background effects like clouds. I also noticed that initial teaser image while loading aircraft/scenery doesn't show off. OSG ensured operational (fgfs.exe shipped with release installer works with OSG 3.0.1 also VS2008-compiled flawless). Anomalies/deviations: - no SVN support included in this build - AL device fails to load (same visual output with sound support disabled via startup parameter) - png loader plugin produces a warning due interlacing beeing off - no teaser image This is how it looks like: http://www.flickr.com/photos/43342833@N04/6190895429/in/photostream Cheers, Paul -- All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel