Max2Babylon: can't export bitmap in a Physical Material

[echadwick-artist]

Max2Babylon-1.3.23
3ds Max 2018.4

This seems like something new. Maybe a bad commit?

1. Create a Plane primitive.
2. Create a Physical Material, assign it to the Plane.
3. Add a bitmap to the material.
4. Export.
   Result attached. If I remove the bitmap, it exports without errors. Tried it with different bitmaps, JPG, PNG, same error.

Max2Babylon export error.zip

[echadwick-artist]

It's also spawning a warning about KHR_texture_transform, even though the Bitmap uses default settings. There seem to be no Offset/Tile/Angle settings that should call for the extension.

[echadwick-artist]

Tested with Max2Babylon-1.3.21... the red error is not spawned, but the KHR_texture_transform warning is still being spawned.

[kcoley]

@echadwick-wayfair I'll take a look

[kcoley]

@echadwick-wayfair I was able to get the bmp to export from your provided scene by re-assigning the material to the mesh, though I'm not sure why that fixed it. This was done with version 1.3.23. Can you try that on your end?

I also tried to follow the creation steps you outlined using your source bmp with a new scene, but I was not able to repro the issue that way.

As for the KHR_texture_transform warning, I have been trying to fix the warning (the conditional check is not passing for some reason), though it should not cause an issue with the scene.

[echadwick-artist]

I have a theory that perhaps I didn't Unblock one of the DLLs properly, after downloading them. Our Windows security settings are such that DLLs have to be manually unblocked in order to load them.

[echadwick-artist]

Nope that wasn't it. Installed & Unblocked 1.3.24, but it still occurs. Won't write a GLB. Have to revert back to .21 for now to get a project done.

[echadwick-artist]

Actually, 1.3.22 works.

[kcoley]

@echadwick-wayfair it seems to be an issue with exporting to glb, when converting textures to binary. I am looking into a fix.

[kcoley]

@echadwick-wayfair I found the issue and merged a fix. It was how I was handling uri paths . Feel free to try on version 1.3.25.

[echadwick-artist]

It works now, thanks for the fix!