Re: [Flightgear-devel] CVS compiling error
David Luff wrote: Cygwin doesn't have HUGE, so change HUGE to HUGE_VAL and -HUGE to -HUGE_VAL and I suspect this should compile. Ok, I've committed a fix. I guess that we could do something in compiler.h along the lines of #ifdef __CYGWIN__ #define HUGE HUGE_VAL #define -HUGE -HUGE_VAL #endif or something like that. Erik? There is already an instance of this problem in TerraGear. Maybe someone has to convince the Cygwin developers to add it to the appropriate header files instead? I've seen several projects that have to make special cases just for this. It's better fixed at the root of the problem. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS compiling error
David Luff wrote: Fair point. Do you know if HUGE is part of a standard anywhere that definately should be supplied by Cygwin, or is it simply available from everyone else by unwritten convention? According to the IRIX header file it would be an ANSI definition. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Problems with 'V' (backwards view) on Mac os X
[Flightgear-devel] Problems with 'V' (backwards view) on Mac os X Lee Elliott leee at spatial.freeserve.co.uk Wed Oct 19 22:00:29 CDT 2005 Previous message: [Flightgear-devel] Problems with 'V' (backwards view) on Mac os X Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] On Thursday 20 Oct 2005 03:31, Ima Sudonim wrote: On Thursday 20 Oct 2005 01:10, Ima Sudonim wrote: Hi, Someone else had mentioned something similar recently, but I can't find the post in flightgear-devel. I noticed that with latest CVS on mac os x, I can scroll thru views (forward) with 'v' as many times as I like, but that 'V' (reverse) only works 1-3 times until I reach the view that has a name ending in 'w/o yaw'. 'V' will no longer work, until I move forward in the views with 'v' at least once. Then the 'V' cycle works (or fails to work) as mentioned above. Thanks! Ima Have you found this with several different aircraft or have you only tried a single type so far? If it only happens with a specific aircraft, which one is it? LeeE I was using the default cessna (didn't give --aircraft= option) (it's the chase view w/o yaw option, where the problem occurs in all instances with reverse view). DOES happen with default cessna, sopwithCamel, spitfireIIa, 747-100, ufo, Citation-II, A380, shuttle (gave a 'failed to load aircraft from, falling back to glider.ac' message, ornithopter (BTW, the ornithopter is already moving forward when fg starts, unlike the other airplane models), bell206 DOESN'T happen with A-10cl (my personal favorite) 8-) or A-10fl (there is no chase view w/o yaw option) Hope this helps! Thanks! Ima Heh ;) I don't mind top or bottom replies but sticking them in the middle throws me a bit. Anyway... I can't find any problems here - cvs a day or two old - I tried just calling fgfs with no params, to get the C-172, and could scroll backwards and forwards through the views ok. Cycled forward to chase w/o yaw, cycled backwards from it - no problems. Then tried both the A-10s, because you mention that they had no chase view w/o view and had no problems there either, including the chase view w/o yaw. Do you get a 'Drop View' with the A-10s? The Drop view should be the 'last' view on the A-10s, before you end up back in the Cockpit and should come after the chase view w/o yaw. Do you get both the chase view w/o yaw and drop view on the A-10s? LeeE Lee, thank you for your interest and suggestions... Sorry, I tend to put the answer right by the question, less chance of forgetting to answer something... 8-( There is NO chase view on my A10s -- cockpit view, helicopter view, chase view above, chase view, tower view, tower view look from, drop view and then back to cockpit view -- NO chase view w/o yaw. I am using latest cvs. Calling flightgear with no --aircraft param, I see the problem: the views are -- cockpit view, helicopter view, chase view above, chase view, tower view, tower view look from, chase view wo yaw, THEN helicopter view (again, note NOT cockpit view), but if I reverse from the 2nd helicopter view, I DO get cockpit view as I would have expected, then backing up again, the screen is labled chase view wo yaw, but is really just cockpit view. Except for the first time, there is NO cockpit view moving forward with 'v', moving backward, I see cockpit view where it belongs, but 'V' stops working with a screen labelled chase view wo yaw, but that looks like cockpit view. Using --aircraft=Citation-II, I get the following views: cockpit view, helicopter view, chase view above, chase view, tower view, tower view look from, chase view wo yaw, THEN helicopter view (again, note NOT cockpit view), but if I reverse from the 2nd helicopter view, I DO get cockpit view as I would have expected, then backing up again, the screen is labled chase view wo yaw, but is really just cockpit view. Except for the first time, there is NO cockpit view moving forward with 'v', moving backward, I see cockpit view where it belongs, but 'V' stops working with a screen labelled chase view wo yaw, but that looks like cockpit view. In other words, going forward with 'v', the views are: CV, HV, CVA, CV, TV, TVLF, CVWOY, HV, CVA, CV, TV, TVLF, CVWOY, HV, CVA, CV, etc. going back with 'V' on a broken aircraft here, I'd get: CVA, HV, CVWOY (stuck at this point and 'V' doesn't work anymore until I move forward with 'v' first) The a-10s don't have CVWOY, cycling backwards or forwards, I get: CV, HV, CVA, CV, TV, TVLF, DV, CV, HV, CVA, CV, TV, TVLF, DV, CV, HV, CVA, CV, etc. So, the broken aircraft have chase view wo yaw instead of drop view and don't display the 2nd or more cockpit views going forward (after CVWOY and before helicopter view) with 'v', but will display cockpit view with 'V' (backwards), but 'V' stops working when you get to the CVWAY view, until you move
RE: [Flightgear-devel] CVS compiling error
Erik Hofman David Luff wrote: Fair point. Do you know if HUGE is part of a standard anywhere that definately should be supplied by Cygwin, or is it simply available from everyone else by unwritten convention? According to the IRIX header file it would be an ANSI definition. IRIX that is almost as compliant as MSDOS derivitaives where HUGE is a reserved word :-) This is an anachronism from mixed memory model programing on Intel Norman ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS compiling error
The same problem is present using MSYS/Mingw with 5min old cvs.. Georg Vollnhals wrote: David Luff schrieb: Cygwin doesn't have HUGE, so change HUGE to HUGE_VAL and -HUGE to -HUGE_VAL and I suspect this should compile. Changing HUGE to HUGE_VAL in simple.cxx solved the problem! Thank you, thank you :-) Have just made a testflight with the new FG version! I guess that we could do something in compiler.h along the lines of #ifdef __CYGWIN__ #define HUGE HUGE_VAL #define -HUGE -HUGE_VAL #endif I tried this *before* I did the huge-change. I put it between two other #ifdef .. (Microsoft and Borland, as far as I remember) but it caused some other strange errors. May be it was my fault to put it the wrong place or the wrong file (there are two compiler.h files in my Cygwin folder, I changed the one in the SimGear-0.3 .. folder. BTW, Georg, CVS SimGear should compile on Cygwin 3.4.4 now, and CVS FlightGear will probably compile on it if you add #ifdef HAVE_CONFIG_H # include config.h #endif as the first include for every source (cxx or cpp) file where you get the strange error message you reported a while ago. Then send the output of cvs diff -u from the FlightGear directory to Erik, and the 3.4.4 problem should be sorted :-) Ok, this has to be done when I have a little more time than this evening, but I will go for it within the next days and report so that you have some feedback. Thank you once again, David, your help saved the day for me! Regards Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Problems with 'V' (backwards view) on Mac os X, fixed (somewhat)
If I trash my preferences.xml file and go back to the default, I now get a view cycle of: cockpit view, helicopter view, chase view, tower view, tower view look from, chase view wo yaw 'v' and 'V' both work fine with the Citation-II and the default aircraft. The only difference between the two preferences files is the following diff: diff preferences.xml preferences.xml.IMA 187a188,209 nameChase View Above/name typelookat/type config from-model type=boolfalse/from-model from-model-idx type=int0/from-model-idx eye-lat-deg-path/position/latitude-deg/eye-lat-deg-path eye-lon-deg-path/position/longitude-deg/eye-lon-deg-path eye-alt-ft-path/position/altitude-ft/eye-alt-ft-path eye-heading-deg-path/orientation/heading-deg/eye-heading- deg-path at-model type=booltrue/at-model at-model-idx type=int0/at-model-idx ground-level-nearplane-m type=double0.5f/ground-level- nearplane-m x-offset-m type=double4400/x-offset-m y-offset-m type=double0/y-offset-m z-offset-m type=double-1/z-offset-m /config /view view I don't know why it makes a difference, but it does. Darn, I really liked that Chase View Above 8-( Could anyone suggest a new Chase View Above that doesn't break the view cycle via the keyboard? I find it's good for orienting myself while flying... Sorry for the false alarm. If changing views via 'v' or 'V' stop working, please check your views in data/preferences.xml! Thanks again! Ima [Flightgear-devel] Problems with 'V' (backwards view) on Mac os X Lee Elliott leee at spatial.freeserve.co.uk Wed Oct 19 22:00:29 CDT 2005 Previous message: [Flightgear-devel] Problems with 'V' (backwards view) on Mac os X Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] On Thursday 20 Oct 2005 03:31, Ima Sudonim wrote: On Thursday 20 Oct 2005 01:10, Ima Sudonim wrote: Hi, Someone else had mentioned something similar recently, but I can't find the post in flightgear-devel. I noticed that with latest CVS on mac os x, I can scroll thru views (forward) with 'v' as many times as I like, but that 'V' (reverse) only works 1-3 times until I reach the view that has a name ending in 'w/o yaw'. 'V' will no longer work, until I move forward in the views with 'v' at least once. Then the 'V' cycle works (or fails to work) as mentioned above. Thanks! Ima Have you found this with several different aircraft or have you only tried a single type so far? If it only happens with a specific aircraft, which one is it? LeeE I was using the default cessna (didn't give --aircraft= option) (it's the chase view w/o yaw option, where the problem occurs in all instances with reverse view). DOES happen with default cessna, sopwithCamel, spitfireIIa, 747-100, ufo, Citation-II, A380, shuttle (gave a 'failed to load aircraft from, falling back to glider.ac' message, ornithopter (BTW, the ornithopter is already moving forward when fg starts, unlike the other airplane models), bell206 DOESN'T happen with A-10cl (my personal favorite) 8-) or A-10fl (there is no chase view w/o yaw option) Hope this helps! Thanks! Ima Heh ;) I don't mind top or bottom replies but sticking them in the middle throws me a bit. Anyway... I can't find any problems here - cvs a day or two old - I tried just calling fgfs with no params, to get the C-172, and could scroll backwards and forwards through the views ok. Cycled forward to chase w/o yaw, cycled backwards from it - no problems. Then tried both the A-10s, because you mention that they had no chase view w/o view and had no problems there either, including the chase view w/o yaw. Do you get a 'Drop View' with the A-10s? The Drop view should be the 'last' view on the A-10s, before you end up back in the Cockpit and should come after the chase view w/o yaw. Do you get both the chase view w/o yaw and drop view on the A-10s? LeeE Lee, thank you for your interest and suggestions... Sorry, I tend to put the answer right by the question, less chance of forgetting to answer something... 8-( There is NO chase view on my A10s -- cockpit view, helicopter view, chase view above, chase view, tower view, tower view look from, drop view and then back to cockpit view -- NO chase view w/o yaw. I am using latest cvs. Calling flightgear with no --aircraft param, I see the problem: the views are -- cockpit view, helicopter view, chase view above, chase view, tower view, tower view look from, chase view wo yaw, THEN helicopter view (again, note NOT cockpit view), but if I reverse from the 2nd helicopter view, I DO get cockpit view as I would have expected, then backing up again, the screen is labled chase view wo yaw, but is really just cockpit view. Except for the first time, there is NO cockpit view moving forward with 'v',
Re: [Flightgear-devel] Re: contacting tower
Melchior FRANZ wrote: * Frank Olaf -- Wednesday 19 October 2005 10:55: I don't think that is the problem. Pressing 'v' works several times, but 'V' works only once. The entries in keyboard.xml are similar.. Which interface have you compiled fgfs with? (non-free) glut, freeglut, or SDL (./configure --enable-sdl)? Which version thereof? Whatever interface, I'd try a newer version, maybe even CVS/HEAD. Also, if you are using glut, try SDL instead, or the other way around. Is the fgfs source really CVS/HEAD (as after doing a $ cvs up -AC)? This looks too strange to suspect a FlightGear bug, but you can also try to apply the attached patch to src/Input/input.cxx. It reverses the only relevant change in keyboard handling since a while. It's not acceptable for cvs, but it would help to falsify it as possible cause. m. I have been compiling with SDL, and I do not seem to have the necessary glut libraries to try to make the switch. I am definitely compiling with the latest CVS of flightgear and simgear, and I am using the versions of SDL, pthread and such from the tarball on plausible.org/andy. Anyway, I applied your patch to today's CVS, and besides the problem with HUGE when compiling, all keys are now operating as expected, I was able to press all keys multiple times such as v/V cycled back and forth in the view is as much as I wanted :). --- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Problems with 'V' (backwards view) on Mac os X, fixed (somewhat)
* Ima Sudonim -- Thursday 20 October 2005 12:54: I don't know why it makes a difference, but it does. Darn, I really liked that Chase View Above 8-( What about also increasing the number of views in the preferences file, if you add some? number-views type=int7/number-views No idea, why we don't simply count the view nodes? Hmmm ... Please stop the annoying full-quoting (and top-posting). m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: contacting tower
* Frank Olaf -- Thursday 20 October 2005 13:03: [...] I am using the versions of SDL, pthread and such from the tarball on plausible.org/andy. Anyway, I applied your patch to today's CVS, and besides the problem with HUGE when compiling, all keys are now operating as expected, I don't know what Andy's SDL does differently from the official SDL, but the latter works for me (CVS/HEAD, at least :-). The patch reverts a bugfix, so it's rather unlikely to get into CVS. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Bug in ATC code.
Hi All, I have noticed two annoying bugs in the ATC dialog boxes. When you press ' for the first ATC dialog labelled ATC menu is displayed. (btw, Can we change that title as it's not an accurate description, perhaps ATC communication) Anyway, if you change frequencies for another ATC tower, extra lines showing :- 1. Contact tower for VFR arrival (full stop) 2. Contact tower for VFR arrival (full stop) 3. Contact tower for VFR arrival (full stop) etc, depending on how often you have switched frequencies. The other one which might be related is if you reset FlightGear (File-Reset), the state for the ATC is not reset back to the Contact tower ... dialog. Instead it will continue when you partially finished from before.. Contact tower- Report Downwind - Runway vacated. George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Two problems - 1 easy and 1 hard! - in XP using MSVC7
Hi all,
Last CVS update Oct 19.
1. The Easy fix
When trying --airport=LFPO, after downloading, and
installing the required scenery ... FG exited with -
Adding subsystem gui
fgtzfile_read(): : Invalid argument
Timezone reading failed
in the console ...
This turned out to be the usual file line ending problem ...
mine has the 'normal' WIN32 0x0d, 0x0a, ending,
and could be solved by 'fixing' the zone.tab file, or, as I
would suggest, a small 'fix' in SimGear, timezone.cxx ...
Changing the line 104, in timezone.cxx -
while (!((infoString[i] == '\t') || (infoString[i] == '\n'))) {
to a more robust, cross platform search ...
while (!((infoString[i] == '\t') || (infoString[i] == '\n') ||
(infoString[i] == '\r'))) {
and all is well ...
Looking further into this, I note that the zone.tab in the Fred B.
binary release (from fgsetup-0.9.8a.exe) is in unix format!
Then why does my CVS update file have 0x0d,0x0a? I
am sure it is unix format on the server, is it not?
I delete my local old copy (22/10/2000), and did another
update, and it returns, with 0x0d,0x0a. I have read
somewhere that some FTP clients handle, cause this
change, transparently!!! If true, another reason to
adjust the code, rather than the file each time ... ;=))
Maybe there is a CVS command to inhibit this
change, if that is where it happens ...
As part of this investigation I note that
fgInitTimeOffset(), the service that uses the information
from the zone.tab load, is called twice ... first as part of
fgInitSubsystems() (idle_state == 7), with the code comment -
fgInitTimeOffset(); // the environment subsystem needs this
and then again in idle_state == 8, with the code comments
// Initialize the time offset (warp) after fgInitSubsystem
// (which initializes the lighting interpolation tables.)
fgInitTimeOffset();
This does not cause any problem, since the loader is
quite tidy in deleting the previous allocations ...
And for those wondering why this does not occur with
the default KSFO, that particular Los_Angeles line in the
tab file has a comment, thus an extra tab, which is
discarded ...
2. The Hard find
I am getting an exception ABORT again, and again, especially
since I changed to using LFPO ... the console does not help
much, log level debug, the last lines just showing -
Unknown exception in the main loop. Aborting...
Possible cause: No error
Deleting a sample ... (written another 4 times!)
Actually this could be two different ABORTS. One is
during the start-up, before the flash fades, which I suspect
is due to one of my system.fgfsrc file 'disable' lines, and the
other is after a few, plus minutes of running ... I know not
why ...
I am still trying to track this/these down ... are any other
Windows XP SP2 - MSVC7 users getting this/these? Any
ideas welcome ... I would like to get back to smooth
flying ...
Regards,
Geoff.
OT1: It has been a few years since my last post ... but
have been reading here, and playing with FG/TG, now and then ...
Usually, when there is a MSVC question, that I could
add to, Fred B. is so fast to answer ... Thanks Fred ;=))
OT2: Also for quite a few years now, I have been adding
my FG experiences to my site - it all starts at -
http://geoffmclane.com/fg
Excuse the long, rambling, quite messy, site ;=))
The latest build, and these ABORTS are here -
http://geoffmclane.com/fg/fgfs-014.htm,
and it continues, a follow-on ...
http://geoffmclane.com/fg/fgfs-015.htm
if you can stand the pain ...
EOF
_
SEEK: Over 80,000 jobs across all industries at Australia's #1 job site.
http://ninemsn.seek.com.au?hotmail
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Bug in ATC code.
On 20/10/2005 at 21:40 George Patterson wrote: Hi All, I have noticed two annoying bugs in the ATC dialog boxes. When you press ' for the first ATC dialog labelled ATC menu is displayed. (btw, Can we change that title as it's not an accurate description, perhaps ATC communication) Anyway, if you change frequencies for another ATC tower, extra lines showing :- 1. Contact tower for VFR arrival (full stop) 2. Contact tower for VFR arrival (full stop) 3. Contact tower for VFR arrival (full stop) etc, depending on how often you have switched frequencies. The other one which might be related is if you reset FlightGear (File-Reset), the state for the ATC is not reset back to the Contact tower ... dialog. Instead it will continue when you partially finished from before.. Contact tower- Report Downwind - Runway vacated. Thanks George. I'll attend to those in the next few weeks. The extra lines problem I was aware of, but the state persistance through reset is new to me. Cheers - Dave This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Problems with 'V' (backwards view) on Mac os X, fixed (somewhat)
-Original Message- snip Interestingly enough, if I add a 7th node, the new view works and so does 'V'. Overwriting one of flightgear's default views must be unacceptable to some portion of the code. snip Not true. The only possiblilty would be view 0, the cockpit view, and it's relationship to the FDM altitude above ground level output and maybe something unique regarding rendering (OpenGL stuff), but even that I'm not sure of currently. Certainly you should be able to replace or eliminate any of the other views. Best, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Bug in ATC code.
On Thu, 2005-10-20 at 13:49 +0100, David Luff wrote: On 20/10/2005 at 21:40 George Patterson wrote: Hi All, I have noticed two annoying bugs in the ATC dialog boxes. When you press ' for the first ATC dialog labelled ATC menu is [Snipped] Thanks George. I'll attend to those in the next few weeks. The extra lines problem I was aware of, but the state persistance through reset is new to me. Yeah, Persistance or Persistence even was the word i was looking for. :-) David, Let me know when you have it committed and I'll check again. :-) George Patterson ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Problems with 'V' (backwards view) on Mac os X, fixed (somewhat)
-Original Message- From: Melchior FRANZ * Ima Sudonim -- Thursday 20 October 2005 12:54: I don't know why it makes a difference, but it does. Darn, I really liked that Chase View Above 8-( What about also increasing the number of views in the preferences file, if you add some? number-views type=int7/number-views No idea, why we don't simply count the view nodes? Hmmm ... This is one of the older bits of code that did one of these arrays of subsystem objects. I did it wrong and never got back to fix it. Counting and writing out the property would work fine. The only changes required would be within the init() in viewmgr.cxx. It'd be a week anyway before I could get to it myself. Best, Jim ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Problems with 'V' (backwards view) on Mac os X, fixed (somewhat)
Melchior FRANZ wrote: * Ima Sudonim -- Thursday 20 October 2005 12:54: I don't know why it makes a difference, but it does. Darn, I really liked that Chase View Above 8-( What about also increasing the number of views in the preferences file, if you add some? number-views type=int7/number-views No idea, why we don't simply count the view nodes? Hmmm ... Please stop the annoying full-quoting (and top-posting). m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d I tried that once, and found that it caused problems. I think it was either the joystick config or the keyboard config, but something assumes that number-views is 6, and breaks. I think the whole system needs an overhaul and like Mel says FG should just count the views. They don't even need to be numbered. Just have FG add them to a list as they are read in from the xml config files and assign them numbers then. That way you could have the default ones, then add an arbitrary number of personal ones, and after that an airplane designer can come along and add as many as he wants (co-pilot, BN, tail gunner, view of munitions, etc) without mucking up the already existing views that someone obviously wants to be there. I got around this in the B-29 by having a Nasal script modify the pilot view, but that is a hack. I should have been able to define multiple views without cannibalizing existing ones. Josh ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] PLIB version for building from CVS
--- Buchanan, Stuart [EMAIL PROTECTED] wrote: Hi All, Which version of PLib is required to build the current FG CVS? v1.8.4 is the latest stable release. Unfortunately, I can't add any other useful info regarding the compile error. Mike I'm getting a build error (output below), which I assume is due to an incorrect PLIB version. I'm using v1.8.4 Thanks -Stuart g++ -g -O2 -D_REENTRANT -L/usr/local/lib -o js_demo.exe js_demo.o -lplibjs - lwinmm -lplibul /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../libplibjs.a(jsWindows.o): In func tion `_ZN10jsJoystick4openEv': /home/Stuart/plib-1.8.4/src/js/jsWindows.cxx:107: undefined reference to `_joyGe [EMAIL PROTECTED]' /usr/lib/gcc-lib/i686-pc-cygwin/3.3.3/../../../libplibjs.a(jsWindows.o): In func tion `_ZN10jsJoystick7rawReadEPiPf': /home/Stuart/plib-1.8.4/src/js/jsWindows.cxx:191: undefined reference to `_joyGe [EMAIL PROTECTED]' collect2: ld returned 1 exit status make[2]: *** [js_demo.exe] Error 1 make[2]: Leaving directory `/home/Stuart/FlightGear-0.9/source/src/Input' ___ Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail http://uk.messenger.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: contacting tower
Melchior FRANZ wrote: * Frank Olaf -- Thursday 20 October 2005 13:03: [...] I am using the versions of SDL, pthread and such from the tarball on plausible.org/andy. Anyway, I applied your patch to today's CVS, and besides the problem with HUGE when compiling, all keys are now operating as expected, I don't know what Andy's SDL does differently from the official SDL, but the latter works for me (CVS/HEAD, at least :-). The patch reverts a bugfix, so it's rather unlikely to get into CVS. I am still unable to find the appropriate glut libraries to compile with msys. I have however done a clean check out and downloaded the latest SDL libraries from their web page and recompiled. The error is still there, so I don't think SDL is the problem, at least not my versions of it. -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: contacting tower
Hi, I am still unable to find the appropriate glut libraries to compile with msys. There is now a short documentation docs-mini/README.mingw in the CVS. It may give you some hints. Cheers Olaf ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Two problems - 1 easy and 1 hard! - in XP using MSVC7
Geoff Air wrote:
...
This turned out to be the usual file line ending problem ...
mine has the 'normal' WIN32 0x0d, 0x0a, ending,
and could be solved by 'fixing' the zone.tab file, or, as I
would suggest, a small 'fix' in SimGear, timezone.cxx ...
Changing the line 104, in timezone.cxx -
while (!((infoString[i] == '\t') || (infoString[i] == '\n'))) {
to a more robust, cross platform search ...
while (!((infoString[i] == '\t') || (infoString[i] == '\n') ||
(infoString[i] == '\r'))) {
and all is well ...
I just tried : I did delete the file zone.tab then made a checkout.
The checkout gives me a 'text' file with msdos line endings. I don't
understant why.
The zone.tab from the 0.9.8 package from F.B. contains the file with a
unix line-ending.
2. The Hard find
I am getting an exception ABORT again, and again, especially
since I changed to using LFPO ... the console does not help
much, log level debug, the last lines just showing -
Unknown exception in the main loop. Aborting...
Possible cause: No error
Deleting a sample ... (written another 4 times!)
...
I am still trying to track this/these down ... are any other
Windows XP SP2 - MSVC7 users getting this/these? Any
ideas welcome ... I would like to get back to smooth
flying ...
There is no startup abort for xp with the one week ago cvs.
You should trap the exceptions (set that in the debug menu) to find the line
that throw the exception.
Harald.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Problems with 'V' (backwards view) on Mac os X
Ima Sudonim wrote: I noticed that with latest CVS on mac os x, I can scroll thru views (forward) with 'v' as many times as I like, but that 'V' (reverse) only works 1-3 times until I reach the view that has a name ending in 'w/o yaw'. 'V' will no longer work, until I move forward in the views with 'v' at least once. Then the 'V' cycle works (or fails to work) as mentioned above. Hrm... it works for me on linux. Are any other keys affected? Specifically, check the operation of other shifted keys. If I had to guess what would cause something like this, it would be a keymap bug in the OS X plib or glut port... Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Problems with 'V' (backwards view) on Mac os X, fixed
[ Unrelated nit: who's mail client keeps breaking this thread? ] Ima Sudonim wrote: The actual problem was my error: the number-views was one less than the actual number of views. Sorry to waste bandwidth on a user error... OK, then the real symptom here is an interaction with the Nasal view management code, which doesn't read number-views at all, but instead loops through the actual property children of the view node. I agree with Melchior: what is this thing doing there? Who reads it, and why do we need it? Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Bug in ATC code.
* David Luff -- Thursday 20 October 2005 14:49: On 20/10/2005 at 21:40 George Patterson wrote: When you press ' for the first ATC dialog labelled ATC menu is displayed. (btw, Can we change that title as it's not an accurate description, perhaps ATC communication) Anyway, if you change frequencies for another ATC tower, extra lines showing :- 1. Contact tower for VFR arrival (full stop) 2. Contact tower for VFR arrival (full stop) 3. Contact tower for VFR arrival (full stop) etc, depending on how often you have switched frequencies. I'll attend to those in the next few weeks. Don't bother. I'm almost finished rewriting ATCDialog.cxx, and both these issues are fixed already. The goal is to replace hard-coded dialogs with dialogs managed by the gui-subsystem. They'll be easy to edit (xml files), accept the gui style, are properly aligned by the layouter, etc. I'll submit the patch for review. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: Two problems - 1 easy and 1 hard! - in XP using MSVC7
Thank you, Harald for your quick reply ...
1. Easy fix - line endings
Glad you could confirm my CVS check out ... but the
suggested code fix takes care of it, which ever line
endings there are in zone.tab ;=))
2. Hard find - ABORT
Thank you for the Debug menu pointer ... I had not found
MSVC very good with exceptions, in the distant past,
but it has really improved ...
Trapping the exception, and returning to the debugger, the
Call Stack showed, in part, the simple answer ...
FlightGear.exe!_nh_malloc_dbg(unsigned int nSize=1, int nhFlag=3, int
nBlockUse=1235168, const char * szFileName=0x0012d9ec, int nLine=1242460)
Line 267 + 0x7
FlightGear.exe!_CxxThrowException(void * pExceptionObject=0x0012d8fc, const
_s__ThrowInfo * pThrowInfo=0x00e95db0) + 0x39
FlightGear.exe!std::_Nomemory() Line 10
FlightGear.exe!operator new(unsigned int size=73056) Line 15
...
FlightGear.exe!FGTileMgr::update(SGLocation * location=0x201ac898, double
visibility_meters=20.000) Line 437
And of course, passing the exception back to FG, I end up
at the lines in bootstrap.cxx -
} catch (...) {
cerr Unknown exception in the main loop. Aborting... endl;
perror(Possible cause);
}
The console last few lines showed, confirming the call stack -
FGTileMgr::update()
State == Running
Loading tile
C:/FG0981/FlightGear/data/Scenery/Terrain/e000n40/e001n47/2974291
token = OBJECT_BASE name = 2974291.btg
So these ABORTS were a SIMPLE case of OUT-OF-MEMORY, of a
certain type ... This is the very first time I have found
Windows wanting in the memory allocation area ... I
thought the virtual memory was virtually unlimited ;=))
well, depending only on settings, and HDD size ...
So, maybe I can increase the swap file size, and
certainly REDUCE my very unreasonable visibility,
20 meters, or BOTH ...
Note, Windows is not completely out of memory,
since I was able to open Word, and commence writing
this, while still in the debugger ... with several
other windows open ... ???
Removing my unrealistic 20 from my system.fgfsrc
file, thus allowing the default visibility, and I could
fly around, with fog, and sky-blend, all day ;=))
I took off from Orly, flew generally NNW, and ended up
at Lands End, with some help from Google Earth ...
followed the southern coast around to Manston,
then left into Heathrow, over London, then
took about a 160 track, hit the French coast at 49 48'N,
0 30'E, adjusted to 135 track, and back to Orly, after
some other adjustments ...
Over 2 hours of UFO flying ... sometimes at many times the
speed of sound ... stoping here and there to look around,
identify an airport, etc, and not a single ABORT ...
Checking my virtual memory options, I note it has
a maximum size of 1536MB, with 1534MB currently
allocated! ... since I have 30 plus GB left on the
drive, maybe I could increase the maximum ... and be
flying in clear air, with extreme visibility ...
but will experiment with that another day ;=))
Thank you ... thank you ... thank you
I have certainly learned a lesson about push the
parameters ... if you want clear air and long distant
vision, be careful about MEMORY ABORTS ;=)) I kind
of knew it had something to do with my system.fgfsrc
preferences ...
So, the problem is sort of solved ... back to
quiet flying ... thanks again
Regards,
Geoff.
EOF
_
REALESTATE: biggest buy/rent/share listings
http://ninemsn.realestate.com.au
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: Two problems - 1 easy and 1 hard! - in XP using MSVC7
In regards to #2. Hard find - ABORT
Question, which version of MSVC7 are you using?
7.0 is .net 2002, 7.1 is .net 2003
I was having a memory allocation error in one application that I was using
.net 2002 (7.0) on that I could not solve. After upgrading to .net 2003 (7.1),
the memory allocation problem went away, in other words, it was a
compiler problem.
-- Original message -- Thank you, Harald for your quick reply ... 1. Easy fix - line endings Glad you could confirm my CVS check out ... but the suggested code fix takes care of it, which ever line endings there are in zone.tab ;=)) 2. Hard find - ABORT Thank you for the Debug menu pointer ... I had not found MSVC very good with exceptions, in the distant past, but it has really improved ... Trapping the exception, and returning to the debugger, the Call Stack showed, in part, the simple answer ... FlightGear.exe!_nh_malloc_dbg(unsigned int nSize=1, int nhFlag=3, int nBlockUse=1235168, const char * szFileName=0x0012d9ec, int nLine=1242460) Line 267 + 0x7 FlightGear.exe!_CxxThrowException(void * pExceptionObject=0x0012d8fc, const _s__ThrowInfo * pThrowInfo=0x00e95db0) + 0x39 FlightGear.exe!std::_Nomemory() Line 10 FlightGear.exe!operator new(unsigned int size=73056) Line 15 ... FlightGear.exe!FGTileMgr::update(SGLocation * location=0x201ac898, double visibility_meters=20.000) Line 437 And of course, passing the exception back to FG, I end up at the lines in bootstrap.cxx - } catch (...) { cerr "Unknown exception in the main loop. Aborting..." endl; perror("Possible cause"); } The console last few lines showed, confirming the call stack - FGTileMgr::update() State == Running Loading tile C:/FG0981/FlightGear/data/Scenery/Terrain/e000n40/e001n47/2974291 token = OBJECT_BASE name = 2974291.btg So these ABORTS were a SIMPLE case of OUT-OF-MEMORY, of a certain type ... This is the very first time I have found Windows wanting in the memory allocation area ... I thought the virtual memory was virtually unlimited ;=)) well, depending only on settings, and HDD size ... So, maybe I can increase the swap file size, and certainly REDUCE my very unreasonable visibility, 20 meters, or BOTH ... Note, Windows is not completely out of memory, since I was able to open Word, and commence writing this, while still in the debugger ... with several other windows open ... ??? Removing my unrealistic 20 from my system.fgfsrc file, thus allowing the default visibility, and I could fly around, with fog, and sky-blend, all day ;=)) I took off from Orly, flew generally NNW, and ended up at Lands End, with some help from Google Earth ... followed the southern coast around to Manston, then left into Heathrow, over London, then took about a 160 track, hit the French coast at 49 48'N, 0 30'E, adjusted to 135 track, and back to Orly, after some other adjustments ... Over 2 hours of UFO flying ... sometimes at many times the speed of sound ... stoping here and there to look around, identify an airport, etc, and not a single ABORT ... Checking my virtual memory options, I note it has a maximum size of 1536MB, with 1534MB currently allocated! ... since I have 30 plus GB left on the drive, maybe I could increase the maximum ... and be flying in clear air, with extreme visibility ... but will experiment with that another day ;=)) Thank you ... thank you ... thank you I have certainly learned a lesson about push the parameters ... if you want clear air and long distant vision, be careful about MEMORY ABORTS ;=)) I kind of knew it had something to do with my system.fgfsrc preferences ... So, the problem is sort of solved ... back to quiet flying ... thanks again Regards, Geoff. EOF _ REALESTATE: biggest buy/rent/share listings http://ninemsn.realestate.com.au___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
