FSDreamTeam forum
Products Support => Charlotte KCLT Support FSX/P3D => Topic started by: Wise87 on May 31, 2017, 03:53:40 am
-
After doing the install of KCLT I started up the sim and my entire scenery.cfg is erased. I now get Scenery.Cfg Error. Scenery Remote Directory invalid. Would you like to unload this area.
I'm pissed now. >:( >:( >:(
I uninstalled it all and I'm done with it.
-
Same here, none of my stuff works. This is the worst way to install products. It seems whenever I install one of your products, it breaks my sim.
-
After doing the install of KCLT I started up the sim and my entire scenery.cfg is erased. I now get Scenery.Cfg Error. Scenery Remote Directory invalid. Would you like to unload this area.
What sim ? The new installer, under P3D V3 and P3D V4 DOES NOT touch the scenery.cfg anymore! That's the whole point of the new installation system, we DO NOT touch the scenery.cfg.
Under FSX, instead, the new installer is unchanged, so it uses the scenery.cfg exactly as it always did.
-
Same here, none of my stuff works. This is the worst way to install products. It seems whenever I install one of your products, it breaks my sim.
You also haven't said which sim you use. As I've said, under P3D V3 and V4, the scenery.cfg is not changed by the installer. Sceneries just not go there anymore so, there's no reason to change it or touch it.
-
For some reason the installer added Remote= under all my scenery.cfg files. Once I cleared them out it loads fine. Not sure if it's conflicting with the Migration tool. I'm running P3D v3 with Migration tool disabled. I got KCLT to load now but now I have to go back and reload all my other scenery. I made a backup of my Scenery.cfg before the install and I don't have Remote= listed anywhere.
BEFORE KCLT
[General]
Title=Prepar3D Scenery
Description=Prepar3D Scenery Areas Data
Clean_on_Exit=TRUE
[Area.001]
Title=Default Terrain
Texture_ID=1
Local=Scenery\World
Layer=1
Active=TRUE
Required=TRUE
[Area.002]
Title=Default Scenery
Local=Scenery\BASE
Layer=2
Active=TRUE
Required=TRUE
[Area.003]
Title=0000 Base
Local=Scenery\0000
Layer=3
Active=TRUE
Required=FALSE
AFTER KCLT
[General]
Title=Prepar3D Scenery
Description=Prepar3D Scenery Areas Data
Clean_on_Exit=TRUE
[Area.001]
Title=Default Terrain
Texture_ID=1
Layer=1
Active=TRUE
Required=TRUE
Local=Scenery\World
Remote=
[Area.002]
Title=Default Scenery
Layer=2
Active=TRUE
Required=TRUE
Local=Scenery\BASE
Remote=
[Area.003]
Title=0000 Base
Layer=3
Active=TRUE
Required=FALSE
Local=Scenery\0000
Remote=
-
What ever it was I'm re-downloading all the installer and it seems to be working now and it's putting the files a new ad on manager folder
Sent from my iPhone using Tapatalk
-
For some reason the installer added Remote= under all my scenery.cfg files.
Maybe I wasn't entirely clear: under P3D V3.3 and up and V4, the installer does not touch the scenery.cfg AT ALL! In addition to that, even in FSX or P3D pre-v3, the installer never added the "remote=" line.
I double-checked again the whole installer code, and there's nothing that even contains the word "remote" in the entire program code, just to be sure that I never forgot something in, and for some reason P3D was mistakenly detected as being FSX, or if you P3D version was lower than 3.3, which doesn't fully support the new addon installation system, so it's treated in the old way.
So, if you saw all these "remote=" lines which weren't there before, you can be sure it has nothing to do with our installer.
Instead, if you run ANY other utility which is not fully compatible with P3D V4, there's the concrete risk the scenery.cfg will be DESTROYED, because that file is now encoded as Unicode so, any 3rd party installer or utility which is not ready for it and doesn't take this into account, will surely cause issues to it.
Which is why, in order to stay away from the problem entirely, we decided to use the new, much reliable, add-on distribution system, where addons (including scenery), are NOT added in the scenery.cfg, but in their own add-ons.xml file, in their own private folders under Documents\Prepar3d folders.
With this method, installers will not have to touch the scenery.cfg anymore, which is exactly what our new installers do, from P3D 3.3 and above.
-
What ever it was I'm re-downloading all the installer and it seems to be working now
That's because the KCLT installer was never the problem to begin with. Please read my explanation above, whatever issue you had, it was caused by something else.
-
Than it was a conflict with the migration tool which may of us use. Either way I'm moving forward with fresh downloads and install.
-
I'm running FSX and everytime I load one of my FSDT airports or Flightbeam now, I get The addon unknown is causing the Coualti Script engine to restart. I have uninstalled and reinstalled scenery, downloaded the stand alone manager and still get this error.
couatl v3.2 (build 3823)
panic log started on Tue May 30 23:23:08 2017
problem raised by addon <unknown>
Traceback (most recent call last):
File "couatl\common\__init__.py", line 137, in onSimStart
File "couatl\common\collisions.py", line 54, in reloadGeometries
File "couatl\common\aircraftData.py", line 1262, in getAircraftData
File "couatl\common\aircraftData.py", line 694, in __init__
ValueError: need more than 21 values to unpack
-
This installation crushed FSX for me too. I even did a system restore and it's still not fully fixed. Looks like I'll be trying to fix this all week. All of the buildings in other sceneries (fsdt and flightbeam) are now missing. Plus I cannot tweak anything in the addon manager in FSX. And again when I did the system restore I had the same problem where FSX couldn't locate certain sceneries. I couldn't even find them in Windows Explorer. Please help.
-
This installation crushed FSX for me too
No, it hasn't.
I even did a system restore and it's still not fully fixed. Looks like I'll be trying to fix this all week.
It will probably took 10 minutes for me with Teamviewer, pointing you out to the problem you already had, which might have tripped the installer. Most likely, your scenery.cfg was already corrupted, because having edited it by hand.
Plus I cannot tweak anything in the addon manager in FSX
You call this a problem ? Users have been asked for years the Addon Manager should NOT change the FSX.CFG without their knowledge (it didn't, you had to Save first), so we know added an additional security, for users that are too quick to press the Save button: each tweak must be first ENABLED, so it will be active, and saved, when you press Save, of course...
And again when I did the system restore I had the same problem where FSX couldn't locate certain sceneries. I couldn't even find them in Windows Explorer. Please
I'm not sure what do you mean with "certain sceneries" but, if you mean what it seems, so they are not just the FSDT sceneries, it seems to be a confirmation your scenery.cfg already had problems to begin with, that you were supposed to fix before installing anything new.
If contact me in private, we can have a Teamviewer session, so I can point you out to the problem very easily.
-
Dear Umberto,
Thank you for the explanation ( if I understand correctly) that now your products ( and flightbeam's) will not show up in the scenery config file anymore. That is actually what I see after having installed KCLT. All entries are now gone. I had all my sceneries sorted by continent in my scenery.cfg file and I use Simstarter to only activate the scenery that I actually fly to and from. This to save vas as some good folks advised. Your sceneries do show in the in-sim-scenery library function in my P3d 3.4. They are now all activated and all on top. But they do not show anymore in Simstarter. Furthermore I only see buildings in KCLT. None of your other airports ( or flightbeam's) show buildings anymore. Also GSX does not work anymore.
The fact that I cannot use Simstarter anymore to deselect scenery that I am not flying to is a showstopper for me.
Fortunately I have I have a recent backup of my flightsim and I will rollback but apart from advantages that you list in your earlier message I do also see some unwanted side effects.
b rdgs/ Dick
-
I had all my sceneries sorted by continent in my scenery.cfg file and I use Simstarter to only activate the scenery that I actually fly to and from. This to save vas as some good folks advised
The advice of keep changing the scenery.cfg might be useful with most sceneries, but it's totally useless with the FSDT/Flightbeam sceneries, since we do a custom memory management, so everything related to the scenery is discarded from memory as soon as you are outside the scenery loading range, which is about 15NM out.
By enabling/disabling our sceneries before a flight, you are just wasting effort.
Your sceneries do show in the in-sim-scenery library function in my P3d 3.4. They are now all activated and all on top. But they do not show anymore in Simstarter.
That's simply because that program hasn't been updated to support what is now the official and suggested way to install any addon in Prepar3D 3 and above. It has been introduced by LM with P3D 3, and was finalized in 3.3 so, any addon developer, and especially some that do utilities that handle precisely the scenery library, had plenty of time to adapt it to support it.
Just an example, SODE didn't support this system until few weeks ago, so we asked to Jeffrey Stahli to add it, and since he immediately recognized the obvious advantages, he added to it.
Furthermore I only see buildings in KCLT. None of your other airports ( or flightbeam's) show buildings anymore. Also GSX does not work anymore.
It's possible your scenery.cfg already had a problem, so the migration didn't go well. Install using the latest full installers might fix it.
-
I posted about some issues, I am having with this install in a new thread because I thought they were different, but after having looked closer at my scenery.cfg file, there are some issues there.
While most of the scenery.cfg file is fine, all of the FSDT entries have been removed and the file is showing updated this evening and the only sim change that has been made this evening is installing KCLT, GSX, and KLAS.
Is it possible that one of those installers has caused this issue?
-
While most of the scenery.cfg file is fine, all of the FSDT entries have been removed and the file is showing updated this evening and the only sim change that has been made this evening is installing KCLT, GSX, and KLAS.
Are you using P3D 3.3+ or 4.0 ? If yes, that's entirely normal and correct, and the reasons why they don't appear there, have been explained in this thread.
-
Unberto, thank you for your quick reply.
I mentioned that I had the missing building problem again. Your answer: " it's possible your scenery.cfg already had a problem, so the migration didn't go well. Install using the latest full installers might fix it."
I did not migrate Umberto. I mentioned P3dv3.4 in my message. I have not touched v4 yet.
I see various other simmers having these problems Could it be that you observation that my scy.cfg already had a problem is a bit premature ? Also because I did not even migrate ?
You did a great job in supporting V4, very fast, with nice savings. Kudo's to FSDT. Let's now try to solve the situations that I see other simmers and myself have with earlier p3d versions and even FSX.
thank you/ Dick
-
I did not migrate Umberto. I mentioned P3dv3.4 in my message. I have not touched v4 yet.
The new scenery installation system is supported from P3D 3.3 and above, it's not related to V4 only so yes, with 3.4, your sceneries were surely migrated so, something happened.
-
Thank you Umberto for your explanation. It is because of you that I ( and many others) find out about the new scenery approach. Although I do see the advantages, at the moment it does cause inconvenience now for existing owners of P3dV3. I guess many simmers are left wondering what happened to their sceneries.
I guess I better change soon to P3D V4.
-
Good day Umberto,
Having now gained access to the forum I see I'm not alone. Let me start by saying nice work. The scenery looked really great when testing it out earlier this morning. I say looked because after my initial test flight I haven't been able to launch P3Dv3. I did observe when installing KCLT that all FSDT/FB scenery were removed from their original place (in my case G:\ to C:\Programfiles x86 like that of SODE. I assumed that this function would provide better functionally of these associated scenery/files and perhaps better performance too. I see now that was your intent. Much appreciated for that. However, unfortunately after spending an hour trying to figure out why P3DV3.4 would not load (open splash would hang and disappear and freeze in the processing tray) I was left to uninstall KCLT and the addon Manager to get P3DV3.4 running again.
Can you advise what may be happening and how I may be able to overcome this if I reinstall KCLT. (I've assumed that all the flies are in the C:\ directory and that perhaps all it requires is for me to reinstall KCLT and the addon Manager. If there is something else to consider I'd like to know before this reattempt)
Thanks
-
The failure to load the sim shouldn't have anything to do with the move of the files to the new location (which you can choose, it's just you accepted the proposed default location).
First, check the following key in the registry editor ( REGEDIT )
HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
And see if you have anything for Prepar3D.EXE. If you have, remove that line (the one that contains Prepar3D.exe ), and try reinstalling now.
-
That didn't work. Unfortunately, I'm not seeing Chaseplane start up, FSDG seasonal indicator or Ultimate Traffic Live startup. I'll need to uninstall again
-
Also, I not sure I follow what you said earlier that FSDT or / and beam did not touch the scenery.cfg
Here's what mine looked like before installing KCLT
-
Also, I not sure I follow what you said earlier that FSDT or / and beam did not touch the scenery.cfg
I wasn't entirely clear.
The new installer surely won't touch the scenery.cfg anymore, to install the NEW scenery you are installing now but, if it finds old scenery installed with the old system, it will obviously have remove from there, in order to add them using the add-on.xml system.
But, of course, this part of the installer, the one that removes a scenery from the scenery.cfg, has always been the same as it always were, when it removed the scenery during the uninstall.
Fact you said you couldn't edit the scenery.cfg yourself, seems to indicate that something is wrong, maybe a permission problem, or another application that opened the file, which might have caused the installer to fail to remove the old installations properly.
-
Umberto, I sent you a few PMs so I was just seeing if you received them. Thanks
-
Also, I not sure I follow what you said earlier that FSDT or / and beam did not touch the scenery.cfg
I wasn't entirely clear.
The new installer surely won't touch the scenery.cfg anymore, to install the NEW scenery you are installing now but, if it finds old scenery installed with the old system, it will obviously have remove from there, in order to add them using the add-on.xml system.
But, of course, this part of the installer, the one that removes a scenery from the scenery.cfg, has always been the same as it always were, when it removed the scenery during the uninstall.
Fact you said you couldn't edit the scenery.cfg yourself, seems to indicate that something is wrong, maybe a permission problem, or another application that opened the file, which might have caused the installer to fail to remove the old installations properly.
I don't think I ever said I attempted to manually edit the scenery.cfg. I typically leave that to installers and the add/remove device in system settings. Nonetheless, I think I'm in a good place to be advised how to go about reinstalling
Here's what I have done.
1. Under ADD remove Devices I have removed all FSDT and FB scenery including addon manager(s) and Couatl (Closed and Rebooted Computer)
2. Started up P3DV3.4 and it asked me if I wanted to "enable" these same scenery. This brought to my attention that during the migration, the FSDT installer placed two new files in the Program Data\ Lockheed Martin Folder beginning with the name "add-on". The file(s) contained all the scenery I had purchased under the aforementioned developers.
I chose not to enable and continued with loading of P3dv3. Did a test flight in the F15 and then exited
3. Reboot computer
4. Loaded up P3DV3.4 again and this time I was not prompted to "enable". Continued and flew two sessions successfully. However, whilst in flight I pursued through the Menu bar to ensure all was in order, when I came upon a new "Add on" selection. This revealed the perhaps a xml file still exist within my associated files with the pertinent information to enable the FSDT and FB scenery.
So From this point I ask, what should my next steps be?
How should I conduct a reinstall of all scenery (FSDT and FB)?
Should I start from the oldest to the newest or does it not matter?
Will the new procedures follow with any of the scenery I install first (KLAS, KORD etc) or do I need to start with KCLT?
I think this is important, because every previous install was a failure. (with an exception to the initial installed which worked the first time, but closing out P3DV3.4 and restarting it is where troubles began)
Also, I noticed there is now a FSDT Live update desktop shortcut - Can you enlighten us as to how this works. Does it require us to launch it (should we) every week or is there an alternate routine schedule for it (Will a notice be posted in the FSDT forum to run the live update?)?
-
1. Under ADD remove Devices I have removed all FSDT and FB scenery including addon manager(s) and Couatl (Closed and Rebooted Computer)
2. Started up P3DV3.4 and it asked me if I wanted to "enable" these same scenery
Yes, I can see how you would be easily confused. Have a look at this post of mine here:
http://www.fsdreamteam.com/forum/index.php/topic,15688.msg112880.html#new
Which explains a quirk of the migration process that we really cannot fix it entirely, and I see how you could have been confused.
What happened, is that you launched the OLD Uninstallers AFTER the scenery were already migrated. Those uninstaller didn't really do much, because the files were moved from their original folder.
However, since you already migrate them, the very presence of the add-on.xml file in the Documents\Prepar 3d add-ons folder, triggered what is called "Auto-discovery": the sim found an xml for an addon, but it wasn't activated, so it asked to reactivate it.
And, I also found an explanation for the "mystery" lines you found in the scenery.cfg, like this:
[Fsdreamteam KCLT]
Active=TRUE
You might have assumed this were added by KCLT, but they weren't. It was the sim ITSELF that added them, when it asked to reactivate (if you have Active set to True), or when it said it found an orphaned area, asking to disable (if you Active is False ).
So yes, it's confirmed: the KCLT installed hasn't trashed your scenery.cfg...
-
Is there any way that I can edit the names of the sceneries please.
I have slight OCD and I rename all my scenery entries in the form of
<ICAO code> - <scenery name>
e.g KCLT - FSDreamTeam Charlotte
And then have sort them alphabetically in my scenery list. Right now I'm being triggered because all of the FSDT sceneries in P3D now appear at the top of my scenery list and I don't want that.
Panman
-
Is there any way that I can edit the names of the sceneries please.
You can do this by editing the <Name> tag (not the <Addon.Name>!! ) in the add-on.xml for the scenery, which is located in Documents\Prepar3d v4 Add-ons
-
1. Under ADD remove Devices I have removed all FSDT and FB scenery including addon manager(s) and Couatl (Closed and Rebooted Computer)
2. Started up P3DV3.4 and it asked me if I wanted to "enable" these same scenery
Yes, I can see how you would be easily confused. Have a look at this post of mine here:
http://www.fsdreamteam.com/forum/index.php/topic,15688.msg112880.html#new
Which explains a quirk of the migration process that we really cannot fix it entirely, and I see how you could have been confused.
What happened, is that you launched the OLD Uninstallers AFTER the scenery were already migrated. Those uninstaller didn't really do much, because the files were moved from their original folder.
However, since you already migrate them, the very presence of the add-on.xml file in the Documents\Prepar 3d add-ons folder, triggered what is called "Auto-discovery": the sim found an xml for an addon, but it wasn't activated, so it asked to reactivate it.
And, I also found an explanation for the "mystery" lines you found in the scenery.cfg, like this:
[Fsdreamteam KCLT]
Active=TRUE
You might have assumed this were added by KCLT, but they weren't. It was the sim ITSELF that added them, when it asked to reactivate (if you have Active set to True), or when it said it found an orphaned area, asking to disable (if you Active is False ).
So yes, it's confirmed: the KCLT installed hasn't trashed your scenery.cfg...
Maybe not, but with a fresh install I still cannot start P3dv3.4.9. The splash screen vanishes 40 sec after launch. Funny though the application is still showing in the processes (tray) but hangs at 342,000K.
All works in pd3v4 with no issue...
In this fresh install I ran:
Sode1.50
LASv2
KCLT,
KSFOHD (FB)
KDEN (FB)
GSX
But again, I can't load in P3dv3.4.9. Can you tell, me what gives? Why does this work with p3dv4 and not with p3dv3.4.9
-
But again, I can't load in P3dv3.4.9. Can you tell, me what gives? Why does this work with p3dv4 and not with p3dv3.4.9
There's no reason why it wouldn't but, please, in order to have a better chance to be supported, only use the latest version of each supported sim.
Just like in FSX, we ONLY supported SP2 or Acceleration, in P3DV3, we can only support the most current version of it because, you cannot expect we could test it with all the dozen of updates that has been made during its life.
So, please, update to the latest version, which is 3.4.23, and report back.
-
But again, I can't load in P3dv3.4.9. Can you tell, me what gives? Why does this work with p3dv4 and not with p3dv3.4.9
There's no reason why it wouldn't but, please, in order to have a better chance to be supported, only use the latest version of each supported sim.
Just like in FSX, we ONLY supported SP2 or Acceleration, in P3DV3, we can only support the most current version of it because, you cannot expect we could test it with all the dozen of updates that has been made during its life.
So, please, update to the latest version, which is 3.4.23, and report back.
updated and still no sunshine. btw the latest version is 3.4.22.19868. in fact it shuts down faster now. I'm going to uninstall again
-
So I decided to uninstall one by one...starting with Charlotte...... guess what....its kclt. Once I uninstalled it (kclt) prepar3dv3.4.22 and or v3.4.9 works and loads up perfectly
Correction...I had to uninstall the addon Manager and then clear/uninstall the other scenery too
-
Is there any way that I can edit the names of the sceneries please.
You can do this by editing the <Name> tag (not the <Addon.Name>!! ) in the add-on.xml for the scenery, which is located in Documents\Prepar3d v4 Add-ons
Okay I can rename them successfully. How about reordering them so that all the FSDT entries do not appear at the top of my scenery list?
-
DO we need to turn off anti Virus or and assign privileges to the installers?
-
How about reordering them so that all the FSDT entries do not appear at the top of my scenery list?
They *should* appear on top of the list, because that's the safest place against possible conflicts caused by airports. The general rule, is that airports, which usually cover the smallest area, should always stay on top of sceneries covering larger areas.
It's not possible to rearrange them using the UI of the sim. The only way to do it, at this time, is to set the <Layer> property in the add-on.xml file, located in the Documents\Prepar3d v4 addons.
We hope that either LM or some 3rd party developer would came out with a solution, because the system definitely supports rearranging, just now with the default UI of the sim.
-
They *should* appear on top of the list, because that's the safest place against possible conflicts caused by airports. The general rule, is that airports, which usually cover the smallest area, should always stay on top of sceneries covering larger areas.
When it comes to rearranging I know what I am doing. I like to have my scenery in alphabetical order. I don't put libraries, larger areas etc at the top. It looks neater and it doesn't trigger my OCD when I have them arranged alphabetically. Will try that layer property.
-
I hate to add to this thread, but I'm at a loss now.
I had successfully installed KCTL into v4 and v3. It worked perfectly fine up until about 2 hours ago. I had not changed a thing. I wanted to test something in v3 for KCTL and then get back to v4. Once I tried opening v4 again, it crashed during startup.
To get to the bottom of this, I uninstalled KCTL (including the add-on manager) and re-installed it -> to no avail. Then I thought, what the hell, let's start with a fresh v4 install, I hadn't installed that much yet. Did that, worked flawlessly. Then re-installed KCTL -> same crash.
I really don't know what's going on, reading all the above issues and experiencing mine. And I don't want to be in Umberto's position. But something is wrong...
Was anything changed in the KCTL installer (Live update) over the last say 3 to 4 hours (between 1600 CET and 2000 CET)? That's the only clue I have at this point. Because it did work until then :O.
Edit: Even after only installing GSX (no other FSDT scenery is installed in v4) now lets P3D v4 crash at start up. Everything works fine until I install anything FSDT... I'm about to give up. v3 works flawlessly.
Edit 2: Once I uninstall GSX P3D v4 will start up as usual and work perfectly fine.
Edit 3: Tried the same with KLAS now -> same result. Once I have installed it P3D v4 crashes. Upon uninstall everything works fine...
I don't think there is anything else I can try?
Jan
-
See this thread named "Addon Manager crashes Prepar3D v4 **SOLVED** "
http://www.fsdreamteam.com/forum/index.php/topic,15721.msg113190.html#msg113190
The user was also convinced it was something wrong with our software, because the sim started when disabling it. Had a Teamviewer session with him and, guess what, it was Windows applying a sneaky compatibility setting, that's cause the conflict.
Once the flag was cleared, P3D started again immediately.
-
Thanks so much Umberto. That did it. How do you find this stuff :)?
Glad I can finally start building up v4 again :)
Thanks,
Jan