After some research I found out that the bglmanx.dll file (and corresponding .dat files) are not placed in the Modules folder, but in the root folder
There's not an error of course (why you think the installer would place files in wrong folders ?? If it was true, it won't work for everybody ), and the "modules" folder doesn't even exists in FSX and Prepar3D.
Using a folder named "modules", it's a legacy from FS9 times, when modules HAD to be placed in the modules folder and nowhere else, and they ran automatically (if compiled in a certain way) and only from there. Under FSX and P3D there's no modules folder anywhere and the concept of a dedicated place to put modules doesn't exist anymore, since it's possible to specify any path in the DLL/EXE XML files.
Some users get confused and believe the "modules" folder exists in FSX or P3D, but that's just because installing FSUIPC will CREATE a modules folder for itself, maybe for consistency with add-ons coming from FS9 and looking for it in the modules folder, but other than that, the modules folder doesn't have any special meaning in FSX/P3D.
So no, the installer is obviously correct placing the files in the sim root, because that's where the DLL/EXE XML file the installer also create will reference, so you must put them back.
. Also, after moving those files to the modules folder, it does not work (probably need to update registry files)??
The reason why they are not starting, is likely a problem in your system, the most common case is the antivirus blocking the files, in this case you must:
- DOWNLOAD AND INSTALL with the antivirus Entirely OFF
- BEFORE you start the sim, configure the antivirus to exclude the Following files from scanning:
YourP3DFolder\bglmanx.dll
YourP3DFolder\fsdreamteam\Couatl\couatl.exe
Then you can launch P3D
If it's not the antivirus, it might be a problem with your VC++ 2005 runtumes installation, that might be corrupted or missing or in conflict with something else, see here:
http://www.fsdreamteam.com/forum/index.php/topic,9908.msg78006.html#msg78006