Jump to content
The simFlight Network Forums

FSUIPC6/P3Dv5 - Runif kill and close statements trouble


Recommended Posts

Hi,

I've just upgraded to FSUIPC6 and now I'm using it for both P3D4 & 5 (separate installs but same settings, addon.xml method for both). With P3D5 it seems that the Kill or Close actions in Runif are not working. No problem with P3D4 (same behaviour than with FSUIPC5). 

Any idea of the cause?

Thanks. Skip.

Link to comment
Share on other sites

7 minutes ago, Skipy33 said:

With P3D5 it seems that the Kill or Close actions in Runif are not working. No problem with P3D4 (same behaviour than with FSUIPC5). 

Any idea of the cause?

I'm using them both here quite happily with FSUIPC6 on both P3D4 and P3D5. Are you sure it's not just a matter of different privilege levels? Check that you are running both P3D4 and P3D5 with the same "compatibility" settings (right click on the EXE or shortcut and choose properties - compatibilty.

I forgot to set mine correctly originally and got simlar problems.

If this isn't the problem i need to see your FSUIPC6.LOG file from the P3d5 run.

Pete

 

Link to comment
Share on other sites

Hum... The only difference was the "disable full screen optimization" not set in P3D5 (I remember I had to set this in P3D4 because I had issues with snapshots). I've just made the test with it and I've got the same result. P3D5 exits well (Chaseplane exits few seconds after) but the 3 programs launched by FSUIPC6 no:

[Programs]
Runif1=READY,HIDE,CLOSE,I:\P3Dtools\sadvX.exe
Runif2=KILL,I:\P3Dtools\Greenshot\Greenshot.exe
Runif3=READY,HIDE,CLOSE,I:\VRInsight\bin\SerialFP2.exe

Skip.

Link to comment
Share on other sites

18 minutes ago, Skipy33 said:

but the 3 programs launched by FSUIPC6 no:

[Programs]
Runif1=READY,HIDE,CLOSE,I:\P3Dtools\sadvX.exe
Runif2=KILL,I:\P3Dtools\Greenshot\Greenshot.exe
Runif3=READY,HIDE,CLOSE,I:\VRInsight\bin\SerialFP2.exe

Where's the log, please, showing this.as requested.

I'm taking a little time off now, so it'll be later -- enought time for you to find the log, for sure! 😉

Pete

 

 

Link to comment
Share on other sites

3 hours ago, Pete Dowson said:

Where's the log, please, showing this.as requested.

I'm taking a little time off now, so it'll be later -- enought time for you to find the log, for sure! 😉

Pete

 

 

Ok, here's the log. I've made the comparison with an old FSUIPC5 log and I can see that FSUIPC6 isn't closing properly. The last line is :

101984 === Closing session: waiting for DLLStop to be called ...

My P3D5 is still very "light" in terms of addons so it exits very fast. Is it possible that Prepare3d.exe is exiting so fast that FSUIPC6.dll doesn't have the time to finish the job?

Skip.

FSUIPC6.log

Link to comment
Share on other sites

17 hours ago, Skipy33 said:

Ok, here's the log. I've made the comparison with an old FSUIPC5 log and I can see that FSUIPC6 isn't closing properly. The last line is :

101984 === Closing session: waiting for DLLStop to be called ...

Right. DLLStop is the procedure in FSUIPC (in all added SimConnect DLLs) which is called by the simulator when it is closing. without that notification FSUIPC cannot do any tidying up.

17 hours ago, Skipy33 said:

My P3D5 is still very "light" in terms of addons so it exits very fast. Is it possible that Prepare3d.exe is exiting so fast that FSUIPC6.dll doesn't have the time to finish the job?

No, it isn't even getting the notification. I think your P3D5 is not closing but crashing out. Check the Windows Event Viewer to see if there are any errors listed mentioning Prepar3D.exe. They'll be in the Windows Logs/Application section.

Pete

 

Link to comment
Share on other sites

55 minutes ago, Pete Dowson said:

Right. DLLStop is the procedure in FSUIPC (in all added SimConnect DLLs) which is called by the simulator when it is closing. without that notification FSUIPC cannot do any tidying up.

No, it isn't even getting the notification. I think your P3D5 is not closing but crashing out. Check the Windows Event Viewer to see if there are any errors listed mentioning Prepar3D.exe. They'll be in the Windows Logs/Application section.

Pete

 

Pete, you were right as always! I found a Kernelbase.dll crash exiting prepar3d. The fault is on ORBX objectflow addon and I'll now investigate with them.

Thanks for your help.

Skip.

Link to comment
Share on other sites

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.