Re: [Flightgear-devel] Re: [Flightgear-users] Live-CD
Op woensdag 21 januari 2004 10:10, schreef Erik Hofman: > Ronny Standtke wrote: > > Hi Curtis, > > > > I post my answers to the list as your questions where so good that they > > deserve to be answered in public :-) > > > >>2. It would be interesting to have flightgear startup automatically > >> rather than just giving an icon to click on. > > > > I would think it would be best to use FlightGear as the window manager. > You could acomplish this: > http://baron.flightgear.org/pipermail/flightgear-devel/2002-March/006012.ht >ml > That's how I used to run flightgear. In my bin folder I placed a script startfgfs that I could start from the console, which would start the x server, at a very low resolution and start flight gear. Of course, I could still use the startx for all the other things. Because no window manager runned (resources) and because my resolution was smaller (800*600) I got a noteable increase in frame rate. I used this procedure on a i810 celeron 400Mhz with 128Mb ram and got a frame rate of 8 fps. Still not very fast, but I think that machine was way under the specs for a program like flight gear. Pieter ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] What is ...
Op woensdag 11 juni 2003 20:48, schreef Curtis L. Olson: > Pieter Pareit writes: > > Op woensdag 11 juni 2003 19:37, schreef Jon S Berndt: > > > What's a wiki? > > > > http://www.wikipedia.org/w/wiki.phtml?search=wiki&go=Go > > > > In short, a web page that can contain anything, that can be > > updated by anyone at anytime. > > Given the current climate on the internet to abuse anything that's > world writable/accessible for spam, warez, etc. do these things > have a problem with being abused? Does unwanted material ever show > up on them, etc. etc.? Yes they get abused. Yes unwanted material shows up on them. But: 1) Whoever it uses will have an interest in FlightGear. 2) It is easy to revert back to a know good state. 3) Anybody can revert it back to a good state. 4) Wiki's can block the ip of abusers. 5) It is very easy to spot changes and abusers. 6) It works. (I use the regularly and am a big fan of them) pieter ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] What is ...
Op woensdag 11 juni 2003 19:37, schreef Jon S Berndt: > What's a wiki? http://www.wikipedia.org/w/wiki.phtml?search=wiki&go=Go In short, a web page that can contain anything, that can be updated by anyone at anytime. pieter ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Help with close event
Op dinsdag 10 juni 2003 19:49, schreef Miller, M B: > I have a application that interfaces with Flightgear using shared > memory. I was wanting to set a flag for when the application was > closed. I have code in place for when the menus are used. Since > you pointed out the specifics about the window controls, it might > be easier for me to monitor the state of the executable from the > other app. > You could always use constructor/destructor tricks or look at atexit(). I should not recommend doing this. pieter ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Profiling/Graphics/Menus
Op dinsdag 10 juni 2003 19:40, schreef Michael Selig: > At 6/10/03, Christopher S Horler wrote: > > I'm wondering what kind of graphics acceleration would be > > required to run flightgear at adequate speed. I have to admit > > that I haven't had time to try in months (I hope to get a bit of > > coding time soon as well as finishing other started bits - > > Spitfire). > > > > > >If it is anymore than a 32 MB graphics card for the simple stuff > > then I think that steps need to be taken to add a menu for > > graphics options if these are indeed configurable (and assuming > > the menu doesn't already exist). This menu would allow you to > > configure the game to run adequately on some defined baseline > > system. I would also like to see less reliance on command line > > options (I think this was getting better with xml driven menus > > when I last looked?) > > > > > >Finally can anyone tell me if they're looking at finding the > > bottlenecks in the code? Clarifying; points which slow it down > > which might be implemented in a different manner, not including > > possible small increases which I consider almost trivial. > > On some computers that we use here at uiuc [fast computers w/ > GeForce 4 graphics cards (4200) running Linux RH 8], when fgfs runs > it will periodically pause for 1 sec or so. This can happen every > ~30 secs. At the same time as the pause, fgfs spits out a bunch of > stuff to the terminal window. I don't know what causes this, but > I'd define it as bottleneck. It is not a new problem. If it has > to do w/ computing the sun angle or loading in more scenery, then > it would be useful to be able turn off this "feature"; that is, fly > beyond the scenery and forget about updating the sun time, etc (or > whatever is going on). We run 3 fgfs computers in our teaching > lab, and they all have this "pregnant pause" issue. > > Does anyone else experience this problem and/or know what causes > it? > You should configure fg with with-threads during the configure stage of your compile. See if the halts go away this way. pieter ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Help with close event
Op dinsdag 10 juni 2003 19:14, schreef Miller, M B: > I am trying to capture the close message generated when closing > Flightgear via the window controls (minimize/maximize/close). I > have been unable to find the function handlers for these events. > Could someone please point me in the right direction. I am running > Windows 2000. Flightgear uses glut, which means that once glutMainLoop() is called it never returns. Glut will call all kinds of callbacks for the application, like when to draw, when a key was pressed and so on. Glut does not notify the application when it gets closed. So the only nice way to close an glut application is through the user interface. There is code that notifies io code that the application is quiting, so files can be flushed and network connections can be closed but this is only when the application was closed through the gui (menus). It might help to know why you need that event. pieter ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
