FSDreamTeam forum
September 20, 2018, 03:50:28 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News:
 
   Home   Help Login Register  
Pages: [1]
  Print  
Author Topic: KDFW - No Fuel? plus a Couatl crash issue at KPBI  (Read 74 times)
ArJuna
Newbie
*
Posts: 5


« on: September 14, 2018, 10:38:00 PM »

I have two issues I need help with. One is specific to FSDT KDFW which I recently purchased. The other is a COUATL crash at a default airport.

I am on a trek in my A2A C182 from Bolivia to Alaska. One of my stops for fuel was in the default P3Dv4.3 airport at KPBI Palm Beach, FL . It seemed fine the first time I landed at KPBI and I got my fuel and called it a night. When I loaded the flight back up this morning the COUATL engine crashed and threw up the following Couatl.err

=============================
couatl v3.2 (build 3997)
panic log started on Fri Sep 14 04:21:51 2018

problem raised by engine or unspecified addon
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
User collision geometries reloaded
=============================


I tried reloading Couatl engine and this kept repeating. I tried rebooting everything twice and it persisted, so I finally chose to not restart Couatl and moved on. My next planned stop for fuel was FSDT KDFW. When I landed Ground control offered no options to taxi to fuel. My onnly choices were taxi to gate or parking. I searched the airport using Little Navmap and I could not find fuel anywhere. I searched the KDFW manual and the word fuel does not appear anywhere.

Can you tell me how to find a place to fuel up at KDFW?

Can you explain why Couatl would crash at KPBI?

I will mention that yesterday when I stated P3D it told me to exit and run the FSDT Live Update. I did so and it told me I had to download the new GSX Level 2 product before I could continue. I cancelled out of that as I had no intention to install GSX Level 2 at that time. I need to take precautions with my build before I install new software, especially untested software.  I should mention that I've been using P3D a LOT since I bought GSX 3-4 weeks ago and I have not had this crashing of Couatl issue before. I was wondering if the attempt to run the Live Update might have caused an issue, but I tried loading up 5 airports I use regularly to see if Couatl crashed anywhere besides KPBI, but it worked fine, so now I suspect it is some conflict with the default KPBI airport.

Much thanks for your assistance.
AJ
Logged
virtuali
Administrator
Hero Member
*****
Posts: 31158



WWW
« Reply #1 on: September 14, 2018, 10:47:01 PM »

couatl v3.2 (build 3997)
panic log started on Fri Sep 14 04:21:51 2018

problem raised by engine or unspecified addon
{'Airport': 'KPBI', 'User Pos': (26.679292358609057, -80.09707367422462, 6.95646 m, 1.16546 m, 269.38902634557223)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'

You are running with an old version of Couatl, one that came with the previous GSX, but you have the newer code GSX L2 code which calls jetways.

Normally, it's impossible to get an old version of Couatl *and* L2 code that tries to create jetways, since they are downloaded and installed together from the same Live Update server.

And, if you "just" ran the Live Update now, it would stop with an error message, not letting to continue until you download and install the latest GSX full installer, which comes with the current version of Couatl so, it's not even possible to be stuck with the old version by mistake.

The only possible reason I can think of for this to be happeing, is if you somehow manually replaced the Couatl.exe from an old version of GSX. This won't ever work.

Try to remove this file:

Addon Manager\Couatl\Couatl.exe

Then run Live Update again. I'm sure it will download the latest version.
Logged

ArJuna
Newbie
*
Posts: 5


« Reply #2 on: September 14, 2018, 11:47:59 PM »

Thanks for the quick response.  I never changed anything myself. When P3D told me to run the Live Update yesterday, I did. It must have changed something.  I did not want to install GSX Level 2. That's why I cancelled the live update and did not proceed when it asked me to do that.

Against my wishes I have now installed both GSX Level 2 and the "setup_addonmanagerX.exe" and the problem is gone.

To be clear, the live updater caused the issue.

Do you have any suggestions on my other question on how to get fuel at FSDT KDFW?  it seems very odd that there is no fuel at this large airport.  The real airport has plenty of fuel.  Can you please add this in the next update?

Thanks for the help sir.
Logged
ArJuna
Newbie
*
Posts: 5


« Reply #3 on: September 15, 2018, 01:50:15 AM »

Please read my previous post.

I rest my case on not appreciating being forced to install buggy new software. Now my hotkeys for both GSX and for the YouControl menus no longer work.  I have checked the COUATL settings and they are set correctly and worked before.

I simply wanted to fly these last couple days and instead I am dealing with updating to a product I don't own and now having lost my normal control I had before.

Can you point to instructions for removing GSX Level 2. I will install the old GSX if you can tell me how to turn off the live updater so it doesn't want to "update" my GSX to the new version. Otherwise i will be happy to take a refund for the entire GSX thing.

I am, shall I say, pissed!

Of course this post will probably be deleted, which seems to be SOP around here.
Logged
ArJuna
Newbie
*
Posts: 5


« Reply #4 on: September 15, 2018, 02:57:15 AM »

Please read also my previous two posts in this thread.

OK, I am using the Add-ons menu to try and use the new GSX at FSDT KDFW Gate 14 and at first it was working and I was able to get the jetway to move onto the front door of my PMDG 747.  I then tried rebooting to try rerunning the live update and hopefully resolving the issues mentioned in previous two posts. I started the exact same scenario from scratch, again at KDFW Gate 14. Now when I try to select GSX from the add-on menu I get a message from GSX saying "the gate is too small for your aircraft.  Ground Services are not available." The exact same gate.  gate 14 is listed as "Large".  Is there something larger?

GSX is basically useless since this new Level 2 was shoved down  my throat. As you can see I am very bitter that I had no choice but to install this massive beta software.

I just love headaches.
AJ
« Last Edit: September 15, 2018, 03:07:02 AM by ArJuna » Logged
virtuali
Administrator
Hero Member
*****
Posts: 31158



WWW
« Reply #5 on: September 15, 2018, 08:31:27 AM »

Thanks for the quick response.  I never changed anything myself. When P3D told me to run the Live Update yesterday, I did. It must have changed something.  I did not want to install GSX Level 2. That's why I cancelled the live update and did not proceed when it asked me to do that.

If you had the old version of Couatl (= GSX with no Level 2), the update wouldn't even start, since it checks if you installed the full Level 2 installer and, if you don't, you cannot even proceed with it.

Quote
Against my wishes I have now installed both GSX Level 2 and the "setup_addonmanagerX.exe" and the problem is gone.

Of course it's gone, the product clearly works.

Quote
To be clear, the live updater caused the issue.

No, it didn't. If you were on the old version, it won't changes anything to your files if you don't install the new full installer.

Quote
Do you have any suggestions on my other question on how to get fuel at FSDT KDFW?  it seems very odd that there is no fuel at this large airport.  The real airport has plenty of fuel.  Can you please add this in the next update?

You asked ATC for fuel, but there's no need to do that anymore, since the GSX fuel tanker can come to your airplane regardless where you parked, and regardless if the scenery has a Fuel parking.

Quote
I rest my case on not appreciating being forced to install buggy new software. Now my hotkeys for both GSX and for the YouControl menus no longer work.  I have checked the COUATL settings and they are set correctly and worked before.

This doesn't obviously have anything to do with GSX. If GSX is running (you have the GSX menu under the Addons menu), if the hotkey don't work, it's caused by a key conflict with another addon.  UT2, for example, use CTRL+Shift+F12 to change the traffic density, stealing the key from GSX. So, you must fix the conflict yourself, either in GSX or in the conflicting addon and be sure they don't use the same keys.

Quote
OK, I am using the Add-ons menu to try and use the new GSX at FSDT KDFW Gate 14 and at first it was working and I was able to get the jetway to move onto the front door of my PMDG 747.

If GSX works from the menu and not from the hotkey, this is a clear confirmation your problem you mistakenly flagged as "buggy software" in your previous post, didn't had anything to do with GSX, and was just a key conflict with another addon.

Quote
started the exact same scenario from scratch, again at KDFW Gate 14. Now when I try to select GSX from the add-on menu I get a message from GSX saying "the gate is too small for your aircraft.  Ground Services are not available." The exact same gate.  gate 14 is listed as "Large".  Is there something larger ?

And this, AGAIN, doesn't have anything to do with "buggy" or "beta" software. Since GSX was released in 2012, it ALWAYS worked this way: to check if the parking is large enough for your airplane, it compares the parking radius against your airplane wingspan, and will issue that message.

The Small, Medium, Heavy names are just labels, what matters is the parking radius in the scenery AFCAD.

OF COURSE, GSX being the flexible program it is, since many years it has offered the option to override what's inside the scenery AFCAD so, if you are reasonably sure that parking *should* large enough for a 747, you can customize the parking position, by clicking the small icon with an airplane in the parking customization page.

This is of course fully explained in the GSX manual, at Page 34, the explanation of the "Max Allowed Wingspan" parameter. It's been there since forever.
Logged

ArJuna
Newbie
*
Posts: 5


« Reply #6 on: September 15, 2018, 09:47:39 PM »


Thank you very much for your response.

The keystrokes I am using for GSX level 2 is the same as it was in GSX Level 1 and was working perfectly right up to the forced upgrade to GSX Level 2.

I tried many other keystroke combinations and it fails to work with any combination.


On the airport parking issue, Gate 14 at FSDT KDFW is large enough for the 747. GSXL2 even worked the 1st time I  tried using it there, but the second time it said it was too small.  i hear you about being able to customize a parking space, but I am not in the mood to edit every parking space I use in P3D just to get GSX working. It kind of kills the immersion to have to reprogram every parking when I get to an airport and get assigned a parking spot. IMO GSX should have worked out the issues on parking, especially on this one since it is one of your airports.

I am beginning to realize that nothing is FSDT's fault and will proceed forward with that in mind, including where I spend my $$$.
Logged
virtuali
Administrator
Hero Member
*****
Posts: 31158



WWW
« Reply #7 on: September 16, 2018, 02:57:04 AM »

IMO GSX should have worked out the issues on parking, especially on this one since it is one of your airports.

You are right. It should work at our airports. But, the issue is, you are entirely wrong about this being a GSX problem or a bug. GSX is working as expected. If anything, it's KDFW that might require some improvements.

GSX always works correctly. When it doesn't, 99% of the times is the scenery's fault. And in this case, it's an FSDT scenery. One that has been made years before GSX, but still, we'll probably should have a second look at it.

Adding SODE jetways to it will be a good chance to do that.
Logged

Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Valid XHTML 1.0! Valid CSS!