FSDreamTeam forum
Products Support => Zurich scenery for FSX/P3D => Topic started by: ckaack on May 18, 2012, 03:46:52 pm
-
I installed LSZH v2.5, but I can not see any buildings. Besides this, the FSX stops working periodically for about 2 sec every 4 sec. I de-installed the scenery and deleted the entire FSDT folder before I re-installed LSZH. Does anybody have an idea about this strange behaviour at LSZH only?
https://lh3.googleusercontent.com/-MnAwyaCRDnk/T7ZSe7cB4hI/AAAAAAAAEyk/scWVi0f6ItE/s1600/2012-5-18_15-40-46-679.jpg (https://lh3.googleusercontent.com/-MnAwyaCRDnk/T7ZSe7cB4hI/AAAAAAAAEyk/scWVi0f6ItE/s1600/2012-5-18_15-40-46-679.jpg)
-
The lack of buildings and the pauses every 4 seconds, indicates you haven't installed the latest version of Zurich, but an older version. Be sure you install the latest version.
-
As I wrote, I removed all previous versions of FSDT and reinstalled the latest version of FSDT Zurich v2.5.2 today.
-
I can only repeat and confirm, that just by installing Zurich 2.5.2, what you are describing, simply can't and doesn't happen, while instead, your description of the problem is exactly what happens when you install either a old version of Zurich with the new Addon Manager
OR
The new version of Zurich, and an old version of the Addon Manager on top of it.
Both will result in the same effect, which is exactly what you are describing.
-
I just installed the latest add-on manager and the same issue.
-
Installing the newest version of the Addon Manager won't fix the problem if you have an old version of Zurich. You need to install the most current version of Zurich, which will of course come with the correct Addon Manager so, there's no need to install anything else.
If you install something older after the last version of Zurich, it will create exactly what you are reporting so, if you are reporting it, it means you haven't installed the current version of Zurich, or you are trying to downgrade it by installing something else after it.
There are no other explanations for what you are describing.
If something wasn't loaded and wasn't running, you would just have "no buildings", and that's it. If you are getting the pauses, it means everything IS working (which you can confirm by check if you have BOTH the Addon Manager AND the Couatl menus under the "Addons" menu), but you are using old version of something.
Of course, since you said "the same issue", I'm assuming you are still observing the "same issue", which is no buildings AND pauses.
If something has changed, and you don't see the pauses anymore, but still no buildings, then it's not the same issue anymore, and it's an entirely different problem so, please clarify if you are still getting the pauses, or the pauses have gone, and you just don't have buildings.
-
I removed all FSDT software, downloaded the latest Zurich V2.5.2 and reinstalled it, but again and again the same behaviour. It looks to me that the the Add-on manager is somewhere else installed and I can simply not remove it. Where can I find this beast on PC to kill it?
-
The Addon Manager is installed in only one place, and it's only one file ( FSX\bglmanx.dll ) and the Addon Manager is NOT your problem.
There's obviously a proper uninstaller for all our software, which is where any uninstaller in Windows is normally located: in the Add/Remove Programs section of the Windows Control Panel.
This is how you uninstall any of our products and, if you reply YES to the question "Do you want to remove the Addon Manager" and reply YES to the question "Do you want to remove the Couatl scripting engine" which are made at the end, EVERYTHING related to the Addon Manager, Couatl and the scenery WILL be removed entirely, as if you never installed it.
And by the way, you still haven't confirmed that with "same behaviour" you mean you get BOTH the pauses AND the missing buildings, so I must continue to assume you still have both because, if you are not having pauses anymore, then it's an ENTIRELY different problem so again, please, clarify your current situation, as I've asked in my previous message.
-
I used the uninstall function of the Windows Control Panel and confirmed to delete the addon manager. Nevertheless the folder FSDreamTeam was still available and I deleted even this folder. Besides this the entire registry still includes couatl, virtuali and FSDT entries and in the %appdata\roaming path was a folder called virtuali. I deleted all of it! I scanned my entire PC and bglmanx.dll was not found. When I started FSX, first a message popped up, that Zurich is still shown in the scenery.cfg, but not available.
Therefore I installed the latest Zurich v2.5.2 again. The behaviour was the same as it was before, no buildings, just jetways and periodically paused FSX ~2/4 sec. But even I installed Zurich from the scratch, my previously entered serial was still recognized. This shows to me, that the deinstall was not successfull.
Btw. I have tried KJFK and KLAX too and the same behaviour!
-
Besides this the entire registry still includes couatl, virtuali and FSDT entries and in the %appdata\roaming path was a folder called virtuali. I deleted all of it!
We don't put anything in these registry entries. The only key should be your Serial Number in the registry, which is obviously not removed when uninstalling, otherwise you'll have to reactivate after uninstalling.
But it's possible Windows itself has set some flags about the executable (for example, to store the fact you trusted a module), but it's all normal.
Files in the %APPDATA% path belongs to GSX or store your custom configuration like key redefinitions and such, so they are obviously not removed (no uninstaller should remove user preferences) but they surely can't cause any problem.
When I started FSX, first a message popped up, that Zurich is still shown in the scenery.cfg, but not available.
Our uninstaller correctly remove the Zurich area from the scenery.cfg. If it hasn't on your system, it further confirms something is very wrong in your system.
Therefore I installed the latest Zurich v2.5.2 again. The behaviour was the same as it was before, no buildings, just jetways and periodically paused FSX ~2/4 sec.
This even more proves your system configuration is wrong, because it simply doesn't happen
But even I installed Zurich from the scratch, my previously entered serial was still recognized. This shows to me, that the deinstall was not successfull.
This not a proof that deinstall wasn't successful, at all. Your Serial Number is obviously NOT removed when uninstalling, and it's made intentionally, so you won't need to reactivate when just uninstalling/reinstalling.
Are you maybe running FSX into "Compatibility mode" ? This is wrong, is not how FSX defaults to, and it creates all sort of problem, like missing objects, files in the wrong folders (as you described it).
Turn every Compatibility mode in the "Compatibility" tab in FSX and reinstall.
-
FSX is not running in Compatibilty Mode.
I've tried all software from FSDT and none is working at all. Now I am getting the attached error message during the removal of the Addon Manager:
https://lh3.googleusercontent.com/-FmiXXebynqA/T7eaa1oMzJI/AAAAAAAAEy0/9FX6utI2d_k/s454/FSDT.jpg (https://lh3.googleusercontent.com/-FmiXXebynqA/T7eaa1oMzJI/AAAAAAAAEy0/9FX6utI2d_k/s454/FSDT.jpg)
The funny thing is, that all other software is running fine.
-
That error message indicates your DLL.XML or EXE.XML (or both) has been corrupted by another product you installed. Our installer will NOT touch the XML, if they were already corrupted, so the problem was caused by another faulty installer.
Our installers can't create a corrupted XML, since they don't touch the XML directly, but handle the actual modification (ONLY if the file was not already corrupted), by the official Windows XML parser by MS.
Try to post your DLL.XML and EXE.XML files in the %APPDATA%\Microsoft\FSX folder, so I can fix them or check what's wrong with them.
Don't post the files directly, ZIP them together first, and attach the ZIP file to a message, so they are transfered as they are.
-
thx for your kind support. Please find the files in the help.zip file. I attached others too.
-
Ciao Umberto,
any conclusion?
Kind regards
Christian
-
There's nothing wrong in your XML files, I've copied them on my system, and the installer doesn't give any error. So, it must be some other file that is not correct on your system.
Try to log the installation, this way:
- Open a command prompt ( start -> CMD -> enter )
- go to the folder where you have the installer, for example:
CD c:\Users\Yourname\Desktop
Assuming you put the installer on the Desktop
- launch the installer with this command:
zurichx_setup.exe /log=install.log
Proceed with the installation and let it end normally. This should hopefully create a file named install.log on your Desktop. If you have it, then send it to me ( via Email, please )
-
I just purchased, installed and activated LSZH in P3D v1.4 and I am experiencing the same exact problem i.e. no buildings and pauses every few seconds. I installed it as an administrator, so that should not be an issue. I am also running what I believe to be the latest versions of:
Addon Manager (v2.9.0.4)
ZurichX (v2.5.3.0)
The Addon Manager says the scenery is activated so as you may imagine, I am not best pleased about this. Would appreciate any help in resolving this issue.
Thanks.
-
Check if you have BOTH the Addon Manager AND the Couatl menus inside P3D
If not, it's likely your antivirus has blocked one of both, so no scenery will be seen.
- DOWNLOAD AND INSTALL with the antivirus entirely OFF
- Uninstall the scenery. Reply YES when asked if you want to remove the Addon Manager and the Couatl Engine. Reply YES to both questions.
- TURN OFF your antivirus. Don't just exit from its interface, but turn off the real time protection. Actual wording changes between products, however, it's the option to scan every file that gets open in real time, without user intervention.
- Reinstall the scenery with the Antivirus TURNED OFF. Don't launch the sim yet.
- Configure the antivirus to exclude the following files from scanning:
YourP3DFolder\bglmanx.dll
YourP3DFolder\fsdreamteam\Couatl\couatl.exe
- Now you can turn the antivirus back on, and launch P3D
- Check you are seeing BOTH the "Addon Manager" menu AND the "Couatl powered products" menu under the "Addons" menu.
-
Hi Umberto,
Followed your instructions. Same result. FYI, the antivirus (MS Security essentials) is set to exclude the P3D folder and subfolders.
To respond to your query re: Add-ons menu; yes I do see Couatl-powered products and Addon Manager listed. The entries in the dll.xml and exe.ml seem to be fine as well. This was the case even when I installed the product the first time.
I am running P3D on Windows 7 64-bit. Did the other user resolve the issue? If so did he ever say how?
Thanks for the help.
-
To respond to your query re: Add-ons menu; yes I do see Couatl-powered products and Addon Manager listed. The entries in the dll.xml and exe.ml seem to be fine as well.
Then it means everything's working correctly. Are you using the FSX Migration tool maybe ? If yes, there's a whole sticky thread about it, please read it, because you need to follow all the instructions listed there in order to use our products (which are P3D NATIVE) together with the FSX Migration tool:
http://www.fsdreamteam.com/forum/index.php?topic=7237.0
-
I never used the FSX Migration tool. The only thing I've done is to substitute FSX's folder path with that of P3D in the 2 registry entries. Could this be the culprit?
I read the sticky thread but it did not seem to apply to my case. Regardless, I tried using the batch file (substituting FSX.exe with Prepar3D.exe in the batch file) suggested in the thread to see if that would make it work, but again, no luck.
Thanks for the help once again. I hope we can resolve the issue!
-
I never used the FSX Migration tool. The only thing I've done is to substitute FSX's folder path with that of P3D in the 2 registry entries. Could this be the culprit?
It shouldn't, provided you have valid P3D registry entries. If you have, the installer should have asked if you wanted to install into P3D. If it didn't, it means it installed in "FSX mode" so, even if you changed the registry.
The most important thing to be checked is:
On the %APPDATA%\Lookheed Martin\Prepar3D\EXE.XML file, the section that launched the Couatl program should look like this:
<Launch.Addon>
<Name>Couatl</Name>
<Disabled>True</Disabled>
<ManualLoad>False</ManualLoad>
<Path>fsdreamteam\couatl\couatl.exe</Path>
<CommandLine>--mode=prepar3d</CommandLine>
</Launch.Addon>
Note this line:
<CommandLine>--mode=prepar3d</CommandLine>
If the installer believes it's running in FSX, it will not add that line so, you will add it yourself after the installation.
-
The installer detected P3D (as indicated in the pop-up window during installation) and seems to have (prima facie) installed correctly, including the entry in the exe.xml, which I am pasting in its entirety below:
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Couatl</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>fsdreamteam\couatl\couatl.exe</Path>
<CommandLine>--mode=prepar3d</CommandLine>
</Launch.Addon>
</SimBase.Document>
The only difference in my entry seems to be this line: <Disabled>False</Disabled>. Yours is set to True. Could this be causing the problem?
-
only difference in my entry seems to be this line: <Disabled>False</Disabled>. Yours is set to True. Could this be causing the problem?
well, of course not...it shouldn't be disabled, sorry if it looks confusing in my post but, as I've said in that message, the important line is the <Commandline> entry which sets the P3D mode.
I'm sorry but, other than a problem with playing with registry entries, I don't see what else could be. Check your P3D registry entries are correct.
-
I am pretty certain that the P3D registry entries are correct as other addons like the QualityWings RJ that are P3D compliant installed without any trouble. Even though it shouldn't matter I will set the FSX registry entries to their original values and try installing again. Not sure if this may shed any light but I just tried uninstalling Zurich and I got this error in a pop-up window after agreeing to uninstaling Couatl/Addon Manager:
Runtime Erroe (at 124:2318): Error on line 0, position 0: The system cannot locate the object specified.
As I said I will try installing again from scratch but should it fail, I will probably have to ask (regrettably) for a refund. I assume it's a problem related to my system, given that it works on others' machines... but I will try for a final time first.
Thanks for the help anyway!
-
Runtime Erroe (at 124:2318): Error on line 0, position 0: The system cannot locate the object specified.
That seems there's an error in your DLL.XML and/or EXE.XML, post them both, from the following folders:
%APPDATA%\Lookeed Martin\Prepar3d\DLL.XML
%APPDATA%\Lookeed Martin\Prepar3d\EXE.XML
Please DO NOT post them in the forum as a message. ZIP them together, and Attach the .ZIP file to the message, so it's sure the XML won't be changed when posted on the forum.
-
DLLs in the attached ZIP file.
-
Your P3D files looks fine, which seems to indicate the problem is in the FSX ones, meaning the installer (because of the problem with the registry) is still trying to install into FSX.
Are you running P3D in one of the "Compatibility" modes ? This will likely screw up all the files locations, check the Properties for the Prepar3D.exe file and be sure is not running in any of the Compatibility modes.
-
Afraid not. Neither P3D or FSX are running in any of the available compatability modes. Incidentally I tried installing Zurich for FSX... same result. Any yet I have both Couatl and Addon Manager on the menu and the scenery is tagged as "Active". I also checked the registry and it contains the FSDT entry with the serial number.
Unless there is anything else we can try, I'd like to ask you what the procedure for a refund is please. It's a shame though I was looking forward to using this scenery after recently flying to Zurich in real life!
-
Afraid not. Neither P3D or FSX are running in any of the available compatability modes. Incidentally I tried installing Zurich for FSX... same result. Any yet I have both Couatl and Addon Manager on the menu and the scenery is tagged as "Active".
Has the scenery being added to the Scenery Library ? If not, it's possible the error you saw was related to the scenery.cfg file instead, which was corrupted by hand-editing, so the installer couldn't add it and the uninstalled complained about the error.
The scenery.cfg is located in the C:\ProgramData\Lookheed Martin\Prepar3D folder
-
The scenery library file is ok, and the entry points to the right folder. I am able to see the ground texture/s as well as the jetways. However, as stated, I don't see any buildings/terminals and get pauses every few seconds.
-
The scenery library file is ok, and the entry points to the right folder. I am able to see the ground texture/s as well as the jetways. However, as stated, I don't see any buildings/terminals and get pauses every few seconds.
This really seems to indicate that either of the following is happening:
- You haven't installed the latest version of Zurich
OR
- You have installed the latest version of Zurich, but you have an old version of the Addon Manager, because the antivirus is blocking the update
OR
- Something is wrong in your Prepar3d.CFG file, so the Simobject folder is not pointing to the correct disk folder, most likely caused by another product installer, or by having hand-edited the .CFG file.
Check your Prepar3D.cfg file and look for all lines that contains:
SimObjectPaths=
And post them here. Just those lines.
-
a ha! I suspect the SimObjects path is probably the culprit then. I did modify the SimObjects paths, which point to a "common" SimObjects folder which FSX and P3D can share. I had a look and saw the Zurich folders in the Simobjects/Misc folder. Would I be able to move these folders to my common SimObjects library or would that affect the copy-protection system?
-
Hi again Umberto.
Some partial success. I modified the SimObjects paths so that now the FSDT folders are being seen by P3D, which means that now I see all the buildings etc in the scenery.
However, I still get the pauses. The Addon Manager version I have is v2.9.0.4 and it says that ZurichX is "Installed and ACTIVE".
Any ideas?
FYI here is the SimObjects paths section:
SimObjectPaths.0=S:\SimObjects\Airplanes
SimObjectPaths.1=S:\SimObjects\Rotorcraft
SimObjectPaths.2=S:\SimObjects\GroundVehicles
SimObjectPaths.3=S:\SimObjects\Boats
SimObjectPaths.4=S:\SimObjects\Animals
SimObjectPaths.5=SimObjects\Misc <-- Contains only the FSDT-Zurich scenery
SimObjectPaths.6=S:\SimObjects\IVAO_MTL
SimObjectPaths.7=SimObjects\Airplanes <-- Contains aircraft that will only work if left inside the P3D folder structure (e.g. SimSkunkWorks' aircraft; no duplicates)
SimObjectPaths.8=S:\SimObjects\Misc <-- Contains the Default Misc objects
User Objects=Airplane, Helicopter
-
Such configuration won't work, you can't share Simobjects folders between P3D and FSX, and our sceneries expect the Simobject are in the same flight sim folder as the scenery, and each and every sim.cfg of every Simobject has fallback paths that take this for granted. The pauses are caused by the program trying to create simobjects that don't exists or have missing files, because of this editing.
You should have said before you modified your .CFG file in such complex way, we would have saved lot of time, by simply saying such modifications are simply not supported, unless you know EXACTLY what you are doing but, we can't support you in such editing, and expect any scenery or GSX update will likely break any changes you might eventually have to do to the simobjects, so you'll have to do everything from scratch again.
-
Restoring the original SimObject path structure resolved the issue entirely. Thanks Umberto, and apologies for the waste of time. Very happy with the scenery and will be looking forward to purchasing other products in the future.