An odd problem when importing objects in FBX format... :: RPG Developer Bakin General Discussions

Store Page

RPG Developer Bakin

All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

RPG Developer Bakin > General Discussions > Topic Details

UK Infinity has RPG Developer Bakin

2 Mar @ 7:14am

An odd problem when importing objects in FBX format...

So, I have been creating a few scenery objects to throw into my world and seem to have an issue whereby I can import a model, but all subsequent imported models will adopt the texture from that model. This I have tracked down to the fact that the modeler I am using packs the textures into the FBX using the format 'Texture_x' where 'x' is a numbered texture.

I should be able to import multiple models without this being an issue, right? With each loading their own textures (packed into the FBX), or am I being stupid and missing something obvious??

Thanks for your insights, cuz this is driving me mental!

< >

Showing 1-1 of 1 comments

UK Infinity has RPG Developer Bakin

2 Mar @ 7:49am

Further experimentation shows that it doesn't seem to matter what I name the textures in Blender, when I import into Bakin it creates a new folder (presumably as part of the import process) where it places the textures extracted from the FBX.. it ALWAYS calls them 'texture_0.png' which causes a conflict.

Only way around it I can see is the rather long-winded method of importing the model, going into the newly created folder and renaming the 'texture_0.png' to something unique such as the base model name, then going into Resources and changing the texture to your renamed texture file in the created .FBM folder.

Fine for the odd object... but when you are importing loads of them, it would be FAR more convenient for Bakins FBX importer to keep track of what texture names are already in use and instead of assigning the first texture to every object, name them incrementally so that textures do not clash.

How does one go about raising this as a bug?