ipc.display + P3Dv2 = crash?

[Artem Crum]

Hello Pete,

 

I've stumbled upon strange situation.

 

This simple command crashes the P3Dv2 to desktop. No other Lua scripts are running simultaneously, the only script executed is a file with this one and only string (script is executed by 'Lua testscript' command assigned to joystick button):

ipc.display('Test')

Windows Error log:

Fault bucket 73316406496, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Prepar3D.exe
P2: 2.2.10437.0
P3: 533d6c08
P4: FSUIPC4.dll
P5: 4.9.3.4
P6: 537f5a02
P7: c0000005
P8: 00013586

=========================================================

Fault bucket 73349789338, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0
 
Problem signature:
P1: Prepar3D.exe
P2: 2.2.10437.0
P3: 533d6c08
P4: FSUIPC4.dll
P5: 4.9.2.8
P6: 52d1eec2
P7: c0000005
P8: 00012b3e
P9: 
P10: 

FSUIPC4 versions tested: 4.928 & 4.934a

[Pete Dowson]

Hello Pete,

 

I've stumbled upon strange situation.

 

This simple command crashes the P3Dv2 to desktop. No other Lua scripts are running simultaneously, the only script executed is a file with this one and only string (script is executed by 'Lua testscript' command assigned to joystick button):

P1: Prepar3D.exe
P2: 2.2.10437.0

 

As clearly stated in the download place and in the release notes AND in the sticky post at the top of this forum, you MUST update to P3Dv2.2 build 10438 if you want to use FSUIPC. There are many possible crashes otherwise, and half the facilities won't be working in any case. Lockheed-Martin changed quite a bit and the hooks FSUIPC uses just don't match!

 

And there's certainly no point at all trying FSUIPC 4.928 because that pre-dates 10437 by several versions!

 

Pete

[Artem Crum]

Oh... my apologies. Missed that.