Re: [Flightgear-devel] 3D HUD Support

2003-03-21 Thread Erik Hofman
Norman Vine wrote: Erik Hofman writes: I want to apply the 3D HUD patch which was originally written by Andy Ross and later modified by you. I understand and I am all for it :-) In fact the Win32 binary users already have this. It is the 'requires aircraft tobe repositioned' is what I was

RE: [Flightgear-devel] 3D HUD Support

2003-03-21 Thread Norman Vine
Erik Hofman writes: Norman Vine wrote: Erik Hofman writes: I want to apply the 3D HUD patch which was originally written by Andy Ross and later modified by you. I understand and I am all for it :-) In fact the Win32 binary users already have this. It is the 'requires

Re: [Flightgear-devel] 3D HUD Support

2003-03-21 Thread Erik Hofman
Norman Vine wrote: If I apply the patch and start FlightGear using the F-16 the hud is positioned to far up, leaving the HUD area. This has to be fixed (and can be fixed), but other then the F-16 I have no authoroty over the aircraft section, so other people need to do that themselves. How

Re: [Flightgear-devel] 3D HUD Support

2003-03-21 Thread Erik Hofman
Erik Hofman wrote: Norman Vine wrote: Yes but I think this is what Andy intended ie the 3D HUD is alligned with the horizon That is what mean, all the current HUD's need to be realligned ebcause of this change. It looks like just three HUD types are used, the default, a custom default

RE: [Flightgear-devel] 3D HUD Support

2003-03-20 Thread Norman Vine
Erik Hofman writes: 1. 3D HUD code, written by Andy Ross and modified by Norman Vine. I realy like this patch, but it requires aircraft to be repositioned. As far as I know only the F-16 doesn't use a full-screen HUD, but I'm not sure. Does any object or can I go ahead? Please

Re: [Flightgear-devel] 3D HUD Support

2003-03-20 Thread Erik Hofman
Norman Vine wrote: Erik Hofman writes: 1. 3D HUD code, written by Andy Ross and modified by Norman Vine. I realy like this patch, but it requires aircraft to be repositioned. As far as I know only the F-16 doesn't use a full-screen HUD, but I'm not sure. Does any object or can I go ahead?

RE: [Flightgear-devel] 3D HUD Support

2003-03-20 Thread Norman Vine
Erik Hofman writes: Norman Vine wrote: Erik Hofman writes: 1. 3D HUD code, written by Andy Ross and modified by Norman Vine. I realy like this patch, but it requires aircraft to be repositioned. As far as I know only the F-16 doesn't use a full-screen HUD, but I'm not sure. Does

Re: [Flightgear-devel] 3D HUD

2002-10-31 Thread Erik Hofman
Norman Vine wrote: Hi All I have placed a tarball of hud.cxx hud.hxx that contains a modified version of Andy's patch that implements the 3D HUD as the 'normal' and the 2D HUD as the 'minimal' HUD.i and shift I keys I am not submitting this as a patch to Curt in that it has significant

Re: [Flightgear-devel] 3D HUD

2002-10-31 Thread Norman Vine
Erik Hofman writes: Norman Vine wrote: I am not submitting this as a patch to Curt in that it has significant whitespace changes These are the same files, but in the original layout: http://www.a1.nl/~ehofman/fgfs/download/FlightGear-HUD-20021031.tar.gz It's actually quite easy to

Re: [Flightgear-devel] 3D HUD

2002-10-31 Thread Erik Hofman
Norman Vine wrote: Erik Hofman writes: Norman Vine wrote: I am not submitting this as a patch to Curt in that it has significant whitespace changes These are the same files, but in the original layout: http://www.a1.nl/~ehofman/fgfs/download/FlightGear-HUD-20021031.tar.gz It's actually

[Flightgear-devel] 3D HUD

2002-10-30 Thread Norman Vine
Hi All I have placed a tarball of hud.cxx hud.hxx that contains a modified version of Andy's patch that implements the 3D HUD as the 'normal' and the 2D HUD as the 'minimal' HUD.i and shift I keys I am not submitting this as a patch to Curt in that it has significant whitespace changes

Re: [Flightgear-devel] 3D HUD

2002-10-30 Thread C. Hotchkiss
Norman Vine wrote: Hi All I have placed a tarball of hud... I am working on a major restructuring of the HUD to make having multiple versions of both the 2D and 3D HUDs available at the same time Good. When I worked on the code I expected that is would eventually be expanded to support