Jump to content
The simFlight Network Forums

FSUIPC error code in fs9


Recommended Posts

I have downloaded the new 3.8.5 Version of FSUIPC amd also I have installed ASA weather since doing this I have been getting random blackscreem crashes with the following error code....

AppName: fs9.exe AppVer: 9.1.0.40901 ModName: fsuipc.dll

ModVer: 3.8.5.0 Offset: 000273e6

I am hoping someone might be able to help with this..I have reregistered my copy and I thought it had solved the problem but it has started crashing again and I am at a complete loss.......

Geoff

Link to comment
Share on other sites

I have downloaded the new 3.8.5 Version of FSUIPC amd also I have installed ASA weather since doing this I have been getting random blackscreem crashes with the following error code....

AppName: fs9.exe AppVer: 9.1.0.40901 ModName: fsuipc.dll

ModVer: 3.8.5.0 Offset: 000273e6

Not exactly random if they always have the same details! ;-)

I am hoping someone might be able to help with this..I have reregistered my copy and I thought it had solved the problem but it has started crashing again and I am at a complete loss......

Registration shouldn't have anything to do with it. This is the first report of any such problem, so I'd need details.

1. Is this only with ASA running?

2. How long does it take, after starting ASA, before a crash, typically?

3. Do you have any weather options set in FSUIPC? Maybe there's some sort of conflict with something ASA is doing? Try temporarily removing your FSUIPC.KEY file from the FS Modules folder, so that it runs unregistered and so with no weather options active. Let me know.

Finally, could you try it with the current interim Beta version, 3.858, available in the "Other Downloads" announcement above, and let me know. Please include the same sort of details, which might change a little.

Regards

Pete

Link to comment
Share on other sites

I have downloaded the new 3.8.5 Version of FSUIPC amd also I have installed ASA weather since doing this I have been getting random blackscreem crashes

I've now installed ASA on my FS9 test PC and have had it running on a flight for some time without any problems. This is with FSUIPC 3.858. I have no FSUIPC options selected in Winds, Visibility or Clouds, and I've not touched any options in ASA.

Maybe it needs some combination of options in one or the other of FSUIPC and ASA, so I am desperately in need of more information from you -- all of the options (your FSUIPC.INI file would help -- just the [General] section) and a note of anything you've changed in ASA.

I'm sure HiFi Simulations would have tested ASA with FSUIPC and FS9 quite thoroughly before the released it, so it is going to take some help from you to narrow this down and determine the cause.

Regards

Pete

Link to comment
Share on other sites

Pete thanks for your help and interest with this error. I have tried running fs9 without a registered copy of fsuipc and it ran with no problem for a couple of hours, then it crashed and i got this code..

AppName: fs9.exe AppVer: 9.1.0.40901 ModName: ariane.737.fmc.gau

ModVer: 1.0.5.0 Offset: 000972cb

Now this ive been having problems with for over a year and I have had little help from anyone in solving it, im now starting to wonder if the two are in fact linked as there are some simularities in the codes but im not all that clued up on the tech side of a flight sim program.

This is a copy of the fsuipc file ( addrress removed) found in the modules file at the time of the crash with the fsuipc error, I was not using the level D 767 at the time but a 737 from Ariane.

********* FSUIPC, Version 3.85 by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 3

Verifying Certificate for "C:\Program Files\microsoft games\Flight Simulator 9\MODULES\FSUIPC.dll" now ...

SUCCESS! Signature verifies okay!

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="xxxxxxx

User Addr=" xxxxxxx

FSUIPC Key is provided

WIDEFS not user registered, or expired

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=609E3729[609E3729]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=15

11516 System time = 00:30:32

11516 C:\Program Files\microsoft games\Flight Simulator 9\

11516 System time = 00:30:32, FS2004 time = 12:00:00 (00:00Z)

25797 C:\Documents and Settings\geoff mulligan\My Documents\Flight Simulator Files\Previous flight.flt

25844 AIRCRAFT\LVLD_B763\B767-300.air

26531 Aircraft="Level D Simulations B767-300ER - British Airways G-BNWD"

40281 Advanced Weather Interface Enabled

49109 C:\Documents and Settings\geoff mulligan\My Documents\Flight Simulator Files\UI generated flight.flt

51578 Clear All Weather requested: external weather discarded

3255953 System time = 01:24:37, FS2004 time = 19:16:35 (18:16Z)

3255953 *** FSUIPC log file being closed

Memory managed: 30 Allocs, 104789 Freed

********* FSUIPC Log file closed ***********

I latter ran the flight sim again and this time it crashed with a oom ( this seems to be a known fault with ASA on their forum) I will get back to you on here when it crashes again as im sure it will. It seems to crash at random times and if I reset up the flight exactly the same it will then run fine and crash somewhere completly different, sometimes hours latter, some times within a few mins........

Geoff

Link to comment
Share on other sites

Hello Pete

Since my last post I have downloaded the 3,8,5 that you asked, and I have just completed 3 hours on line, using the Ariane 737 and ASA working through fsuipc registered set up for winds, clouds etc...with no error.

I will report back after the next session and let you know how it continues,,,,

thanks geoff :D

Link to comment
Share on other sites

I have tried running fs9 without a registered copy of fsuipc and it ran with no problem for a couple of hours, then it crashed and i got this code..

AppName: fs9.exe AppVer: 9.1.0.40901 ModName: ariane.737.fmc.gau

ModVer: 1.0.5.0 Offset: 000972cb

Now this ive been having problems with for over a year and I have had little help from anyone in solving it, im now starting to wonder if the two are in fact linked as there are some simularities in the codes but im not all that clued up on the tech side of a flight sim program.

Actually, there's no similarities, but it is indeed quite possible that this Ariane gauge, or some other component of the aircraft you are using, has a bug which is resulting in memory being corrupted. the end results of that will vary enormously depending on the particular configuration you are running at the time.

When checking for an error in a particular program it is best to narrow it down by only using defaults first. If ASA + FSUIPC doesn't cause any problem with a default aircraft loaded, but does with that Ariane one, then it is more likely to be a problem with the aircraft than either ASA or FSUIPC.

This is a copy of the fsuipc file ( addrress removed) found in the modules file at the time of the crash with the fsuipc error, I was not using the level D 767 at the time but a 737 from Ariane.

No, this log shows you were using

25844 AIRCRAFT\LVLD_B763\B767-300.air

26531 Aircraft="Level D Simulations B767-300ER - British Airways G-BNWD"

... no sign of any different aircraft being loaded.

I latter ran the flight sim again and this time it crashed with a oom ( this seems to be a known fault with ASA on their forum) I will get back to you on here when it crashes again as im sure it will. It seems to crash at random times and if I reset up the flight exactly the same it will then run fine and crash somewhere completly different, sometimes hours latter, some times within a few mins........

Give up on add-on aircraft for a few tests, use only defaults. I cannot believe, at present, that this is anything to do with either ASA or FSUIPC.

If you supply any more data for FSUIPC please be sure to use the latest increment as I requested, not 3.85.

Regards

Pete

Link to comment
Share on other sites

Okay i got the fsuipc crash again. This time I had just started fs9 and set it up to start at the last previous flight when it crashed to a black screen and the option to report to microsoft,

This is the error code

AppName: fs9.exe AppVer: 9.1.0.40901 ModName: fsuipc.dll

ModVer: 3.8.5.8 Offset: 00027646

and this is a copy of thr fsuipc file right after the shut down

********* FSUIPC, Version 3.858 by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 3

Verifying Certificate for "C:\Program Files\microsoft games\Flight Simulator 9\MODULES\FSUIPC.dll" now ...

SUCCESS! Signature verifies okay!

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="

User Addr=""

FSUIPC Key is provided

WIDEFS not user registered, or expired

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=6082B789[6082B789]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=15

9234 System time = 17:55:50

9234 C:\Program Files\microsoft games\Flight Simulator 9\

9234 System time = 17:55:50, FS2004 time = 12:00:00 (00:00Z)

I was using the ariane 737 but it hadnt even had the chance start up before it crashed again the other programs/add ons were EGKK extreme by uk 2000 and ASA

hope this tells you something

once again thanks in advance for your help

Geoff

Link to comment
Share on other sites

This is the error code

AppName: fs9.exe AppVer: 9.1.0.40901 ModName: fsuipc.dll

ModVer: 3.8.5.8 Offset: 00027646

and this is a copy of thr fsuipc file right after the shut down

The FSUIPC log isn't much use, except that it looks like, although you said ASA was running, I'd be surrised if it had yet had time to do anything. So far the most likely culprit is that Ariane 737. Why can't you test for a while with default aircraft, as I suggested?

... hope this tells you something

Since it appears that this problem is unique to you and is happening so frequently, it suggests that one or more of your add-ons, probably the 737, is corrupted and messing the memory values up thereby corrupting and crashing other parts of FS, including FSUIPC an, previously, another component. If I were in your shoes I'd be seriously considering a complete uninstall and re-install of FS, testing fully before installing any add-ons and after installing each one.

I'll certainly have a look at that location, Offset 00027646 in FSUIPC 3.858 -- it appears to inside the Process Request routine, processing a request from an add-on. Does that Ariane 737 use FSUIPC? Otherwise I can't see what should be running which would be trying to access it so early. There's certainly no record here of any Ariane product licensed to use FSUIPC, but it may just be a re-badged older product from FS2000 or FS2002 days.

If it is accessing FSUIPC and this crash is in one of the calls that it is making, then it is in the wrong place -- the routine is for EXTERNAL programs only. If there's a Gauge in the Ariane 737 accessing FSUIPC using the external method then this can certainly cause crashes. It is breaking the rules. Some very old (FS2000, FS2002) gauges used to do this and create no end of such problems.

If you can definitely reproduce the crash right at the start like that, it would be worthwhile first editing the FSUIPC.INI file and adding

LogReads=Yes

LogWrites=Yes

to the [General] section. This will log all attempts to access FSUIPC for any reason, and the last one before the crash may show us something. However, if it does turn out to be all down to that add-on aircraft I shall not be pleased and will not be able to do anything about it.

[LATER]

I've located exactly in FSUIPC where that crash occurs, and it is where it is processing the data passed by a program trying to use FSUIPC. Either something is passing invalid data (wrong length by the look of it), or, more likely from the logs, an internal Gauge or DLL is incorrectly calling FSUIPC using the external method. If it is the latter I can probably stop them doing that, which would cause whatever it is (e.g. that 737) not to work any more, which might be the best thing.

I may supply you with a little updated version of FSUIPC3 which protects itself as far as possible against rogue programs, but I think you need to carry out a process of elimination to see what it is, whether it genuinely is that 737 or not. So, stop using it for a while and see what crashes you do or don't get then.

Regards

Pete

Link to comment
Share on other sites

Thankyou so much for your help with this, I am beging to think it might be the 737 reacting with your program that caused the original problem as you have said. I have had this error now for about a year, their web site does recomended it is not to be used with fsuipc, but as it is the best 737 availiable and I only use fs9 on line I am up a creeck without a paddle.

I was using this combination without problems for ages then the error before Fmc.gau error started.This is a dll file as you have said so I am starting to think this might be it. I have already deleated fs9 and reinstalled it( they told me it was due to fs9.1 update not being installed correctly) but the error soon returned.

I will swop over aircraft as you have sugested but the fsuicp only happens when im using ASA. since this crash tonight i have deactivated fs passengers and have now completed three hours without a hitch using the 737. However I will try changing over, and as a result I doubt I will encounter the earilier error as this only happens with the ariane 737.

I am not sure where the fsuipc.ini file would be found in order to edit it...I guess if I find it I just use notebook to add the lines you sugested..?

one other thing what follows is a copy of a reply I had yesterday through the Active sky web site I logged on to see if I am unique with this error...........

I was getting spontaneous fsuipc crashes as well. Figured someone else would back you up, so I never got around to posting about it :) I've gone back to AS6.5 for the time being, so can't update on whether it's still happening

link = http://forums1.avsim.net/index.php?showtopic=238964

I will let you know how I get on

thanks

once again

Geoff

Link to comment
Share on other sites

Hello again.

Right here is my new report, I have been using defalt 737 and level d 767 alternatly

And during the loading of fs9 tonight it crashed as it was loading the the program through ASA. It failed to complete loading at the terrain files. It actualy froze at 11% ,then up popped the error code and my chance to email Bill Gates with the details...as follows. I hadnt actualy run any aircraft at the time of the error, this has never happened before. I did crash eairlier while I was using the level D but that wasnt your fsuipc error it was a hungerror so I wont bother you with the details of that. but this was the Crash during the loading.

AppName: fs9.exe AppVer: 9.1.0.40901 ModName: fsuipc.dll

ModVer: 3.8.2.0 Offset: 00027322

I did copy the lines you recomended into the configuration file as I guess these is the fsuipc.ini file....I was looking for a file called .ini ( not very computer litirate ) the result from fsuipc from the log is huge and im not sure how much of the log you will require. I have saved it so I can send it to you should you want the whole thing, but im not sure how to get it to you

This is the start of it in case this helps

********* FSUIPC, Version 3.82 by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 3

Verifying Certificate for "C:\Program Files\microsoft games\Flight Simulator 9\MODULES\FSUIPC.dll" now ...

SUCCESS! Signature verifies okay!

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="geoffrey mulligan"

User Addr="

FSUIPC Key is provided

WIDEFS not user registered, or expired

Module base=61000000

ClassOptions: UIPCMAIN=FF7F, FS98MAIN=FF7F, FS2KMAIN=FF5E

WeatherOptions(Orig)=6082B789[6082B789]

InitDelay: 0 seconds

WeatherReadInterval=4

LogOptions=0000000D

DebugStatus=15

42578 System time = 22:49:44

42578 C:\Program Files\microsoft games\Flight Simulator 9\

42594 System time = 22:49:44, FS2004 time = 12:00:00 (00:00Z)

58969 C:\Documents and Settings\geoff mulligan\My Documents\Flight Simulator Files\Previous flight.flt

58984 AIRCRAFT\b737_400\Boeing737-400.air

59734 Aircraft="Boeing 737-400"

61609 READ0 3304, 4 bytes: 00 00 20 38

61609 READ0 3308, 4 bytes: 07 00 DE FA

61609 WRITE0 (failed, read-only!) 330A, 2 bytes: B0 04

61609 READ0 3304, 4 bytes: 00 00 20 38

61609 READ0 3308, 4 bytes: 07 00 DE FA

61609 WRITE0 (failed, read-only!) 330A, 2 bytes: B0 04

61609 READ0 3304, 4 bytes: 00 00 20 38

61609 READ0 3308, 4 bytes: 07 00 DE FA

61609 WRITE0 (failed, read-only!) 330A, 4 bytes: 02 00 00 00

61609 WRITE0 8001, 26 bytes: 31 43 30 51 41 48 4B 39 53 52 33 36 73 62 6D 70

61609 6A 6F 69 6E 39 2E 64 6C 6C 00

61609 WRITE0 7BE8, 1 bytes: 01

61609 READ0 7BE9, 1 bytes: 00

63750 WRITE0 8001, 23 bytes: 59 39 42 45 38 4E 41 58 41 4B 4F 43 53 44 53 63

63750 65 6E 65 2E 64 6C 6C

63750 READ0 7BE9, 1 bytes: 00

63750 READ0 0274, 4 bytes: 00 00 00 00

63828 READ0 3364, 1 bytes: FF

63828 READ0 3D00, 256 bytes: 42 6F 65 69 6E 67 20 37 33 37 2D 34 30 30 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63828 READ0 0560, 8 bytes: 00 00 48 0A AA 03 4A 00

63828 READ0 0568, 8 bytes: 00 00 C5 82 1D 6F 1F 05

63828 READ0 11BA, 2 bytes: 00 00

63828 READ0 3367, 1 bytes: 00

63828 READ0 3102, 4 bytes: 00 00 00 00

63828 READ0 3103, 4 bytes: 00 00 00 00

63828 READ0 0264, 2 bytes: 00 00

63828 READ0 13FC, 4 bytes: 00 00 00 00

63828 READ0 0840, 2 bytes: 00 00

63828 READ0 0240, 2 bytes: D9 07

63828 READ0 023E, 2 bytes: 06 00

63828 READ0 0239, 1 bytes: 32

63828 READ0 023B, 1 bytes: 15

63828 READ0 0238, 2 bytes: 16 32

63828 READ0 313C, 12 bytes: 00 00 00 00 00 00 00 00 00 00 00 00

63828 READ0 30C0, 12 bytes: 00 00 00 00 00 00 00 00 00 00 00 00

63828 READ0 0560, 8 bytes: 00 00 48 0A AA 03 4A 00

63828 READ0 0568, 8 bytes: 00 00 C5 82 1D 6F 1F 05

63828 READ0 0570, 8 bytes: 00 00 8C CA 05 00 00 00

63828 READ0 0570, 8 bytes: 00 00 8C CA 05 00 00 00

63828 READ0 0580, 8 bytes: 45 8A D8 1F 00 00 00 00

63828 READ0 0578, 4 bytes: 9D EC 44 00

63828 READ0 057C, 4 bytes: A4 FA FC FF

63828 READ0 0EEE, 2 bytes: 00 00

63828 READ0 0E90, 2 bytes: 00 00

63828 READ0 0E92, 8 bytes: 00 00 00 00 00 00 00 00

63828 READ0 02A0, 2 bytes: 1E FF

63828 READ0 115E, 1 bytes: 04

63828 READ0 02B4, 4 bytes: 00 00 00 00

63828 READ0 02B8, 4 bytes: 00 00 00 00

63828 READ0 02BC, 4 bytes: 00 00 00 00

63828 READ0 0BC8, 2 bytes: 00 00

63828 READ0 036C, 2 bytes: 00 00

63828 READ0 036D, 2 bytes: 00 00

63828 READ0 0366, 2 bytes: 01 00

63828 READ0 02C8, 4 bytes: 00 00 00 00

63828 READ0 0574, 4 bytes: 05 00 00 00

63828 READ0 034E, 2 bytes: 85 24

63828 READ0 3118, 2 bytes: 00 00

63828 READ0 3122, 1 bytes: 00

63891 READ0 3304, 4 bytes: 00 00 20 38

63891 READ0 3308, 4 bytes: 07 00 DE FA

63891 WRITE0 (failed, read-only!) 330A, 2 bytes: B0 04

63891 WRITE0 8001, 23 bytes: 50 4B 4E 4C 58 59 44 5A 45 46 46 4A 73 62 6D 6F

63891 64 39 2E 64 6C 6C 00

63891 READ0 320C, 4 bytes: 38 00 00 00

63891 READ0 3210, 224 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 WRITE0 3210, 4 bytes: FF FF 00 00

63891 WRITE0 2FE0, 18 bytes: 00 53 74 61 72 74 20 26 53 71 75 61 77 6B 42 6F

63891 78 00

63891 READ0 3304, 4 bytes: 00 00 20 38

63891 READ0 3308, 4 bytes: 07 00 DE FA

63891 WRITE0 (failed, read-only!) 330A, 2 bytes: 4C 04

63891 WRITE0 8001, 28 bytes: 35 47 33 45 55 48 46 4F 42 51 45 34 41 63 74 69

63891 76 65 52 61 64 61 72 2E 64 6C 6C 00

63891 READ0 0564, 4 bytes: AA 03 4A 00

63891 READ0 056C, 4 bytes: 1D 6F 1F 05

63891 READ0 0580, 4 bytes: 45 8A D8 1F

63891 READ0 0574, 4 bytes: 05 00 00 00

63891 READ0 C000, 1024 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

63891 00 00 00 00 00 00

Link to comment
Share on other sites

And during the loading of fs9 tonight it crashed as it was loading the the program through ASA.

Do you always load FS from ASA?

It is looking more and more like a bug in ASA rather than the add-on aircraft. I'm not sure it is wise, until we get to the bottom of this, to run ASA until FS is loaded and ready to fly. All sorts of things might be going wrong if ASA is messing with FS whilst it is initialising.

AppName: fs9.exe AppVer: 9.1.0.40901 ModName: fsuipc.dll

ModVer: 3.8.2.0 Offset: 00027322

Why have you reverted to FSUIPC version 3.82? That's really very old, and no use to anything I can do. Please stay with 3.858 until i send an update for you to try.

the result from fsuipc from the log is huge

It is huge even though FS crashed/hung on loading? That is VERY suspicious, and even more indicative of a problem caused by ASA trying to do something whilst FS is initialising, before it is ready for whatever it is ASA wants it to do.

... and im not sure how much of the log you will require. I have saved it so I can send it to you should you want the whole thing, but im not sure how to get it to you

The MOST important part is the last part, the bit before the crash, though if FS hung instead of crashing that might not be so useful.

ZIP it and send it as an attachment to petedowson@btconnect.com. Do NOT send it without Zipping -- it will zip up quite small.

I'll look at that one, but please try to get one from a CRASH not a HANG, and using FSUIPC 3.858, not 3.82. Please also do some testing where you run ASA later, when FS is ready to fly. It sounds like it isn't waiting for the "FS is ready" signal from FSUIPC before trying to set the weather -- FS will certainly not like attempts to set weather when it is still initialising all that stuff!

Have you reported all this yet to HiFi Simulation, as a potential ASA bug? If not I think you should. I am on good terms with them and we can resolve it between us, but bugs need to be reported by users, not by third parties like me.

Oh, just looking at the start of the Log, you have other FSUIPC clients also running. "SBMPJOIN9.DLL" (part of Squawkbox?) and "SDscene.DLL", which I don't know though must have licensed. Then, later, SBMOD9.DLL starts up too, followed by ACTIVERADAR.DLL.

You didn't mention any of this before, did you? Any one of those could also be part or the whole of the problem. Maybe you should continue doing some elimination. Do you know what SDscene.DLL is for? Try removing it temporarily from the Modules folder. SBMPJOIN9.DLL and SBMOD9.DLL too if you aren't flying on-line during these tests. You really do need to pare it down to the minimum setup which crashes if we are ever to resolve it! You don't need ACTIVERADAR.DLL either just to use ASA. Move all these optional FSUIPC-using DLLs out of the Modules folder for now -- keep them safe, then run more tests with just ASA.

If that's then okay, add them back, bit by bit. ActiveRadar first, test, then the two Squawkbox ones, test, then finally that SDscene, whatever that's for.

If it still fails with no FSUIPC users excepting ASA, we know it is definitely ASA.

Regards

Pete

Link to comment
Share on other sites

Im going to be sending you a new fsuipc file with all the details of this problem with the configurations that you requseted to you email address.

The log file you already sent shows nothing useful I'm afraid. Of course it was for a hang, not a crash, and for 3.82, not the current version.

The procedure to narrow this down has simply got to be a process of elimination. there are too many things going on with your system normally. Something certainly has a bug in it -- a program sending invalid data to FSUIPC. I can deal with that (rejecting the data) but I would then have no idea what it would do to that program. Best to isolate it first.

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.