Hi,
Alex Perry schrieb:
Try watching your virtual memory usage and see whether you're hitting
the 2GB (or 3GB) limit within that process. If you are, it is worth
patching TerraGear until it runs cleanly on all 64 bit architectures.
If it isn't a memory problem, we can stick with the 32 bit for
Hello,
I just started with FlightGear on Windows XP.
I recently purchased a Saitek Cyborg Evo joystick. The rudder control
was not working in FlightGear. After some exploring, I discovered
(using js_demo) that the stick identifies itself as
Joystick 0 is Saitek Cyborg Evo
In the Inputs folder
Ralf Gerlich wrote:
Hi,
Alex Perry schrieb:
Try watching your virtual memory usage and see whether you're hitting
the 2GB (or 3GB) limit within that process. If you are, it is worth
patching TerraGear until it runs cleanly on all 64 bit architectures.
If it isn't a memory problem, we can
Steve Knoblock wrote:
In the Inputs folder there is a joystick configuration file for this
stick, which puzzled me at first as to why it didn't work. The name in
the file is
Saitek Cyborg USB Stick
Once I changed this to
Saitek Cyborg Evo
the rudder and everything else worked fine.
Hi,
Curtis L. Olson schrieb:
[SNIP]
It's been a while, but scan the fgfs-construct code for some sort of
ulimit checking built into the code. I seem to recall there was some
code there that would cause the process to self destruct if it sensed it
was taking too long or consuming too much
I have been having issues with a pretty much repeatable floating
exception during final approach to any airport with any aircraft. It
does never crash in-flight, only within visual range of an
airport/runway, and usually during final approach.
Is there any likely way that this can be worked
for a while now i've been noticing that flightgear takes an incredible
amount of time to start. today i attached gdb to the fgfs process and
this is what i got:
#1 0x08410bde in netSocket::select (reads=0xbfa895c0, writes=0xbfa895c8,
timeout=0) at netSocket.cxx:384
#2 0xb7e99b3c in
Hi all,
The generation is on the go and I'll probably release _two_ versions of
the scenery this evening (UTC+2) - one with all the backstreets and one
without.
Nope, only one version - without all the small backstreets - most of the
white lines to be seen on the Status page. However, Curt's
Alex Romosan [EMAIL PROTECTED] writes:
i am starting at the default airport (KSFO) so i wonder why we are
even trying to load the data for KHOU (which is in huston)? could it
be we are trying to load the metar data for all the airports? does
anybody have any idea what's going on?
looking at
