Conflict with FSUIPC and FSInn

[Neil Purdon]

I run FS2002 and FSInn/Copilot to connect to the VATSIM network.

I have now installed vasFMC 1.1 and added the required file FSUIPC.dll in the Modules folder of FS2002.

vasFMC is great and works perfectly with FS2002, however there is a problem when I run FSInn in that the transponder on the FSInn Control Panel is now permanently squawking Mode C and the transponder display alternates betweeen Mode C and "Ident".

If I remove FSUIPC then FSinn operates correctly again, but of course then vasFMC is not connected to FS2002.

Any suggestions?

Neil

[Pete Dowson]

vasFMC is great and works perfectly with FS2002, however there is a problem when I run FSInn in that the transponder on the FSInn Control Panel is now permanently squawking Mode C and the transponder display alternates betweeen Mode C and "Ident".

If I remove FSUIPC then FSinn operates correctly again, but of course then vasFMC is not connected to FS2002.

What about if you remove vasFMC instead of FSUIPC? Because FSUIPC does nothing unless asked -- it sounds more like something in vasFMC.

You may need to ask FSInn support about this, because only they would know what could be affecting their transponder mode indication (there's no simulation of those modes in FS itself, and therefore no facilities in FSUIPC for them).

Alternatively, possibly you have some conflict between button or key assignments between vasFMC and FSInn -- specifically the one operating the IDENT.

Pete

[Neil Purdon]

Thanks Pete.

The problem was simply resolved thanks to Bill Casey of VATSIM-UK who advised me to disable the dll "sb3gaugebridge.dll" sitting in the Modules folder having been placed there by FSInn/Co-pilot. However, having got past that issue I've hit another which appears to be a vasFMC / FSUIPC issue and a tricker nut to crack.

Departing Amsterdam, FS hangs and then crashes half-way through the SID even if vasFMC is not controlling the autopilot. I see no option but to go back to default FS2002 navigation.

I'm embarrassed to be asking for help seeing as though my copy of FSUIPC is both unregistered and unpaid for!

Neil Purdon

VATSIM-UK (G-GNQH Biggin Hill)

[Pete Dowson]

Departing Amsterdam, FS hangs and then crashes half-way through the SID

That sounds more like a scenery or terrain problem. What FS module is mentioned in the crash report? Generally those are G2D or G3D.DLL.

Pete

[Neil Purdon]

Hello Pete

The FS error report states:

AppName: fs2002.exe AppVer: 8.0.0.10919 ModName: fsuipc.dll

ModVer: 3.8.0.0 Offset: 0001f012

Regards

Neil

[Pete Dowson]

The FS error report states:

AppName: fs2002.exe AppVer: 8.0.0.10919 ModName: fsuipc.dll

ModVer: 3.8.0.0 Offset: 0001f012

Ah, that's very interesting.

I need more information. could you enable IPC read and write logging (in the FSUIPC options, logging Tab), and repro the error for me please? Zip up the FSUIPC.LOG and send it to petedowson@btconnect.com.

Regards

Pete

[Pete Dowson]

I need more information. could you enable IPC read and write logging (in the FSUIPC options, logging Tab), and repro the error for me please? Zip up the FSUIPC.LOG and send it to petedowson@btconnect.com.

Actually, please amend that -- enable Weather logging too, please. I've just checked, and that offset is in the weather reading part of FSUIPC.

I'm wondering now if it might be a corrupted weather file. Are you always starting with the same weather? Where is the weather coming from? Does it happen if you clear all weather first?

Regards

Pete

[Neil Purdon]

Hello Pete

Thanks for the replies and when I get a chance will gather the data and email.

I also wondered if it is weather related. What I was doing was setting the weather manually in FS (only temps and pressure, no wind or cloud), setting global temps and pressure at a mean of departure and arrival airports, then setting the exact temps and pressure at departure airport EHAM and arrival airport EGPH. FSInn weather was set to CAVOK so that it doesn't try to get it's own weather.

If there's a preferred sequence for the setting or sourcing of weather, I'd be happy to comply. I also wondered if there were any specific .ini setting required.

Regards

Neil

[Pete Dowson]

If there's a preferred sequence for the setting or sourcing of weather, I'd be happy to comply. I also wondered if there were any specific .ini setting required.

No, nothing. You shouldn't get a crash no matter what.

When you do the re-run to get the Logging files, at a point before you get the crash, could you please Save a Flight (press ; and give it a name). Include the resulting FLT + WX files with the logs, and tell me how to proceed from that point to get to the crash. If I can reproduce the problem it will be much easier for me to work out what is happening -- I think I still have an FS2002 around here somewhere. ;-)

Regards

Pete

[Pete Dowson]

Thanks for the replies and when I get a chance will gather the data and email.

Okay. I received the files and managed to reproduce the crash.

It is a localised weather data structure from FS which contains a NULL pointer where the current visibility should be. It seems to do this because the visibility is unlimited, but I've never seen it set NULL before -- it has always had a pointer to the value which indicates unlimited.

This is in a part of FSUIPC dealing with the weather reading which has remained pretty much unchanged since FS2000 days (i.e. over 9 years ago), and yours is the first occasion I've been told about which crashes! Amazing!

Anyway, it is certainly my fault, as the possibility of a NULL pointer should have been checked.

Please download version 3.801 using this link:

http://fsuipc.simflight.com/beta/FSUIPC3801.zip

and the problem should be fixed. Just put the revised FSUIPC.DLL into your FS2002 Modules folder.

Regards

Pete

[Neil Purdon]

Dear Pete

Thank you so much! I really appreciate the time and trouble you've been to. From here on take it that no news is good news! :D

Regards

Neil