FSUIPC Beta 4.539 appears to break GoFlight

[BAW019]

Hi Pete

I'm getting abends starting FSX with the new beta module FSUIPC 4.5.3.9 The previous beta worked fine but with this one the FSX form opens as a completely black window and after several seconds I get the "FSX has encountered a problem and needs to close" dialog.

The FSUIPC log is pretty sparse so I'm including it below and I took a look in the Event log - the abend is also shown below.

Let me know if you have time to look at this and need anything other info:

All the best

Ian

System Spec

===========

Gigabyte Alive STAT2 Glan motherboard

Dual 3.0Ghz AMD Athlon CPU (3gb)

ATI Radeon HD4800 graphics card

Sound Blaster Audigy sound card

ATI High Def Audio sound driver

Maxronix MX98715 Ethernet adapter

Windows XP SP3

FSX 10.0.616370.0

FSUIPC 4.5.3.9

GoFlight Inc GFDevFSX.exe 1.76.0.5

********* FSUIPC4, Version 4.539 by Pete Dowson *********
Reading options from "C:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"
User Name="Ian Niblo"
User Addr="xxxxxxxxxxxxxxxxx"
FSUIPC4 Key is provided
WideFS7 Key is provided
Running inside FSX (using SimConnect Acc/SP2 Oct07)
Module base=61000000
Wind smoothing fix is fully installed
DebugStatus=255
     1187 System time = 29/09/2009 18:44:30
     1187 FLT UNC path = "\\FLIGHTSIM\MyDocsFSX\"
     1187 FS UNC path = "\\FLIGHTSIM\Microsoft Flight Simulator X\"
     1969 LogOptions=00000000 00000001
     1969 SimConnect_Open succeeded: waiting to check version okay

Event Type:	Error
Event Source:	Application Error
Event Category:	None
Event ID:	1000
Date:		29/09/2009
Time:		18:40:27
User:		N/A
Computer:	FLIGHTSIM
Description:
Faulting application gfdevfsx.exe, version 1.76.0.5, faulting module gfdevfsx.exe, version 1.76.0.5, fault address 0x000268da.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74   Applicat
0008: 69 6f 6e 20 46 61 69 6c   ion Fail
0010: 75 72 65 20 20 67 66 64   ure  gfd
0018: 65 76 66 73 78 2e 65 78   evfsx.ex
0020: 65 20 31 2e 37 36 2e 30   e 1.76.0
0028: 2e 35 20 69 6e 20 67 66   .5 in gf
0030: 64 65 76 66 73 78 2e 65   devfsx.e
0038: 78 65 20 31 2e 37 36 2e   xe 1.76.
0040: 30 2e 35 20 61 74 20 6f   0.5 at o
0048: 66 66 73 65 74 20 30 30   ffset 00
0050: 30 32 36 38 64 61 0d 0a   0268da..

[Pete Dowson]

I'm getting abends starting FSX with the new beta module FSUIPC 4.5.3.9 The previous beta worked fine but with this one the FSX form opens as a completely black window and after several seconds I get the "FSX has encountered a problem and needs to close" dialog.

By "previous beta" do you mean 4.538? Because the change between 4.538 and 4.539 is simply a new Lua plug-in facility. nothing else.

I'm pretty sure the GoFlight module for FSX doesn't use FSUIPC, so I'm really not convinced FSUIPC can have anything to do with it, other than, of course, memory arrangements might be slightly different. Not only that but the log seems to show that the GoFlight module is crashing before FSUIPC is even doing anything -- it doesn't get to do anything until that request to SimConnect returns with version details. Those affect which SimConnect functions FSUIPC can link to.

I don't appear to have any FSX GoFlight software here, so perhaps you could enable FSUIPC's IPC read/write logging and just re-check that the GoFlight module is not attempting to use FSUIPC.

[LATER]

Three more comments.

First, you say FSX crashes with a windows erorr message. Have you got the module name and address for that crash? The details you appended were for the GoFlight driver which appears to be a separate crash:

Faulting application gfdevfsx.exe, version 1.76.0.5, faulting module gfdevfsx.exe, version 1.76.0.5, fault address 0x000268da.

It is an EXE, a separate process altogether to FSX. Where did FSX itself crash?

Second, I found my GFDEVFSX.EXE but I'm not sure it is doing anything. Is it supposed to allow units like the GF-T8 and GF-P8 operate, or do I need to assign things to them somewhere in the GF software? It doesn't seem to have a menu or anything. The EXE certainly runs here without crashing itself or FSX, but perhaps that's because it is doing nothing?

Third, it might help to get a SimConnect log, please. The "FSX Help" Announcement explains how to do that.

Regards

Pete

[Pete Dowson]

I'm getting abends starting FSX with the new beta module FSUIPC 4.5.3.9 The previous beta worked fine but with this one the FSX form opens as a completely black window and after several seconds I get the "FSX has encountered a problem and needs to close" dialog.

I still couldn't reproduce this, but I suspect it may be a similar bug to one i did just find and fix in FSUIPC 3.935. So could you try version 4.541, which has a similar timing issue fixed? It is now in the Updates folder, please. If you still get a problem, I'll need more details.

Thanks,

Pete

[BAW019]

Thanks Peter, sorry for the delay, something cropped up last night and am at work at the moment. However I'll take a look at the new version when I get in this evening and report back asap,

Best as always!

Ian

[BAW019]

Hi Pete, I've tried the latest beta (4.541) and the problem appears to be solved so many thanks your efforts!

All the best

Ian