FSX and P3d crash installing 4.8.9.5.5

[cellular55]

Hi,

I'm facing issues tryng to install the new version of FSUIPC. Both simulators crash at startup with the following message:

 

roblem signature:
  Problem Event Name:    APPCRASH
  Application Name:    Prepar3D.exe
  Application Version:    3.1.2.15831
  Application Timestamp:    5672b60a
  Fault Module Name:    FSUIPC4.dll
  Fault Module Version:    4.9.5.5
  Fault Module Timestamp:    574e288e
  Exception Code:    c0000005
  Exception Offset:    0001017a
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1040

Additional information about the problem:
  LCID:    1040

How could I solve the problem?

Thanks and best regards

Joe
 

[Pete Dowson]

8 minutes ago, cellular55 said:

Application Name:    Prepar3D.exe
  Application Version:    3.1.2.15831

Version 3.1 of P3D still? I no longer have that to test against. Why are you sticking with older buggy versions of P3D?

I'll have a look, but I need to see the FSUIPC4.LOG file up to the point of the crash, both for FSX and P3D. It sounds like a corrupted weather file, but I can't tell without logs.

I also need the crash info for the FSX one -- or is it EXACTLY the same?

Pete

 

[cellular55]

Hi Peter,

the error on FSX is the same:

Problem signature:
  Problem Event Name:    APPCRASH
  Application Name:    fsx.exe
  Application Version:    10.0.61472.0
  Application Timestamp:    475e17d3
  Fault Module Name:    FSUIPC4.dll
  Fault Module Version:    4.9.5.5
  Fault Module Timestamp:    574e288e
  Exception Code:    c0000005
  Exception Offset:    0001017a
  OS Version:    6.1.7601.2.1.0.256.48
  Locale ID:    1040

Additional information about the problem:
  LCID:    1040

the only difference is that before to crash FSX is presenting before a message bow saying the flight simulator has found a problem with FSUIP and does reccomend to uninstall it, proceeding I get the crash.

I have just installed the last P3D version, but nothins is changed.

Attached the FSUIPC logs

The last FSUIPC I can use without problem is the 4.9.4.8

BR

Joe

 

FSUIPC4.log

FSUIPC4.log

[Pete Dowson]

47 minutes ago, cellular55 said:

The last FSUIPC I can use without problem is the 4.9.4.8

What have you tried later than that, or is that the most recent other one you have?

I think the problem is related to your FSUIPC4.INI file(s). Can you show me those please? 

Pete

 

[cellular55]

Hi,

after the 4.9.4.8 I tried with the  4.9.5.3 with the same type of issue. I was hoping that the new version was solving it.

Attached the 2 FSUIPC.INI

BR

Joe

 

 

FSUIPC4.ini

FSUIPC4.ini

[Pete Dowson]

22 minutes ago, cellular55 said:

after the 4.9.4.8 I tried with the  4.9.5.3 with the same type of issue. I was hoping that the new version was solving it.

Oh, I wish you had reported the problem with 4.953. Version 4.955 was a major release, and its a lot more work to have rebuild everything. There's never going to be a fix for something that isn't reported -- I can't possibly test every scenario here.

28 minutes ago, cellular55 said:

Attached the 2 FSUIPC.INI

Those are INI files when using FSUIPC 4.948, so they aren't exactly relevant. I need the ones after the crashes, please.

Also I see you use Profiles in Files. Does the default aircraft being loaded use one of those profiles? Because if so I'm afraid I need to see its file in its Profiles folder too, please.

Pete

 

[cellular55]

Hi Peter,

attached the FSUIPC.INI after the attempt to run FSX/P3D after the reinstallation of version 4.9.5.5.

The default aircraft loaded at FSX start does not use any profile, by the way I attach ini file related PMDG that is the aircraft I use more.

BR

Joe

FSUIPC4.ini

PMDG.ini

FSUIPC4.ini

[Pete Dowson]

2 hours ago, cellular55 said:

attached the FSUIPC.INI after the attempt to run FSX/P3D after the reinstallation of version 4.9.5.5.

Thanks. Interesting that it hasn't got the new "Annotate=Yes" parameter -- and the assignments aren't annotated -- so it isn't getting that far.

2 hours ago, cellular55 said:

The default aircraft loaded at FSX start does not use any profile

Good. That makes it a little easier to search for the problem. Leave it with me for now.

Pete

 

 

[Pete Dowson]

I think I've found it. It's a missing Macro file, and my code for dealing with it wasn't checking sufficiently thoroughly.

Please try FSUIPC4955b.zip and let me know. It's only the FSUIPC4.DLL -- copy into the FS modules folder. But please make sure you've run the 4.955 installer (again) first, otherwise your documentation and so on could be out of date.

If this works okay, check the INI file -- search for entries marked with "<unknown macro> !!!".  One or more of those were the problem. If you're no longer using those assignments, best to delete the line.

Pete

 

[cellular55]

Hi Peter,

as usual your support is more than fantastic: that dll solved the issue for FSX and P3D!!!

A last question: why in the .INI file I get the 'unknown macro' mark even if the macro with that name is existing?

Thanks a lot once more.

Joe

 

 

[Pete Dowson]

2 hours ago, cellular55 said:

why in the .INI file I get the 'unknown macro' mark even if the macro with that name is existing?

The macro file is one thing, the macros themselves are named within and assigned by sequence number.  So, are they all there? When you press the button or key assigned to any of those which say "missing", does the correct name show in the assignment?

If it looks wrong to you, I need to investigate, but I don't have your macros (nor for that matter your devices). You'll need to provide the new FSUIPC4.INI file containing the wrong "missing" comments, and the macro file which shows otherwise. If there are more than one, just one example will do.

I'll hold off releasing 4.955b generally until this is resolved one way or the other.

Pete

 

 

[cellular55]

Hi Peter.

here the FSUIPC.INI and the PMDG Macro for which error comments are reported.

Comments seem to be referred to parts of the macro considering keyboard strokes and not mouse clicks.

The other macro mentioned (WX) is effectively not existing.

BR

Joe 

FSUIPC4.ini

PMDG.MCRO

[Pete Dowson]

I'm looking now, but just scanning down you seem to be missing some other things. eg Lua plug in number 81 as listed here:

56=GS,B,-16384,-16253,L81:R,0    -{ Entering=Lua ERROR: unknown Lua! }-

2 hours ago, cellular55 said:

Comments seem to be referred to parts of the macro considering keyboard strokes and not mouse clicks.

The PMDG ones it thinks are missing sre not in  Key Strokes.  Not sure what you mean by "mouse clicks2 -- you can't assign mouse clicks in FSUIPC. Did you mean buttons? 

In fact the only references to the PMDG macro are these, in axis assignments:

65=DX,256
66=DX,B,11776,16383,M24:38,1    -{ Entering=Macro PMDG: <unknown macro> !!! }-
67=DX,B,-9362,9856,M24:39,1    -{ Entering=Macro PMDG: <unknown macro> !!! }-
68=DX,B,-16384,-9882,M24:40,1    -{ Entering=Macro PMDG: <unknown macro> !!! }-

Now I do see those entries (38, 39, 40) in the Macro file, so I'll investigate this now. Can you confirm that the Macro file is definitely in the Modules folder, not elsewhere? Why are there so few assignments to it when it contains 54 different macro names?

1 hour ago, cellular55 said:

The other macro mentioned (WX) is effectively not existing.

Okay. Best delete that line, then, unless you have the macro somewhere.

Pete

 

 

[Pete Dowson]

Right. Found it and fixed it, thanks to you.

All that it was -- the macros weren't being loaded before the comments were added, but only for the Axis assignments section. It was okay for buttons and keys. It's a one line fix, and i'll make a new release (probably with installer, to avoid the comments about it not liking P3D 3.3.5) tomorrow or monday.

Meanwhile it doesn't do any harm. It just gives incrrent "missing2 comments in the Axes sections.

Pete

 

[cellular55]

Hi Peter,

thanks.

Only another possible issue: if I close FSX and P3D and the restart them I get the following message:

'There seems to be duplicate copies of FSUIPC installed, or another running still in memory! Please remove older copies! Never simply rename modules, move them OUT of the Modules folder!
If there are no duplicates please use Task Manager to check that the'

I do not have any duplictaed or renamed FSUIPC.DLL and going in the task manager no multiple FSUIPC instances result running.

Joe

 

 

[Pete Dowson]

48 minutes ago, cellular55 said:

Only another possible issue: if I close FSX and P3D and the restart them I get the following message:

'There seems to be duplicate copies of FSUIPC installed, or another running still in memory! Please remove older copies

This is an old misconception. You are restarting it before it has finished closing down. It takes a good few seconds after the FS window disappears. FSUIPC detects it is still running.

Pete

 

[cellular55]

Hi Peter,

you are right!

I have noticed that  when shut down the new version of P3D it remains still active in the processes list and I have to manually close it.

I will open a topic on the P3D forum about that.

Joe

 

[Pete Dowson]

38 minutes ago, cellular55 said:

I have noticed that  when shut down the new version of P3D it remains still active in the processes list and I have to manually close it.

You should not need to close it manually. It takes a while for FSUIPC to close all the threads, especially if you have any Lua plug-ins running. Also network use can delay the final termination. But if you've waited and it never closes that's something else. I've had that happen with some versions of P3D, but it's been okay with P3D version 3 so far. You don't get it with FSX do you?

Pete

[cellular55]

Hi Peter,

even after more than 30 mins after I have shut down P3D I see it in the list of processes yet: I think is some add-on I have.

I will do some more tests and checks and i will let you know.

Joe