If I wait 2 more weeks we"ll be on v 3.135278... LOL

 

As I am painting my cockpit floor I won't be able to start upgrading to v 2.5 before next weekend.

( Lucky me...you guys will have worked it all out by then ... )

If I wait 2 more weeks we"ll be on v 3.135278... LOL

 

As I am painting my cockpit floor I won't be able to start upgrading to v 2.5 before next weekend.

( Lucky me...you guys will have worked it all out by then ... )

If I wait 2 more weeks we"ll be on v 3.135278... LOL

 

As I am painting my cockpit floor I won't be able to start upgrading to v 2.5 before next weekend.

( Lucky me...you guys will have worked it all out by then ... )

 

Thank god im on vacation and enjoying the warm thai sun with a cool drink in my hand soon and not being online for the next three weeks

I uninstalled two of the 3 simconnect files I had - but the stuttering is persisting even with default aircrafts. Now I will try a complete reinstall of P3D as I remember stuttering was less of an issue when I first started using P3D v2.5

Rob

 

I could not find 12944 hot fix. Do you have link?

 

Thanks

Terry

Rob, conjecture on other forums is that this will break compatibility with addons again...any input on how it's behaving on your system?

 

 

I could not find 12944 hot fix. Do you have link?

 

Hmmm ... looks like it wasn't released.

 

 

 

Rob, conjecture on other forums is that this will break compatibility with addons again...any input on how it's behaving on your system?

 

I'm testing today, but I would urge end users to get very specific details as to why some (not all) add-ons no longer work when nothing about the fixes made in 12944 would affect them?  ... this is a hot potato subject ... but I am getting a little frustrated at finger pointing by some (not all) 3rd party.  LM have reached out to 3rd party with the same question ... let's hope the 3rd party affected by a changing core EXE/DLL will work with LM to get a long term solution.

 

Cheers, Rob.

I think it's more user conjecture that I've seen (nice to nip that in the bud too).

 

Edit: just see that ORBX have pushed a new objectflow dll...looks like they're already on the ball with this one.

I can confirm ORbx is fine, PMDG is fine, FSGRW is fine, Q400 is fine.  I'll test Virtuali after I get some lunch.

 

Cheers, Rob.

 

 

I can confirm ORbx is fine, PMDG is fine, FSGRW is fine, Q400 is fine

 

Thanks, that's good to know... Pete Dowson is also ready with FSUIPC as it seems (according to the docs for the latest release, obviously I don't have the hotfix to test ^_^).

 

Really no need for the doom and gloom all over again... :wink:

 

Tym

939 FSUIPC isn't causing any issues so far.

 

CS 777 is working fine

939 FSUIPC isn't causing any issues so far.

 

 

It was the FSUIPC full installer that wouldn't install in P3d 2.5.12943 because of a version checking issue. I just saved my modules folder and copied it over after installing the first P3d Hotfix.

 

However, installing  that newest FSUIPC (4.939c) with P3d 12943 caused P3d not to start for me. Disabling FSUIPC in DLL.XML fixed the issue, as did returning to the original FSUIPC 4.939 build.  My guess is that there is nothing wrong with FSUIPC, but rather there is something incompatible with an addon that uses it.  EDIT: At least one other user has already reported this to Pete on his official forum, so be careful. The error was:

Faulting application name: Prepar3D.exe, version: 2.5.12943.0, time stamp: 0x54e39da6
Faulting module name: ai_player.dll, version: 2.5.12943.0, time stamp: 0x54e39da2
Exception code: 0xc0000005
Fault offset: 0x00045d19
Faulting process id: 0x864
Faulting application start time: 0x01d0538cd180f3d7
Faulting application path: G:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe
Faulting module path: G:\Program Files (x86)\Lockheed Martin\Prepar3D v2\ai_player.dll
Report Id: 26f9a090-bf80-11e4-822c-001fbc02953f
Faulting package full name: 
Faulting package-relative application ID: