FSDreamTeam forum
General Category => General Discussion => Topic started by: Lude2Envy on May 31, 2017, 03:40:59 am
-
The CLT installer moved everything from my FSX/P3D folder into the Addon Manager folder, but the sceneries are no longer in the scenery library in FSX/P3D. They're only in the library for P3D v4. Is this a mistake or do we have to go back and add each airport manually in FSX/P3D? Thanks.
-
Me too, nothing works now. What a mess!
-
The CLT installer moved everything from my FSX/P3D folder into the Addon Manager folder, but the sceneries are no longer in the scenery library in FSX/P3D
The installer will not just move the sceneries, but will of course update the entries on the scenery library, in FSX or P3D up to version 3.2.
Version 3.3 and above will use the new method of the add-on.xml, so they won't be in the scenery.cfg anymore and this is CORRECT, but they will obviously work in the sim.
The most likely issue is that your scenery.cfg in FSX ALREADY had some kind of syntax error or illegal commands or other issues, so the installer couldn't updated it automatically, risking corrupting it even more.
You should be able to fix by downloading and installing the updated installers. The migration was made for the obvious reason to SAVE you from re-downloading anything, and it surely works, but it cannot work if your scenery.cfg already had issues so, I would like to have a look at it, if you could send it to my by email.
-
Holy crap!
Same here in FSX!
ALL my FSDT and FliGHTBEAM and Cloud9 sceneries
-like 6 GB are moved by the new KCLT-installer
from my big Flightsim HD to my small C HD,into the Addon-manager folder,
and there is no way to change that.
To click the browse-spot in the installer does not work.
My C Harddisc now has no space anymore.
All the FSDT and Flightbeam sceneries do not work anymore.
To download the latest installer of any of your sceneries,as you propose just lets this
process repeat again.
And to make this clear : my scenery.cfg is in the best shape!!!
All kind of sceneries of any developer worked perfect till now!
But the installer changes the paths in the scenery.cfg correctly to the Addon-manager
folder.
But as said above,I do not have enough space on this harddisc an I do not want any
scenery in my programs folder!
What a mess,what a desaster!
-
from my big Flightsim HD to my small C HD,into the Addon-manager folder, and there is no way to change that.
You were offered a chance to choose the installation folder for KCLT. The installer just moved everything else in that folder because, as usual, all our sceneries must stay together in the same place.
To click the browse-spot in the installer does not work.
The browse button surely works, the 1st time, allowing to choose an installation folder.
The 2nd time you run an installer, it will defaults to the previously chosen one. FSDT and Flightbeam sceneries ALWAYS had to stay together, under the simulator main folder, you didn't had the ability to move them around freely so, really, what's changed now ?
Nothing, they still must be together, just that now, you can CHOOSE where you want to have them, while before, you didn't even had that choice: they always went under the sim.
My C Harddisc now has no space anymore.
Them why you chose to install under C:\ ?? Again, the first time you WERE offered a choice, it's just for subsequent installs that you cannot choose anymore. Before, you didn't even have the ability to choose, now you CAN, and you can do a mistake...
To download the latest installer of any of your sceneries,as you propose just lets this
That's because you never said your problem was that you didn't had enough space on the drive you choose to install into.
But as said above,I do not have enough space on this harddisc an I do not want any scenery in my programs folder!
Then why you haven't selected a bigger drive when asked to, which was the fist time you installed KCLT ?
What a mess,what a desaster!
Which you caused, by purposely telling the installer to use a drive you knew didn't had much space. But of course, the installer obviously have a logical way to fix this, if you realize you made a mistake, and chose the wrong drive initially, you can do as follows:
- Uninstall all sceneries. During any of the uninstall processes, reply YES to the question:
"Do you want to remove the Addon Manager" ?
Which will CLEAR the choice you made initially so, on the next reinstall, you will be allowed to choose the installation folder freely, like the first time so, this time, just be careful and choose the correct place.
-
In all previous FSDT-installers and Flightbeam-installers over all the years the installer always found the
FS root folder and installed the scenery by default there.
There should be at least a warning
that now by default everything is installed into the addon-manager-folder and all other FSDT-sceneries
are moved across the computer to the addon-manager folder.
No other installer ever did that.
And I suppose I am not the only one,who has the addon-manager in the programs(x86)-folder
on another harddisc than the FS root-folder.
-
In all previous FSDT-installers and Flightbeam-installers over all the years the installer always found the FS root folder and installed the scenery by default there.
More precisely:
"In all previous FSDT-installers and Flightbeam-installers over all the years the installer always found the FS root folder and installed the scenery by default there, not allowing you any choice
Now, the installer offers you a choice for the installation folder, which is obviously a good thing, since you might not have enough space on the same drive you installed the sim on, but you might have lots of space elsewhere, which is exactly the point and the main advantage of the new system.
Of course, when you are free to select a drive and a folder, you might also do mistakes. As I've said, you can change this, by Uninstalling the Addon Manager entirely, so it will allow to choose again
And I suppose I am not the only one,who has the addon-manager in the programs(x86)-folder on another harddisc than the FS root-folder.
I really don't understand the issue: you can choose the folder freely now, it can be under C:\programs(x86), D:\programs(x86), K:\fsdt, J:\MyFSDTSTUFF, whatever you like, it will go there, with everything.
We assumed that most user would LIKE this enhanced freedom of being able to choose the drive and folder freely. What you cannot do, is to have an FSDT scenery in one place, and another FSDT scenery in another place, which is exactly the same as before, with the added limitation that, before, you weren't even allowed to choose anything, so it always went into the sim folder.
-
I think the issue is more that there was no instruction to the install. The default was simply to install Addon Manager to C:\Program Files (x86)\Addon Manager. There was no indication that EVERYTHING FSDT was also going to get installed there. It's a rather big change from how you've done it previously and isn't explained at all.
-
I think the issue is more that there was no instruction to the install. The default was simply to install Addon Manager to C:\Program Files (x86)\Addon Manager. There was no indication that EVERYTHING FSDT was also going to get installed there. It's a rather big change from how you've done it previously and isn't explained at all.
Yes, I agree, but we were so busy updating the things that matters the most (the actual files), that there simply wasn't enough time to rewrite the install guide in order to make it in time for the release.
But sure enough, even the install guide is now covered under the Live Update so yes, we'll update that one as soon as possible, trying to explain the new system in detail.
-
The CLT installer moved everything from my FSX/P3D folder into the Addon Manager folder, but the sceneries are no longer in the scenery library in FSX/P3D
The installer will not just move the sceneries, but will of course update the entries on the scenery library, in FSX or P3D up to version 3.2.
Version 3.3 and above will use the new method of the add-on.xml, so they won't be in the scenery.cfg anymore and this is CORRECT, but they will obviously work in the sim.
The most likely issue is that your scenery.cfg in FSX ALREADY had some kind of syntax error or illegal commands or other issues, so the installer couldn't updated it automatically, risking corrupting it even more.
You should be able to fix by downloading and installing the updated installers. The migration was made for the obvious reason to SAVE you from re-downloading anything, and it surely works, but it cannot work if your scenery.cfg already had issues so, I would like to have a look at it, if you could send it to my by email.
I made a mistake. My sceneries are there in FSX. They weren't loading because of SimstarterNG. My FSDT sceneries are NOT loading in P3D though. I'm using version 3.3.5. I'm also only using SimstarterNG in FSX, not P3D.
-
I made a mistake. My sceneries are there in FSX. They weren't loading because of SimstarterNG.
Which, as we explained so many times on the forum, is totally useless, for our sceneries. They do custom memory management, keep disabling/reenabling them won't save you any memory.
My FSDT sceneries are NOT loading in P3D though. I'm using version 3.3.5. I'm also only using SimstarterNG in FSX, not P3D.
It's possible it was active when you installed ?
-
It's possible it was active when you installed ?
They were all active when I installed KCLT.
-
They were all active when I installed KCLT.
I said "it", referring to the Simstarter NG.
-
I said "it", referring to the Simstarter NG.
No. I never used Simstarter with P3D. Only with FSX.
-
Any suggestion to get my sceneries back into v3 with the new method?
-
Try to download and install the Stand-Alone Addon Manager.
-
Try to download and install the Stand-Alone Addon Manager.
Tried it. Still nothing showing up in v3.
-
Then download and install the full scenery installer.
-
Am having similar issue in FSX. My issue is regarding the migration function of the new Addon Manager. Will not rehash all the prior complaints about the lack of notification of the new program moving all of the sceneries. My issue is that after all of the sceneries are moved to the selected / default directory, none of the sceneries terminals and buildings or GSX vehicles display in the sceneries. This condition is true for all FSDT and Flightbeam sceneries. In my instance it is after installing FSDT Chicago O'Hare.
They all work before the new Addon Manager installs and migrates the existing sceneries to the new directory. And before you reply, Antivirus is disabled before the install, the Scenery.cfg paths for all sceneries are updated successfully to the new directory location, Couatl, GSX and the Addon Manager load into FSX Addon pulldown menu on startup.. just no GSX vehicles or buildings. Runways and ground textures display as expected.
-
And before you reply, Antivirus is disabled before the install, the Scenery.cfg paths for all sceneries are updated successfully to the new directory location, Couatl, GSX and the Addon Manager load into FSX Addon pulldown menu on startup.. just no GSX vehicles or buildings. Runways and ground textures display as expected.
The problem was likely that your FSX.CFG was already corrupted or had some error, so when the installer moved all the sceneries, it didn't updated it, in order not risk to corrupt it even more.
Before, we just dumped our objects in the default Simobject\Misc folder so, if you were lucky, and no other addon had corrupted the lines that should always be present in each default install (we had plenty of these case reported), the objects could be found.
Now, since we install outside the sim, we need to *add* the line that loads the objects containing the new path to the fsx.cfg so, if this one has some kind of problem, it's possible the installer couldn't add it, which explain why Couatl gives you an error, because the SIM itself cannot find the objects.
Check if all the Simobjectspaths lines in the FSX.CFG are all numbered in sequence, there are no double section and the line that adds the objects in the Addon Manager folder is present and pointing to the correct one. It should, because we add it from the installer but, as I've said, only if your FSX.CFG was clean.
-
Before I attempt reinstalling O'Hare, is there anything that is modified other than migrating the existing scenery folders and revising paths or new entries in FSX.CFG, DLL.XML and EXE.XML for the Addon Manager and SODE that I should check if it again fails? I have done the uninstall process and reinstall three times now (before my original post here), and would like to minimize the need to do that again. I have six FSDT & and three Flightbeam purchased sceneries, so is a bit of wasted time to keep doing this process. I look at all of these files and there does not appear to be any errors or bad syntax in the existing entries (and they work). Unfortunately I did not know to check all of these when I had the error condition after installing O'Hare to see what might have failed. They are correct with the installs prior to Addon Manager, all prior existing sceneries work and I have now backed them up. Next step reinstall O'Hare.
Thanks.
-
First, be sure you use the most current version of all the installers, since we updated them a couple of times during the past week. This is what the migration does in FSX:
- It will move all your FSDT/Flightbeam sceneries, from their actual location under FSX\fsdreamteam or FSX\flightbeam, into the new Addon Manager folder, which is the one you'll specify when installing.
- It will move all the FSDT and Flightbeam Simobjects from the FSX\Simobjects\Misc folder, into to the new Addon Manager\Simobjects\Misc folder
- If will update the scenery.cfg to indicate updated paths. This assumes the scenery.cfg is clean of syntax errors.
- It will update the DLL.XML and EXE.XML files with the updated paths for bglmanx.dll (DLL.XML) and Couatl.exe (EXE.XML).
- It will add the following line to the FSX.CFG, assuming it's clean from errors, and all the existing Simobjectpaths lines are numbered in order, which is how it's supposed to be:
Simobjectpaths.XX=C:\Program Files (x86)\Addon Manager\Simobjects\Misc ( where XX is +1 than the currently highest number in the list )
-
Well, thanks for the replies. Unfortunately, everything in your last list of what the migration was to perform worked but the previously existing sceneries that were moved from the FSDT and Flightbeam subfolders and in FSX still do not display the terminals (same as before described in original post). The O'Hare scenery installed with the new Addon Manager setup EXE (oharex_setup.exe) displays fine.
I have screen prints of 1) PHNL after the install with no terminals displaying, FSX Addon drop down menu with Couatl, GSX and Addon Manager loaded and functioning, 2) Addon Manager control panel screen showing PHNL "Installed and ACTIVE", and 3) the O'Hare scenery loaded in FSX displaying correctly. I do not know how to attach/paste images or a PDF into this message using the "Insert Image" menu for this forum (sorry, first time poster). If it helps resolve, I can send separately in JPG or PDF format if you can provide directions. Also can send you the FSX.exe, EXE.xml and DLL.xml if they would help troubleshoot... I have before and after O'Hare install copies.
Seems at this point of troubleshooting, there should be few other possible causes. If no other suggestions, I wonder if installing O'Hare first then follow with all other sceneries after Addon Manager path is set and locked. Would this option also work correctly with setting the scenery installation path for all Flightbeam sceneries installers? If can't get this resolved soon, I am just going to live with the previously installed FSDT sceneries, trash the newly purchased O'Hare and live without any FSDTs that I do not currently own. Love your sceneries and Flightbeam so much I have pretty much abandoned using freeware sceneries, but this will soon get where no longer worth the effort to install for a game.
Please do not suggest reinstalling Windows as I have seen for some other posts. This is the only game on a system primarily used for business. Not an option to reinstall and reconfigure other software to make scenery work.
UPDATE: While browsing & trying to resolve issue myself tonight, have found that all Flightbeam sceneries do work/display correctly after the migration of existing sceneries. The only sceneries that do not work are the migrated FSDT sceneries. Have checked all of them and none display including terminals, nor airport ground/runway elements. Only the MegaScenery photoreal scenery displays (FSDT sceneries are at highest level in the Scenery.CFG). Secondly, was going to attempt reinstalling KHOU for grins to see if it would display after reinstalling, but it wanted to install in the FSX\Fsdreamteam directory not the Addon Manager\Fsdreamteam subdirectory. Also noticed that there is not a airport subdirectory for the migrated FSDT airports containing a __init__.pye in Addon Manager\couatl (i.e. <path>\Addon Manager\couatl\<airport subdirectory>). There is one for common, GSX, Liveupdate, wx, OhareX and each of the Flightbeam sceneries. Is this correct, or should there be subdirectories for the migrated FSDT sceneries?
-
I'm sorry, but I find very difficult to follow your post and it would be close to impossible trying to figure it out which file of the sim was corrupted or with errors, which lead to some of the migrated sceneries to stop working.
But it's really a waste of time trying to retro-troublshooting it, it will be just easier to:
- Uninstall *EVERY* FSDT and Flightbeam scenery. Reply YES to the question "Do you want to remove the Addon Manager?"
- Download ALL their updated installers and install only using the updated installers.
-
OK... reinstalling everything again was a pain but it worked, so worth the effort. Guess I needed the new installer versions for all FSDT and Flightbeam sceneries to reinstall in lieu of the auto migration using the single new scenery. Don't see what is different in the affected files, but all now display and work correctly. Thanks for your input to resolve, and the work you guys do creating all of the great sceneries.