On 11 Dec 2009, at 19:32, Csaba Halász wrote:
Also, the whole positioned code seems to be ignorant of the fact that
buckets don't have the same size. Staying with the spatialGetClosest,
it assumes it can just use NxN boxes when in fact a different row
(latitude) could have half or double the
Afte taxiing a little ways down runway 31L at JFK, the
display freezes and the sim starts spewing messages to
the console:
Warning:: Picked up error in TriangleIntersect
For additional details see
http://www.av8n.com/fly/fgfs/nan--25387.log
This is observed when some properties are being
On 12/12/2009 04:53 AM, I wrote:
Afte taxiing a little ways down runway 31L at JFK, the
display freezes and the sim starts spewing messages to
the console:
Warning:: Picked up error in TriangleIntersect
For additional details see
http://www.av8n.com/fly/fgfs/nan--25387.log
John,
I as I understood we don't have any real artificial/ interacting ATC in FGFS.
That means the messages are more or less just for fun.
If we use a generic rwy no we could argument that it is the wrong rwy for the
given wind.
The better solution would be to program a working/ interacting
On 12/12/2009 05:16 AM, Csaba Halász wrote:
Hi John,
Could you please use the --enable-fpe option and try to get a backtrace?
Sure.
In one case I had to taxi a little while before getting an FPE:
http://www.av8n.com/fly/fgfs/fpe--27376.log
In another case I got an FPE very early, while the
On 12/12/2009 10:25 AM, Heiko Schulz wrote:
I as I understood we don't have any real artificial/ interacting ATC in FGFS.
That means the messages are more or less just for fun.
If we use a generic rwy no we could argument that it is the wrong rwy for the
given wind.
The better solution
Hi guys , Ive started some scenery developement ,have learned a fair
bit in the last few days , but have more questions than answers at the
moment.
Ive been using the original hgt files for the Vancouver area , Im more
interested in fixing the materials , roads, streams , coastline , etc.
I did
On Sat, Dec 12, 2009 at 1:59 PM, syd adams adams@gmail.com wrote:
Hi guys , Ive started some scenery developement ,have learned a fair
bit in the last few days , but have more questions than answers at the
moment.
Ive been using the original hgt files for the Vancouver area , Im more
I have some basic questions about the --metar command-line
option.
AFAICT the getstart.pdf manual doesn't mention this option.
The --verbose --help message mentions the option, and
implies that it takes an argument ... but doesn't say
anything about the syntax or semantics of the argument.
I
Update: To observe this bug, I don't even need to taxi.
I can just sit at the starting point of runway 31L at
JFK with the engine off. After sitting about 8 minutes,
I observe nan messages on the console.
One interesting thing is that *no* floating point
exception was raised this time. The
On 12/12/2009 02:03 PM, Heiko Schulz wrote:
I could solve that issue with disabling AI-Traffic (Not the Interactive
Traffic)
I hate to ask silly questions, but ... are you suggesting
--disable-ai-models Disable the artificial traffic subsystem.
The last time I used that option
On Sun, Dec 13, 2009 at 12:21 AM, John Denker j...@av8n.com wrote:
Any additional suggestions for things to try would be
welcome.
It is very strange because I have never seen a NaN slip past the
--enable-fpe guard.
You could try to build my nan-fixes branch from gitorious
On Sat, 2009-12-12 at 16:21 -0700, John Denker wrote:
On 12/12/2009 02:03 PM, Heiko Schulz wrote:
I could solve that issue with disabling AI-Traffic (Not the Interactive
Traffic)
I hate to ask silly questions, but ... are you suggesting
--disable-ai-models Disable the
On Sat, 2009-12-12 at 07:29 +, Ron Jensen wrote:
On Fri, 2009-12-11 at 10:44 -0700, John Denker wrote:
But there may also be issues with the prop efficiency at ultra-low
airspeed (high blade angle of attack).
Low blade angle of attack? Increasing airspeed increases blade AoA
14 matches
Mail list logo
