FSDreamTeam forum
General Category => General Discussion => Topic started by: zap51 on July 02, 2019, 02:11:20 am
-
I updated FSDreamteam using FSDT Live Update. I updated to the latest GSX2. Every time I start a flight my couatl crashes. I am unable to use FSDT or GSX. I'm caught in a loop. This is very frustrating. Any suggestions?
My error: couatl v3.2 (build 4231)
panic log started on Mon Jul 1 19:04:57 2019
problem raised by engine or unspecified addon
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_5_LOGO__SWA'
{'Airport': 'KDAL', 'User Pos': (32.84586626528172, -96.84752667060448, 150.904 m, 2.46661 m, 289.8449455949881)}
reset FSDT_GSX_BATTERY_VOLTAGE to 0
User collision geometries reloaded
-
Do you use FSX ? If yes, we are aware of it, and the only solution is move the .INI customization for that airport to a different folder, while waiting for a fix.
-
Yes, I have FSX-SE. None of my airports are showing up. When will this be fixed?
-
Yes, I have FSX-SE. None of my airports are showing up. When will this be fixed?
Which airports ? If you mean your FSDT airports, then you must apply the solution I indicated in my previous reply, until we'll come up with a proper fix.
-
All of them. All my FSDT airports. All my payware airports (buildings won't load). I am trying to do a flight from KDAL to KDEN. After being told to update for addon I went to the site and it only showed available for FS9. I tried FSDT Live update. After I updated and tried to do a flight, couatl will crash and ask me if I want to restart couatl. I get stuck in this loop until I choose not to restart it, then I have no GSX. I went to the KDEN airport (Flightbeam) and only the jetways show. Same with KDFW (FSDT).
-
Where do I find these INI customization files and which folder do I move it to?
-
?
-
Since today's Live update both FSX and P3Dv4.5HF1 (KJFKv2 only one tested) failed.
Typical err Log:
couatl v3.2 (build 4231)
panic log started on Mon Jul 1 23:58:51 2019
problem raised by engine or unspecified addon
{'Airport': 'KJFK', 'User Pos': (40.64087157704115, -73.7928489431911, 6.53392 m, 2.42152 m, 353.6695431251415)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_JBT_1_4_LOGO__HSBC'
{'Airport': 'KJFK', 'User Pos': (40.64087157704115, -73.7928489431911, 6.53392 m, 2.42152 m, 353.6695431251415)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_1_4_LOGO__HSBC'
{'Airport': 'KJFK', 'User Pos': (40.64087157704115, -73.7928489431911, 6.53392 m, 2.42152 m, 353.6695431251415)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_JBT_1_4_LOGO__HSBC'
{'Airport': 'KJFK', 'User Pos': (40.64087157704115, -73.7928489431911, 6.53392 m, 2.42152 m, 353.6695431251415)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_JBT_2_5_LOGO__HSBC'
{'Airport': 'KJFK', 'User Pos': (40.64087157704115, -73.7928489431911, 6.53392 m, 2.42152 m, 353.6695431251415)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_JBT_2_5_LOGO__HSBC'
{'Airport': 'KJFK', 'User Pos': (40.64087157704115, -73.7928489431911, 6.53392 m, 2.42152 m, 353.6695431251415)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_JBT_2_5_LOGO__HSBC'
{'Airport': 'KJFK', 'User Pos': (40.64087157704115, -73.7928489431911, 6.53392 m, 2.42152 m, 353.6695431251415)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_JBT_2_5_LOGO__SIXT'
{'Airport': 'KJFK', 'User Pos': (40.64087157704115, -73.7928489431911, 6.53392 m, 2.42152 m, 353.6695431251415)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_1_4_LOGO__HSBC'
{'Airport': 'KJFK', 'User Pos': (40.64087157704115, -73.7928489431911, 6.53392 m, 2.42152 m, 353.6695431251415)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_2_7_LOGO__HSBC'
{'Airport': 'KJFK', 'User Pos': (40.64087157704115, -73.7928489431911, 6.53392 m, 2.42152 m, 353.6695431251415)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_SODE_JW_TB_1_4_LOGO__HSBC
-
I got a Couatl.err log and changed it to a txt file to attach here:
-
My FSX has the same problem.
Is FSX not suitable for new updates?
My English is not good, I can only use translation software. Sorry.
-
Since the Live Update I cannot fly any FSDT airport (e.g., KJFKv2-KLAXv2) using FSX or P3Dv4.5 (with HF1).
-
Already discussed and asnwered here:
http://www.fsdreamteam.com/forum/index.php/topic,21159.msg144234.html#msg144234
There's already a fix online on Live Update now, for OUR airports but, if you have some airport customizations made with the previous version, you must move those files away to prevent the error, UNTIL we'll come with a proper FSX.
-
Already discussed and asnwered here:
http://www.fsdreamteam.com/forum/index.php/topic,21159.msg144234.html#msg144234
There's already a fix online on Live Update now, for OUR airports but, if you have some airport customizations made with the previous version, you must move those files away to prevent the error, UNTIL we'll come with a proper FSX.
I just did Live update again.
KJFKv2 failed.
-
You haven't provided the error log.
-
Fresh error log:
-
Remove your own customization file from JFK from %APPDATA%\Virtuali\GSX, because if you customized our airport, your customization will take precedence over our fixed one, which is in the fsdreamteam\KFJK\scenery fodlder.
-
Remove your own customization file from JFK from %APPDATA%\Virtuali\GSX, because if you customized our airport, your customization will take precedence over our fixed one, which is in the fsdreamteam\KFJK\scenery fodlder.
I do not customize anything in FSDT airports / GSX.
I just install the FSDT airports / GSX and go fly.
I only have GSX for the SODE Jetways because the GSX basic version (demo or whatever the basic is) is required.
All was ok before the Live Update.
-
Your error log shows that either:
1) you have a customization file for JFK, which you must remove
OR
2) you haven't run the Live Update
Those are the only two possible option, since the JFK customization file which is online now, doesn't call that object anymore, so it cannot show that error in your log.
-
Your error log shows that either:
1) you have a customization file for JFK, which you must remove
OR
2) you haven't run the Live Update
Those are the only two possible option, since the JFK customization file which is online now, doesn't call that object anymore, so it cannot show that error in your log.
There were two ini files in that GSX folder you mentioned from April 2019
One was from KJFK and one from KORD.
I removed them.
Rebooted PC.
Ran Live Update. It completed ok.
Start P3D.
Went to KLAXv2 .
The airport loads then about 30 seconds later I get the COuatl error.
Same problem as far as I can tell.
-
Again, your error log shows that either:
1) you have a customization file for KLAX, which you must remove
OR
2) you haven't run the Live Update
Those are the only two possible option, since the KLAX customization file which is online now, doesn't call that object anymore, so it cannot show that error in your log.
-
Again, your error log shows that either:
1) you have a customization file for KLAX, which you must remove
OR
2) you haven't run the Live Update
Those are the only two possible option, since the KLAX customization file which is online now, doesn't call that object anymore, so it cannot show that error in your log.
The FSDT was off line for a while.
I will re-run the Live Update again now.
Note:
The only thing in the GSX folder is a Texture folder which is empty.
-
The FSDT was off line for a while.
Millions of websites were offline in the past half hour, because of a Cloudflare outage:
https://metro.co.uk/2019/07/02/cloudflare-outage-means-websites-including-detector-10103471/
It's possible you were still getting the old files, because of this problem, since we run over Clouflare too, just like millions of other websites, which went all down at the same time.
-
The FSDT was off line for a while.
Millions of websites were offline in the past half hour, because of a Cloudflare outage:
https://metro.co.uk/2019/07/02/cloudflare-outage-means-websites-including-detector-10103471/
It's possible you were still getting the old files, because of this problem, since we run over Clouflare too, just like millions of other websites, which went all down at the same time.
Well, I had no idea about that but while FSDT was not available all others were.
Anyway,
I ran the Live Update again , got a complete message (screenshot).
Tested KJFK again and it loads (screenshot ) without a complete Jetway? then crashes .
Where is this custom file that I need to delete?
-
Where is this custom file that I need to delete?
As I've said in one of the first of my replies, Remove your own customization file for JFK from %APPDATA%\Virtuali\GSX
-
Where is this custom file that I need to delete?
As I've said in one of the first of my replies, Remove your own customization file for JFK from %APPDATA%\Virtuali\GSX
I just took a screenshot of my GSX folder contents:
-
I just took a screenshot of my GSX folder contents:
Could you please post the .INI file for JFK in the Addon Manager\FSdreamteam\KJFK\scenery folder ?
ZIP it and Attach it to a message.
-
I just took a screenshot of my GSX folder contents:
Could you please post the .INI file for JFK in the Addon Manager\FSdreamteam\KJFK\scenery folder ?
ZIP it and Attach it to a message.
What is the full path an I will look for it?
-
What is the full path an I will look for it?
The path you chose to install GSX into
-
What is the full path an I will look for it?
The path you chose to install GSX into
This is what I see:
-
This is what I see:
And as I've said, the .INI for JFK will be here:
Addon Manager\FSdreamteam\KJFK\scenery
So, it's UP from the GSX install folder.
-
Is this it?
-
Yes. However, you keep sending screenshots, instead of posting the actual file, ZIPPED, as I asked. So I cannot check the whole file, to be sure it's the last version.
-
Yes. However, you keep sending screenshots, instead of posting the actual file, ZIPPED, as I asked. So I cannot check the whole file, to be sure it's the last version.
I did send the file (not zipped) , renamed as a txt file which you can click on and open it right now.
-
The file is correct, so it's not possible you are still getting the same error as in your previous log. Are you sure you are still getting the *same* error ?
-
The file is correct, so it's not possible you are still getting the same error as in your previous log. Are you sure you are still getting the *same* error ?
Just did another test of KJFKv2 (error txt file also).
-
Just did another test of KJFKv2 (error txt file also).
I'm sorry, but that error simply cannot happen now with the file you have. Are you SURE you ran the Live Update ?
-
Just did another test of KJFKv2 (error txt file also).
I'm sorry, but that error simply cannot happen now with the file you have. Are you SURE you ran the Live Update ?
I previously showed you a screenshot of the completed live update.
Got a screenshot of a test flight into KJFK 6-18-19 before the current Live update all was ok>
-
I previously showed you a screenshot of the completed live update.
As I've said, it's possible that happened during or before the Cloudflare outage, and you might have possible got outdated files because of this. We don't know what really happened, so it's possible they might have lost some of the updates we sent.
Could you please try again now ?
-
I previously showed you a screenshot of the completed live update.
As I've said, it's possible that happened during or before the Cloudflare outage, and you might have possible got outdated files because of this. We don't know what really happened, so it's possible they might have lost some of the updates we sent.
Could you please try again now ?
Sure:
-
I'm sorry, but it's simply not possible you would see that error. The error message is very clear: the program is trying to load this object from your JFK .INI file
FSDT_SODE_JW_JBT_1_4_LOGO_HSBC
Do you see this name ANYWHERE in the .INI file for JFK you sent before ?
-
Just did a fresh installation and the problem still exist with "Couatl Scripting Engine has encountered an unrecoverable error...." Also the jetways are seen my FSDT KJFK and KFLL scenery but no terminal buildings. I also tried to revert to the previous version (v2.5.0.0) but during installation it updates to your updated version (v2.6.0.0). Please note I do not have any customize GSX .ini files for those sceneries.
-
Just did a fresh installation and the problem still exist with "Couatl Scripting Engine has encountered an unrecoverable error...." Also the jetways are seen my FSDT KJFK and KFLL scenery but no terminal buildings. I also tried to revert to the previous version (v2.5.0.0) but during installation it updates to your updated version (v2.6.0.0). Please note I do not have any customize GSX .ini files for those sceneries.
I can only repeat and confirm the problem cannot possibly happen, unless you have another .INI file in use.
I'll repeat it again: the error message is very clear: the program is trying to load this object from your JFK .INI file
FSDT_SODE_JW_JBT_1_4_LOGO_HSBC
Do you see this name ANYWHERE in the .INI file for JFK you sent before ?
The only possible reason I can think of, is that you sent an .INI file taken from your Addon Manager folder, but GSX is not installed *there* and is not running from *there*
And not only that. We FIXED this problem so, regardless of which .INI file you use, the error won't appear anymore. The fix is already online on the Live Update so again, it just cannot happen with either .INI.
-
Couatl constantly gives unrecoverable error in P3Dv4.5 after restartin it, which is annoying. If one stops couatl the terminals and jetways disappear. I have searched for the *.ini files for KJFK and KFLL which there is none in the C:\.....\AppData\Roaming\Virtuali\GSX folder. I would like to revert to the previous version but your installer automatically update during installation. If you find the location of the other .ini file as you indicated, then otherwise your software needs looking at. It also affects all airports that uses Jetways and GSX services.
-
As explained in several other threads:
- This problem with the jetway logo in existing .INI files causing an error at start ONLY affected FSX or P3D1/2/3. Or P3D4, but ONLY if the "Disable RTT" option was *checked* (NOT default) in the Addon Manager.
- The problem has already fixed in the current Live Udpate so, regardless of the sim used or the INI file used, it won't happen anymore
-
Still no luck although doing recent updates twice. The recent update does not work on my system and no matter what FSDT or payware airport I load up in P3Dv4.5, I am constantly getting the Couatl Scripting Errors. I have uninstall the program until there is a complete fix.
-
Hoping for a quick Fix :-\
-
Still no luck although doing recent updates twice. The recent update does not work on my system and no matter what FSDT or payware airport I load up in P3Dv4.5 cause I am constantly getting the Couatl Scripting Errors. I have uninstall the program until there is a complete fix.
Then you should post the content of those error, because since the fix is already made, there are only two possibilities:
1) You haven't got the update for some reason
OR
2) You are getting a different error that doesn't have anything to do that previous problem.
-
I'm sorry, but it's simply not possible you would see that error. The error message is very clear: the program is trying to load this object from your JFK .INI file
FSDT_SODE_JW_JBT_1_4_LOGO_HSBC
Do you see this name ANYWHERE in the .INI file for JFK you sent before ?
No, it is not in the error log file.
I searched my system for anything with JBT_1_4 in it and found references to some logos and mdl (screenshot).
I did a test.
I disabled GSX and P3Dv4.5HF1 starts ok (no errors) at KJFK but with HSBC Jetway incomplete (screenshot).
-
No, it is not in the error log file.
Surely it must be in your error log, at least the last one you posted. Are you still getting THAT error ?
If yes, as I've said multiple times, it simply cannot happen with either the current update, or even before the current update, but with the updated KFJK .INI we posted before fixing it completely (regardless of the ini)
My question was: since the error log you posted show the program couldn't load an object named FSDT_SODE_JW_JBT_1_4_LOGO_HSBC, the only possible place where this object should be called from is either:
- A customization .INI file for JFK you made/download under the %APPDATA%\Virtuali\GSX, but you said you have none
OR
- The customization .INI file we supply with JFK in the Fsdreamteam\KJFK\scenery folder and, since I asked you to post this file, to be sure you got the update, I asked you to check into THAT file if the FSDT_SODE_JW_JBT_1_4_LOGO_HSBC line is anywhere in the file.
If it's not in the file, how could you possibly have an error of a missing object, if there's nothing that calls that object ?
But that's besides the point, since with the latest update, the error won't appear in any case. So, again, either you haven't update the program, or you are seeing a DIFFERENT error from your last report.
-
"- A customization .INI file for JFK you made/download under the %APPDATA%\Virtuali\GSX, but you said you have none"
Correct, only a texture folder there with nothing in it.
I zipped the ini file from here on my PC:
C:\Program Files (x86)\Addon Manager\Fsdreamteam\KLAX_V2\scenery
Should I uninstall / Reinstall GSX (demo version)?
-
You don't seem to understand: with the current version of the program, you are not supposed to see any error, regardless of the .INI used. That was only relevant before we fixed it entirely. So, again, either you don't have the latest update, or you are getting a different error now.
-
You don't seem to understand: with the current version of the program, you are not supposed to see any error, regardless of the .INI used. That was only relevant before we fixed it entirely. So, again, either you don't have the latest update, or you are getting a different error now.
Both KJFK and KLAX are not working with GSX enabled.
The only thing I know to do is to run YOUR Live Update and it runs and says Completed (no problem indicated).
So, how do I uninstall or delete what I currently have to start over?
-
Both KJFK and KLAX are not working with GSX enabled.
Both KJFK and KLAX works normally with the current update. Nobody else is not reporting this problem anymore.
The only thing I know to do is to run YOUR Live Update and it runs and says Completed (no problem indicated).
Then you are updated, unless there might be some issues on your local Cloudflare server, possibly caused by the yesterday outage, which brought down million of sites.
So, how do I uninstall or delete what I currently have to start over?
GSX is uninstalled/reinstalled from the Windows Control Panel, like any other software. You'll have to download the latest full installer from the website, of course, so you won't be reliant on the updater.
-
I too did download the setup file from your website, but keep receiving the same Coualt Scripting Errors. Although restarting Coualt Engine, the error keeps poping up until you stop Coualt. With Coualt stopped, the buildings and jetways disappear, sometimes the entire terminals and no GSX services. I even delete the .ini file in the FSDT KJFK v2 scenery and there is no customize files in the GSX folder, but still receiving Coualt scripting errors although updated several times. Somehow the updates doesn't work for everyone. The missing Jetways as you claim is from the program during installation, because when installation is done I run P3D and select an airport. After sim loads up that's when errors occured. Again the updates works for some users.
However I have uninstalled the latest GSX version until the problem is solved for all users.
-
Have you set the "Disable RTT" option in the settings ?
That's not default, and should be un-checked in PBR. It was added a while ago only as a temporary fix for possible crash on exit (only visible in the Event Viewer and totally harmless ), which affect a very limited number of users in Windows 7, but it's shouldn't be used with PBR.
Also, it will result in all Logo textures being black, so it's really best not to use it. We are updating the program to have the option ignored when running with P3D4.4 and above.
-
"Have you set the "Disable RTT" option in the settings" It was un-checked. Never used that tweak.
-
"Have you set the "Disable RTT" option in the settings" It was un-checked. Never used that tweak.
That was the only possible reason for still seeing that error after the update that has surely fixed it, is that you had that option enabled. And we updated it again now, so it's ignored in PBR.
-
Thanks for help and possible solutions, but as for now I will not install GSX2 latest version until I hear a satisfactory review.
-
Hi guys I may be a solution for you...
Warning I am under FSX ACC SP2 and not P3D......
*So uninstall all products FSDT -> GSX, ADDON MANAGER, and AIRPORTS
*Deleted the folder: ADDON MANAGER of your disk (the folder where you installed GSX)
*Reinstalled the update PBR, reinstalled the airports (advice re-downloaded airports on the site)
*Do an update with the FSDT Live Update and normally its should be good ;)
(For virtuali: It's a shame that the best update is only for P3D we would have liked also to have new vehicles or animations under FSX ACC SP2 damage...)
Regards.
-
(For virtuali: It's a shame that the best update is only for P3D we would have liked also to have new vehicles or animations under FSX ACC SP2 damage...)
That's easy, just convince Microsoft to make a patch for their 12-years old sim, which would add all the following we require to create the new vehicles and animations, with the most important ones being:
- PBR support
- Human skeletons with 64 bones
- Render to Texture in DirectX for the variable logos, with DirectX 11 support, which our code requires.
- And while they are at it, a 64 conversion, so all this new stuff won't crash with an OOM
If you could convince Microsoft to do such patch for FSX-SP2, there are no issues from our side supporting it.
-
:D ;D :) I understand you Umberto and you are absolutely right, but without having big animations, of new designs of vehicles, or to have the trucks of WATER and LAVATORY present in the configuration of the vehicles ... where a small animation with the truck of FUEL ... (It seems to me that at the beginning of GSX the character connected the pipes to the wing with a screen on the truck to see the filling) often flying on PMDG we can not fill the plane with the truck anymore ... :)
-
You should really stop using FSX. You said you use PMDG airplanes: are you aware that PMDG stopped supporting FSX as well ?
-
:o In addition, no I was not aware ... cool for future updates ... :-\
And yes it should change the simulator but having MANY ADDON not compatible P3D it would be a shame to start from nothing ...
I will continue to fly on 1 wing :) while waiting for the new version "FSX 2020"
Good day to you
Cordially.
-
Umberto, good evening!
Is there an ETA as to when this will be fixed? Just now I ran FSDT Live update and still the same problems. I use FSX Steam and I couatl is still crashing on me. I still don't see any buildings for my FSDT or Flightbeam airports. Any eta would be great. Thanks.
The error I got at KDEN:
couatl v3.2 (build 4231)
panic log started on Wed Jul 3 21:23:15 2019
problem raised by engine or unspecified addon
{'Airport': 'KDEN', 'User Pos': (39.85807593653836, -104.67735501029003, 1657.27 m, 1.90564 m, 359.71165775161853)}
User collision geometries reloaded
-
Is there an ETA as to when this will be fixed? Just now I ran FSDT Live update and still the same problems. I use FSX Steam and I couatl is still crashing on me. I still don't see any buildings for my FSDT or Flightbeam airports. Any eta would be great. Thanks.
All the known problems with FSX has already been fixed yesterday.
I cannot possibly say from your error log if your problem is the same which we already fixed, or is a new one. To get a complete error log, you should enable Logging in the Troubleshooting section of the GSX settings, so the log will be more detailed.
-
I will check that out. Is there an updated version of 'FSDT Live Update'? Should the one I'm using suffice? Where would I go to find 'FSDT Live Update'?
-
The Live Update has an icon on your Desktop, just start it, and will update both *itself* and the program.
-
I just did live update. Couatl seems to work as I can bring up GSX however, none of my Flightbeam airports show any buildings. FSDT airports seen to work fine. What could be the cause of this?
BTW thanks for the responses to this post.
-
none of my Flightbeam airports show any buildings.
You must update all Flightbeam sceneries to their latest version, because they have a new installer which don't use our Addon Manager anymore.
-
Will do. Thanks Umberto.
-
Hello Umberto!
I wanted to have information on the functioning of "Adon Manager "...
What is the operation of the section (ANTIPOPUP)??
Thank.
-
Hi Umberto.......So a New update mess again...Well will you help me also or run like last time BTW I fixed it myself .....So what do we do now huh. Why dont you leave it alone for people to enjoy. We spend more time fixing than flying.
-
Hi Umberto.......So a New update mess again...Well will you help me also or run like last time BTW I fixed it myself .....So what do we do now huh. Why dont you leave it alone for people to enjoy. We spend more time fixing than flying.
I really don't know what you are trying to say here. What do you mean with "new" update ? New from when ? From the last version in December ?
If yes, ALL reported problems with the update has been fixed and, 90% of them were ( as usual ) missing feature in the update to defend itself from mistakes in users configurations,
The most common one was wrong registry keys from non installed simulators, usually created by Migration Tools or hand made to force-install non compliant add-ons into P3D, or fake FSX installs to achieve the same goal, sometimes made more or less properly (with a real FSX.EXE ), but in a couple of cases, with an FSX.EXE of 0 length, which crashed the updater.
Other supposedly "update problems", were again caused by non-compatible Shader mods, or in some cases simply faulty ones, or not made for PBR.
Other supposedly "update problems", were caused by users having updated P3D from a non-PBR version to a PBR version using the Client only. This is known to cause problems, and all other developers that do PBR stuff suggests using the Full installer, otherwise textures will look wrong, or black.
These problems couldn't be found by any of our testers (there are about 30 testers, and they are all forum users), because apparently their installations were clean, without tricks to install ancient products or usage of dangerous Migration Tools, which can be basically compared to a virus.
The ONLY TWO bugs which really were OUR fault were:
- A bug with FSX which resulted in an error loading jetway logo. I ALREADY apologized for not having texted enough under FSX.
- A bug in the Updater which didn't work if the users installed ALL its FSDT stuff in a custom folder with "GSX" in the name.
Both of these have been both obviously fixed already, as soon they were found so, unless you found NEW bugs, which you are supposed to REPORT, your comment is now redundant.
Enjoy your FREE UPDATE: we could have made a whole new payware product, like a small airport or another GSX paid expansion, in the time it took to do this free update.
-
Hello Umberto!
You had forgotten me ?? :)
-
Well Umberto ......Everything worked fine until this update and now FSX-SE crashes and does not work
couatl v3.2 (build 4231)
panic log started on Sun Jul 7 11:59:28 2019
problem raised by engine or unspecified addon
{'Airport': 'YBTL', 'User Pos': (-19.256495261658085, 146.76978633159945, 7.88208 m, 2.39608 m, 100.64138097161457)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'YBTL', 'User Pos': (-19.256495261658085, 146.76978633159945, 7.88208 m, 2.39608 m, 100.64138097161457)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'YBTL', 'User Pos': (-19.256495261658085, 146.76978633159945, 7.88208 m, 2.39608 m, 100.64138097161457)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'YBTL', 'User Pos': (-19.256495261658085, 146.76978633159945, 7.88208 m, 2.39608 m, 100.64138097161457)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_TB3_STANDARD_RP_39_19_static'
{'Airport': 'YBTL', 'User Pos': (-19.256495261658085, 146.76978633159945, 7.88208 m, 2.39608 m, 100.64138097161457)}
reset FSDT_GSX_DEBOARDING_CARGO_PERCENT to 0
Any ideas as this comes up now since UPDATE
-
How can my comment be REDUNDANT why cant you say I DONT KNOW.......EVERYTHING WORKED . Then UPDATE.......NOT WORKING. So is this your way of saying cannot help or do not know. Too busy counting your money huh?
Why dont you roll back the changes prior to the update when FSX-SE worked and tell everyone the new addons dont work in FSX-SE instead of a long drawn out answer that meant nothing. When you make something it has to work especially when you UPDATE it. So perhaps you can swallow your pride and roll it back to when it did work send it out as a fix and we can get busy flying.People will understand that only certain things will work in FSX-SE. Telling us you could have spent time making money proves nothing...YOU made a change it affected a lot of people who were happy flying.......then fixing again....not flying.
Also did you explain that those using Flyinside may have issues with VR and to contact Flyinside. Perhaps working with them to get things going smoothly so all can enjoy flying and using your program.
-
The problem doesn't have anything to do with the update. It's caused by the lines of the objects required by GSX not being added in the FSX.CFG. Of course, the GSX Update DOES normally add the required lines, under normal conditions.
If it hasn't on your system, it's usually caused by a problem of your FSX.CFG being the wrong one, usually because of a problem in your registry keys so, the GSX Update is tricked into updating the wrong FSX.CFG file, because your registry keys are wrong.
Do you have FSX:SE ? If yes, do you have the regular FSX installed too ? If no, do you have this folder ?
%appdata%\Microsoft\FSX-SE\FSX_SE.CFG
If yes, it means your registry keys ARE wrong, because that file is not supposed to exists on a clean FSX:SE installation with no regular FSX installed at the same time. This is usually caused by having installed FSX:SE when the original FSX was still installed, and having removed FSX without reinstalling FSX:SE
However, the current version of the FSDT Live Update has been updated to deal with this mistake in your configuration so, it will update both FSX.CFG files, even if they shouldn't be there.
Another possible reason for the lines not being added to your FSX.CFG file, is that it was ALREADY corrupted, so the GSX update didn't touched it.
Another possible reason for this problem, is that you used a 3rd party utility to restore the FSX.CFG to a previous state, one without the lines containing the paths to find the GSX Simobjects, or you reset the FSX.CFG manually.
If the FSX.CFG is reset for any reason, you must run the FSDT Live Update again, so the missing Simobject lines will be placed back.
-
Thanks Umberto I am grateful for your trying to help .
So Here is what is happening now ... If I run FSX-SE on the Screen EVERYTHING WORKS NOW.
If I go through Flyinside I get an error. and NOT WORKING........Last week all worked fine.
OKOK so moving on I have deleted FSX-SE Flyinside CFG and FSX Flyinside CFG and generated new ones ...Not Working
I fixed this problem before by installing your update then Uninstalling Flyinside then Reinstalling Flyinside....Now that wont work.
If it is in the registry as a FSX original problem how do I get rid of this , I do not want to Re Install Windows 10.
Also Yes I apologise and THANK YOU for your efforts in Advance........you replied and helping me. I just want to fly and have this lovely program working.
I have P3Dv4 all works fine in VR as well using Flyinside.
My folder
%appdata%\Local\Microsoft\FSX
-
If I go through Flyinside I get an error. and NOT WORKING........Last week all worked fine.
That's a KNOWN problem of Flyinside!
I don't recall exactly how it works, but this has been discussed so many times on the forum and it's caused by the fact FlyInside uses its own configuration, so you must be sure even THAT one contains the Simobjectpaths required by GSX. The same is valid for other products that needs new SimobjectPaths lines, like AI products, etc.
The issue is, you haven't replied to any of my question, for example this one:
Do you have FSX:SE ? If yes, do you have the regular FSX installed too ? If no, do you have this folder ?
%appdata%\Microsoft\FSX-SE\FSX_SE.CFG
Yes, you said you have %appdata%\Local\Microsoft\FSX ( which is ALSO wrong, if you typed it correctly, it's supposed to be %appdata%\Microsoft\FSX ), but do you ALSO have the %appdata%\Microsoft\FSX-SE too ?
This would indicate if you have a problem in the registry too, which is possibly confusing FlyInside too.
-
Hi ......Yes I am running FSX-SE
No I dont have %appdata%\Microsoft\FSX-SE\FSX_SE.CFG ....Mine is User ...me %appdata%\Local\Microsoft\FSX and again User ...me %appdata%\Roamingl\Microsoft\FSX
If I go %appdata%Local,Low ,Roaming these are the only folders no Microsoft
At some stage a long time ago I had FSX on this current Windows 10 But totally Unistalled it step by step and deleted registry of FSX entries.
-
Ok, so your only problem is caused by Flyinside, which is using a configuration that is missing the SimobjectsPaths added by our installer so, you must be sure even the configuration used by Flyinside contains them.