Re: [Flightgear-devel] [ANN] Shader Development
Seeing similar here both in Windows and Linux. Alan -Original Message- From: James Turner Sent: Friday, December 02, 2011 1:43 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] [ANN] Shader Development On 1 Dec 2011, at 22:47, Vivian Meazza wrote: I think it's all in Gitorious now - so you should be able to see for yourself. Getting a couple of compile errors from my Radeon 3870: glLinkProgram FAILED Program infolog: ERROR: No definition of fog_Func in vertex shader ERROR: No definition of fog_Func in fragment shader Scaling image '/Users/jmt/Library/Application Support/flightgear.org/TerraSync/Objects/e000n50/e004n52/pharos.rgb' from (24,312) to (32,256) FRAGMENT glCompileShader FAILED FRAGMENT Shader infolog: ERROR: 0:59: Call to undeclared function 'texture2DLod' ERROR: 0:109: Call to undeclared function 'texture2DLod' ERROR: 0:110: Call to undeclared function 'texture2DLod' glLinkProgram FAILED Program infolog: ERROR: One or more attached shaders not successfully compiled Any hints on narrowing down the errant shader? I really we could report the shader file name :) This is at EHAM with the UFO, if it matters. 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. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ 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. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [ANN] Shader Development
Also, on laptop which only has Intel Graphics (Windows 7) see ERROR: 0:1: ´´ version number not supported by GL2 Alan -Original Message- From: James Turner Sent: Friday, December 02, 2011 1:43 PM To: FlightGear developers discussions Subject: Re: [Flightgear-devel] [ANN] Shader Development On 1 Dec 2011, at 22:47, Vivian Meazza wrote: I think it's all in Gitorious now - so you should be able to see for yourself. Getting a couple of compile errors from my Radeon 3870: glLinkProgram FAILED Program infolog: ERROR: No definition of fog_Func in vertex shader ERROR: No definition of fog_Func in fragment shader Scaling image '/Users/jmt/Library/Application Support/flightgear.org/TerraSync/Objects/e000n50/e004n52/pharos.rgb' from (24,312) to (32,256) FRAGMENT glCompileShader FAILED FRAGMENT Shader infolog: ERROR: 0:59: Call to undeclared function 'texture2DLod' ERROR: 0:109: Call to undeclared function 'texture2DLod' ERROR: 0:110: Call to undeclared function 'texture2DLod' glLinkProgram FAILED Program infolog: ERROR: One or more attached shaders not successfully compiled Any hints on narrowing down the errant shader? I really we could report the shader file name :) This is at EHAM with the UFO, if it matters. 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. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ 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. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] [ANN] Shader Development
James On 1 Dec 2011, at 22:47, Vivian Meazza wrote: I think it's all in Gitorious now - so you should be able to see for yourself. Getting a couple of compile errors from my Radeon 3870: glLinkProgram FAILED Program infolog: ERROR: No definition of fog_Func in vertex shader ERROR: No definition of fog_Func in fragment shader Scaling image '/Users/jmt/Library/Application Support/flightgear.org/TerraSync/Objects/e000n50/e004n52/pharos.rgb' from (24,312) to (32,256) FRAGMENT glCompileShader FAILED FRAGMENT Shader infolog: ERROR: 0:59: Call to undeclared function 'texture2DLod' ERROR: 0:109: Call to undeclared function 'texture2DLod' ERROR: 0:110: Call to undeclared function 'texture2DLod' glLinkProgram FAILED Program infolog: ERROR: One or more attached shaders not successfully compiled Any hints on narrowing down the errant shader? I really we could report the shader file name :) This is at EHAM with the UFO, if it matters. After much searching, we have found and fixed this one: glLinkProgram FAILED Program infolog: ERROR: No definition of fog_Func in vertex shader ERROR: No definition of fog_Func in fragment shader We haven't done anything to Lod - so that one is a bit more mysterious. In Gitorious - see if we fixed it Vivian -- 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. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Fw: CMake, tomorrow (Sunday 23rd)
Another question please? Is it correct to have a floder called src under C:\FGDev\fg-fatimais-flightgear under C:\FGDev\fg-fatimais-flightgear\build? Maybe why I have a fatal error when I try to compile FlightGear.sln under C:\FGDev\fg-fatimais-flightgear\build ... Many thanks, Cheers, Fatima -Message d'origine- De : ThorstenB [mailto:bre...@gmail.com] Envoyé : jeudi 1 décembre 2011 20:16 À : Iervolino Fatima Cc : FlightGear developers discussions Objet : Re: [Flightgear-devel] Fw: CMake, tomorrow (Sunday 23rd) Am 01.12.2011 15:53, schrieb Iervolino Fatima: Hi Thorsten, I've rebuilt all successfully. But I'm still have the same problem as before: What I can do to solve it? First of all, are you really using CMake to configure your FlightGear build (not just for OSG!) - or are you maybe using the MSVC project which is (still) located in the FlightGear folder below project/VC90 ? The latter is unmaintained now - since we switched to CMake a few days ago (see our email topic :) ). I have no idea what happens if you compiled with the now-obsolete MSVC project file. @James/Frederic: Could we drop the VC90 project file now? It's confusing if that's still around. No one is checking this file now, and it's impossible to know what people are using as long as it's still around. Fatima, if you have used cmake for FlightGear (not just for OSG), then check the generated file src/Include/config.h from your FlightGear (build) directory. It should contain: #define ENABLE_YASIM #define ENABLE_JSBSIM = If these were missing (or commented out), then this explains your problem. You could add/enable these defines manually to have a quick success with building. But better also fix the root cause, otherwise issues will be back later. Also check the CMakeCache.txt file (not sure if that has the same name for Windows). It should contain: //Set to ON to build FlightGear with JSBSim FDM ENABLE_JSBSIM:BOOL=ON //Set to ON to build FlightGear with YASIM FDM ENABLE_YASIM:BOOL=ON If these switches are set to OFF (or even missing), then the CMake configuration step hasn't worked for FlightGear. If you can't fix the issue, then please attach the src/Include/config.h and CMakeCache.txt files to your email, so we can see how your build is configured. And remember, these files should be _generated_ on your machine (whenever you run cmake) - so check their file date/time to see if they are really fresh. It may also be a good idea to see if you maybe have any other (old) config.h in one of your include directories - so that the compiler somehow finds the wrong file first... 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. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Sound support broken by AI traffic
Hi Erik et al, sound support is broken here (GIT of today). When I start with the UFO at an airport with AI traffic, e.g. KSFO, then I hear a roar for a few seconds during start-up - but then there is silence for the rest of the simulation. No sound when the UFO moves. On shutdown, I do get a few error messages like these: AL Error (sound manager): Invalid Operation at release buffer AL Error (sound manager): Invalid Operation at release buffer It's working fine when I start at some remote location which doesn't have AI traffic, i.e. ENSD. I commented out the new code in AIBase::update - and then sound is back to normal. However, the error messages (see above) are still there - so these could be unrelated. Anyone else seeing this issue? Any ideas? Another thing I noticed: The sound manager is the last remaining subsystem that is created and initialized at run-time (thanks to James for structuring all the other systems so far!). The sound manager is still initialized in the main loop, and it's done _after_ the scenery is fully loaded (about when the splash screen is withdrawn). However, at this time the first AI aircraft may already be loaded, initialized, updated... Hence, nothing guarantees that AI aircraft won't (try to) use the sound subsystem even _before_ this is properly initialized. Maybe this is already the reason for the issues I'm seeing. Maybe it'd be a good idea to make the sound manager a proper subsystem now, to make sure it's created and initialized with all the other subsystems - so even _before_ the mainloop is run for the very first time. Futhermore, since AI+MP traffic may now depend on sound, the sound manager should probably be initialized before the AI, traffic and MP subsystems now. I'm sure we can resolve these issues for the 2.6.0 release (well, we have to :) ), but it'd probably still be a good idea to also add a switch, so that the new AI sound effects can be disabled - for example on slower systems. 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. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
Am 02.12.2011 20:44, schrieb ThorstenB: sound support is broken here (GIT of today). When I start with the UFO Sorry, only checking the bug tracker now (yes, should have done that first :) ). Someone reported a related issue, different effect though: http://code.google.com/p/flightgear-bugs/issues/detail?id=501 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. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Sound support broken by AI traffic
On Fri, 02 Dec 2011 20:44:06 +0100 ThorstenB bre...@gmail.com wrote: Hi Erik et al, sound support is broken here (GIT of today). When I start with the UFO at an airport with AI traffic, e.g. KSFO, then I hear a roar for a few seconds during start-up - but then there is silence for the rest of the simulation. No sound when the UFO moves. On shutdown, I do get a few error messages like these: AL Error (sound manager): Invalid Operation at release buffer AL Error (sound manager): Invalid Operation at release buffer Hm, this migh be an OpenAL incompatibility since obviously I didn't notice this. I'll try to test it with OpenAL-Soft tomorrow. Erik -- 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. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
