Frederic Bouvier wrote: > Curtis L. Olson wrote: > > > Andy Ross wrote: > > > > >Are you sure you're not using "full screen" mode, which does pretty > > >much the same thing? > > > > > > > > > > Well, at least with "windowmaker", --enable-fullscreen leaves a window > > with decorations, although it does fill up the screen (minus the > > decorations.) It's my perception that different window managers (and > > different OS's) do not always act exactly the same here. > > > > Maybe there is a better way to do this, but right now, > > --enable-game-mode is the only thing I've seen that consistantly opens > > up a full screen window with no WM decorations. > > > > >Regardless, I think this is back. It was wrapped inside a stale ifdef > > >(GLUT_WRONG_VERSION) which no longer exists. But I misread the sense > > >of the test (#ifndef, not #ifdef) and assumed it was dead. There was > > >also some WIN32 code in there to pick up current desktop settings, > > >which I didn't include because it was commented out and I can't test > > >it anyway. > > > > > > > > > > Thanks for the quick fix. > > The current game mode ( I mean the code Andy resurrect ) is totally useless > for me : less than a frame every 3 seconds, in 640x480 resolution, and > the image tinted in blue. --enable-fullscreen give me correct image at > 1600x1200 and about 30 fps.
Last update : if I use "--enable-game-mode --bpp=32" instead of --enable-game-mode alone, I have a good picture and very good framerate at 640x480 ( steady 60fps ). -Fred _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
