Author Topic: couatl crash  (Read 5369 times)

brocka03

  • Newbie
  • *
  • Posts: 5
couatl crash
« on: April 05, 2020, 09:45:15 am »
whenever i attempt to load gsx or whenever the airport cache is regenerated, i get an error saying "Couatl encountered an uncoverable error, please run live update" so I did and to no avail, i also tried reinstalling and those sorts of things. Error Details:

couatl v3.2 (build 4308)
panic log started on Sun Apr  5 17:37:15 2020

problem raised by engine or unspecified addon
{'Airport': 'KVPS', 'User Pos': (30.499341575302754, -86.51128613394975, 28.3284 m, 1.81136 m, 192.17778308605745)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KVPS', 'User Pos': (30.499341575302754, -86.51128613394975, 28.3284 m, 1.81136 m, 192.17778308605745)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KVPS', 'User Pos': (30.499341575302754, -86.51128613394975, 28.3284 m, 1.81136 m, 192.17778308605745)}
reset FSDT_GSX_AIRCRAFT_EXIT_3_TOGGLE to 0

p3dx3

  • Hero Member
  • *****
  • Posts: 592
Re: couatl crash
« Reply #1 on: April 06, 2020, 01:41:15 am »
whenever i attempt to load gsx or whenever the airport cache is regenerated, i get an error saying "Couatl encountered an uncoverable error, please run live update" so I did and to no avail, i also tried reinstalling and those sorts of things. Error Details:

couatl v3.2 (build 4308)
panic log started on Sun Apr  5 17:37:15 2020

problem raised by engine or unspecified addon
{'Airport': 'KVPS', 'User Pos': (30.499341575302754, -86.51128613394975, 28.3284 m, 1.81136 m, 192.17778308605745)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KVPS', 'User Pos': (30.499341575302754, -86.51128613394975, 28.3284 m, 1.81136 m, 192.17778308605745)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KVPS', 'User Pos': (30.499341575302754, -86.51128613394975, 28.3284 m, 1.81136 m, 192.17778308605745)}
reset FSDT_GSX_AIRCRAFT_EXIT_3_TOGGLE to 0


What scenery is there in your sim for KVPS?

brocka03

  • Newbie
  • *
  • Posts: 5
Re: couatl crash
« Reply #2 on: April 06, 2020, 02:24:23 am »
none, its default no additions made, this also happens at all addon sceneries, including FSDT sceneries

p3dx3

  • Hero Member
  • *****
  • Posts: 592
Re: couatl crash
« Reply #3 on: April 06, 2020, 03:24:02 am »
none, its default no additions made, this also happens at all addon sceneries, including FSDT sceneries

Open add-on.cfg file in notepad
Location is c:\programdata\lockheed martin\prepar3d v4

are there any fsdt sections?

brocka03

  • Newbie
  • *
  • Posts: 5
Re: couatl crash
« Reply #4 on: April 06, 2020, 05:10:11 am »
yes, exclude, memphis, sode and aerosoft a318-a319

p3dx3

  • Hero Member
  • *****
  • Posts: 592
Re: couatl crash
« Reply #5 on: April 06, 2020, 05:20:43 am »
yes, exclude, memphis, sode and aerosoft a318-a319

I had this problem too FSDT is installing to the wrong location. You also have folders in the My Documents \ Prepar3d V4 Add Ons
For those FSDT programs?
Remove them from the add-on.cfg (be sure of the right one)
c:\programdata\lockheed martin\prepar3d v4
Renumber the other entries after removing the FSDT entries for Exclude and Memphis. Start p3d. Should not crash now.

brocka03

  • Newbie
  • *
  • Posts: 5
Re: couatl crash
« Reply #6 on: April 06, 2020, 05:21:34 am »
i'll try it now hold on

brocka03

  • Newbie
  • *
  • Posts: 5
Re: couatl crash
« Reply #7 on: April 06, 2020, 05:34:16 am »
ok its all fixed now thank you  :) :)

p3dx3

  • Hero Member
  • *****
  • Posts: 592
Re: couatl crash
« Reply #8 on: April 06, 2020, 06:15:10 am »
ok its all fixed now thank you  :) :)

 :)

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: couatl crash
« Reply #9 on: April 06, 2020, 10:45:47 pm »
I had this problem too FSDT is installing to the wrong location.

FSDT is surely not installing in the wrong location. If you think it does, than please file a proper report, and we'll check if it's really the case.

p3dx3

  • Hero Member
  • *****
  • Posts: 592
Re: couatl crash
« Reply #10 on: April 08, 2020, 11:21:52 pm »
I had this problem too FSDT is installing to the wrong location.

FSDT is surely not installing in the wrong location. If you think it does, than please file a proper report, and we'll check if it's really the case.

Where do I file a report? I helped many people with this exact issue. The installer is placing entries in c:\programdata add-on.cfg AND adding folders to My Documents so the addons are being added 2 times which causes the crashing. Removing the add-on.cfg entries that I said above will resolve it.

n452mk

  • Newbie
  • *
  • Posts: 19
Re: couatl crash
« Reply #11 on: April 11, 2020, 03:17:09 am »
I think is something in my windows preventing this, I updated this week over ten times for different flights so the coualt will show, can anyone help? I dont even use antivirus just windows defender and on or off does the same thing, please help

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51400
    • VIRTUALI Sagl
Re: couatl crash
« Reply #12 on: April 13, 2020, 04:16:03 pm »
Where do I file a report? I helped many people with this exact issue.

Here, of course. Where else ?

Quote
The installer is placing entries in c:\programdata add-on.cfg AND adding folders to My Documents so the addons are being added 2 times which causes the crashing. Removing the add-on.cfg entries that I said above will resolve it.

Sorry, but this is NOT while the program crashes and the installer is CORRECT doing this. In fact, it's not even "the installer", it's P3D ITSELF which creates those two entries, and this is exactly how it's supposed to work. I believe you are assuming a double entry, but there isn't one, if you use ONLY the FSDT installers. I'll try to explain:

When an add-on use the P3D own facilities ( it should ) to install using the add-on.xml method, the following will happen:

- The add-on.xml will be created, in a folder named like the addon itself, under Documents\Prepar3d V4 Add-ons

- An entry for the add-on will be created in the add-on.cfg. WHICH one, depends on the permission level the installer ran with. If the installer ran with Admin permissions ( all our installer runs like that ), the entry will be created in the add-on.cfg in %PROGRAMDATA%, if it doesn't, the entry will be created in the add-on.cfg in %APPDATA%

This is NOT a "double entry", the add-on.xml in Documents and the add-on.cfg file are two entirely different things, the first *defines* the files used by the add-on, and the other *enables* the add-on. BOTH are required in order for the add-on to be visible so no, it's not a double entry.

If you manage the files manually, or using external utilities, it might be possible to end up with double entries, which are NOT created by our installers. For example, you might have decided to move the entry correctly created by the installer in the add-on.cfg located under %PROGRAMDATA% to %APPDATA%, then you run our installer again, and it *might* create a 2nd entry in %PROGRAMDATA% ( again, it's NOT our installer, it's P3D itself that does it, when called from our installer ), so if you got a double entry, it was because you moved something manually, but it's surely not created when always using our installers, and nothing else.

p3dx3

  • Hero Member
  • *****
  • Posts: 592
Re: couatl crash
« Reply #13 on: April 14, 2020, 01:57:58 am »
there should be no add-on.cfg entry created it will be added by p3d to appdata once p3d runs and it finds a folder in my documents \ prepar3d v4 addons
« Last Edit: April 14, 2020, 10:11:14 pm by virtuali »

n452mk

  • Newbie
  • *
  • Posts: 19
Re: couatl crash
« Reply #14 on: April 14, 2020, 04:22:52 am »
I see the files, see picture attached and please let me know if this is correct, this was after I just did an update so maybe tomorrow will disappear again :(