Author Topic: TechnoBrain Osaka SMBC error  (Read 1959 times)

Crazy_Milojko

  • Newbie
  • *
  • Posts: 3
TechnoBrain Osaka SMBC error
« on: February 20, 2020, 09:31:27 am »
I'm currently getting CREATE_OBJECT_FAILED error for unknown reason on the Technobrain Osaka scenery, and i'm using FSX,



Here is the log:

couatl v3.2 (build 4061)
panic log started on Thu Feb 20 09:26:13 2020

problem raised by engine or unspecified addon
{'Airport': 'RJOO', 'User Pos': (34.79121878370015, 135.43908149327063, 15.9385 m, 4.05152 m, 68.24198306273608)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'SMBC'
{'Airport': 'RJOO', 'User Pos': (34.79121878370015, 135.43908149327063, 15.9385 m, 4.05152 m, 68.24198306273608)}
Added GSX customized bgl jetway for Gate 9
Added GSX customized bgl jetway for Gate 10
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'SMBC'
{'Airport': 'RJOO', 'User Pos': (34.79121878370015, 135.43908149327063, 15.9385 m, 4.05152 m, 68.24198306273608)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'SMBC'
{'Airport': 'RJOO', 'User Pos': (34.79121878370015, 135.43908149327063, 15.9385 m, 4.05152 m, 68.24198306273608)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'SMBC'
{'Airport': 'RJOO', 'User Pos': (34.79121878370015, 135.43908149327063, 15.9385 m, 4.05152 m, 68.24198306273608)}
Added GSX customized bgl jetway for Gate 18
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'SMBC'
{'Airport': 'RJOO', 'User Pos': (34.79121878370015, 135.43908149327063, 15.9385 m, 4.05152 m, 68.24198306273608)}
Added GSX customized bgl jetway for Gate 5
Added GSX customized bgl jetway for Gate 6
Added GSX customized bgl jetway for Gate 14
Added GSX customized bgl jetway for Gate 17
Added GSX customized bgl jetway for Gate 19
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'SMBC'
{'Airport': 'RJOO', 'User Pos': (34.79121878370015, 135.43908149327063, 15.9385 m, 4.05152 m, 68.24198306273608)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'SMBC'
{'Airport': 'RJOO', 'User Pos': (34.79121878370015, 135.43908149327063, 15.9385 m, 4.05152 m, 68.24198306273608)}
Error: exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'SMFL'
{'Airport': 'RJOO', 'User Pos': (34.79121878370015, 135.43908149327063, 15.9385 m, 4.05152 m, 68.24198306273608)}



I also think it may affect Chitose too
« Last Edit: February 20, 2020, 09:50:42 am by Crazy_Milojko »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51235
    • VIRTUALI Sagl
Re: TechnoBrain Osaka SMBC error
« Reply #1 on: February 21, 2020, 07:02:01 am »
There must be some kind of problem in the GSX customization you are using ( which might be something you made, downloaded, or supplied with the scenery ), because it seems to download objects that are not part of GSX, likely custom logos for jetways.

Check this folder for any .INI file related to RJOO airport:

%APPDATA%\Virtuali\GSX

But there might also be a similar .INI file in the \scenery own directory, together with its .BGL files. Removing those files will surely fix the error, but you'll lose the customization so, if you haven't made it yourself, maybe it might be useful to inquire with the author, perhaps it requires extra files.

Crazy_Milojko

  • Newbie
  • *
  • Posts: 3
Re: TechnoBrain Osaka SMBC error
« Reply #2 on: February 21, 2020, 02:04:47 pm »
I do have one, it's called rjoo-envrko, and also i have texture folder in GSX folder, is that okay?
And no, i don't have any INI file in the Scenery directory, but i do have files that i renamed their extensions to OFF file
« Last Edit: February 21, 2020, 02:11:29 pm by Crazy_Milojko »

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51235
    • VIRTUALI Sagl
Re: TechnoBrain Osaka SMBC error
« Reply #3 on: February 22, 2020, 11:43:11 am »
I do have one, it's called rjoo-envrko, and also i have texture folder in GSX folder, is that okay?

As I've said, that's the one causing the problem, so you should remove it, and see if it goes away.