General Category > General Discussion

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

<< < (2/3) > >>

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:

--- Quote from: rhadamantys on June 13, 2017, 02:36:08 am ---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?
--- End quote ---

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:

--- Quote from: rhadamantys on June 13, 2017, 03:32:55 am ---And for more information, before the new update, my all FSDT Sceneries worked like a charm with coualt engine. .
--- End quote ---

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.

Navigation

[0] Message Index

[#] Next page

[*] Previous page