FSDreamTeam forum
General Category => General Discussion => Topic started by: DesertPilot85 on February 21, 2015, 03:21:03 am
-
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.
-
You're right, it kills all FSDT productos!!
Hope they can fix it asap
Regards
-
All FSDT sceneries gone as well as GSX. I tried re-installing, but it doesn't work. Will await a fix from FSDT.
Lee
-
Indeed, hotfix from LM screwed it up.
-
Same problem ;-( waiting for fix.
-
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.
-
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.
-
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...
-
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
-
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.
-
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.
-
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
-
OK, thanks
-
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.
-
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.
-
Yes I am experiencing CTD also after re install KLAX and KLAS.....However, I do have ORBx base,vector,and some USA regions previously tested with NOT issues for several hours, my question is should I move fsdream airports down to scenary list or I should keep them in the default install order???..I am asking just to make sure that Orbx Lib should be on top??? , I believe, and then everything else???.....but regardless the order I do have crash after last Fsdream add manager (KLAS-KLAX) update that covered the last P3D fix...
Thanks
Pedro
no specific error just "P3D stop working"
-
I don't have any idea about where the Orbx library should be, but the airports will surely be on top of everything else. But I don't thing this is an issue regarding the crash. See my previous reply about it.
-
yeah I saw it...There are three thing that came out pretty much at same time..The P3D fix, the ASN for that fix and the new FSD addon manager for the last P3D update....we have to test them individually so we can come out with a conclusion.....any of them can maybe mismatching some how with each others.....
I am going to uninstall FSD and fly same route . (No ASN) .will report back tonight
Thanks
Pedro
Thanks for let me know that FsD must to be on top...I have it that way though..
-
Did a clean install of Win7 + P3Dv2.5+ Hotfix at the weekend and plain sailing until this afternoon when I installed one and only addon so far ... FSDT PHNL and I get the crash ...
-
I can also confirm I am receiving a CTD with Stackhash error ONLY when installing addon manager with GSX, uninstalling GSX and Addon Manager results in no crashes.
-
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
I'd like to add, that I also have Estonia Migration Tool, the latest version installed (but disabled). May be the culprit may be not.
-
Hello,
I am also seeing the same thing...CTDs during the first minutes of flight or even before it (when selecting an aircraft). That after installing the latest hotfix and running the Addon Manager downloaded from the website of GSX to update the files for the hotfix.
Event Viewer gives me the following errors:
--------------------------------------------------------------------------
Fault bucket 879237685, type 17
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Prepar3D.exe
P2: 2.5.12943.0
P3: 54e39da6
P4: StackHash_0a9e
P5: 0.0.0.0
P6: 00000000
P7: c0000005
P8: ff990016
P9:
P10:
Attached files:
C:\Users\Ifikratis\AppData\Local\Temp\WERCEB4.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\Ifikratis\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_a69d25d74b7150d28477689826a0c361ac93896d_1f8bfdcf
Analysis symbol:
Rechecking for solution: 0
Report Id: a63cd2b7-bc4b-11e4-b3a0-902b34da42e2
Report Status: 0
----------------------------------------------------------------------------
Faulting application name: Prepar3D.exe, version: 2.5.12943.0, time stamp: 0x54e39da6
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0xff9e0016
Faulting process id: 0x1e0
Faulting application start time: 0x01d05050280095cd
Faulting application path: C:\Program Files (x86)\Lockheed Martin\Prepar3D v2\Prepar3D.exe
Faulting module path: unknown
Report Id: baebee68-bc47-11e4-b3a0-902b34da42e2
----------------------------------------------------------------------------
Application: Prepar3D.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address FF9E0016
----------------------------------------------------------------------------
Any help would be really appreciated.
-
Me too, same error following install of FSDT / Addon Manager.
Daz
-
I can also confirm I am receiving a CTD with Stackhash error ONLY when installing addon manager with GSX, uninstalling GSX and Addon Manager results in no crashes
As I've said, there's something strange about this, because I can see errors (which you can't see, if you don't run P3D under a debugger) even WITHOUT the Addon Manager loaded, and they happens only with the Hotfix.
The only theory I have, is those errors that happens even without the Addon Manager loaded, will become more serious when the Addon Manager is loaded, so they appear as proper errors with a crash, but they might be the original cause of the problem.
As I've said, the Addon Manager is unchanged, except for allowing to run with the Hotfix, because nothing of the things that needs to be updated has actually changed so, if there was an issue with the Addon Manager, it should have happened with plain 2.5 too, while all these reports are coming only after the Hotfix.
The issue is, I also get crashes with the Addon Manager loaded, but they are entirely random. Once I can run with no issue for quite a while, the next I get a crash within a minute. Perhaps there's some kind of conflict between VC++ libraries, but I just can't trace it to anything.
Again, the case is NOT considered closed or solved, it's just that right now I don't have any idea, other than the Hotfix doesn't seem to be very stable.
-
Once all airports have been activated via the Addon Manager will they still work if the Addon Manager is uninstalled to prevent the crashing?
Thanks,
Daz
-
As I've said, the Addon Manager is unchanged, except for allowing to run with the Hotfix, because nothing of the things that needs to be updated has actually changed so, if there was an issue with the Addon Manager, it should have happened with plain 2.5 too, while all these reports are coming only after the Hotfix.
Again, the case is NOT considered closed or solved, it's just that right now I don't have any idea, other than the Hotfix doesn't seem to be very stable.
The problem occurs even without the Hotfix. As I mentioned before, I had everything working in P3D 2.5 (No Hotfix). All I did was install your updated Addon Manager and the P3D 2.5 immediately started with the CTDs. No Hotfix involved. So there must have been something in the update you released for the Hotfix that causes this. P3D 2.5 No Hotfix + previous Addon Manager = no problems, P3D 2.5 No Hotfix + current Addon Manager = CTDs all the time.
I hope this can be resolved soon. Is LM aware of your findings regarding the errors in their program?
-
Once all airports have been activated via the Addon Manager will they still work if the Addon Manager is uninstalled to prevent the crashing?
As explained, many times already, the Addon Manager is not needed "just" for the activation management, which is less than 1% of its features.
Both the Addon Manager and the Couatl programs are needed by all our products, because the *create* most of the scenery. In fact, if you don't run them, the scenery won't work even in Trial so, it's more or less like FSUIPC: if it cannot be loaded for any reason, lots of products won't work, regardless of their registration status.
-
I hope this can be resolved soon. Is LM aware of your findings regarding the errors in their program?
I would like to find a more clear way to display such errors, because running P3D under the VS debugger is not how it's supposed to be used, it's even possible the debugger itself is causing this, so I would like to be sure, before reporting it.
So there must have been something in the update you released for the Hotfix that causes this
I agree that it SEEMS logical. But, again, since none of the memory locations we need to check has changed in the Hotfix, I really can't explain how this line:
if( ( build == 12942 ) || ( build == 12943 ))
{
// go on loading
}
could cause a problem, while this one wouldn't:
if( build == 12942 )
{
// go on loading
}
That's all that has changed in the latest build. So, the only possible explanation, if this is happening without the Hotfix installed, is that even the previous version was already unstable and nobody noticed it, because the same code it's running.
-
Thanks for the update Umberto.
I completely understand your frustration.
Is there any way of installing the last build (of your Addon Manager) before the update of your Addon Manager again? It would be interesting to see if I could install that and run it without CTDs again, as I did previously in 2.5 for over a week on many flights. Might also help in narrowing down on why this is happening?
-
Disabling the Addon Manager in dll.xml also stops the crashes but obviously also disables all of the FSDT addons.
Daz
-
Could you with crashes, please test THIS version of the Addon Manager ? Download the following file:
http://www.fsdreamteam.com/download/setup/bglmanx/2013/bglmanx_2013.zip
And place it in the P3D root folder, overwriting the files with the same names that are already there. This version is compiled with VS 2013, so it requires the VC++ 2013 runtimes. If you don't have them installed (or don't know), download them from here:
http://www.microsoft.com/en-us/download/details.aspx?id=40784
Download and install the x86 version of the runtimes, and let me know if you find this version more stable.
EDIT:Link fixed
-
Sadly I have to report that I had several CTD yesterday after re installing the last compatible Fsdream Addmanager to P3D (last fix)....Today I just uninstalled everything related with FSD and went to fly the same KLAX (default) to KSFO (default) and have no issues or any CTds at all.....Sorry guys but FSD add manager is conflicting with this last P3D fix....
Regards
Pedro
I will try this
"Could you with crashes, please test THIS version of the Addon Manager ? Download the following file:
http://www.fsdreamteam.com/download/setup/bglmanx/2013/bglmanx_2013.zip
And place it in the P3D root folder, overwriting the files with the same names that are already there. This version is compiled with VS 2013, so it requires the VC++ 2013 runtimes. If you don't have them installed (or don't know), download them from here:
http://www.microsoft.com/en-us/download/details.aspx?id=40784
Let me know if you find this version more stable."
-
Could you with crashes, please test THIS version of the Addon Manager ? Download the following file:
http://www.fsdreamteam.com/download/setup/bglmanx/2013/bglmanx_2013.zip
And place it in the P3D root folder, overwriting the files with the same names that are already there. This version is compiled with VS 2013, so it requires the VC++ 2013 runtimes. If you don't have them installed (or don't know), download them from here:
http://www.microsoft.com/en-us/download/details.aspx?id=40784
Let me know if you find this version more stable.
EDIT:Link fixed
Hi,
So far so good, no crashes with the replacement files and the x86 runtimes installed.
Flew around New York in the PMDG 777 and the QW 757 with no issues.
Thanks for the fix (fingers crossed), great support.
Regards,
Daz
-
testing right now....I will post as soon I land at KSFO
pedro
-
I just did a quick test flight with the new files and didn't get a CTD in 10 minutes. That's the longest I've been without CTD since the update, so fingers crossed.
Will test more extensively tomorrow...
Thanks for the great support!
-
The fix works for me. Many thanks!
Best regards,
Jim
-
yeap same here .... I just landed at KSFO NO problems at all....seems that problem fixed...Thank you guys
Pedro
-
Same here. Flew for two hours and no CTD.
-
guys which one of this three files did you install? (I'm on Win7 64bit)
vcredist_arm.exe
1.4 MB
vcredist_x64.exe
6.9 MB
vcredist_x86.exe
I've tested installing the last one, and could fly for 40 min., but just at the end, tried access FSUIPC4939 and got the same module error CTD.
vcredist_arm.exe, was a no go for my system: "vcredist_arm.exe is not a valid Win32 application"
Will keep testing...
-
vcredist_x86.exe
If it asks only to repair/ uninstall (which means that you already have it installed), either quit or select repair.
x64 is for 64 bit programs and the arm one is for the MS Surface tablet which runs an ARM CPU.
-
Thanks Jabloom, then that's the one i've installed.
Sadly I had that CTD at the end, I'll keep testing
-
I did add this as I was having ctds but my add on manager and coautl have disappeared.
-
Thanks Jabloom, then that's the one i've installed. Sadly I had that CTD at the end, I'll keep testing
Well, you got an FSUIPC crash, right ? If yes, that's unrelated to the Addon Manager, since it doesn't use or interact with FSUIPC.
-
I did add this as I was having ctds but my add on manager and coautl have disappeared.
That's likely because you haven't installed the VC++ 2013 runtimes from the Microsoft site I also linked in my post. Use the x86 version.
-
OK. I'll try the x86 version.
-
Thanks Jabloom, then that's the one i've installed. Sadly I had that CTD at the end, I'll keep testing
Well, you got an FSUIPC crash, right ? If yes, that's unrelated to the Addon Manager, since it doesn't use or interact with FSUIPC.
No, I got the same module error CTD: StackHash_0a9e, P3D Appcrash
-
I too was getting the stackhash crash within 60 seconds after opening P3D 2.5 (plus hotfix) after installing the first of several FSDT airports I own (JFK).
I am happy to report that the installation of the VC 2013 runtimes, plus the updated bglmanx.dll has completely solved the problem.
How soon will this fix be incorporated into the retail add-on manager? I plan to install the rest of my FSDT and FlightBeam airports tonight. Until I hear otherwise, I will simply hand-copy the updated DLLs back into my P3D folder after doing the rest of the installations.
Jim Barrett
Sent from my iPhone using Tapatalk
-
No, I got the same module error CTD: StackHash_0a9e, P3D Appcrash
That's likely entirely unrelated to the Addon Manager. As you can see from all the replies arrived so far, everyone that installed the new version using VC++ 2013 libraries, reported the problem has been fixed.
-
I am happy to report that the installation of the VC 2013 runtimes, plus the updated bglmanx.dll has completely solved the problem.
This is very good to hear, and all the others that tried it seems to confirm it. It's very relieving. We haven't changed a single line of code in the Addon Manager, just compiled with the latest Visual Studio, so the executable would now use the VC++ 2013 runtime libraries instead. It was clearly an issue of a conflict between runtime libraries, which are very difficult to find.
How soon will this fix be incorporated into the retail add-on manager?
We'll test it further, I would also like to hear more feedback from FSX users too, but I already got a couple of reports by email from some FSX users, and they seems to be positive so, hopefully this update would be included with the standard installation.
I plan to install the rest of my FSDT and FlightBeam airports tonight. Until I hear otherwise, I will simply hand-copy the updated DLLs back into my P3D folder after doing the rest of the installations.
Yes, just do that once as the last step, after installing everything else.
-
No, I got the same module error CTD: StackHash_0a9e, P3D Appcrash
That's likely entirely unrelated to the Addon Manager. As you can see from all the replies arrived so far, everyone that installed the new version using VC++ 2013 libraries, reported the problem has been fixed.
I will reformat and reinstall everything from scratch, it may vey well be another add-on that uses the same .dll that triggers that specific CTD.
I'll be posting in LM's forum also, if it's the hotfix issue it will happen with other add ons as you said
Thanks for your support
-
Happy to report, I did 12 hours flight and no CTD!! Thanks...
-
Seems to work, fixed my crashes, I'm assuming do not up date add-on-mgr or if I do re install the files downloaded from this thread into the main Prepar3d directory...thanks for speedy fix to this ,, much appreciated...
-
Seems to work, fixed my crashes, I'm assuming do not up date add-on-mgr or if I do re install the files downloaded from this thread into the main Prepar3d directory...
Yes, for the time being, I guess (considering the very good feedback we are having) we'll exit from the testing phase and make it official, so that download link will go away, and you'll will then know the files has made it in the standard installer.
-
I was also able to complete two full flights last night without incident. Great job in fixing this, thanks!
-
Re-installed VC++ 2013 libraries, and re-copied the files from the new add-on manager and that worked fortunately.
Strange but maybe as I've installed the 64bit version first and then the 32bit one, that created some problem and was still having the CTD's.
Thanks again for the fix
Regards
-
One more voice that the updated bglmanx and vc runtimes fixed my stackhash issues (have several fsdt airports and the QW 757) in P3Dv2.5 post-hotfix.
-
Fixed my P3D crashes so great work on the update :)
-
Thank you to all of you. I guess it looks like we could make it official then very soon.
-
The new Addon Manager .DLL/.DAT files we tested in this thread are now the official version so, from now on, everybody will get it automatically, even when running a previous installer.
The only thing to note, for those using existing installers, is that they don't contain the VC++ 2013 runtime redistributables so, if you still don't have it installed it in your system, you must download it separately, from the below link, and choose the x86 version:
http://www.microsoft.com/en-us/download/details.aspx?id=40784
We also updated the Stand-Alone Addon Manager installer, so it now includes and installs the VC++ 2013 runtimes automatically, so if you are not sure about the runtimes, the updated Stand-Alone Addon Manager contains the correct version and installs it automatically. In the next days, we'll also update all the products installers to include and install the VC++ 2013 runtimes, so this won't be an issue anymore.
Also, the link we posted to the testing version has been replaced to a link to download the Stand-Alone Addon Manager installer, so nobody reading this thread will end downloading the testing version by mistake...
-
In English we have a phrase 'from the frying-pan into the fire' and that applies very much to my experience with this CTD ... I applied the workaround and it worked. What do I do next?? ... I install Flightbeam';s KIAD ... and what do I get ... you've guessed ... the good old oa9e ... I am beginning to wonder why I bother ... life's too short ... UPDATE since posting, downloaded the latest standalone Addon Manager, reinstalled the airports involved and so far so good ...
-
In English we have a phrase 'from the frying-pan into the fire' and that applies very much to my experience with this CTD ... I applied the workaround and it worked. What do I do next?? ... I install Flightbeam';s KIAD ... and what do I get ... you've guessed ... the good old oa9e ... I am beginning to wonder why I bother ... life's too short ...
This cannot possibly happening, because all existing installers, will DOWNLOAD the updated Addon Manager files, and now the only version which is online for the installer to be downloaded, is the new correct one, the one that work and that everybody that posted in this thread after it has been released, confirmed there are no crashes anymore.
I've checked the KIAD installer, and of course it downloads and install the correct version, the same which was posted here to test, that everyone that posted here said if fixes the issue.
The only possible explanation I can think of, is that you have a firewall/antivirus/anti-spyware program that is BLOCKING the download of the updated files, so you are still getting the OLD version that comes internally in the installer.
This can be fixed either by disabling any product that might block the download OR downloading and installing the Stand-Alone Addon Manager installer, and install it as the last thing you do, because that one downloads AND contain the very latest version so, if will always install it, even if the download is blocked by another software.
-
The new Addon Manager .DLL/.DAT files we tested in this thread are now the official version so, from now on, everybody will get it automatically, even when running a previous installer.
The only thing to note, for those using existing installers, is that they don't contain the VC++ 2013 runtime redistributables so, if you still don't have it installed it in your system, you must download it separately, from the below link, and choose the x86 version:
http://www.microsoft.com/en-us/download/details.aspx?id=40784
We also updated the Stand-Alone Addon Manager installer, so it now includes and installs the VC++ 2013 runtimes automatically, so if you are not sure about the runtimes, the updated Stand-Alone Addon Manager contains the correct version and installs it automatically. In the next days, we'll also update all the products installers to include and install the VC++ 2013 runtimes, so this won't be an issue anymore.
Also, the link we posted to the testing version has been replaced to a link to download the Stand-Alone Addon Manager installer, so nobody reading this thread will end downloading the testing version by mistake...
So while I've read the entire thread (I just had this issue last night, as I finally had the chance to sit down and actually USE P3D from uninstalling FS9 15 months ago), the TL;DR of it basically is:
[list=1
- Uninstall existing scenery,
- Install new x86 VC++2013 runtime libs,
- Apply P3D Hotfix from LM, and
- Reinstall scenery
I acknowledge that the uninstall/reinstall is a bit overkill, but that should take care of it, yes?
BL.
-
Uninstall existing scenery
Nobody said anything about uninstalling anything. It's enough you run ANY installer, including the Stand-Alone Addon Manager installer, so you don't have to reinstall anything else.
Install new x86 VC++2013 runtime libs
Only if you don't have them installed already, and if you download the updated Stand-Alone Addon Manager, it comes with the x86 VC++2013 runtime libraries and it will install them automatically.
Apply P3D Hotfix from LM
That's unrelated to our stuff, you can do it or not, before or after, it's no longer an issue now, since the updated Addon Manager will work with either version, patched or not.
So, it's way easier than what you listed, and it boils down to:
1) Run ANY FSDT installer you already have. If you already had the VC++ 2013 runtimes installed in your system, it will work right away, even if your installer is not the latest version, because they *all* download the very latest Addon Manager files from our site when they run.
2) Download and install the updated Stand-Alone Addon Manager, so you don't have to wonder which version of the VC++ libraries you need or where to download them, because they come with it.
Step #2 is ONLY needed if you don't have the VC++ 2013 runtimes installed in your system, or you don't know, or you don't want to have to wonder about the issue.
-
Perfect! Thanks, Umberto! I'll be giving this a try tonight!
BL.
-
Perfect! Thanks, Umberto! I'll be giving this a try tonight!
BL.
Just an update. Umberto's post above worked for me, especially with the following sceneries from FSDT:
KLAS
KLAX
CYVR
KDFW
I haven't tried any of the FlightBeam sceneries yet (though I don't think they will be a problem) but I also realize as I type this that I didn't even apply the hotfix from LM, so the above definitely works.
Now to install a boatload of sceneries! Thanks again, all!
BL.
-
The updated version that supports the 2nd Hotfix ( 2.5.12944 ) is now online, just run any FSDT installer ( GSX, a scenery or the Stand-Alone Addon Manager ), will download the updated version automatically.