[Flightgear-devel] Hud bug or feature?
The hud zooms with changes in FOV (zooming the view). Can that be fixed? Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Hud bug or feature?
Jim Wilson wrote: The hud zooms with changes in FOV (zooming the view). Can that be fixed? No, if the HUD is added to a 3d cockpit of the F-16 this is the behavior one would expect. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Hud bug or feature?
Erik Hofman [EMAIL PROTECTED] said: Jim Wilson wrote: The hud zooms with changes in FOV (zooming the view). Can that be fixed? No, if the HUD is added to a 3d cockpit of the F-16 this is the behavior one would expect. Ah yes, didn't think of that. A couple of suggestions: 1). Default to the 2D HUD unless there's a specific aircraft level configuration parameter made to override it (e.g. for the F16 2D panel). 2). Use the default HUD design in 2D HUD mode. The one that currently comes up in 2D HUD mode now is not very useful. If we're only concerned about realism we should just ditch the HUD as a default feature. But if we leave it in it should work as it used to for the majority of aircraft without special configuration. Right now it just doesn't work. Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Hud bug or feature?
Jim Wilson wrote: Ah yes, didn't think of that. A couple of suggestions: 1). Default to the 2D HUD unless there's a specific aircraft level configuration parameter made to override it (e.g. for the F16 2D panel). 2). Use the default HUD design in 2D HUD mode. The one that currently comes up in 2D HUD mode now is not very useful. If we're only concerned about realism we should just ditch the HUD as a default feature. But if we leave it in it should work as it used to for the majority of aircraft without special configuration. Right now it just doesn't work. The HUD needs an overhaul, that's for sure. But different people seem to expect different things from the HUD. I for one would like the HUD to behave like a HUD. right now it partially does that. The 2d doesn't. What the HUD needs to do is translate the real positions (ladder for instance) into a smaller display by compressing it with the proper value(s). Right now the 2d HUD code doesn't do that. Next thing I really want to see in the modified HUD code is the ability to set the height, width and distance to the viewer so I can project the HUD information in the appropriate display region. There are quite a number of different HUD layouts (small, wide angle, different aspect ratios, etc.) I see no real solutions for the current code but to leave it like it is right now. Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Hud bug or feature?
Erik Hofman [EMAIL PROTECTED] said: I see no real solutions for the current code but to leave it like it is right now. You didn't read my message. Most of our aircraft don't have HUDs in real life so it is only there for the convenience of the user. For these aircraft it doesn't have to behave like a real HUD because it isn't real. Can't we just default to the 2D? The ONE aircraft that needs the 3D could have a configuration parameter to initiate it. We don't have to make major changes now, but we should at least be releasing code that works, even if it is considered inadequate by some. The 2D hud works. Should I submit a patch? Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Hud bug or feature?
At Thu, 16 Oct 2003 23:45:29 - , Jim Wilson wrote: Can't we just default to the 2D? The ONE aircraft that needs the 3D could have a configuration parameter to initiate it. We don't have to make major changes now, but we should at least be releasing code that works, even if it is considered inadequate by some. The 2D hud works. Should I submit a patch? umm how about just adding --disable-hud3d or its XML equivalent to your local preferences Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
