Prepar3D v2 Hotfix (2.5.12943.0) **SOLVED**

[DesertPilot85]

LM just released a hotfix to bring 2.5.12942.0 to 2.5.12943.0:  http://www.prepar3d.com/forum-5/topic/prepar3d-v2-hotfix-2-5-12943-0-2/

I think this will require an updated FSDT addon manager...I'm holding off installing the hotfix until FSDT's confirmation.

[SN737]

You're right, it kills all FSDT productos!!
Hope they can fix it asap
Regards

[Midnight Music]

All FSDT sceneries gone as well as GSX. I tried re-installing, but it doesn't work. Will await a fix from FSDT.

Lee

[Drumcode]

Indeed, hotfix from LM screwed it up.

[jodle]

Same problem ;-( waiting for fix.

[virtuali]

There are several threads about it already, there's no need to keep opening new ones.

As already discussed many times already on the forum, each time there's a new build of a sim, you must wait for an upgrade to our modules to support it, just like FSUIPC, which requires an update for every new build of the sim.

We'll surely release it soon, as we always did for each new P3D build that came out since P3D was released.

[virtuali]

The updated Addon Manager is online now. No need to redownload anything: just run any installer you have ( a scenery, GSX, or the Stand-Alone Addon Manager ), to have the installer download the updated DLL files, which supports the P3D 2.5.12943 Hotfix.

[RAY VLASEK]

FSDT Logs file attached,  used latest installers... most crashes at kdfw but randomly at other FSDT airports...KIAH, KLAX

Fresh install, no other add-ons,  no tweaks, default airports no problem, crash with no windows or Prepar3d errors, it just shuts down after message saying "Prepar3d has stopped working".  I'm using Win 7 64bit fresh clean install, no anti virus installed yet...

Update,  did a complete re install of Prepar3d,  used for about 35 minutes on default airport, no crashes,   installed KDFW,  as soon as i started moving in aircraft crashed at KDFW,  again no error just went to desktop,  ?  Both add on mgr and Couatl shows in pull down menus.    2.5.12943.0_Hotfix Has Not been installed...

[SN737]

Hi Umberto

I've installed P3D v2.5 hotfix and the latest FSDT addon manager too, I'm getting CTD's StackHash_0a9e error like crazy.
I've un-installed all my FSDT and FlightBeam addons and could complete a 90min flight without any sort of CTD's.

So for me the latest FSDT update that works with P3D's hotfix, causes CTD, StackHash_0a9e module error, almost every time I open the sim.

Regards

[virtuali]

So for me the latest FSDT update that works with P3D's hotfix, causes CTD, StackHash_0a9e module error, almost every time I open the sim.

I can't see how this can have anything to do with the updated Addon Manager. Usually, when we need to support a new build of the sim, we need to change a few internal pointers to access directly in memory, that always (almost) change between builds.

But in THIS specific case, we found (after testing each one, of course) the hotfix hasn't changed anything in those memory offsets so, the ONLY update we had to do to the Addon Manager, was just to allow it to recognize the new build, and that's it.

Nothing else has changed so, if the pre-Hotfix 2.5 version worked for you (the change from 2.4 to 2.5 WAS, instead, VERY significant), there's no reason why you would have problems with the Hotfixed version, since the code it 100% the same, except for the line that accepts both build numbers as valid, in order to continue executing the Addon Manager.

Of course, before replying to you, I've loaded the P3D at FSDT KDFW, used GSX to pushback the default Lockheed Constellation, and no problems came out.

If you can contact me with a PM, we might arrange a Teamviewer session, so we might find out what the problem really was.

[virtuali]

Your log file shows there's nothing wrong with Couatl, and it has detected a P3D crash.

I made some test, and yes, I got crashes too but, the issue is:

1) I got several access violations at start by Prepar3D.exe, but I get them with the ADDON MANAGER DISABLED!

2) I also got an RPC error with Prepar3D.exe and again, it shows regardless if the Addon Manager is loaded or not.

3) The Windows Event Viewer shows, in addition to a StackHash error, a .NET runtime error too. NONE of our software use or has any relationship with .NET

Now, it's possible these issues would cause a visible crash only together with the Addon Manager, but it's clear there's something wrong with P3D even without the Addon Manager installed, because I can see the access violations it in the debugger, even with NO Addon Manager running.

We'll surely investigate it further, and report it to LM, maybe they'll have some ideas.

[speedbird217]

I can confirm this issue. After installing the update I get CTDs with the below error in usually less than a minute. Sometimes it even crashes when just in the main flight setup screen of P3D.
Before the update I never had any CTD with this error. I uninstalled all FSDT software and tested for hours without crash. Reinstalled FSDT/GSX and get a CTD immediately. It is definitely the updated FSDT/GSX installation that is causing this:

Problem Event Name:    APPCRASH
  Application Name:    Prepar3D.exe
  Application Version:    2.5.12942.0
  Application Timestamp:    54d283cc
  Fault Module Name:    StackHash_0a9e
  Fault Module Version:    0.0.0.0
  Fault Module Timestamp:    00000000
  Exception Code:    c0000005
  Exception Offset:    ffb10016

[RAY VLASEK]

OK, thanks

[virtuali]

Before the update I never had any CTD with this error. I uninstalled all FSDT software and tested for hours without crash. Reinstalled FSDT/GSX and get a CTD immediately. It is definitely the updated FSDT/GSX installation that is causing this

No, it's not. Not directly. In fact, if you read the result of a test I just made here:

http://www.fsdreamteam.com/forum/index.php/topic,11608.msg89082.html#msg89082

I can see the StackHash crash with a c0000005 (access violation) error even WITHOUT the Addon Manager. You will not see it, because in order to see it, I had to run P3D under the Visual Studio debugger, but I assure you the error happens even without the Addon Manager loaded, so this is probably CAUSING the issue.

What might happen is, this invisible error (not invisible if you run under a debugger), might become an actual crash when P3D is also loading a module, so you assume it's caused by the Addon Manager because it's the only way you can see it.

Not just that. Your P3D.EXE is not even patched when the hotfix and, in addition to that, as I've already explained, NOTHING has changed in the Addon Manager, except that it now accepts both versions 2.5.12942.0 (yours, pre-Hotfix) and 2.5.12943.0 (with the Hotfix), but it's otherwise identical.

But don't assume we consider the case closed. We'll surely further test this, because there might be other unknown issues. In fact, the largest change (from our point of view) was when moving from 2.4 to 2.5, but nobody ever had problem with plain 2.5 as of today, and you are still running without the Hotfix, it seems.

[speedbird217]

Thanks for the explanation.

This is very odd, as I was using 2.5 with GSX before and never got a single crash. Then I installed the new addon manager and the crashes started. No crashes when the addon manager is uninstalled, so forgive me for pointing the finger.

I will try tonight with the hot fix and see if that changes anything. Until then I am looking forward to anything you can find out, as I would rather not reinstall everything (just done that 2 weeks ago for 2.5) and don't want to fly without FSDT/GSX.