Re: [Flightgear-devel] No Rembrandt here...
Hi Thorsten, I think that is what we have for now. You can do better by increasing your shadow map size to 8192 or 16384, but at the 16384 resolution my performance goes into the tank, and at 8192, there are still many shadow artifacts due to lack of resolution. (clearly blocky/xelated/aliasing edges, something that looks like z-buffer fighting for objects further way, etc.) Hopefully this will improve with future tuning. I'd love to be able to overfly the SFO terminal at 1000' for instance and have solid shadows on the AI aircraft, solid shadows on the light poles, solid shadows from the terminal building, etc. I'm hoping that will ultimately be possible. Otherwise, just getting one good clear shadow of our own aircraft onto the ground and onto ourselves would be a good 90% solution. Curt. On Wed, Apr 11, 2012 at 7:52 AM, Renk Thorsten wrote: > > Try --prop:/sim/rendering/no-16bit-buffer=true > > > > although the symptoms were a bit different > > Same here, this sort of works up to the 4096 map size. I do see shadows > and lights at night at KSFO, but the shadows are very... restless - they > seem to flicker quite a bit, and all in all the light I get to see depends > very much on the view angle - is that normal? The grainy shadow edge seems > to be a function of the map size, it gets a lot worse when I go to 1024... > > Thanks for the fix in any case! > > Cheers, > > * Thorsten > > > > -- > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- Curtis Olson: http://www.atiak.com - http://aem.umn.edu/~uav/ http://www.flightgear.org - http://gallinazo.flightgear.org -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
> Try --prop:/sim/rendering/no-16bit-buffer=true > > although the symptoms were a bit different Same here, this sort of works up to the 4096 map size. I do see shadows and lights at night at KSFO, but the shadows are very... restless - they seem to flicker quite a bit, and all in all the light I get to see depends very much on the view angle - is that normal? The grainy shadow edge seems to be a function of the map size, it gets a lot worse when I go to 1024... Thanks for the fix in any case! Cheers, * Thorsten -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
On Wed, 2012-04-11 at 14:15 +0200, Frederic Bouvier wrote: > > On Wed, 2012-04-11 at 13:35 +0200, Frederic Bouvier wrote: > > > Hi Erik, > > > With this "patch" you are trading a bug for a bug. Assigning the > > > same attachment to three buffers as the same effect than assigning > > > three different values to the same variable. > > > > I was already afraid something like that was happening. > > Try --prop:/sim/rendering/no-16bit-buffer=true > > although the symptoms were a bit different Yes! that works. Erik -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
> On Wed, 2012-04-11 at 13:35 +0200, Frederic Bouvier wrote: > > Hi Erik, > > With this "patch" you are trading a bug for a bug. Assigning the > > same attachment to three buffers as the same effect than assigning > > three different values to the same variable. > > I was already afraid something like that was happening. Try --prop:/sim/rendering/no-16bit-buffer=true although the symptoms were a bit different Regards, -Fred -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
On Wed, 2012-04-11 at 13:35 +0200, Frederic Bouvier wrote: > Hi Erik, > With this "patch" you are trading a bug for a bug. Assigning the > same attachment to three buffers as the same effect than assigning > three different values to the same variable. I was already afraid something like that was happening. Erik -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
Hi Erik, > De: Erik Hofman > > On Wed, 2012-04-11 at 10:18 +0200, Frederic Bouvier wrote: > > > I have to make guess as I don't have a card that exhibit that > > issue. > > You can try to edit fg/src/Main/renderer.cxx and change > > GL_DEPTH_COMPONENT32 to GL_DEPTH_COMPONENT24. You may also try to > > add the --bpp=32 option to the fgfs command line. > > > > Last, make sure that you didn't enable multithreading in > > preferences.xml > > (AutomaticSelection or something else) > > None of these seems to help but when I apply the attached patch (as > suggested by http://markmail.org/message/yfuz7je43bdzt6h2) at least > the warnings are gone and I see the scenery (but not yet perfect). With this "patch" you are trading a bug for a bug. Assigning the same attachment to three buffers as the same effect than assigning three different values to the same variable. Regards, -Fred -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
Vivian, or anyone else with "optional-Rembrandt" experience, feel free to add some instructions on how to make an aircraft support both renderers to http://wiki.flightgear.org/Project_Rembrandt#Porting_aircraft So we can forward aircraft devs to that (once Rembrandt is stable/complete). Cheers, Gijs -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
Thorsten wrote: > -Original Message- > From: Renk [mailto:thorsten.i.r...@jyu.fi] > Sent: 11 April 2012 09:33 > To: FlightGear developers discussions > Subject: Re: [Flightgear-devel] No Rembrandt here... > > > Be sure I value your feedback, but we are exploring new lands here. > > There is not so much OSG deferred rendering example or real > > application around, so please be forgiving. > > And I don't think Flightgear is unusable for anybody. The Rembrandt > > renderer is optional and the classical/2.6 renderer should work for > > everybody. > > Sorry if that came across the wrong way. I am well aware of this - I am > probably more worried about aircraft and/or scenery being converted and > committed at this stage than about project Rembrandt as such, since the > default renderer is working just fine. What also bothers me is the attitude > I've come across with other people (not you!) which goes like 'Don't bother > writing something for the 2.6 renderer because Rembrandt will be there.' - > which sounds more like replacement than optional. I'm also observing > statements being made in the forum by various people - some are rather > cautious, others raise expectations for a release which may backfire badly if > there turn out to be issues with many cards. So I'm not writing this out of the > blue. > > Personally, I can live without shadows if my GPU turns out not to support this > at all in the end - but I can't really if all aircraft at night use Rembrandt in a > non-optional way and all I get to see with default rendering is darkness. And > so on. > > I'll explore your suggestions and let you know what happens. > Ah the dangers of forums! Whether or not an aircraft is converted to Rembrandt depends on the aircraft developer. Personally, I have taken the route of adding a Rembrandt version to the inventory and leaving a version still fully compatible with 2.6.0. This is by way of being a test-bed for Rembrandt. So far it has taken several weeks, and most of it is just eye-candy. This is partly my learning curve, partly bugs, and not least the sheer size of the task. I think that you are quite right to express your concerns. I suppose in the future there might be aircraft or scenery developed purely for Rembrandt (and that would be a poor decision by the developer), but at the moment I cannot see why your fears would be realised while Rembrandt remains optional. Vivian -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
On Wed, 2012-04-11 at 10:18 +0200, Frederic Bouvier wrote: > I have to make guess as I don't have a card that exhibit that issue. > You can try to edit fg/src/Main/renderer.cxx and change > GL_DEPTH_COMPONENT32 to GL_DEPTH_COMPONENT24. You may also try to add > the --bpp=32 option to the fgfs command line. > > Last, make sure that you didn't enable multithreading in preferences.xml > (AutomaticSelection or something else) None of these seems to help but when I apply the attached patch (as suggested by http://markmail.org/message/yfuz7je43bdzt6h2) at least the warnings are gone and I see the scenery (but not yet perfect). Erik diff --git a/src/Main/renderer.cxx b/src/Main/renderer.cxx index a4848d3..9f4ed10 100644 --- a/src/Main/renderer.cxx +++ b/src/Main/renderer.cxx @@ -761,9 +761,9 @@ osg::Camera* FGRenderer::buildDeferredGeometryCamera( flightgear::CameraInfo* in camera->setRenderTargetImplementation( osg::Camera::FRAME_BUFFER_OBJECT ); camera->setViewport( new osg::Viewport ); attachBufferToCamera( info, camera, osg::Camera::DEPTH_BUFFER, flightgear::GEOMETRY_CAMERA, flightgear::RenderBufferInfo::DEPTH_BUFFER ); -attachBufferToCamera( info, camera, osg::Camera::COLOR_BUFFER0, flightgear::GEOMETRY_CAMERA, flightgear::RenderBufferInfo::NORMAL_BUFFER ); -attachBufferToCamera( info, camera, osg::Camera::COLOR_BUFFER1, flightgear::GEOMETRY_CAMERA, flightgear::RenderBufferInfo::DIFFUSE_BUFFER ); -attachBufferToCamera( info, camera, osg::Camera::COLOR_BUFFER2, flightgear::GEOMETRY_CAMERA, flightgear::RenderBufferInfo::SPEC_EMIS_BUFFER ); +attachBufferToCamera( info, camera, osg::Camera::COLOR_BUFFER, flightgear::GEOMETRY_CAMERA, flightgear::RenderBufferInfo::NORMAL_BUFFER ); +attachBufferToCamera( info, camera, osg::Camera::COLOR_BUFFER, flightgear::GEOMETRY_CAMERA, flightgear::RenderBufferInfo::DIFFUSE_BUFFER ); +attachBufferToCamera( info, camera, osg::Camera::COLOR_BUFFER, flightgear::GEOMETRY_CAMERA, flightgear::RenderBufferInfo::SPEC_EMIS_BUFFER ); camera->setDrawBuffer(GL_FRONT); camera->setReadBuffer(GL_FRONT); -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
> Be sure I value your feedback, but we are exploring new lands here. > There is not so much OSG deferred rendering example or real > application around, so please be forgiving. > And I don't think Flightgear is unusable for anybody. The Rembrandt > renderer is optional and the classical/2.6 renderer should work for > everybody. Sorry if that came across the wrong way. I am well aware of this - I am probably more worried about aircraft and/or scenery being converted and committed at this stage than about project Rembrandt as such, since the default renderer is working just fine. What also bothers me is the attitude I've come across with other people (not you!) which goes like 'Don't bother writing something for the 2.6 renderer because Rembrandt will be there.' - which sounds more like replacement than optional. I'm also observing statements being made in the forum by various people - some are rather cautious, others raise expectations for a release which may backfire badly if there turn out to be issues with many cards. So I'm not writing this out of the blue. Personally, I can live without shadows if my GPU turns out not to support this at all in the end - but I can't really if all aircraft at night use Rembrandt in a non-optional way and all I get to see with default rendering is darkness. And so on. I'll explore your suggestions and let you know what happens. Cheers, * Thorsten -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
> De: Erik Hofman > > On Wed, 2012-04-11 at 06:25 +, Renk Thorsten wrote: > > > The first line says it all. > > > > Okay... so what does it mean? It means that a required Framebuffer Object failed to setup and the fallback isn't OK for Rembrandt. > > > > > I'd first try to reduce the size of the shadow map : > > > --prop:/sim/rendering/shadows/map-size=1024 > > > > No success, problem persists. > > > > > or reduce the window size : --geometry=800x600 > > > to reduce the memory footprint. > > > > Same as above, problem persists. Also when I use small shadow map > > in addition to 800x600 window no success (leaving aside the fact > > that Flightgear running in a window of less than a quarter of my > > screen isn't really thrilling...) . > > Maybe this may help developers, it's about the same message: > http://forum.openscenegraph.org/viewtopic.php?t=8905 This issue is related to iOS and OGL ES, that is a bit different. There is the concept of implicit attachment in OSG, so INCOMPLETE_ATTACHMENT shouldn't occur if an attachment was missing in the first place. I am thinking of an explicit attachment that failed silently. There is a way to increase the OSG log level, but I don't remember it for the moment. I have to make guess as I don't have a card that exhibit that issue. You can try to edit fg/src/Main/renderer.cxx and change GL_DEPTH_COMPONENT32 to GL_DEPTH_COMPONENT24. You may also try to add the --bpp=32 option to the fgfs command line. Last, make sure that you didn't enable multithreading in preferences.xml (AutomaticSelection or something else) > Plus, so far with one exception (landmass effect at high quality) > pretty much everything so far ran just fine out of the box with very > acceptable framerates. So, I have a feeling that Rembrandt might be > going to leave a lot of folks with blank screens at this point. I > don't want to be negative here, maybe it is a trivial problem, but > this isn't really a shader which I don't really need to see, this > gives me an unusuable Flightgear. Be sure I value your feedback, but we are exploring new lands here. There is not so much OSG deferred rendering example or real application around, so please be forgiving. And I don't think Flightgear is unusable for anybody. The Rembrandt renderer is optional and the classical/2.6 renderer should work for everybody. Regards, -Fred -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
On Wed, 2012-04-11 at 06:25 +, Renk Thorsten wrote: > > The first line says it all. > > Okay... so what does it mean? > > > I'd first try to reduce the size of the shadow map : > > --prop:/sim/rendering/shadows/map-size=1024 > > No success, problem persists. > > > or reduce the window size : --geometry=800x600 > > to reduce the memory footprint. > > Same as above, problem persists. Also when I use small shadow map in addition > to 800x600 window no success (leaving aside the fact that Flightgear running > in a window of less than a quarter of my screen isn't really thrilling...) . Maybe this may help developers, it's about the same message: http://forum.openscenegraph.org/viewtopic.php?t=8905 Erik -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
On Wed, 2012-04-11 at 06:25 +, Renk Thorsten wrote: > > The first line says it all. > > Okay... so what does it mean? > > > I'd first try to reduce the size of the shadow map : > > --prop:/sim/rendering/shadows/map-size=1024 > > No success, problem persists. > > > or reduce the window size : --geometry=800x600 > > to reduce the memory footprint. > > Same as above, problem persists. Also when I use small shadow map in addition > to 800x600 window no success (leaving aside the fact that Flightgear running > in a window of less than a quarter of my screen isn't really thrilling...) . In fact I have the same problem with a AMD-X2/3Ghz with 2Gb memory and a GeForce 9600GT: fgfs --enable-rembrandt --prop:/sim/rendering/shadows/map-size=1024 --geometry=800x60 RenderStage::runCameraSetUp(), FBO setup failed, FBO status= 0x8cd6 Warning: RenderStage::runCameraSetUp(State&) Pbuffer does not support multiple color outputs. Erik -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
> The first line says it all. Okay... so what does it mean? > I'd first try to reduce the size of the shadow map : > --prop:/sim/rendering/shadows/map-size=1024 No success, problem persists. > or reduce the window size : --geometry=800x600 > to reduce the memory footprint. Same as above, problem persists. Also when I use small shadow map in addition to 800x600 window no success (leaving aside the fact that Flightgear running in a window of less than a quarter of my screen isn't really thrilling...) . > You have a laptop right ? Maybe you have shared memory between the > CPU and the GPU (NVidia calls that TurboCache) and you didn't > reserve enough memory for the GPU. This is a BIOS setting. > Allocate the more you can to the GPU and retry. Can't do - this is a SONY VAIO laptop, which means you don't get to set anything relevant in the BIOS unless you start hacking it. :-( Somehow I have the feeling that this isn't a memory problem though. Experimenting with Earthview, I can load a sphere textured with 5 4096x4096 and 11 2048x2048 texture sheets allright without bothering with any smart texture management in addition to a normal Flightgear scenery and it works just fine - going through the numbers, that's quite a lot of raw data to be stored somewhere. My GPU isn't exactly new, but given what cloud and weather I can run and what others get as framerates out of the same scene, it is still rather competitive and probably better than what most people in the forum run (i.e. those who don't invest in a dedicated high-end GPU). Plus, so far with one exception (landmass effect at high quality) pretty much everything so far ran just fine out of the box with very acceptable framerates. So, I have a feeling that Rembrandt might be going to leave a lot of folks with blank screens at this point. I don't want to be negative here, maybe it is a trivial problem, but this isn't really a shader which I don't really need to see, this gives me an unusuable Flightgear. Cheers, * Thorsten -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] No Rembrandt here...
Hi Thorsten, The first line says it all. I'd first try to reduce the size of the shadow map : --prop:/sim/rendering/shadows/map-size=1024 or reduce the window size : --geometry=800x600 to reduce the memory footprint. You have a laptop right ? Maybe you have shared memory between the CPU and the GPU (NVidia calls that TurboCache) and you didn't reserve enough memory for the GPU. This is a BIOS setting. Allocate the more you can to the GPU and retry. Regards, -Fred - Mail original - > De: Renk Thorsten > > Just freshly pulled and compiled GIT, fresh FGData master, trying to > start with --enable-rembrandt results in garbage on the screen and > an impressive list of errors - (I've omitted messages with meaning > known to me in the following as well as repetitions). Running > without Rembrandt looks fine to me on first glenace. > > Graphics card is an NVIDIA GeForce 8600M running under Linux with the > nvidia driver. > > Cheers, > > * Thorsten > > > > RenderStage::runCameraSetUp(), FBO setup failed, FBO status= 0x8cd6 > Warning: RenderStage::runCameraSetUp(State&) Pbuffer does not support > multiple > olor outputs. > Warning: RenderStage::runCameraSetUp(State&) Pbuffer does not support > multiple > olor outputs. > Warning: RenderStage::runCameraSetUp(State&) Pbuffer does not support > multiple > olor outputs. > Failed to create beacon for unknown runway 'KONT 26L OM'. > Failed to create beacon for unknown runway 'KONT 26R OM'. > Failed to create beacon for unknown runway 'KSAV 01 OM'. > Failed to create beacon for unknown runway 'KSAV 10 OM'. > Failed to create beacon for unknown runway 'PAYA 11 OM'. > Failed to create beacon for unknown runway 'WARQ 26 OM'. > Failed to create beacon for unknown runway 'WARR 10 OM'. > Failed to create beacon for unknown runway 'ZULS 27R OM'. > Failed to create beacon for unknown runway 'EDDB 07 MM'. > Failed to create beacon for unknown runway 'EDDB 25 MM'. > Failed to create beacon for unknown runway 'KIAD 01C MM'. > Failed to create beacon for unknown runway 'KONT 08L MM'. > Failed to create beacon for unknown runway 'KONT 26L MM'. > Failed to create beacon for unknown runway 'KONT 26R MM'. > Failed to create beacon for unknown runway 'KSAV 01 MM'. > Failed to create beacon for unknown runway 'KSAV 10 MM'. > Failed to create beacon for unknown runway 'PAED 06 MM'. > Failed to create beacon for unknown runway 'PAYA 11 MM'. > Failed to create beacon for unknown runway 'WADD 27 MM'. > Failed to create beacon for unknown runway 'WALL 25 MM'. > Failed to create beacon for unknown runway 'WAOO 10 MM'. > Failed to create beacon for unknown runway 'WAOP 34 MM'. > Failed to create beacon for unknown runway 'WARJ 09 MM'. > Failed to create beacon for unknown runway 'WARQ 26 MM'. > Failed to create beacon for unknown runway 'WARR 10 MM'. > Failed to create beacon for unknown runway 'WIDD 04 MM'. > Failed to create beacon for unknown runway 'WIHH 24 MM'. > Failed to create beacon for unknown runway 'KIAD 19C IM'. > Failed to create beacon for unknown runway 'KONT 26L IM'. > RenderStage::runCameraSetUp(), FBO setup failed, FBO status= 0x8cd6 > Warning: detected OpenGL error 'invalid enumerant' at end of > SceneView::draw() > Loading local weather routines... > Animated jetways ... initialized > loading scenario 'nimitz_demo' > Image "/home/fgfs/FGData/fgdata/Textures/Water/waves-ver10-nm.dds" > uses compressed textures which cannot be supported on some systems. > Please decompress this texture for improved portability. > (...) > RenderStage::runCameraSetUp(), FBO setup failed, FBO status= 0x8cd6 > Warning: detected OpenGL error 'invalid enumerant' at start of > State::apply() > (...) > -- > Better than sec? Nothing is better than sec when it comes to > monitoring Big Data applications. Try Boundary one-second > resolution app monitoring today. Free. > http://p.sf.net/sfu/Boundary-dev2dev > ___ > Flightgear-devel mailing list > Flightgear-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] No Rembrandt here...
Just freshly pulled and compiled GIT, fresh FGData master, trying to start with --enable-rembrandt results in garbage on the screen and an impressive list of errors - (I've omitted messages with meaning known to me in the following as well as repetitions). Running without Rembrandt looks fine to me on first glenace. Graphics card is an NVIDIA GeForce 8600M running under Linux with the nvidia driver. Cheers, * Thorsten RenderStage::runCameraSetUp(), FBO setup failed, FBO status= 0x8cd6 Warning: RenderStage::runCameraSetUp(State&) Pbuffer does not support multiple olor outputs. Warning: RenderStage::runCameraSetUp(State&) Pbuffer does not support multiple olor outputs. Warning: RenderStage::runCameraSetUp(State&) Pbuffer does not support multiple olor outputs. Failed to create beacon for unknown runway 'KONT 26L OM'. Failed to create beacon for unknown runway 'KONT 26R OM'. Failed to create beacon for unknown runway 'KSAV 01 OM'. Failed to create beacon for unknown runway 'KSAV 10 OM'. Failed to create beacon for unknown runway 'PAYA 11 OM'. Failed to create beacon for unknown runway 'WARQ 26 OM'. Failed to create beacon for unknown runway 'WARR 10 OM'. Failed to create beacon for unknown runway 'ZULS 27R OM'. Failed to create beacon for unknown runway 'EDDB 07 MM'. Failed to create beacon for unknown runway 'EDDB 25 MM'. Failed to create beacon for unknown runway 'KIAD 01C MM'. Failed to create beacon for unknown runway 'KONT 08L MM'. Failed to create beacon for unknown runway 'KONT 26L MM'. Failed to create beacon for unknown runway 'KONT 26R MM'. Failed to create beacon for unknown runway 'KSAV 01 MM'. Failed to create beacon for unknown runway 'KSAV 10 MM'. Failed to create beacon for unknown runway 'PAED 06 MM'. Failed to create beacon for unknown runway 'PAYA 11 MM'. Failed to create beacon for unknown runway 'WADD 27 MM'. Failed to create beacon for unknown runway 'WALL 25 MM'. Failed to create beacon for unknown runway 'WAOO 10 MM'. Failed to create beacon for unknown runway 'WAOP 34 MM'. Failed to create beacon for unknown runway 'WARJ 09 MM'. Failed to create beacon for unknown runway 'WARQ 26 MM'. Failed to create beacon for unknown runway 'WARR 10 MM'. Failed to create beacon for unknown runway 'WIDD 04 MM'. Failed to create beacon for unknown runway 'WIHH 24 MM'. Failed to create beacon for unknown runway 'KIAD 19C IM'. Failed to create beacon for unknown runway 'KONT 26L IM'. RenderStage::runCameraSetUp(), FBO setup failed, FBO status= 0x8cd6 Warning: detected OpenGL error 'invalid enumerant' at end of SceneView::draw() Loading local weather routines... Animated jetways ... initialized loading scenario 'nimitz_demo' Image "/home/fgfs/FGData/fgdata/Textures/Water/waves-ver10-nm.dds" uses compressed textures which cannot be supported on some systems. Please decompress this texture for improved portability. (...) RenderStage::runCameraSetUp(), FBO setup failed, FBO status= 0x8cd6 Warning: detected OpenGL error 'invalid enumerant' at start of State::apply() (...) -- Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
