Jump to content
The simFlight Network Forums

Recommended Posts

Posted

I just made four flights with four crashes. I was able to recover two of the four FSUIPC.log and Windows reports.

 

The crashes are all in the Lua interpreter. Can you tell me what Lua programs are being run? The logs end with the end of ipcReady.lua execution,which is where any Lua plug-ins it starts will run.

 

If you have several Lua plug-ins being started, could you find which one is causing it by elimination, please? Then I'd need to see it, or even try it here if it isn't hardware dependent.

 

Once you've identified the culprit, maybe you could rerun after first enabling Lua/Debug tracing in the FSUIPC Logging options. The Lua logging would identify the actual step.

 

It would be useful to know if this is specific to P3Dv3. Did you use the same settings with FSX at all?

 

Pete

Posted

Pete Good evening,

thank you very much for responding so quickly. I forgot to tell you that I only fly long haul.

All flights are at least seven hours. Never less. Crashes happen 6 8 10 hours after takeoff NEVER NEVER before.

Eleven Lua plugins are started and are dependent.

I could not identify the culprit at start up. I can enable Lua/Debug tracing in the FSUIPC Logging options .......  but the file size will be enormous ..... thousands of lines :smile:)

I'll do it if you think this could help you.

In the attachment FSUIPC.ini ( renamed as .txt to attach it ). You can see my .lua launched.

Two of my friends use the same configuration P3DV3 GSX ASNext and have no crashes ....... maybe it is hardware dependent ?

 

I never use FSX with this configuration.

Thank you in advance for the time spent trying to find a solution.

Best regards.

Francis.

FSUIPC4.txt

FSUIPC4.txt

Posted

All flights are at least seven hours. Never less. Crashes happen 6 8 10 hours after takeoff NEVER NEVER before.

 

Ah, there are many reports of P3Dv3 crashes after long periods. Please see the L-M forum for these. I've not seen any before yours which have FSUIPC specifically identified, but, as I mentioned, the crashes are all pretty deep in the Lua interpreter, which is not actually my code but the freely distributed Lua interpreter used by a large number of games and other applications.

 

The fact that these occur after such a long time indicates that it is likely not a specific bug in FSUIPC or the Lua interpreter -- everything used by all the things you are doing must have been done so many times by then that it has to be something else

 

I could not identify the culprit at start up. I can enable Lua/Debug tracing in the FSUIPC Logging options .......  but the file size will be enormous ..... thousands of lines  :smile:)

 

No, it will not help for the reasons I've given, let alone the size. I suspect that even if you discarded all those add-ons, and even FSUIPC itself, you'd still get the crashes after a length of time. I think it must me down to memory corruption which looks to me the probable cause of the other problems reported with P3Dv3, even with no add-ons whatsoever. Other users appear to be trying to narrow it down. The closest they've come so far it that it might be related to Terrain settings. I recommend you read some of the threads and maybe participate.

 

In the attachment FSUIPC.ini ( renamed as .txt to attach it ). You can see my .lua launched

 

No. That just lists those Lua files you have in the Modules folder and so are available for assignment. I assume you mean that all those which are installed are actually running (actually 11 after ipcReady), but the only thing which would show that is presumably your ipcReady.Lua file. Also, programs like Linda, and possibly others, may well be loading Lua plug-ins from other folders, those not listed for FSUIPC assignment.

 

You don't actually have any keys or buttons assigned to Lua functions. in fact, and -- this is quite unusual -- you have no button assignments whatsoever in FSUIPC, though you do have axis assignments!  nothing wrong with that, it is just that I've never seen anything like that before. Don't you use any buttons on your joysticks?

 

I never use FSX with this configuration.

 

Why not? That would be the best way to prove that it is, after all, a P3Dv3 bug.

 

Pete

Posted

Hi Pete,

I'll go take a look at the LM forum as you suggest. If I find a solution I would not fail to keep you informed.

Button assignments are programmed via LINDA interface. It is more flexible in use ( for me ) to assign complex functions on the 777 PMDG .

Again thank you for your help.

Best regards.

 

Francis.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.