I've been following this for a while now, inactively because I don't use
windows. I have to ask the question why not write a quick replacement
for the command window, if all we are interested in is logging calls?
It would be possible to do this in Assembler I'm guessing - using NAsm
and using
In my experience, worst case is having the terminal (console) window open but covered
(partially or completely) by another window, least bad is to have the console window
selected. Best case for when the console window is not selected is to have it
minimised.
On NT like systems, it feels as if
On 10/23/02 at 11:58 AM Jacek M. Holeczek wrote:
There is also another annoying problem. Basically, the FGFS runs very
smoothly on my machine except that every now and then (I don't have my
machine at hand now, but let's say it is about every 30 seconds) it
stops for a moment - I can see that in
Minimize the console window to minimise the effect.
Richard
-Original Message-
From: David Luff [mailto:David.Luff;nottingham.ac.uk]
Sent: 24 October 2002 11:27 am
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [Flightgear-devel] FlightGear 0.8.0 on Win98SE
On 10/23
Jacek M. Holeczek wrote:
...
There are two problems with the joystick.
First, there are two vertical bars/arrows in the cockpit for the
elevators, but only the right one is following the joystick (the
left one always stays in the middle) - however, if I view the plane
from outside I can see that
On 10/24/02 at 12:48 PM Jacek M. Holeczek wrote:
This is a known problem - Win95/98/Me are absolutely hopeless at
outputting
to the console - NT/2000/XT are much quicker, and Linux quicker still.
I'm not very experienced here ... but are you sure that the problem is
just writing to the
quickest fix
would be to fix the SG_LOG level of that output to be disabled with
--without-logging. The best fix might be to enable full run-time
logging
control. I have commented out all the sun position information
stuff in my
own build in the past and the pauses go away. As someone
On Thu, 24 Oct 2002 09:30:29 -0700
Andy Ross [EMAIL PROTECTED] wrote:
Richard Bytheway wrote:
We really ought to sort out the ability to disable *any*
console
output after initialisation on Windows...
Is it maybe time to revisit the priority of most of the log messages?
I mean, the vast
Richard Bytheway wrote:
We really ought to sort out the ability to disable *any* console
output after initialisation on Windows...
Is it maybe time to revisit the priority of most of the log messages?
I mean, the vast majority of these things are debugging output for
code that is mature and
* [EMAIL PROTECTED] (Jon Berndt) [2002.10.24 08:49]:
quickest fix
would be to fix the SG_LOG level of that output to be disabled with
--without-logging. The best fix might be to enable full run-time
logging
control. I have commented out all the sun position information
stuff in my
Hi,
Thanks for your reply.
This is a known problem - Win95/98/Me are absolutely hopeless at outputting
to the console - NT/2000/XT are much quicker, and Linux quicker still.
I'm not very experienced here ... but are you sure that the problem is
just writing to the terminal window ?
From what
* [EMAIL PROTECTED] (Jon S Berndt) [2002.10.24 12:08]:
On Thu, 24 Oct 2002 09:30:29 -0700
Andy Ross [EMAIL PROTECTED] wrote:
Richard Bytheway wrote:
We really ought to sort out the ability to disable *any*
console
output after initialisation on Windows...
Is it maybe time to revisit the
Hi,
First things first ... very impressive work, congratulations !!!
Then ... I tried your 0.8.0 binary distribution on a AMD Athlon/1333 with
384MB RAM and GeForce2 PRO/32MB machine running Win98SE/Polish.
Here is a brief report ...
The fgfs.exe runs well (on a couple of occasions the sound
13 matches
Mail list logo
