FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Salma on September 09, 2021, 05:31:59 pm
-
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.
-
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.
-
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?
-
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.
-
I removed all the entry Jetway_logo = xxxxxxxx from the ini file, but there is still an error. What else should I modify?
-
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.
-
Can I attach the Couatl.err file?
-
I attached it
-
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.
-
Ahh okay, I attached it again
-
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
-
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
-
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?
-
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.
-
Okay, I shouldn't go to VTBS until the next update comes out
Thank you for your deep intention to solve problems!
-
I'm sorry, but I want to roll back to version 2.9.3 until the next fix comes out. Is there a way?
-
I'm sorry, but I want to roll back to version 2.9.3 until the next fix comes out. Is there a way?
You can't go back, and it doesn't make any sense because, if you have P3D V5, it's obviously way better to have at least 200+ stock liveries than NO LIVERIES, as it was before.
If your issue is only trying to use profiles made for P3D V4 that right now are causing that error, the best solution would be, until we fix them automatically, to MOVE away your P3D V4 profiles that return that error from the %APPDATA%\Virtuali\GSX, to a different folder, so you can just place them back when we'll release the fix to automatically ignore custom textures.
-
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.
In my P5D, gsx ini file does not contain such "jetway_logo", but I still get couatl crash, any advice?
-
You also VTBS problems?
-
In my P5D, gsx ini file does not contain such "jetway_logo", but I still get couatl crash, any advice?
That was just an example. The custom texture might also be one for the ground operator or the catering operator so, the line to look for would be:
handlingtexture
cateringtexture
They cannot contain any operators that are not already included in GSX. But as I've said, I don't suggest doing that because:
- It will take you too much time, if you have many .INI profiles made for P3D V4
- If will force you to downgrade your .INI profile. That might not be a problem if you don't use P3D V4 anymore but, if you do, you might want to keep it as it was.
- We ARE working on a better and more reliable solution, likely in the next days, which will automatically filter out custom textures from .INI files made for V4 when you use V5 and, if you make ANY changes to that file, it will be saved back with a *different* name and a parameter that will flag it to be "P3D5 ONLY", so P3D V4 will continue to load your original file, and the new "cleaned" one will be used only in V5.
So, while we are working on this update, I think the best solution is to MOVE AWAY all your .INI files made for V4 which give you errors due to using custom textures to a different folder, ready to be moved back in, either when you want to fly V4 again, or after we'll release the fix.
-
So, while we are working on this update, I think the best solution is to MOVE AWAY all your .INI files made for V4 which give you errors due to using custom textures to a different folder, ready to be moved back in, either when you want to fly V4 again, or after we'll release the fix.
Thanks you Umberto! Hope next update ;D