Hello !I just finished compiling the latest CVS versions of plib, openAL, simgear and flightgear under x86 linux, everything built without any problems.However, as soon as I try to start fgfs I receive the following warnings in the console:RenderTexture Error: Couldn't find a suitable pixel format.RenderTexture::BeginCapture(): Texture is not initialized!RenderTexture::EndCapture() : Texture is not initialized!Then it takes ages to display the splash screen, a couple of seconds after it's displayed the splash screen gets divided horizontally.And then I have to wait another 3-5 minutes (!) only to see that FlightGear quits ("Killed" message is displayed in console).As I said, I'm using the latest packages for all flightgear dependencies (including the base package), as well as a current gcc (3.3), no errors occured during the build process.Also, I am not using any .fgfsrc file or other special params right now, merely> ./fgfs --fg-root=/usr/local/FlightGear/data-currentThe previous version works without any problems (I have been using FlightGear for a couple of months now)Any hints ?Thanks, also for this great piece of software !!

I am not at home so I can't post a diff, try this if you can :in file source/simgear/scene/sky/bbcache.cxx at the end ofSGBbCache::allocTextureMemory changeif(rt) {withif(rtAvailable ) {in file source/simgear/scene/sky/cloudfield.cxx at the start of file changebool SGCloudField::enable3D = true;withbool SGCloudField::enable3D = false;This will correct a bug if your hardware can't create pbuffers, and also disable 3d clouds because you can't use them without pbuffer atm (it would be too slow).Harald.

Thanks for your help, much appreciated.Two of the warnings disappeared, but one remains:RenderTexture Error: Couldn't find a suitable pixel format.And basically I can watch exactly the same behaviour as before, including the splitting of the splash screen.However, if you assume that this is linked to the new 3D clouds implementation because some cards may not have the required support, I'd like to suggest to enclose the relevant source lines in #ifdef statements, so that one can ./configure --with-3d-clouds=false for such cases.(Even though I am not sure why my relatively new nvidia card shouldn't provide said support)Also, it might be useful if it was possible to allow for parameters to fgfs in order to enable the use of the new 3D clouds implementation for such cases where there is no hardware support available.By the way: there is no core dumped when FlightGear is killed.

> (Even though I am not sure why my relatively new nvidia card> shouldn't provide said support)Your card certainly does. But does your graphics card driver know it? I'd try upgrading it. (And stay away from the last two nvidia Linux drivers. Those are buggy as ####. 6629 is the last that I can recommend.)> By the way: there is no core dumped when FlightGear is> killed.You have to allow core dumps, *big* core dumps. For example, via bash command "ulimit": $ ulimit -c unlimited

> Those are buggy as ####.The censored word was h.e.l.l. Is this an offensive word? I don't get it ...

>> (Even though I am not sure why my relatively new nvidia>card>> shouldn't provide said support)>>Your card certainly does. But does your graphics card driver>know it? I'd try upgrading it. (And stay away from the last>two nvidia Linux drivers. Those are buggy as ####. 6629 is the>last that I can recommend.)Well, I'll look for updates but actually the previous FlightGear versions worked without problems, so I am really a bit hesitant to update an otherwise working system if it's only for the 3D clouds.>> By the way: there is no core dumped when FlightGear is>> killed.>>You have to allow core dumps, *big* core dumps. For example,>via bash command "ulimit":>> $ ulimit -c unlimitedThanks, but that's not the problem: Previous FlightGear versions did "happily segfault" under some circumstances and then I did usually get ~ 150 MB core files.

Just wanted to let you know:The actual problem (the crash) was obviously not caused by the new 3D clouds but rather by a problem with my KSFO scenery, I ran a ./fgfs --log-level=bulk and got:FGTileMgr::update()State == RunningLoading tile /usr/local/share/FlightGear/FlightGear/data/Scenery/Terrain/w130n30/w123n37/942035token = OBJECT_BASE name = 942035.btgLoading tile /usr/local/share/FlightGear/data/Scenery/Objects/w130n30/w123n37/942035generating lightsKilledSo, I simply chose another start airport and everything's working perfectly now, I am not sure what exactly caused the KSFO problem as I did download a fresh base package from CVS, however as long as I can start FlightGear I don't care that much.Thanks for your help