[Flightgear-devel] FlightGear on TheOpenCD
Hello, My name is Henrik Nilsen Omma, and I am a participant in a new Open Source Project called TheOpenCD. Our aim is to create a simple to use CD distribution of Open Source software for Windows that will act as a showcase, and in that way spread the OSS message. We released our first edition in December, and we are now aiminng for a much expanded and improved version in March. We are careful to select only the best quality OSS, so that we can really impress user. As a result our CD will only include around 30 applications (whereas GNUwinII has over 100), and only 3-4 games. Flightgear has impressed us, with it's size, complexity and graphics. However there are a few minor issues which currently doesn't match our profile. 1. When starting the game there are lots of debugg messages, can these be removed? 2. The game and locations are installed in separate packages. This should be combined in a single and smooth install/uninstall along with as much ducumentation as possible. Can we do a collaboration on this? #1 is something we would need help with, while #2 can be done by someone in our team using InnoSetup. The first CD is already in wide circulation, but we expect much more from the second one, as it will be more mature, and we will push it harder. Best wishes, Henrik see: http://theopencd.org -- Henrik Nilsen Omma Theoretical Physics, Oxford 35 Frenchay Road 1 Keble Road Oxford OX2 6TG Oxford OX1 3NP [EMAIL PROTECTED] [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] c172 instrument bugs
Major A writes: > > > Just thought I'd note that these new instruments are pretty heavy on > > texture memory. Might be a big frame hit for some cards. They sure look nice > > though, especially when zooming in! > > Another thought: whenever the full-screen panel models are working > again (they are currently both broken, at least they were on Friday), > I would like to try them out with two screens. The problem here is > that the secondary screen (showing the panel) doesn't have any 3D > hardware (it's a laptop), so the panel will probably be rather > sluggish. So my question is whether it would be possible to create a > panel that's easy on the graphics engine so that you don't need > accelerated OpenGL on each and every screen being used. The basic rule of thumb is that if you draw anything with opengl (especially if it involves textures, alpha transparency, depth buffer, lighting, or fog) it will run very slow unless you have actual 3d hardware acceleration. So, it may be possible to do a 2d panel that runs fast on 2d hardware, but probably not with opengl, and definitely not with the subset of opengl we are using. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] c172 instrument bugs
Jim Wilson writes: > The rpm needle mapping is fixed in cvs now. > > Just thought I'd note that these new instruments are pretty heavy on > texture memory. Might be a big frame hit for some cards. They sure look nice > though, especially when zooming in! That was my screw up. I accidentally overwrote rpm.xml with the new hi-res C172-S rpm gauge. I thought I had reverted it, but apparently forgot to commit. I've done that now. If anyone wants to use this really nice gauge (or any of the other hi-res C172-S gauges) they are named XYZ-c172s.xml So to use the hi-res rpm gauge, you would substitute rpm-c172s.xml for rpm.xml in which ever panel file you are editing. For the split screen panels, it might make sense to come up with a low-res version of these which doesn't burn as much texture RAM. Regards, Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] c172 instrument bugs
Committed to cvs ...
Jim Wilson writes:
> Here's a patch to fix the asi problem (it affects most aircraft panels).
>
> Best,
>
> Jim
>
>
> Index: airspeed_indicator.cxx
> ===
> RCS file:
> /var/cvs/FlightGear-0.9/FlightGear/src/Instrumentation/airspeed_indicator.cxx,v
> retrieving revision 1.4
> diff -r1.4 airspeed_indicator.cxx
> 62c62,65
> < // Now, reverse the equation
> ---
> > // Now, reverse the equation (normalize
> dynamic pressure to avoid "nan" results from sqrt)
> > if (q < 0) {
> >q = 0.0;
> > }
>
>
>
> ___
> Flightgear-devel mailing list
> [EMAIL PROTECTED]
> http://mail.flightgear.org/mailman/listinfo/flightgear-devel
--
Curtis Olson IVLab / HumanFIRST Program FlightGear Project
Twin Cities[EMAIL PROTECTED] [EMAIL PROTECTED]
Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] turbine n1, n2 gauges
Steam gauges for N1 and N2 are available at: http://home.attbi.com/~davidculp2/fg_index.htm ,which also has links to the 737, T-38 and F-16 stuff. Note that the values for N1 and N2 are faked, but are helpful anyway. Now, where do we cram 16 of these gauges into the B-52 cockpit? Dave Culp ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] c172 instrument bugs
> Just thought I'd note that these new instruments are pretty heavy on > texture memory. Might be a big frame hit for some cards. They sure look nice > though, especially when zooming in! Another thought: whenever the full-screen panel models are working again (they are currently both broken, at least they were on Friday), I would like to try them out with two screens. The problem here is that the secondary screen (showing the panel) doesn't have any 3D hardware (it's a laptop), so the panel will probably be rather sluggish. So my question is whether it would be possible to create a panel that's easy on the graphics engine so that you don't need accelerated OpenGL on each and every screen being used. Andras === Major Andras e-mail: [EMAIL PROTECTED] www:http://andras.webhop.org/ === ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] c172 instrument bugs
The rpm needle mapping is fixed in cvs now. Just thought I'd note that these new instruments are pretty heavy on texture memory. Might be a big frame hit for some cards. They sure look nice though, especially when zooming in! Best, Jim Dave Perry <[EMAIL PROTECTED]> said: > I updated SimGear, FlightGear, and the base from cvs and recompiled > today. Since then, all the c172 panels (both 2d and 3d) have two bugs. > 1. The airspeed indicator does not work, and > 2. The tachometer pointer looks like it is part of a dial. It does > rotate, just the wrong graphic. > Regards, > Dave ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] c172 instrument bugs
Dave Perry <[EMAIL PROTECTED]> said:
> I updated SimGear, FlightGear, and the base from cvs and recompiled
> today. Since then, all the c172 panels (both 2d and 3d) have two bugs.
> 1. The airspeed indicator does not work, and
> 2. The tachometer pointer looks like it is part of a dial. It does
> rotate, just the wrong graphic.
> Regards,
> Dave
>
Here's a patch to fix the asi problem (it affects most aircraft panels).
Best,
Jim
Index: airspeed_indicator.cxx
===
RCS file:
/var/cvs/FlightGear-0.9/FlightGear/src/Instrumentation/airspeed_indicator.cxx,v
retrieving revision 1.4
diff -r1.4 airspeed_indicator.cxx
62c62,65
< // Now, reverse the equation
---
> // Now, reverse the equation (normalize
dynamic pressure to avoid "nan" results from sqrt)
> if (q < 0) {
>q = 0.0;
> }
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Re: Boeing 747 cockpit
Melchior, > Doesn't opengc depend on the freetype lib? And isn't that platform > specific? I never got opengc compiled, because it asked for an obsolete > freetype version, while I had only freetype2 installed. So all in all, > point 2 doesn't really sound exciting to me. I got it to compile under Cygwin once, and I think it did compile under Linux once, too. But it was a real hassle (including the freetype stuff and numerous patches which John helped me with). So, if anyone would step forward with this, he definitely must do essential modifications with the dependencies. I must say that the result was quite impressive, though. Regards, Michael -- Michael Basler, Jena, Germany [EMAIL PROTECTED] http://www.geocities.com/pmb.geo/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Re: Boeing 747 cockpit
* Jim Wilson -- Sunday 16 February 2003 00:19: > 1) Use the current 3D Modeling system. [...] > 2) Take code from the opengc project and change it [...] > > Any comments? Doesn't opengc depend on the freetype lib? And isn't that platform specific? I never got opengc compiled, because it asked for an obsolete freetype version, while I had only freetype2 installed. So all in all, point 2 doesn't really sound exciting to me. m. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
