[Flightgear-devel] UIUC compile problem
Hi, When trying to compile the latest UIUC code I got the following error for about a hundred times: ../../../../src/FDM/UIUCModel/uiuc_menu.cpp, line 3399: error(1133): expression must be a modifiable lvalue Cnfabetaf_nAlphaArray[Cnfabetaf_index] = datafile_nxArray; It seems like the compile can't hanle the following: int x[10][100]; int y[100]; x[0] = y; ... Does anybody have any idea of how to solve this?? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] C172 3D Model
David Megginson [EMAIL PROTECTED] said: For those who didn't read my long post about PLIB problems, there is now a new C172 3D model in the base-package CVS, including the much-requested translucent propeller disk for high RPM. Unfortunately, to see the model correctly, you will have to patch your local plib source tree to fix the AC3D loader. Here are the two (small) patches against the latest plib CVS: http://www.megginson.com/flightsim/plib-smoothing.dif http://www.megginson.com/flightsim/plib-transparency.dif Without these patches, the model is unsmoothed, and the propeller disk and windows are opaque. David, This model is really looking great! Did you try just a flat pie disk for the prop blurr? Wondering if it'd work that way. One of these days I have to get blender fired up and do some experimenting with the cessna U-3a model. Have you tried converting the other way (ac3d to blender)? Best, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] glass cockpit
What's the status of OpenGC integration with FlightGear? I have a thought in mind for something it might be used for, and I might be interested in trying it out. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] UIUC compile problem
Robert Deters wrote: Does anybody have any idea of how to solve this?? Erik What are you using to compile it? It compiles fine with gcc version 2.96 under Redhat 7.1. If i change uiuc_menu.cpp (line 1412) CXfabetaf_aArray[CXfabetaf_index] = datafile_xArray; CXfabetaf_betaArray[CXfabetaf_index] = datafile_yArray; CXfabetaf_CXArray[CXfabetaf_index] = datafile_zArray; CXfabetaf_nAlphaArray[CXfabetaf_index] = datafile_nxArray; CXfabetaf_nbeta[CXfabetaf_index] = datafile_ny; to: CXfabetaf_aArray[CXfabetaf_index][0][0] = datafile_xArray[0][0]; CXfabetaf_betaArray[CXfabetaf_index][0] = datafile_yArray[0]; CXfabetaf_CXArray[CXfabetaf_index][0][0] = datafile_zArray[0][0]; CXfabetaf_nAlphaArray[CXfabetaf_index][0] = datafile_nxArray[0]; CXfabetaf_nbeta[CXfabetaf_index] = datafile_ny; it works, but I doubt this is th intention of the code. :-( BTW, what *is* the intention of the code, assigning pointers, copying one entry, or copying the complete table? Erik ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] UIUC compile problem
- Original Message - From: Erik Hofman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, April 02, 2002 1:53 PM Subject: Re: [Flightgear-devel] UIUC compile problem Robert Deters wrote: Does anybody have any idea of how to solve this?? Erik What are you using to compile it? It compiles fine with gcc version 2.96 under Redhat 7.1. If i change uiuc_menu.cpp (line 1412) CXfabetaf_aArray[CXfabetaf_index] = datafile_xArray; CXfabetaf_betaArray[CXfabetaf_index] = datafile_yArray; CXfabetaf_CXArray[CXfabetaf_index] = datafile_zArray; CXfabetaf_nAlphaArray[CXfabetaf_index] = datafile_nxArray; CXfabetaf_nbeta[CXfabetaf_index] = datafile_ny; to: CXfabetaf_aArray[CXfabetaf_index][0][0] = datafile_xArray[0][0]; CXfabetaf_betaArray[CXfabetaf_index][0] = datafile_yArray[0]; CXfabetaf_CXArray[CXfabetaf_index][0][0] = datafile_zArray[0][0]; CXfabetaf_nAlphaArray[CXfabetaf_index][0] = datafile_nxArray[0]; CXfabetaf_nbeta[CXfabetaf_index] = datafile_ny; it works, but I doubt this is th intention of the code. :-( BTW, what *is* the intention of the code, assigning pointers, copying one entry, or copying the complete table? Erik The purpose is to copy the complete table. What I have in uiuc_menu is just a short cut instead of writing a bunch of for loops to copy multiple dimension arrays. But since it looks like this doesn't work for all compilers, I guess I be writing some for loops. Rob ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] UIUC compile problem
So Robert Deters says: BTW, what *is* the intention of the code, assigning pointers, copying one entry, or copying the complete table? Erik The purpose is to copy the complete table. What I have in uiuc_menu is just a short cut instead of writing a bunch of for loops to copy multiple dimension arrays. But since it looks like this doesn't work for all compilers, I guess I be writing some for loops. Rob Can you do a memcpy(), or isn't that supported on all architectures? Groeten,- Jacco -- Think about it: | In Real Life: Jacco van Schaik If the wheel had never been | Mail me at: [EMAIL PROTECTED] reinvented, we'd still be | Spam bait:postmaster@localhost driving on logs...| See also http://www.frontier.nl/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Car Model
I'm working on an automotive simulator, http://vamos.sourceforge.net A while ago, Curt suggested that I try to make my car model work with FlightGear. I'd like to start working on that now, but I don't know where to begin. Could somebody give me some tips on adding a vehicle model to FlightGear? Thanks. Sam ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Car Model
On 02 Apr 2002 15:45:18 -0500 Sam Varner [EMAIL PROTECTED] wrote: I'm working on an automotive simulator, http://vamos.sourceforge.net A while ago, Curt suggested that I try to make my car model work with FlightGear. !! I'd like to start working on that now, but I don't know where to begin. Could somebody give me some tips on adding a vehicle model to FlightGear? Thanks. You might start by looking at the ground dynamics / landing gear modeling code in the various FDMs (flight dynamics model). In JSBSim this would be FGGroundReactions.[cpp|h] and FGLGear.[cpp|h]. You should look at YASim and LaRCSim code, as well, to get the widest exposure to how ground reactions are modeled. Off the top of my head, after first being a bit clueless on where to start, I'd suggest that you ought to be able to get pretty far pretty fast in JSBSim by merely specifying in a config file an aircraft that had very poor aerodynamics ;-) Theoretically, this shouldn't be too hard to get a start with. The same is probably true with YASim, I'm sure Andy will direct you how to do this with YASim. One of the problems we face with JSBSim (and which I haven't had time to deal with, yet) is that ground reactions can be a little tricky. Maybe a driving sim will pay enough special attention to that aspect of modeling that you can help us out with your time. Jon Berndt Coordinator, JSBSim Project http://jsbsim.sf.net ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] US/CA differences
Here's an interesting document on differences between flying in the US and Canada, written from a Canadian perspective: http://www.ofc.ca/files/cdn_us.pdf All the best, David -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] C172 3D Model
Jim Wilson writes: This model is really looking great! Thanks. Did you try just a flat pie disk for the prop blurr? I thought it would be nice for the prop to be visible from the side, so I gave it a little depth (just enough to cover the blade tips). Wondering if it'd work that way. One of these days I have to get blender fired up and do some experimenting with the cessna U-3a model. Have you tried converting the other way (ac3d to blender)? I've had pretty good success importing AC3D into Blender using Willian Germano's Python scripts. I don't remember if texture info survives import, though. All the best, David -- David Megginson [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] glass cockpit
What's the status of OpenGC integration with FlightGear? I have a thought in mind for something it might be used for, and I might be interested in trying it out. The network interface is alive and well. ( it is sync'd with the latest CVS version of FG ) The FMC is in the shop for a major overhaul. The display code builds and runs under linux. Limited checks and tests for required libraries. Requires new freetype and ftgl libraries. URLs provided with download package. Gauges are functional but incomplete - some pieces/symbols under development. The sourceforge CVS has been replaced. New site: cvs -d:pserver:[EMAIL PROTECTED]:/opengc Password is : opengccvs No apologies, just a warning. There is no documentation ATM, but the email channel is open... Regards JW ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Error running flightgear
Latest CVS simgear/flightgear/base compiles OK but crashes when running: Initializing FGLocalWeatherDatabase - Initialising spherical interpolator. [100%] Finished initialising spherical interpolator. out of memory The computer has plenty (512M) physical memory. Any ideas? Cheers - Dave -- [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Error running flightgear
D Luff wrote: Latest CVS simgear/flightgear/base compiles OK but crashes when running: Initializing FGLocalWeatherDatabase - Initialising spherical interpolator. [100%] Finished initialising spherical interpolator. out of memory The computer has plenty (512M) physical memory. Any ideas? I doubt that it's caused in the WeatherCM code. But I can't be sure, as there were major changes behind the scenes that might create such a behaviour. Can you run FGFS again and have a look at the memory consumption? I'm interested in the changes from the [ 0%] to the [100%] mark. CU, Christian -- The idea is to die young as late as possible.-- Ashley Montague Whoever that is/was; (c) by Douglas Adams would have been better... ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Simgear w/OpenGC question
Hi all, Some time back John started using Simgear in OpenGC to form the basis for our local nav database. Although this works fine under Cygwin and Linux, until recently I had problems with it under Windows. The problem turned out to be the following: The two libraries that OpenGC links with, besides Simgear, are FTGL and Freetype 2.06. Under Windows, both of these are set to build with the /MD (multithreaded DLL) compiler option. Simgear is set to build with the /ML (single-threaded) libraries. Linking with both of these simultaneously was causing more than a few linker errors (OpenGC was set up to link using /MD as well). Without Simgear, everything worked fine. By rebuilding FTGL and OpenGC with the /ML library flag, everything seems happy. Although there are no immediate plans to support multithreading in OpenGC, it would be more convenient to Windows users if they did not have to modify the build process in order to allow compatibility with Simgear. Any Windows/Simgear gurus out there have any suggestions? Thanks, -Damion- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Error running flightgear
Christian Mayer wrote: I doubt that it's caused in the WeatherCM code. Hi Christian, I don't think its in the WeatherCM either. On my development copy which worked until I did a cvs update only in the ATC directory I'm getting to: Initializing FGLocalWeatherDatabase - Initialising spherical interpolator. [100%] Finished initialising spherical interpolator. Registering event: weather update Loading Navaids VOR/NDB ILS and Marker Beacons Fixes ATIS out of memory This has Melchior's bug fixes applied only to atislist.cxx but *not* navlist.cxx, wheras in my 'clean' version on which I ran cvs update on the whole tree navlist.cxx also has his patches and probably dies there before the last bit of console output gets flushed. Does anyone know how I can revert to a previous version or date of specific files using CVS in order to test this? Cheers - Dave -- [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: ..yawed OpenGL on 8 MB ATI mach64, was: [Flightgear-devel] Re: framerate
From: Alex Perry [EMAIL PROTECTED] I don't know whether the IIC has the Pro feature set (suspect not). If it does, the Mach64 driver of Utah-GLX works fine for me. You might want to have a look at recent DRI development. I'm following this already for a while and it appears to me that the guys got quite far with implementing DRI for Mach64, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Error running flightgear
D Luff wrote: dies there before the last bit of console output gets flushed. Does anyone know how I can revert to a previous version or date of specific files using CVS in order to test this? OK, I can now confirm that the latest 'bug fixes' to ilslist, fixlist, navlist and atislist.cxx are crashing Flightgear on Windows. Can I request that the changes get rolled back out of the official CVS until this is resolved please, especially since they fix only valgrind/compiler warnings rather than user-visible bugs. Melchior, don't take this the wrong way, I appreciate what you're doing, but in this case somewhere along the line something is going pear- shaped. Cheers - Dave -- [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Error running flightgear
D Luff writes:
OK, I can now confirm that the latest 'bug fixes' to ilslist,
fixlist, navlist and atislist.cxx are crashing Flightgear on
Windows. Can I request that the changes get rolled back out of the
official CVS until this is resolved please, especially since they
fix only valgrind/compiler warnings rather than user-visible bugs.
Melchior, don't take this the wrong way, I appreciate what you're
doing, but in this case somewhere along the line something is going
pear- shaped.
Unfortunately, I am able to test Melchior's changes only under Linux.
I have no objection to rolling them back out, but it would also be
useful to find out what part of them is causing the Windows problems,
so we know what to avoid in future patches. If any Windows user has
15 or 30 minutes to spare with gdb, I'll be very grateful.
For the record, here are the changes in atislist.cxx from 1.3 to 1.4
(current CVS):
Index: atislist.cxx
===
RCS file: /var/cvs/FlightGear-0.7/FlightGear/src/ATC/atislist.cxx,v
retrieving revision 1.3
retrieving revision 1.4
diff -c -r1.3 -r1.4
*** atislist.cxx1 Mar 2002 16:39:52 - 1.3
--- atislist.cxx30 Mar 2002 11:50:30 - 1.4
***
*** 47,53
// load the navaids and build the map
bool FGATISList::init( SGPath path ) {
- FGATIS a;
atislist.erase( atislist.begin(), atislist.end() );
--- 47,52
***
*** 59,112
// read in each line of the file
! in skipeol;
in skipcomment;
! #ifdef __MWERKS__
char c = 0;
! while ( in.get(c) c != '\0' a.get_type() != '[' ) {
in.putback(c);
- in a;
- if ( a.get_type() != '[' ) {
- atislist[a.get_freq()].push_back(a);
- }
- in skipcomment;
- }
-
#else
!
! double min = 10;
! double max = 0;
!
! while ( ! in.eof() a.get_type() != '[' ) {
in a;
! //cout id = a.get_ident() endl;
! //cout type = a.get_type() endl;
! //cout lon = a.get_lon() endl;
! //cout lat = a.get_lat() endl;
! //cout elev = a.get_elev() endl;
! //cout freq = a.get_freq() endl;
! //cout range = a.get_range() endl;
! if ( a.get_type() != '[' ) {
! atislist[a.get_freq()].push_back(a);
! }
in skipcomment;
! if ( a.get_type() != 'N' ) {
if ( a.get_freq() min ) {
min = a.get_freq();
}
if ( a.get_freq() max ) {
max = a.get_freq();
}
! }
}
// cout min freq = min endl;
// cout max freq = max endl;
-
- #endif
return true;
}
--- 58,106
// read in each line of the file
! // in skipeol;
in skipcomment;
! // double min = 10;
! // double max = 0;
+ #ifdef __MWERKS__
char c = 0;
! while ( in.get(c) c != '\0' ) {
in.putback(c);
#else
! while ( ! in.eof() ) {
! #endif
!
! FGATIS a;
in a;
! if ( a.get_type() == '[' ) {
! break;
! }
!
! /* cout id = a.GetIdent() endl;
! cout type = a.get_type() endl;
! cout lon = a.get_lon() endl;
! cout lat = a.get_lat() endl;
! cout elev = a.get_elev() endl;
! cout freq = a.get_freq() endl;
! cout range = a.get_range() endl endl; */
!
! atislist[a.get_freq()].push_back(a);
in skipcomment;
! /* if ( a.get_type() != 'N' ) {
if ( a.get_freq() min ) {
min = a.get_freq();
}
if ( a.get_freq() max ) {
max = a.get_freq();
}
! } */
}
// cout min freq = min endl;
// cout max freq = max endl;
return true;
}
All the best,
David
--
David Megginson
[EMAIL PROTECTED]
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Re: Configurable mouse ready to go
Is it possible (under Unix/Linux) to run fgfs directly from a console and let it access the DRI? http://fbdri.sourceforge.net/ ATI Radeon only, I might have a try some time, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Runway numbers: leading zero
[... Erik wrote ...] Alex Perry wrote: In Britain, as far as I know, we always use two-digit numbers Nope, not in the US. Dunno about elsewhere. I think it's the same in Europe as it is in Brittain. Right - seen this last week at EDWJ, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] UIUC compile problem
From: Erik Hofman [EMAIL PROTECTED] When trying to compile the latest UIUC code I got the following error for about a hundred times: [...] What are you using to compile it? It compiles fine with gcc version 2.96 under Redhat 7.1. Erik an I are the ones that form the SGI group in this project. Erik's doing the work and I benefit from him dealing with portability issues ;-) Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Error running flightgear
D Luff wrote: I've now found that its definately only atislist.cxx that is crashing, not navlist, ilslist or fixlist.cxx. Its quite possible that something that Melchior has done has uncovered a latent bug that previously wasn't triggered. I'll have a look, albeit with couts rather than gdb. OK, here's the problem. Melchior's patches are fine - leave them in. In my default.atis I have a comment line at the start - this started with // but looking at simgear/misc/stream.hxx I see it needs to start with # This fixes it. However, default.nav and default.ils both start their comments with // (where I copied it from !) so I don't know how they get away with it and default.atis doesn't. Cheers (and apologies Melchior) - Dave -- [EMAIL PROTECTED] ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: RE: Re: [Flightgear-devel] JSBSim Body Axes question
The definition of a positive aileron deflection is when the right-hand aileron deflects according to the right hand rule - that is, trailing edge down (TED). Unfortunately, this results in a negative roll rate - it would be nice if our choice of coordinate system caused a positive aileron deflection to result in a positive roll rate, but this is not the case. :-( Anyhow, yes, Tony wanted to control each aileron individually, so this was changed. It *should* *be* the same to you and I. It's just that the left aileron will get the negative of the right aileron deflection. A control system *could* use the ailerons as flaps AND as ailerons. These are called flaperons. The space shuttle uses the wing outer control surfaces as ailerons and elevator. These are called elevons. You might also combine flaps, spoilers, ailerons, and elevator and call it a slapevon. Well ... maybe not. ;-) In any case, Tony was right to split out the left and right aileron controls because we might want to model an aircraft that addresses various control surfaces in unique and interesting ways. Jon Yes, It is necessary to control the ailerons separately for widely use. I just found that a positive aileron pos result in a positive roll rate -- the JSBSim version is downloaded 2 weeks ago. It run with C172 model. and I did a little change. If you can be sure that positive aileron pos would result in nagative roll rate, that must be my matter. Let me check it . thank you for your patience. ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Quick question for tower view
Is there a simgear or plib function that I can use to get the angle between two locations? Namely the angle of direction from eye (lon, lat, alt) to aircraft (target_lon, target_lat, target_alt). For example in our current chase view the angle would be the heading since we are always following the plane. In tower view I need to calculate the angle to the plane (which actually will be the way all lookat views work when I am done). Thanks, Jim ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Quick question for tower view
Jim Wilson writes: Is there a simgear or plib function that I can use to get the angle between two locations? Namely the angle of direction from eye (lon, lat, alt) to aircraft (target_lon, target_lat, target_alt). For example in our current chase view the angle would be the heading since we are always following the plane. In tower view I need to calculate the angle to the plane (which actually will be the way all lookat views work when I am done). There's a lot of ways to skin a cat. libGLU provides a function (and I think ssg gives you access to it) that allows you to specify the view point, the target look at point and an up vector. Otherwise, depending on the level of accuracy you need, have a look at simgear/math/sg_geodesy.hxx, look at the *wgs_84() functions. In simgear/math/polar3d.hxx there are functions to do the same sort of thing, but use a simpler spherical model. 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
[Flightgear-devel] UIUC compile problem
I just updated to the newest uiuc_menu.cpp and am still getting the compile problem, but far fewer instances. MSVC error is: c:\flightgear\src\fdm\uiucmodel\uiuc_menu.cpp() : error C2106: '=' : left operand must be l-value on the following lines: 1454, 1506, 1558, 1927, 1979, 2031, 2300, 2352, 2404, 2614, 2666, 2718, 2770, 2822, 3020, 3072, 3124, 3176, 3228, 3438, 3490, 3542, 3594, 3646 Thanks! Jonathan Polley
Re: [Flightgear-devel] Quick question for tower view
Jim Wilson wrote: Is there a simgear or plib function that I can use to get the angle between two locations? I doubt there's explicit API support anywhere, but it's pretty easy to do by hand. Just exploit the fact that the dot product of two unit vectors is the cosine of the angle between them: // Needless to say, from memory and untested! sgNormalizeVec3(v1); sgNormalizeVec3(v2); float angle = arccos(sgScalarProductVec3(v1, v2)); The eager optimizer (Norman :) might note that you could shave a few cycles here by doing the dot product first, and then doing the scaling together to eliminate a division an a sqrt. Andy -- Andrew J. RossNextBus Information Systems Senior Software Engineer Emeryville, CA [EMAIL PROTECTED] http://www.nextbus.com Men go crazy in conflagrations. They only get better one by one. - Sting (misquoted) ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
RE: [Flightgear-devel] Quick question for tower view
Jim Wilson wrote: Is there a simgear or plib function that I can use to get the angle between two locations? SG has some basic code see PLib / src / sg / sgAngleBetweenVec3() and assosciated funcs ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Error running flightgear
D Luff writes: D Luff wrote: I've now found that its definately only atislist.cxx that is crashing, not navlist, ilslist or fixlist.cxx. Its quite possible that something that Melchior has done has uncovered a latent bug that previously wasn't triggered. I'll have a look, albeit with couts rather than gdb. OK, here's the problem. Melchior's patches are fine - leave them in. In my default.atis I have a comment line at the start - this started with // but looking at simgear/misc/stream.hxx I see it needs to start with # This fixes it. However, default.nav and default.ils both start their comments with // (where I copied it from !) so I don't know how they get away with it and default.atis doesn't. Cheers (and apologies Melchior) - Dave It looks like the code to load the nav and ils data automatically dump the entire first line, no matter what it contains. The corresponding code has been commented out of the atis loader code ... that's probably what is happening to you. 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] Simgear w/OpenGC question
Damion Shelton wrote: Hi all, Some time back John started using Simgear in OpenGC to form the basis for our local nav database. Although this works fine under Cygwin and Linux, until recently I had problems with it under Windows. The problem turned out to be the following: The two libraries that OpenGC links with, besides Simgear, are FTGL and Freetype 2.06. Under Windows, both of these are set to build with the /MD (multithreaded DLL) compiler option. Simgear is set to build with the /ML (single-threaded) libraries. Linking with both of these simultaneously was causing more than a few linker errors (OpenGC was set up to link using /MD as well). Without Simgear, everything worked fine. By rebuilding FTGL and OpenGC with the /ML library flag, everything seems happy. Although there are no immediate plans to support multithreading in OpenGC, it would be more convenient to Windows users if they did not have to modify the build process in order to allow compatibility with Simgear. Any Windows/Simgear gurus out there have any suggestions? Its trivial to recompile SimGear multithreaded (/MT). I can make this the default since it is the also the default for plib and metakit. Note that SimGear cannot be compiled as a DLL. Bernie ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Re: [Flightgear-devel] Simgear w/OpenGC question
Ok, I tried doing that (I thought), though with /MD rather than /MT, and still got linker errors. As I understand it the distinction is that the former links against the DLL version of the std libs while the latter links statically - is that true?. I'll give /MT a try and see if it works. -Damion- Its trivial to recompile SimGear multithreaded (/MT). I can make this the default since it is the also the default for plib and metakit. Note that SimGear cannot be compiled as a DLL. Bernie ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
