-
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.
Exporting to Collada
- Thread starter PMS707
- Start date
- Messages
- 56
- Country
Hey -- I just get a dropdown with image.0xx for each of the 25 or so missing textures... So I'm not sure how to get the desired textures into Blender. They are in a TEXTURE folder adjacent to the .fbx file. When I click on the folder icon just to the right and select/load the correct image, nothing happens...
For three of the associated textures, there is a thumbnail that corresponds to the correct texture image, but still only an image.0xx number, and not a filename. These are the textures that seem to have randomly rendered onto the model at import.
Attachments
- Messages
- 56
- Country
Here's what I'm talking about -- the selected area correctly identifies the proper texture file and renders it, but it's still designated image.009...
Attachments
- Messages
- 56
- Country
That's a good question. There are about 25 textures assigned to this model. I am able to see where each is rendered only by highlighting them in MCX. I cannot figure out a way to see how each texture was mapped on a UV map. When I exported to .fbx in MCX, the exported .fbx stayed in the same folder as the original .mdl and correctly pulls the textures from the adjacent TEXTURE folder when viewed in MCX, the same way as any .mdl file would be rendered by MCX.
My understanding about using the Autodesk converter was that it would neatly place the model and textures together into a folder that Blender easily recognizes on import of the .fbx model. When I initially ran the Autodesk converter to update the original conversion, it did this. It left me with a folder containing model and textures. Perhaps this is the trick?
- Messages
- 34,342
- Country
Hi,
Did you try to put the fbx file and textures in the same folder? MCX uses the FS search logic to look for textures, but Blender will not. In the FBX file there is only a filename, no path, just like in the MDL files.
Did you try to put the fbx file and textures in the same folder? MCX uses the FS search logic to look for textures, but Blender will not. In the FBX file there is only a filename, no path, just like in the MDL files.
- Messages
- 56
- Country
Arno -- this is exactly what I ended up having to do. Also, the textures were not being rendered by Blender as the original BMPs. I had to convert to .dds, but then flip them back over again (BMP style) in order for them to appear correctly on the model while in Blender, rather than upside down. Same in reverse once the model was exported back out, to view textures correctly in MCX!
Ultimately, .fbx kept the original UV map, and once I did all of the texture conversions/flipping and relocating, I was able to use MCX to highlight the textured areas of the original model and then assign the corresponding faces the same .dds textures in Blender (a relatively easy and straightforward task), then export again as .fbx, and use MCX to convert to .mdl. Here is the result -- SUCCESS!
I have set out what I originally intended to do, which was simply delete some blast fences from the 1962 CalCassics LHR Oceanic Terminal in order to build the terminal piers out (with Blender, eventually) and add them to the scenery to create T3 as it appeared in 1968. I will post that final model when it's done, along with the Europa Terminal converted to 1968 T2 with the pier extensions, once I use this process to remove the two outer passenger ramps to the tarmac, since that's where the pier extensions will go.
Now that I understand how this process works, I will be able to tweak many early 60s CalCassics terminals and take them into the late 60s and 1970s. Most require that some element be removed in order to make room for whatever enlargements were added later on, but these CalCassics buildings are just GOLDEN and such a fantastic foundation for this endeavor of mine.
Thanks everyone for sharing your tips and insights through this challenging assignment!
Alex
