GSX 2.9.4 error after update

[Salma]

I'm using vtbs of a_a, but in the previous version 2.9.3, it was loaded normally without errors, but after updating to 2.9.4, the following errors occur.

[virtuali]

Assuming you are using P3D5, the problem is your .INI file, which must have been made for P3D V4, using custom textures, because an operator called "SCB" doesn't exists in GSX.

Before the update, this won't cause any problems, because jetway logos were completely disabled but now, since we added multi-liveries back, if an .INI file contains any logos, they MUST be one of the stock logos included with GSX, because in V5 custom textures are not supported.

We are working on an update that will check existing .INI files and will automatically ignore any logos for operators not included by GSX but, in the meantime, the only way to fix it is to edit the file and remove all lines containing

jetway_logo = xxxxxxxx

Unless they contain a name of an operator that does exists in GSX.

[Salma]

I see, As I expected, it was a problem with the logo file, but there was no problem with the 2.9.3 version, but is it normal to have such a problem after the 2.9.4 update?

[virtuali]

I see, As I expected, it was a problem with the logo file, but there was no problem with the 2.9.3 version, but is it normal to have such a problem after the 2.9.4 update?

That's precisely what I explained in my previous post, so I'll repeat it again:

Before the update, this won't cause any problems, because jetway logos were completely disabled but now, since we added multi-liveries back, if an .INI file contains any logos, they MUST be one of the stock logos included with GSX, because in V5 custom textures are not supported.

So yes, it's normal and, if you read also the 2nd part of my post, you would know we are working on a way to fix this automatically.

[Salma]

I removed all the entry Jetway_logo = xxxxxxxx from the ini file, but there is still an error. What else should I modify?

[virtuali]

I removed all the entry Jetway_logo = xxxxxxxx from the ini file, but there is still an error. What else should I modify?

You should have posted the error log too.

[Salma]

Can I attach the Couatl.err file?

[Salma]

I attached it

[virtuali]

Can I attach the Couatl.err file?

No, that's not detailed enough to be helpful. You need to enabled Logging in the Troubleshooting section of the GSX Settings, Restart and go to the airport that gives you the error, then post ( ZIPPED!!! ) the Couatl.LOG file.

Please don't post images. Post your file ZIPPED.

[Salma]

Ahh okay, I attached it again

[Salma]

I personally think

Error: acceptance CREATE_OBJECT_FAILD in call AICreateSimulatedObject parameter #1 'FSDT_SODE_JW_2_7_LOGO_SCB'

is the problem, but I don't know what this means

[virtuali]

Error: acceptance CREATE_OBJECT_FAILD in call AICreateSimulatedObject parameter #1 'FSDT_SODE_JW_2_7_LOGO_SCB'

Already discussed and answered here:

http://www.fsdreamteam.com/forum/index.php/topic,25477.msg167546.html#msg167546

[Salma]

I'm sorry. I've tried various ways, but the results are the same...

This is the link I downloaded =VTBS

https://www.flightsimaddons.net/2021/05/p3d-v4p3d-v5-bangkok-suvarnabhumi.html

Is it problem airport itself?

[virtuali]

Please read the post I linked above carefully ( my post ), it explains what you can do to fix that .INI profile, which was made for P3D V4 using custom textures, which don't work in V5.

As I already explained there, and in other post, we are working on an solution to automatically filter out these custom textures automatically, so no edit will be required but, in the meantime, you should either edit out the custom textures as explained in the above thread, or don't use that profile in P3D V5.

[Salma]

Okay, I shouldn't go to VTBS until the next update comes out

Thank you for your deep intention to solve problems!