OnCourse Software

Hi Dave,

while searching in the debug_monitor.log file to find the reason for the already reported approach-center loop I found the following error:

Code: Select all 04.04.2010 20:39:59: 620 - Error 13 reading from D:\Games\fsx\D:\Games\fsx\SimObjects\Airplanes\Aerosoft Twin Otter 300 modern\aircraft.cfg

Seems that the FSX path is duplicated in the search path for the aircraft.cfg file of the current airplane.

Kind regard
Wolfgang

Quote:

while searching in the debug_monitor.log file to find the reason for the already reported approach-center loop I found the following error:

Code: Select all 04.04.2010 20:39:59: 620 - Error 13 reading from D:\Games\fsx\D:\Games\fsx\SimObjects\Airplanes\Aerosoft Twin Otter 300 modern\aircraft.cfg

Seems that the FSX path is duplicated in the search path for the aircraft.cfg file of the current airplane.

How very strange.... wasn't occurring here (last time I checked) and the only way I can see that happening is if FSUIPC has a hiccup. I do add the FS Path onto the path for the aircraft file as per the FSUIPC documentation

Pathname of the current AIR file, excluding the FS main path
(see 3E00), but including everything from ―Aircraft\…‖ to the
final ―…air‖. This is zero padded to fill the 256 bytes available.
When this changes the 16-bit counter at 32FC is incremented, so
interested programs don‘t have to keep on reading the whole 256
bytes to check

So using the above I use offsets 3C00 and 3E00 and it works fine here... or it did... I'll do some more checks here and if need be report to Pete Dowson. It's an easy enough workaround for me but it clearly shouldn't be reading all of that from FSUIPC.

Thanks for the heads up

Quote:

Later:

Ah ha... looks like it was changed for FSX.

Okay, easy done