Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/src/Main renderer.cxx, 1.27, 1.28
Dave Culp wrote: This sounds more like HAA (height above airport) or HAT (height above touchdown). Height AGL should be the current height above the ground directly below the aircraft. Height AGL should change as the terrain below the aircraft changes. What would expect the HUD to display? I'm quite sure that the F-16 doesn't have a terrain database or an AGL radar. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/src/Main renderer.cxx, 1.27, 1.28
Quoting Erik Hofman: Dave Culp wrote: This sounds more like HAA (height above airport) or HAT (height above touchdown). Height AGL should be the current height above the ground directly below the aircraft. Height AGL should change as the terrain below the aircraft changes. What would expect the HUD to display? I'm quite sure that the F-16 doesn't have a terrain database or an AGL radar. So the HUD is displaying the height for the last known QFE ? -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/src/Main renderer.cxx, 1.27, 1.28
Frederic Bouvier wrote: So the HUD is displaying the height for the last known QFE ? I think so. I suppose it just a barometric instrument with a digital display. It is synchronized by ATC reports. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] AGL and HUD
I have had this problem with an older version of FG, around 8.0, when using a separate computer for the scenery. For reasons unexplained the altitude was set initially in /Network/native_fdm.cxx as an addon to the runway height, then the AGL changed, and with it the altitude. I fixed it for our purposes by locking the AGL to the takeoff runway altitude, but the current version does it the other way, getting AGL from the altitude and subtracting the current ground elevation to get the AGL. I don't know if this helps in your case. Rex [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] AGL and HUD
rhett3 wrote: I have had this problem with an older version of FG, around 8.0, when using a separate computer for the scenery. For reasons unexplained the altitude was set initially in /Network/native_fdm.cxx as an addon to the runway height, then the AGL changed, and with it the altitude. I fixed it for our purposes by locking the AGL to the takeoff runway altitude, but the current version does it the other way, getting AGL from the altitude and subtracting the current ground elevation to get the AGL. I don't know if this helps in your case. This looks suspicious: CVS log for source/src/Cockpit/cockpit.cxx Mathias Fröhlich has his name attached to the change from rev 1.13 to rev 1.14. This changes the AGL strip to read hight above some runway, not current terrain. This isn't intended to be a real instrument I guess, but perhaps work similar to a radio altimeter which does show you the height above current terrain. The CVS logs don't mention any intent to change this behavior, and I don't recall any discussion, so I'd like to change the default behavior back to reporting height above the current location. Hmmm, it seems like the original get_cur_elev() has been removed from the api. Did someone just bandaid in a quick call to runway altitude (which is probably not updated as you fly from place to place?) Regards, Curt. -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Compiling from source
I'm trying to compile FG from the latest CVS and I'm getting two unresolved externals: error LNK2019: unresolved external symbol __imp__alutUnloadWAV referenced in function public: __thiscall SGSoundSample::SGSoundSample(char const *,char const *,bool) (??0SGSoundSample@@[EMAIL PROTECTED]@Z)SimGear.lib error LNK2019: unresolved external symbol __imp__alutLoadWAVFile referenced in function public: __thiscall SGSoundSample::SGSoundSample(char const *,char const *,bool) (??0SGSoundSample@@[EMAIL PROTECTED]@Z) SimGear.lib I'm compiling under Visual Studio 2005 Beta 2 and I have included ALut.lib. I'm also building OpenAL, PLib and SimGear from the latest CVS without issues. Any ideas? Thanks, Vance application/ms-tnef___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/src/Main renderer.cxx, 1.27, 1.28
Curt,
Is on my todo list for tomorrow (friday) since I saw Melchior's patch.
Greetings
Mathias
On Dienstag 04 Oktober 2005 20:52, Curtis L. Olson wrote:
For what it's worth, I don't like this patch. It shouldn't make much
difference on 24/32 bit cards, which is probably most everyone now
anyway, but I think there is a different problem brewing somewhere.
I haven't had time to look into it, but the AGL reading on the HUD no
longer reads correctly. Somewhere along the lines we have introduced
some sort of height above ground bugs. I don't know if that is in the
ground cache code or elsewhere, but the HUD above ground display isn't
working right anymore.
If we get that problem fixed so the system knows the correct AGL, then
we wouldn't need to make this particular huge hack 5 times worse.
Somehow the gear still knows where the ground is, but I recall specific
patches to the individual FDM's. I've lost track of what is going on
with this section of code, but it's important and it really should get
fixed before we get too much further!
I'm going out of town on thursday and rushing to get a bunch of other
stuff done in the mean time, so I really can't look at this in the near
term, but someone really needs to volunteer to step up and track down
what is going on here.
Regards,
Curt.
Melchior Franz wrote:
Update of /var/cvs/FlightGear-0.9/FlightGear/src/Main
In directory baron:/tmp/cvs-serv754
Modified Files:
renderer.cxx
Log Message:
prevent view through big hole in carrier deck
Index: renderer.cxx
===
RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Main/renderer.cxx,v
retrieving revision 1.27
retrieving revision 1.28
diff -C2 -r1.27 -r1.28
*** renderer.cxx 1 Oct 2005 09:56:53 - 1.27
--- renderer.cxx 4 Oct 2005 18:01:45 - 1.28
***
*** 499,503
- cur_fdm_state-get_Runway_altitude_m();
! if ( agl 10.0 ) {
scene_nearplane = 10.0f;
scene_farplane = 12.0f;
--- 499,503
- cur_fdm_state-get_Runway_altitude_m();
! if ( agl 50.0 ) {
scene_nearplane = 10.0f;
scene_farplane = 12.0f;
___
Flightgear-cvslogs mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-cvslogs
2f585eeea02e2c79d7b1d8c4963bae2d
--
Mathias Fröhlich, email: [EMAIL PROTECTED]
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS: FlightGear/src/Main renderer.cxx, 1.27, 1.28
On Dienstag 04 Oktober 2005 22:17, Melchior FRANZ wrote: * Curtis L. Olson -- Tuesday 04 October 2005 22:02: You've been granted CVS commit access so use your best judgement. Yes. I don't usually touch such things, because I don't understand much of this. I did it anyway, because: - this change was already in cvs since a great while, and only had been reverted recently - the commit log of the reverting patch didn't explain why this was reverted; it was part of a completely different change and looked like an accident Well, I reverted. Just because, as it was introduced the first time it was a workaround for something, at this time, hard to fix. At that time, the renderer had a different understanding of ground level than the gear code. I changed that at some time and removed the workaround. I thought that it was clear that it was a workaround, and I silently restored the old, more correct, behavour. Greetings Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] RFC: FlightGear 0.9.9
On Montag 03 Oktober 2005 13:35, Melchior FRANZ wrote: (A) will a new official plib release be required? The current plib cvs contains a fix for a crash occuring with joysicks with more than 16 (?, I believe) axis on Linux. I would vote for a next plib release. (B) which bugs need to be fixed (and by whom :-)? - The AGL/Carrier hole problem discussed in an other thread. ... assigned to me :) Greetings Mathias -- Mathias Fröhlich, email: [EMAIL PROTECTED] ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] A little update to the A380 from me, as well as a little request.
Hello, As some of you may know, I have been working on the A380's cockpit for the past few months. Since my work has been commited to the CVS, I decided to show you guys a screenshot of my progress so far: http://www.students.yorku.ca/~ampere/fgfs-screen-005.jpg As you can see, a few components are still missing, so there is quite a bit of work ahead before the cockpit can be considered as finished. Notably, the sidesticks are missing; as do the throttles, some instruments on the front panel, the seats for the pilots... and the textures (glow, no glow, and in-between). Since I have been quite busy lately, I want to concentrate my work on the scripting aspect of the A380. Thus, it would be nice if people can volunteer to fill in the missing pieces. AJ has already been working on the sidesticks, but it will be nice if there are a few more volunteers. =P Thank you, Ampere ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] A little update to the A380 from me, as well as a little request.
On Friday 07 Oct 2005 01:25, Ampere K. Hardraade wrote: Hello, As some of you may know, I have been working on the A380's cockpit for the past few months. Since my work has been commited to the CVS, I decided to show you guys a screenshot of my progress so far: http://www.students.yorku.ca/~ampere/fgfs-screen-005.jpg As you can see, a few components are still missing, so there is quite a bit of work ahead before the cockpit can be considered as finished. Notably, the sidesticks are missing; as do the throttles, some instruments on the front panel, the seats for the pilots... and the textures (glow, no glow, and in-between). Since I have been quite busy lately, I want to concentrate my work on the scripting aspect of the A380. Thus, it would be nice if people can volunteer to fill in the missing pieces. AJ has already been working on the sidesticks, but it will be nice if there are a few more volunteers. =P Thank you, Ampere I'll try modelling a few bits and bobs if that'll help. Texturing isn't really my forte and I've still got to do the MiG-15... LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
