General Category > General Discussion
Prepar3d Starts, No Add-On Manager in Add-Ons **SOLVED**
virtuali:
--- Quote from: pgde on May 07, 2015, 03:07:16 am ---So I have taken screen shots of what C++ redists are installed.
--- End quote ---
I'm sorry, but that screenshot is not very helpful, because it only indicates how many products can be Uninstalled, it doesn't say anything if they are installed correctly, not corrupted or not conflicting against each other.
I too have VC++ 2010 installed, and there are no problems with it. In any case, the Couatl.exe (version 3) requires the VC++ 2013 by itself, and in inherits a dependency on VC++2005 because it uses Simconnect (which requires the 2005 runtimes, likes FSX) so, in *theory* it shouldn't be affected by the VC++ 2010 runtimes.
--- Quote ---All installations were run without Anti-Virus (Norton) and as "Run As Administrator".
--- End quote ---
Something must have happened at some time, because your error really means the executable image format is "invalid", which really looks like a corruption caused by the antivirus. As I've said, you can check this, if you go to the P3D\fsdreamteam\Couatl\Couatl.exe file, right-click on it, select "Properties", select "Digital Signature" and check if the signature is valid. If it's not, then it's SURE it's antivirus which has corrupted the file trying to "heal" it.
In addition to that, there's no difference whatsoever regardless if you have P3D 2.5 or P3D 2.4, when Couatl is concerned. Couatl doesn't even KNOW what P3D version you are using, surely it doesn't know (and doesn't care) about the difference between 2.4 and 2.5, the only think it needs to know, if it's FSX, P3D 1.x or P3D 2.x, in order to know where to look for the scenery.cfg, but that's it.
So, whatever difference you see running under P3D 2.4 or 2.5, cannot possibly be related to the Couatl program itself, since there isn't a single line in its code that ever knows the difference between the builds. The only program that checks the build and needs to recognized it, it's the Addon Manager.
BTW, the Addon Manager also require VC++ 2013 and 2005 (because of Simconnect) so, if THAT one runs, it seems to indicate there's nothing wrong with your VC++ libraries, and the issue is ( as usual ) the defective Norton.
pgde:
As far as the security information, Win7 shows that "The digital signature is OK."
I have tried the current version of Add-On Manager as well as the beta with the continued problems as noted above. Interestingly both FSUIPC and ASN are shown in the Add-On section of the P3D menu. But not KLAX (my test airport).
Checked DLL.XML and EXE.XML and all look fine.
Norton has the entire drive that Prepar3d is on excluded from scanning.
All simconnect agents have been reinstalled as have the various VC++ redists.
I have disabled Norton without any luck.
Any other ideas? Is there a logging feature we can use to see what is going on?
Thx
P.
virtuali:
--- Quote from: pgde on May 07, 2015, 06:43:52 pm ---As far as the security information, Win7 shows that "The digital signature is OK."
--- End quote ---
In this case, you might exclude a problem with the antivirus, and it's likely a problem with the VC++ libraries instead.
--- Quote ---I have tried the current version of Add-On Manager as well as the beta with the continued problems as noted above. Interestingly both FSUIPC and ASN are shown in the Add-On section of the P3D menu. But not KLAX (my test airport).
--- End quote ---
That doesn't mean anything. If the corrupted version of the VC++ libraries is not required by *those* products ( I *think* ASN uses the VC++ 2010 libraries instead ), its problem won't affect them.
Also, some addons works with several Simconnect versions, our addons requires the SP2/X-Pack version so, if the missing/corrupted library in your system is instead Simconnect, but THAT version WE require (there are 3 versions installed in your system, all at the same time, and this is normal), it will not affect other addons.
--- Quote ---Any other ideas? Is there a logging feature we can use to see what is going on?
--- End quote ---
You can activate the Simconnect diagnostic mode to see what's wrong with your system. Open notepad, and copy the following text:
[SimConnect]
level=errors
console=1
RedirectStdOutToConsole=1
OutputDebugString=1
; file=c:\simconnect%03u.log
; file_next_index=0
; file_max_index=9
Save the file as SIMCONNECT.INI in this folder:
Documents And Settings\YOUR LOGIN NAME\Documents\Prepar3d V2 files
At the next launch of the sim, you should see a text window with diagnostic message, that should tell what's going wrong. Let me know what you are getting, so we can have an idea what's happening. Only the first 15-20 lines are important. If the scrolling goes too fast, try again and use the "Pause" key on the keyboard to read the first lines of the screen.
pgde:
Hi:
Attached is a zip file with the outputs of the simconnect.ini (thanks -- I changed the syntax to output to a file and also "normal" since bglmanx isn't being found so you can see what is happening around it). Also, since that file isn't loading I included copies of dll.xml and exe.xml.
P.
PS I am still getting the 0xc error in beta 3 even after reinstalling the vc++ files in safe mode.
virtuali:
Your log shows that:
- The reason of the modules not loading, is a "Missing dependencies", which means some required libraries are missing/corrupted on your system.
- When you use the Couatl 2 version, which requires only VC++ 2005 libraries, Couatl.exe is loaded, but bglmanx.dll is not
- When you use the Couatl 3 version, which requires both VC++ 2005 and 2013 libraries, both Couatl.exe and bglmanx.dll are not loaded
Since bglmanx.dll always requires the VC++ 2013 libraries in both versions, while Couatl.exe only version 3, the only logical conclusion is that your problem is caused by a problem with the VC++ 2013 libraries, which are either missing or corrupted.
Try to download them from here:
https://www.microsoft.com/en-US/download/details.aspx?id=40784
Download and install BOTH the x64 AND the x86 versions. DO NOT download the "arm" version. And, restart Windows after installing them.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version