• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS20 How to export an aircraft that depends on fallback textures before building an aircraft package?

FrancisJohannes

FrancisJohannes

Messages
278
Country
us-newyork
Hi guys,
How can I export an aircraft to my package folder where most textures need to be called using the texture.cfg before building an aircraft package? How is the workflow in blender to the sdk?
I'm confused on how to do this.

Please let me know. Thank you. I'm very confused on how to rely on the asobo texture folders for callbacks when working with an aircraft.
 
I'm a bit confused here. Why are you using and relying on Asobo texture folders?

Are you making your own aircraft or a repaint?

If it's your own aircraft and you really need to use an Asobo texture (for say, one of the glass cockpit gauges) then I'd recommend copying that texture into your package rather than rely on fallback.

If you don't want to do that then the Blender exporter is going to copy the textures from your projects texture folder into the source package folder. And that's all it does. Anything else you will have to manually setup and that means creating the texture.x folders, any texture.cfg files and copying your textures into the correct folders.

If the exporting process duplicates a texture that you are planning to fallback to the asobo texture folders then you will need to manually remove that texture from the source package's texture folder (you may like to do this at the very end of your project rather than every time you compile the package).
 
Anthony31 said:
I'm a bit confused here. Why are you using and relying on Asobo texture folders?

Are you making your own aircraft or a repaint?

If it's your own aircraft and you really need to use an Asobo texture (for say, one of the glass cockpit gauges) then I'd recommend copying that texture into your package rather than rely on fallback.

If you don't want to do that then the Blender exporter is going to copy the textures from your projects texture folder into the source package folder. And that's all it does. Anything else you will have to manually setup and that means creating the texture.x folders, any texture.cfg files and copying your textures into the correct folders.

If the exporting process duplicates a texture that you are planning to fallback to the asobo texture folders then you will need to manually remove that texture from the source package's texture folder (you may like to do this at the very end of your project rather than every time you compile the package).
Click to expand...
So I thank you for your reply. I figure out that the names of the textures that were exported were off from the original Asobo types.
I'm working with a deluxe premium product, this is why.
 
You must log in or register to reply here.
Back
Top