Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Linda 3.0.2 crash on aircraft change

Featured Replies

Hi Yves 

Thank you for the update. It is strange that ipcready.lua is involved. It is a key FSUIPC function for calling Lua code once the Inter-Process Control (ipc) is running. Please email. A copy of multiaxis.lua so I can try and replicate your fault report. 

I know that changes in Lua were made when moving to 64-bit and code was copied back to the FSUIPC4 baseline.

There are known issues when switching from the sophisticated aircraft, like PMDG777 and FSLABS, but not between default aircraft. 

Andrew Gransden

Scotland, UK

LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer

i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew

Hi Yves

Although I did not see the axes changes, I have been able to reproduce the P3Dv4 crash using the multiaxis.lua code. The crash occurred each time when I change the aircraft (default). The Event Viewer crash reports shows that it in FSUIPC5.dll that is crashing. Even removing the Event.param statement did not prevent the crash. When I renamed the multiaxis.lua extension so that it does not load there was no crash. 

I will send my logs to Pete Dowson (FSUIPC developer) next week when he returns.

Andrew Gransden

Scotland, UK

LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer

i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew

Okay, thanks for checking. So let's wait and see what Pete thinks could cause the crash.

Yves

Yves Guillaume

P3Dv4

Author of "Flight Dynamics in Microsoft Flight Simulator - An Analysis of the Aircraft Specific Input Parameters of FS 2004 and FSX"

  • Author

Awesome. I could not get the p3dv3 start from my backup due to licensing after uninstall/move. Yay DRM. Thank you Yves

  • Author

Just as a follow up. FSUIPC v5.121a has removed the crashing problem for me entirely without changing anything else.

cheers

 

Deimos

1 minute ago, Deimos said:

Just as a follow up. FSUIPC v5.121a has removed the crashing problem for me entirely without changing anything else.

cheers

Deimos

Thank you for the update. I have just this minute logged the problem on the FSUIPC forum.

Andrew Gransden

Scotland, UK

LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer

i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew

Thanks for posting the problem on the fsuipc support forum.

Unfortunately, Version 5.121a didn't resolve the issue here, neither with my multiaxis.lua nor with the test script flapsdisplay.lua I posted earlier (which just gives a simconnect message when flaps are moved). With ipcReady.lua in the [Auto] section of fsuipc.ini there's still a crash of fsuipc5.dll and p3d on aircraft change exactly like before. The Windows event viewer and fsuipc5.log file also look identical.

 

Yves Guillaume

P3Dv4

Author of "Flight Dynamics in Microsoft Flight Simulator - An Analysis of the Aircraft Specific Input Parameters of FS 2004 and FSX"

I am sorry you are still experiencing the problem.  Without ipcready.lua available LINDA core LUA code can not start - LINDA would simply not function. Therefore, if you wish to use LINDA with your multiaxis.lua then we need to get to the bottom of the problem. 

The [auto] entry in FSUIPC5.INI which starts your add-on may lie at the source of the problem. You could try removing this entry and inserting a Lua multiaxis inside ipcready.lua beside the LINDA command. 

I am not sure what else I can offer. LINDA is functioning correctly with other Lua addons. You can continue the conversation with Pete Dawson at http://forum.simflight.com/topic/84157-multiple-lua-files-crashing-p3d-on-aircraft-change/

I will continue to monitor and add comment as necessary. 

 

Andrew Gransden

Scotland, UK

LINDA Support/Developer - VATSIM and BAVirtual - Airbus Flyer

i7 1TB SSD GTX980 - FSX/P3D - Aerosoft Airbus A318/A319/A320/A321 - FS2Crew

Thanks, your hint to the ipcReady.lua was helpful. I added the Multiaxis code in it right below the default Linda entry. This didn't start the script, however when I also keept the Multiaxis code in its own lua file and in the [Auto] section as before, I got it working again. The crash did not appear anymore on aircraft change!

I then edited the code in ipcReady.lua many times and did a lot of tests. The result is not clear yet. It seems that just any code in ipcReady.lua could stop the crash, even if there are only comments in it or just the function-end-block. But in some cases the Multiaxis script stopped working randomly on one plane and then restarted when another plane was selected (not related to any specific aircraft). With some code the crash still happened occasionally after maybe 6 to 7 aircraft changes, sometimes earlier or later.

I can only guess that there is a timing issue between Simconnect and FSUIPC on aircraft change. Maybe too many tasks or scripts are trying to access simconnect at the same time (my orginal issues was with a fresh installed  P3dV4). Even the different log functions of fsuipc could have an impact.

I'll do some more tests. I can report my results directly at http://forum.simflight.com/topic/84157-multiple-lua-files-crashing-p3d-on-aircraft-change/

 

Yves

 

Yves Guillaume

P3Dv4

Author of "Flight Dynamics in Microsoft Flight Simulator - An Analysis of the Aircraft Specific Input Parameters of FS 2004 and FSX"

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.