All FSDT scenery disapeared from scenery.cfg **SOLVED**

[rhadamantys]

Hello, may be this question has been asked yet. But to be sure and because I not found precise answer about this.

Why your last update deleted all my FSDT sceneries from my scenery.cfg? I use P3D V3.4, not used P3D V4 yet.

May be it's normal, but could you just tell me precisely if I have to do something or if I can use all my fsdt sceneries? Even if all of these are not present in scenery.cfg?

Thanks

[Dave_YVR]

Read these threads, this was news last week and is all over these forums.

[SWAPilot]

what threads??

[Dave_YVR]

 Here's a small sample from a quick run look down the threads. It's been covered over and over again all just in the past week.

http://www.fsdreamteam.com/forum/index.php/topic,15897.0.html

http://www.fsdreamteam.com/forum/index.php/topic,15917.0.html

http://www.fsdreamteam.com/forum/index.php/topic,15851.0.html

http://www.fsdreamteam.com/forum/index.php/topic,15799.0.html

[SWAPilot]

Thank you

[rhadamantys]

Thanks for your reply,

But, unfortunately, since the new addon manager update, I cannot use any FSDT Scenery! Even in FSX.

In exemple, I tried KDFW scenery in FSX and once scenery loaded I have a scary error message about Coualt Script Engine.

This is the error message log :

"couatl v3.2 (build 3827)
panic log started on Tue Jun 13 02:33:34 2017

problem raised by engine or unspecified addon
{'Airport': 'KDFW', 'User Pos': (32.87949984381062, -97.03000855604772, 186.93 m, 1.90544 m, 0.25974579547095134)}
Entering KDFW area"

Please! Could you help me and for of course could you explain me what's going on? I don't understand where is the problem after your massive update?

Thanks

[virtuali]

problem raised by engine or unspecified addon
{'Airport': 'KDFW', 'User Pos': (32.87949984381062, -97.03000855604772, 186.93 m, 1.90544 m, 0.25974579547095134)}
Entering KDFW area"

Please! Could you help me and for of course could you explain me what's going on? I don't understand where is the problem after your massive update?

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.

And, you don't say if P3D 3.4 is working.

[rhadamantys]

Hi Umberto, thanks for your quick reply, I will try tomorrow for P3D 3.4 and let you know.

So I have to rebuild a new FSX.cfg to run coualt properly?

[rhadamantys]

And for more information, before the new update, my all FSDT Sceneries worked like a charm with coualt engine. My problem occurred when I pushed the new update. And I don't touch FSX.cfg long time ago.

[virtuali]

And for more information, before the new update, my all FSDT Sceneries worked like a charm with coualt engine. .

That's because 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.

But again, is not possible to say for sure, without checking your FSX.CFG file.

[rhadamantys]

Hi Umberto,

thank you very much for your help. You had right! The new path for Sim objects Misc was not in my FSX.cfg

I added it manually and it solved my Coualt script engine crash for long time...

Thanks again