General Category > General Discussion
Prepar3D v2 Hotfix (2.5.12943.0) **SOLVED**
speedbird217:
--- Quote from: virtuali on February 24, 2015, 09:27:53 pm ---
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.
--- End quote ---
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?
virtuali:
--- Quote from: Dazzlercee on February 24, 2015, 09:40:09 pm ---Once all airports have been activated via the Addon Manager will they still work if the Addon Manager is uninstalled to prevent the crashing?
--- End quote ---
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.
virtuali:
--- Quote from: speedbird217 on February 24, 2015, 09:43:37 pm ---I hope this can be resolved soon. Is LM aware of your findings regarding the errors in their program?
--- End quote ---
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.
--- Quote ---So there must have been something in the update you released for the Hotfix that causes this
--- End quote ---
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.
speedbird217:
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?
Dazzlercee:
Disabling the Addon Manager in dll.xml also stops the crashes but obviously also disables all of the FSDT addons.
Daz
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version