Re: [Flightgear-devel] Problems with 'V' (backwards view) on Mac os X
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 ___ 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
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 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 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 ___ 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
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 ___ 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
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 ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] PLIB version for building from CVS
Hi All, Which version of PLib is required to build the current FG CVS? 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
Re: [Flightgear-devel] Major slowdown since yesterday
Hello Durk, Durk Talsma wrote: > Please let me know if the traffic-manager is enabled, and then I hope I can > give you some more assistance in getting your system up to speed again. Thanks for your kind and detailed reply. I'll keep you posted as soon as I had the chance to check for the mentioned criteria. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ 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 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 #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
[Flightgear-devel] Re: Major slowdown since yesterday
* Durk Talsma -- Wednesday 19 October 2005 19:39: > It does seem that there was another update yesterday, related to a fix in > ssg. > (See the email conversation between Matthias Frolich and Melchior Franz, > yesterday evening). While I have not tested this, it might be possible that > this is causing some slowdown, No, that's not possible. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] [PATCH] TU114-set.xml help/spelling in comments
On Wednesday 19 Oct 2005 02:13, Vassilii Khachaturov wrote: > Index: ../data/Aircraft/TU-114/TU-114-set.xml > == >= RCS file: > /var/cvs/FlightGear-0.9/data/Aircraft/TU-114/TU-114-set.xml,v > retrieving revision 1.1 > diff -u -r1.1 TU-114-set.xml > --- ../data/Aircraft/TU-114/TU-114-set.xml5 Oct 2005 15:59:17 > - 1.1 +++ ../data/Aircraft/TU-114/TU-114-set.xml 19 Oct > 2005 01:11:34 - @@ -9,6 +9,16 @@ > > > > + > + > + K > + Toggle trajectory markers > + > + > +L/U > +Update Tower/Drop View position > + > + > > + > > > > @@ -181,7 +191,7 @@ > > > > -U > +L > Update Tower View position > >nasal Hello Vassilii, there are some fundamental problems with the TU-114 props and engines and it's really only in cvs so that other people can have a look into it. This doesn't mean you can't or shouldn't (try) to fly it or fix bits that you notice are wrong but you should bear in mind that in it's present state it's incomplete and badly flawed. The problems with the props & engines concern controlling the prop pitch and I don't have a clear/good enough understanding of how it should work to fix it. LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Major slowdown since yesterday
On Wednesday 19 October 2005 14:54, Martin Spott wrote: > Hello, > I experience a significant slowdown in the frame rate since my last > build yesterday. As the only significant change in CVS is the AI > traffic on EHAM I assume the slowdown is related to that. > Do I have the ability to disable this feature by command line ? > I already apply "--prop:/sim/ai-traffic/enabled=false" and > "--disable-ai-models" but this does not appear to affect the recent > changes. > > Not that I dislike the new feature, it's quite an interesting add-on. > It's just that the PeeCee I run test on is incapable to keep up with > the work load. > Hi Martin, Have you checked whether in preferences.xml you have the following true true if so, you should set traffic-manager/enabled to false. Next, you could also check using the property browser if any aircraft are listed in /ai/models. However, I do have to add that, while I cannot rule out a performance decrease from the new traffic features, I would consider it unlikely, for a number of reasons, that this is what's troubling you. First, and formost, the new taxiway follow code only works at EHAM, but there is no traffic yet for this airport (unless the KLM schedules are uncommented data/Traffic/fgtraffic.xml, (you might want to check). Secondly, even when you are flying within a relatively small distance of EHAM, currently set at 150 km. Thirdly, the traffic manager is still disabled by default, so the new code shouldn't run, unless you specifically activate it. Fourth and final, the new code doesn't run on a frame to frame basis, but mainly only when a new taxiroute is requested. So while I can imagine that this would result in an occasional pause on slower machines, it should not result in a continuous performance decrease. Unless all three conditions above are satisfied, the new code doesn't run. It does seem that there was another update yesterday, related to a fix in ssg. (See the email conversation between Matthias Frolich and Melchior Franz, yesterday evening). While I have not tested this, it might be possible that this is causing some slowdown, because this patch seems to run on a frame to frame basis. Please let me know if the traffic-manager is enabled, and then I hope I can give you some more assistance in getting your system up to speed again. Cheers, Durk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: fgfs on AMD64 status?
> I'm secure enough now that I'm shopping to build a new machine. I'm looking > at AMD64 motherboards and one of the newer nvidia cards. And what I'm > wondering is whether any fgfs developers can speak to building and running > fgfs, on linux, on an AMD64 box, and/or with the nv 6600's/6800's etc. > I've seen some threads that people are running it on AMD64 OK; but I'm > wondering if there are any suggestions, recommendations, or warnings that > are worth hearing before I start shelling out the big $ (e.g. mobos you're > happy with or had nothing but trouble with). I wanna get back to this stuff. FGFS runs fine under AMD64 in both 32 bit and 64 bit architectures and has done so for 18 months. Debian i386 Testing and AMD64 Unstable, as they were called at the time (AMD64 Testing didn't exist initially). USB joysticks are unaffected by transitioning between 32 bit and 64 bit. You seem to be going for desktop chassis; in which case the motherboard chipset is a minor issue (compared to the nightmare that laptops can be) and not one I can help with. All my non-server AMD64 systems are laptops. Your only real remaining issue is whether your video chipset will run accelerated with the 32 bit and/or the 64 bit kernel. If you use a card that's old enough to have open source drivers, this is trivial. Both NV and ATI provide 32 and 64 bit versions of their binary drivers, supporting both X.org and xfree86, so there is no availability problem. People have had various levels of luck with installation gremlins though. Therefore, I suggest checking the mailing list for your specific chipset. Once that is taken care of, I'd just install and start flying around. Hope that helps. PS. If you're going to be dual boot for both 32 and 64 bit architectures, don't forget to have the disk space containing FGFS's data (and scenery) be shared. You don't want to install (eg) Alaska on one filesystem, then later reboot, then realize you have to do that installation again. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Major slowdown since yesterday
Hello, I experience a significant slowdown in the frame rate since my last build yesterday. As the only significant change in CVS is the AI traffic on EHAM I assume the slowdown is related to that. Do I have the ability to disable this feature by command line ? I already apply "--prop:/sim/ai-traffic/enabled=false" and "--disable-ai-models" but this does not appear to affect the recent changes. Not that I dislike the new feature, it's quite an interesting add-on. It's just that the PeeCee I run test on is incapable to keep up with the work load. Thanks, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: contacting tower
* 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.
? SConscript
Index: input.cxx
===
RCS file: /var/cvs/FlightGear-0.9/FlightGear/src/Input/input.cxx,v
retrieving revision 1.67
diff -u -p -r1.67 input.cxx
--- input.cxx 30 Jun 2005 19:26:29 - 1.67
+++ input.cxx 19 Oct 2005 11:27:23 -
@@ -243,15 +243,18 @@ FGInput::doKey (int k, int modifiers, in
button &b = _key_bindings[k];
// Key pressed.
- if (!(modifiers & KEYMOD_RELEASED)) {
+ if (modifiers&KEYMOD_RELEASED == 0) {
SG_LOG( SG_INPUT, SG_DEBUG, "User pressed key " << k
<< " with modifiers " << modifiers );
if (!b.last_state || b.is_repeatable) {
- const binding_list_t &bindings = _find_key_bindings(k, modifiers);
-
- for (unsigned int i = 0; i < bindings.size(); i++)
-bindings[i]->fire();
- b.last_state = 1;
+ const binding_list_t &bindings =
+_find_key_bindings(k, modifiers);
+ int max = bindings.size();
+ if (max > 0) {
+for (int i = 0; i < max; i++)
+ bindings[i]->fire();
+return;
+ }
}
}
// Key released.
@@ -259,10 +262,14 @@ FGInput::doKey (int k, int modifiers, in
SG_LOG(SG_INPUT, SG_DEBUG, "User released key " << k
<< " with modifiers " << modifiers);
if (b.last_state) {
- const binding_list_t &bindings = _find_key_bindings(k, modifiers);
- for (unsigned int i = 0; i < bindings.size(); i++)
-bindings[i]->fire();
- b.last_state = 0;
+ const binding_list_t &bindings =
+_find_key_bindings(k, modifiers);
+ int max = bindings.size();
+ if (max > 0) {
+for (int i = 0; i < max; i++)
+ bindings[i]->fire();
+return;
+ }
}
}
}
@@ -388,7 +395,6 @@ FGInput::_init_keyboard ()
_key_bindings[index].bindings->clear();
_key_bindings[index].is_repeatable = keys[i]->getBoolValue("repeatable");
-_key_bindings[index].last_state = 0;
_read_bindings(keys[i], _key_bindings[index].bindings, KEYMOD_NONE);
}
}
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS compiling error
Thank you David, now off to work, I'll try it this evening! Regards Georg David Luff schrieb: BTW, Georg, CVS SimGear should compile on Cygwin 3.4.4 now, and CVS FlightGear will probably compile on it if you add .. Then send the output of "cvs diff -u" from the FlightGear directory to Erik, and the 3.4.4 problem should be sorted :-) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] CVS compiling error
On 19/10/2005 at 12:05 Georg Vollnhals wrote: >Hi Erik/Durk? >Since your update of simple.cxx/hxx on the 18.10.05 the newest CVS >version does not compile anymore :-( > >Error: >simple.cxx: In member function `int >FGGroundNetwork::findNearestNode(double, > double)': >simple.cxx:1331: error: `HUGE' undeclared (first use this function) >simple.cxx:1331: error: (Each undeclared identifier is reported only >once for > each function it appears in.) >make[2]: *** [simple.o] Fehler 1 >make[1]: *** [all-recursive] Fehler 1 >make: *** [all-recursive] Fehler 1 > >Any solution? Cygwin doesn't have HUGE, so change HUGE to HUGE_VAL and -HUGE to -HUGE_VAL and I suspect this should compile. 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. 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 #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 :-) 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] CVS compiling error
Hi Erik/Durk? Since your update of simple.cxx/hxx on the 18.10.05 the newest CVS version does not compile anymore :-( Error: simple.cxx: In member function `int FGGroundNetwork::findNearestNode(double, double)': simple.cxx:1331: error: `HUGE' undeclared (first use this function) simple.cxx:1331: error: (Each undeclared identifier is reported only once for each function it appears in.) make[2]: *** [simple.o] Fehler 1 make[1]: *** [all-recursive] Fehler 1 make: *** [all-recursive] Fehler 1 Any solution? Thank you Georg ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] contacting tower
Frederic Bouvier wrote: Quoting Frank Olaf : I just tried the latest compiled snapshot at ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/ and everything work normally, so its only my own compilation that suffers from the problem :( They seemd to rely on different pthreadVC-nd.dlls. It has allways work for me with pthreadVC-nd.dll, but the snapshot required pthreadVC2-nd.dll, could this be the problem? I doubt it is related. I just migrate my own projects to a more recent pthread snapshot that induced the change in library name. The problem with non-repeating keys is certainly a problem with not current keyboard.xml. There was a change by Melchior after I reported a bug and the repeat behavior must be explicit now. Perhaps Melchior can comment as my memory is a bit short on this topic. -Fred 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.. -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] fgfs on AMD64 status? Mobo suggestions/warnings?
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of > [EMAIL PROTECTED] > Sent: 19 October 2005 02:05 > To: flightgear-devel@flightgear.org > Subject: [Flightgear-devel] fgfs on AMD64 status? Mobo > suggestions/warnings? > > > > Hi, > > I've been out of the fgfs development loop for an annoyingly > long time. At > first, I had to adjust to a big drop in free time after > (thankfully) finally > getting employed. Then I had a video card failure that > forced me back to an > old card I had lying around which had no 3D acceleration. > And then, at the > end of July, problems with my motherboard started, and > worsened through the > month until it became basically unusable by September. > > I'm secure enough now that I'm shopping to build a new > machine. I'm looking > at AMD64 motherboards and one of the newer nvidia cards. And what I'm > wondering is whether any fgfs developers can speak to > building and running > fgfs, on linux, on an AMD64 box, and/or with the nv 6600's/6800's etc. > I've seen some threads that people are running it on AMD64 OK; but I'm > wondering if there are any suggestions, recommendations, or > warnings that > are worth hearing before I start shelling out the big $ (e.g. > mobos you're > happy with or had nothing but trouble with). I wanna get > back to this stuff. > > Cheers, > > -c > I build and run FG on an AMD64 3000, on a Gigabyte motherboard (GA-K8VNXP maybe?) in W2K and Linux (FC3, 32 bit). HD is on the SATA port which works seamlessly. Video is an NVidia 5200 (I think) and that is no problem in either OS. I am using the onboard sound, which I now cannot get working with OpenAL under Windows, although it has worked in the past. It works fine in Linux though, and I am moving that way, so I have stopped worrying about that :-) Saitek USB joystick works fine in both OSs (once I had it plugged in while kudzu ran) but the axis numbers are different in Linux and Windows. I will post a patch to the joystick file at some point to fix that one properly. Welcome back. Richard This e-mail has been scanned for Bede Scientific Instruments for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] fgfs on AMD64 status? Mobo suggestions/warnings?
On Wed, 2005-10-19 at 01:04 +, [EMAIL PROTECTED] wrote: > Hi, > > I've been out of the fgfs development loop for an annoyingly long time. At > first, I had to adjust to a big drop in free time after (thankfully) finally > getting employed. Then I had a video card failure that forced me back to an > old card I had lying around which had no 3D acceleration. And then, at the > end of July, problems with my motherboard started, and worsened through the > month until it became basically unusable by September. > > I'm secure enough now that I'm shopping to build a new machine. I'm looking > at AMD64 motherboards and one of the newer nvidia cards. And what I'm > wondering is whether any fgfs developers can speak to building and running > fgfs, on linux, on an AMD64 box, and/or with the nv 6600's/6800's etc. > I've seen some threads that people are running it on AMD64 OK; but I'm > wondering if there are any suggestions, recommendations, or warnings that > are worth hearing before I start shelling out the big $ (e.g. mobos you're > happy with or had nothing but trouble with). I wanna get back to this stuff. > > Cheers, > > -c I am running a AMD64 based system Specifications: Gigabyte GA-K8NS Utlra Sock 939 nForce 3 Dual Bios Corsair DDR Ram 1 gig (matched pair) SATA Hard drive NV 6600GT AGP 128MB (You might want to consider PCI-E these days though.) That's the guts of it... Montherboard has dual network interfaces on board. (More about that one later) You didn't say what OS you are considering but It works a treat With Ubuntu Hoary (5.04) and Windows2000 (not interested in XP at this stage) Problems: After installing windows, the Gigabit network interface driver wasn't happy with it. plugged the network cable into the other socket and downloaded the up to date driver. Problem solved. On Linux, I had a sound problem with Warty (4.10) with the sound not intialising. apt-get update & apt-get upgrade fixed that one. Also install the offical nvidia driver (7667 or higher) as the the version that is packaged for Hoary doesn't work with the AGP version of the NV 6600GT. I'd give the above combination the thumbs up. It is stable and I'm getting about 66fps at 800x600 when sitting on runway 28R at KSFO. The frame rate doesn't change when enlarging to full screen. One thing I didn't notice that --enabled-specular-highlights does kill the frame rate so i disabled that but the new 3D clouds doesn't present a problem. Overall, I'm happy with the purchase :-) George ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] contacting tower
Quoting Frank Olaf : > I just tried the latest compiled snapshot at > ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/ and everything work > normally, so its only my own compilation that suffers from the problem > :( They seemd to rely on different pthreadVC-nd.dlls. It has allways > work for me with pthreadVC-nd.dll, but the snapshot required > pthreadVC2-nd.dll, could this be the problem? I doubt it is related. I just migrate my own projects to a more recent pthread snapshot that induced the change in library name. The problem with non-repeating keys is certainly a problem with not current keyboard.xml. There was a change by Melchior after I reported a bug and the repeat behavior must be explicit now. Perhaps Melchior can comment as my memory is a bit short on this topic. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] fgfs on AMD64 status? Mobo suggestions/warnings?
[EMAIL PROTECTED] wrote: > I'm secure enough now that I'm shopping to build a new machine. I'm looking > at AMD64 motherboards and one of the newer nvidia cards. You could aim at being a pioneer and go for an ATI X800 type board. I've already had FlightGear displayed on such a board using the OpenSource r300 driver and it somehow works - but not stable at that time. In any case I have the impression that the newer ATI boards are definitely a good choice, they have closed source drivers in case you don't want to fiddle with DRI/Mesa/XOrg sources. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] contacting tower
I just tried the latest compiled snapshot at ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32/ and everything work normally, so its only my own compilation that suffers from the problem :( They seemd to rely on different pthreadVC-nd.dlls. It has allways work for me with pthreadVC-nd.dll, but the snapshot required pthreadVC2-nd.dll, could this be the problem? Frank Olaf wrote: Ampere K. Hardraade wrote: On October 18, 2005 05:51 am, Frank Olaf wrote: > >>Another point is that I am not always able to contact the tower when > >>pressing the ' key, even though I am on the correct radiofrequency. > > Er... try flying out of the ATC's control area before you attempt to contact the tower. Ampere It's not the tower that is the problem, it is that the key-press is not recognised more than once, several keys and key combinations are recognised only once in CVS versions I compile. -- Frank Olaf Sem-Jacobsen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
