• 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 Blender2MSFS KHR Texture transform problem

S

superspud

Messages
439
Country
unitedkingdom
I can't get the MSFS SDK to digest a model due to the console saying - required extension not supported: KHR_texture_transform

The one mention of it on here relates to the MSFS glass, not that I really got it. I've exported tons of models with transparent glass before and not once has it ever given this error. Nothing was changed in the export settings and I can't see anything different in any of the models.

Even if I delete everything with transparent glass I get the same message.

What's gone wrong and what can I do about it?
 
Last edited:
is KHR_texture_transform a image texture? then maybe the extension .jpg or .png is missing? 🤔
 
This was happening on 4 different models by 4 different people so it would be very unlikely that all of them had an extension problem.

In the end I sent them back to Sketchup, replaced the glass with Sketchup standard glass, and then re exported them to Blender and then export from there. One's still broken but the others were accepted.

The really odd thing is that it gave the same error on one without any glass. I'm not sure what happened there.
 
Just had it again. This time around it was modifying a texture's scale in Blender that did it. Erasing that made the SDK digest the model.
 
This occurred to me when adding detail UV scale to glass (applies to fingerprint detail, icing map, ....)

You can still use the UV detail scale:
- Go the "shading" tab
- disconnect "vector" of the detail_albedo, metallic and normal at the bottom from the purple "detail_UV_scale" block
- reconnect "vector" to the red "UV" block directly.

Detail UV scale shall work as expected in-sim. You will not see detail scale in blender, so you may need to give it a few iterations by looking at the result in-sim (not that you can see the glass detail very easily in Blender anyway)
 
I've got this once again and this time it's going to be a grind to do any workarounds.

Again it's rescaling the texture that does it. I can't use the texture coordinate and mapping nodes in Blender, or rather the GLTF whatever can't use it. The console will give the khr texture transform error.

Since this seems to be a pretty fundamental thing and 100% vanilla I don't get why this happens every time. Is there another way to scale texture?
 

Attachments

  • image_2021-05-01_204553.png
    image_2021-05-01_204553.png
    124.8 KB · Views: 455
Last edited:
Got the same again. I've been avoiding any texture scaling in Blender since but this time I well and truly can't work around it. This just a normal texture with the scaling applied the same way above. And I had to throw the model draft away that time and start again.

Can anyone who is regularly exporting from Blender tell me how they are managing to scale their textures without this error when compiling with the SDK. There must be thousands of people who are doing it but this error seems to be barely mentioned by anyone else. What am I missing?
 
Last edited:
When I was reading about texture scaling, I recall there was some discussion about the fastidiousness of the sim in regards to the node tree (at least with Blender2MSFS). The alterative given was is to simply scale the UVs in the UV editor tab. Not very precise, but at least is allows scaling.
 
dale in cda said:
When I was reading about texture scaling, I recall there was some discussion about the fastidiousness of the sim in regards to the node tree (at least with Blender2MSFS). The alterative given was is to simply scale the UVs in the UV editor tab. Not very precise, but at least is allows scaling.
Click to expand...

When it comes to Blender I know what I know and that's it, and it's not very much.

This is a normal texture and I can't see any way to access it in the UV editor, only the diffuse. And I can't see any scaling in the UV editor anyway.

I think I'll just have to give up on this forever but I find it very strange that the sim, or addon, can't cope with one of the most unbelievably basic things in a 3d model.
 
Last edited:
It is not working with the mapping node. Delet that then go to the uv editor. Select all scale by 150 there. Then you get the same effect.
 
Mikea.at said:
It is not working with the mapping node. Delet that then go to the uv editor. Select all scale by 150 there. Then you get the same effect.
Click to expand...

It took me about a year how to figure out nodes so I think I might be able to do that by 2025. It's always good to have a long term project I suppose.
 
No that is as easy as i wrote. Select the object. Go to the uv editor, switch to edit mode, select all meshparts with the same material. Press "s" followed by 150 "enter". That is all :D
 
Thanks for this. Something happened. But I don't know what and it's not what I wanted to do.

I will return to this for Microsoft Flight Simulator 2030. I can't take any more Blender.
 
Last edited:
How do you identify it when you are working on a big model with many meshes though?

I've got over 1467 textures and I cant identify 1by1 because that would take ages
 
You must log in or register to reply here.
Back
Top