[Flightgear-devel] New Files
HI all I have temporarily placed three tarballs at my site http://www.vso.cape.com/~nhv/files/fgfs 1) fgfs_exe.tgz24-Mar-2002 14:41 1.6M Current MingW32 executable that includes my patches below This runs on Win2k no gaurantees on anything else :-) 2) nhv_032402.tgz 24-Mar-2002 14:4139k cockpit.cxx - minor tweaks for HUD hud.cxx -- tweak for elevator trim gague to be displayed on HUD main.cxx -- effectively removed fgReshape() from the Main loop model.cxx -- major matrix simplification viewer.cxx -- matrix simplification and a fix for keyboard TILT viewmgr.cxx -- simplifications Note I consider none of these to be in 'final form' and can help integrate them more cleanly if desired however what is there should be easily adaptable to what ever 'style' the maintainer desires if they choose to incorporate any of the above Except for the 2 viewer files which should be considered one patch the other files all stand on their own and can be individulally added 3) nhv_hud.tgz 24-Mar-2002 14:41 1k Huds / Instruments / Default / hudcard.xml Huds / Instruments / Minimal / hudcard.xml Implementation of elevator trim gauge on HUD and minor tweaks to various tick marks Enjoy Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] New Files
Norm, Your viewer/model work looks great. I've been doing some major work in there myself the last few days and what you've done will fit in well. If it's ok with you, I'd like to merge them in with what I've got over the next couple days. Currently where I am at is I've removed a ton of junk and cleaned up the viewer class quite a bit. Also I've got the 3d cockpit so it looks real now and fixed a couple other minor glitches. So I might submit that tonight, or I can hold off and merge in these optimizations and submit in a day or two. What do folks think? Actually, on this matrix topic, been thinking about whether we should just build a few optimized routines (for 3x3 work) into simgear. It would be good to move all the custom matrix manipulators out to simgear (was it you that suggested this last week?) so that both the model and the viewer code can use them. My thinking now is that the viewer code needs to be only concerned with the view (ie the eyepoint and vector) and the model code needs to be it's own class with its own data. This is an issue that needs to be addressed for building multiple model instances. Best, Jim Norman Vine [EMAIL PROTECTED] said: HI all I have temporarily placed three tarballs at my site http://www.vso.cape.com/~nhv/files/fgfs 1) fgfs_exe.tgz24-Mar-2002 14:41 1.6M Current MingW32 executable that includes my patches below This runs on Win2k no gaurantees on anything else :-) 2) nhv_032402.tgz 24-Mar-2002 14:4139k cockpit.cxx - minor tweaks for HUD hud.cxx -- tweak for elevator trim gague to be displayed on HUD main.cxx -- effectively removed fgReshape() from the Main loop model.cxx -- major matrix simplification viewer.cxx -- matrix simplification and a fix for keyboard TILT viewmgr.cxx -- simplifications Note I consider none of these to be in 'final form' and can help integrate them more cleanly if desired however what is there should be easily adaptable to what ever 'style' the maintainer desires if they choose to incorporate any of the above Except for the 2 viewer files which should be considered one patch the other files all stand on their own and can be individulally added 3) nhv_hud.tgz 24-Mar-2002 14:41 1k Huds / Instruments / Default / hudcard.xml Huds / Instruments / Minimal / hudcard.xml Implementation of elevator trim gauge on HUD and minor tweaks to various tick marks Enjoy Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] New Files
Hi all I have temporarily placed a fourth tarball at my site in addition to the earlier 3 http://www.vso.cape.com/~nhv/files/fgfs 1) fgfs_exe.tgz24-Mar-2002 21:51 1.6M Current MingW32 executable that includes my patches below including the new Mouse code This runs on Win2k no gaurantees on anything else :-) 2) nhv_032402.tgz 24-Mar-2002 14:4139k cockpit.cxx hud.cxx main.cxx model.cxx viewer.cxx viewmgr.cxx 3) nhv_hud.tgz 24-Mar-2002 14:41 1k hud xml files implementing a elevator trim gauge 4) mouse_022402.tgz24-Mar-2002 21:3913k These files finish the job of removing the quat from the Mouse code Note not all of the features of the old mouse are reinstated yet but most of them are and I will work on the remaining ones gui_local.hxx gui_local.cxx gui.cxx mouse.cxx Makefile.am Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] New Files
Jim Wilson writes: Actually, on this matrix topic, been thinking about whether we should just build a few optimized routines (for 3x3 work) into simgear. It would be good to move all the custom matrix manipulators out to simgear (was it you that suggested this last week?) so that both the model and the viewer code can use them. Since these routines only run once or twice per iteration of the loop They really don't have to be 'super optimized' and I think my method of handling them as 3x3 and just filling in the 4th row and column by 'inspection' is probably good enough. Where these routines help is that I 'know' somethings about each of the matrices ahead of time that I take advantage of that a general purpose 3x3 set of routines would not be able to do. That said I am all for separating the math from the properties interface as much as possible and I think that we could probably create a 'number crunching core' SimGear 'Viewer' that was passed only numbers from the FlightGear 'Viewer' that provided the properties Interface to FGFS This SimGear Viewer would make it easier for other programs to interface to the FGFS scenery esp if and when we move the tile manager code to SimGear Cheers Norman ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] New Files
Norman Vine [EMAIL PROTECTED] said: Since these routines only run once or twice per iteration of the loop They really don't have to be 'super optimized' and I think my method of handling them as 3x3 and just filling in the 4th row and column by 'inspection' is probably good enough. Yes that's what I was noticing. What I was speculating is that there might be a way to consolidate by either passing a Vec3 or Vec4 as a parameter, but to be honest I haven't taken the time to compare the details of the various matrix functions. Probably what your doing is most efficient! That said I am all for separating the math from the properties interface as much as possible and I think that we could probably create a 'number crunching core' SimGear 'Viewer' that was passed only numbers from the FlightGear 'Viewer' that provided the properties Interface to FGFS Makes sense. It might want to be called ViewMath or something like that. It's got to go somewhere so that models can maintain their own position and rotation data (I mean for the model body itself, not the animations that are already there). Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] new files
The current version of JSBSim in JSBSim CVS is now completely syncronized with several bugs squashed. The intense efforts of the FlightGear and the extended JSBSim team have given us a new vehicle to fly, the Cessna 310. As David Megginson mentioned in his release announcement, there are still a few quirks. I have a complete NASA report on the aerodynamics of an aircraft which - if it is not the Cessna 310 - is very close to it. I will be supporting the addition of this data where applicable into the model as David, Tony, and others refine it. There are a few JSBSim bugs still remaining for the multi-engine model, but it is quite flyable as I am told. Curt: Can you grab the latest stuff from JSBSim CVS and place it into the FGFS CVS? And also, John, can you grab the latest and place the aircraft models into the appropriate Aircraft/* directories? The config file version identifiers have been change inside these files and they need to be placed in the proper repositories simultaneously. If there is a better way to distribute these files to both of you (Curt and John) let me know. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
