ShortAircraftNameOk broken in V 4.8.3.4

[CHBTheDoctor]

In FSUIPC.DLL V4.8.3.4 I found a problem with ShortAircraftNameOk

My FSUIPC.ini normally has entries like these:

[General]
...
UseProfiles=Yes
ShortAircraftNameOk=Yes
....
[Profile.Single Prop Mustang AccuSim]
1=P-51D

[/CODE]

But whenever I started FSX I found that my planes lost contact to their profiles, like this Aircraft.cfg:

[CODE]
[fltsim.0]
title=P-51D 'Kwitcherbitchin'
...

[fltsim.1]
title=P-51D 'Blondie'
...
[/CODE]

I could attach the currently loaded plane to its profile and it was added to the profile

[CODE]
[Profile.Single Prop Mustang AccuSim]
1=P-51D
2=P-51D 'Kwitcherbitchin'
[/CODE]

and the profile worked again for that plane...

I took a close look and found that:

[CODE]ShortAircraftNameOk=Yes[/CODE]

was always reset to:

[CODE]ShortAircraftNameOk=No[/CODE]

when I started FSX or reloaded FSUIPC.ini.

I rolled back to V 4.8.3.1 and the resetting was gone.

Maybe you should have a look at it, until then I continue with V 4.8.3.1

[Pete Dowson]

I took a close look and found that:

ShortAircraftNameOk=Yes[/CODE]

was always reset to:

[CODE]ShortAircraftNameOk=No[/CODE]

when I started FSX or reloaded FSUIPC.ini.

I rolled back to V 4.8.3.1 and the resetting was gone.

I cannot reproduce this problem here at all, no matter what I do. It sounds like something may be corrupting memory. I need more information, maybe your entire INI file and some notes about what you are doing.

Regards

Pete

[CHBTheDoctor]

Thanks for looking into it, tell me what information you need, I'll go for it this evening after work...

[Pete Dowson]

Thanks for looking into it, tell me what information you need, I'll go for it this evening after work...

Complete INI file to start with. FSUIPC4.Log file. Some idea of whether it always occurs no matter what you do -- e.g. just loading FSX, getting to flight mode, then closing don ... does that do it? If not it'll be something you do subsequently, so I'd need to determine what.

If it isn't a hardware memory problem it could only be some corruption occurring from some add-in, so i need a list of all the add-ins. And then it might be a process of eliminatin. i.e. stopping one of those at a time.

The parameter "ShortAircraftnameOk" is written backto the INI from a 32-bit word in the midst of a lot of other data. If it is 0 it is "No", if it is >0 it is "Yes" and if it is <0 it is "Substring". something is zeroing it if itis changing to "No". FSUIPC never writes to it after reading it from the INI, and it only reads it the once, during initialisation. If you can determine exactly when it changes it would be useful.

Pete

[CHBTheDoctor]

F**k, a HeisenBug (try to observe him, he vanishes...)

I put the V4.8.3.4 back into Modules, but everything is ok with ShortAircraftNameOk (sigh).

The only thing that changed since then is the A2A Core Accu-Sim DLL, I updated from Core Accu-Sim v.1.3.1 to Core Accu-Sim v.1.4 (just for the record)

I attached my (zipped) FSUIPC.ini but I don't see much sense in investigating this further, as I said, a HeisenBug. When such a thing happens again, I know what info you need and will collect it. Until then we should close the case and I go on with V 4.8.3.4.

Nevertheless, I switched the console window on for the second try, maybe something interesting for you...

Console Started ...
********* FSUIPC4, Version 4.834 by Pete Dowson *********
User Name="XXXXXXXXXXXXX"
User Addr="XXXXXXXXXXXX"
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
Running inside FSX on Windows 7
Module base=61000000
	  203 System time = 11/06/2012 20:43:57
	  203 FLT path = "C:\Users\XXXX\Documents\Flight Simulator X-Dateien\"
	  219 Trying to connect to SimConnect Acc/SP2 Oct07 ...
	  266 FS path = "G:\Flight Simulators\FSX\"
	  531 LogOptions=00000000 00000001
	  531 Wind smoothing fix is fully installed
	  531 G3D.DLL fix attempt installed ok
	  531 SimConnect_Open succeeded: waiting to check version okay
	  531 Trying to use SimConnect Acc/SP2 Oct07
	 6459 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0)
	 6459 Initialising SimConnect data requests now
	 6459 FSUIPC Menu entry added
	 6490 C:\Users\XXXXX\Documents\Flight Simulator X-Dateien\Cessna in Egelsbach.FLT
	 6490 G:\Flight Simulators\FSX\SimObjects\Airplanes\C172\Cessna172SP.AIR
	17145 Weather Mode now = Custom
	17145 c:\users\XXXX\documents\flight simulator x-dateien\_Fall City 1WA6.FLT
	80107 System time = 11/06/2012 20:45:17, Simulator time = 08:48:56 (15:48Z)
	80138 Aircraft="Cessna Skyhawk 172SP Paint1"
	82041 Starting everything now ...
	83305 Advanced Weather Interface Enabled
   162663 G:\Flight Simulators\FSX\SimObjects\Airplanes\WoP3_P51D\p51d.AIR
   163084 Aircraft="P-51D 'McSwine'"
Error, no table returned
   197030 Sim stopped: average frame rate for last 34 secs = 30.7 fps
[/CODE]

FSUIPC4.zip

[Pete Dowson]

F**k, a HeisenBug (try to observe him, he vanishes...)

;-). Nice name for it!

Nevertheless, I switched the console window on for the second try, maybe something interesting for you...

If you mean the instrusion of the message

Error, no table returned[/CODE]

then it doesn't interest me. it isn't from FSUIPC, but from some other add-in DLL or Gauge you have installed. The Console Window is owned by the EXE process that is FS, and anything sending messages to it will have them appearing there even if they haven't actually opened it themselves. I see this quite a lot. One process can only have one console window.

Regards

Pete

[CHBTheDoctor]

The Console Window is owned by the EXE process that is FS, and anything sending messages to it will have them appearing there even if they haven't actually opened it themselves. I see this quite a lot.

That's nevertheless interesting, so this could be useful when looking for other problems...

Ok, thanks for your help, as I said, when it's happening again I'll tell you.

Currently I'm happy, FSUIPC and A2A Accusim nicely integrate the controllers for my A2A Mustang setup...

...so I'm off, WARBIRD flying :mrgreen: