- This topic has 4 replies, 2 voices, and was last updated 1 hour, 53 minutes ago by
.
-
A plugin user reported an issue that couldn’t be resolved, so I exported nearly identical scenes from both 3ds Max and Blender (a default scene with a ring model). I used the same puzzle setup, imported the same diamond .glb model, and the same v3d.js file. However, the Blender version showed abnormal behavior, despite no errors being reported. I would like to ask the official team: what is the root cause of the differences between the software versions?@Yuri Kovelenov @Alexander Kovelenov
demo-Max
demo-blenderAttachments:
As behavior differences between Blender/Max, for now I can only point to the flipped normals, e.g. material.normalScale.y is inverted for MeshStandardMaterials imported from 3ds Max assets.
@Alexander At first, I also thought the objects loaded in the two versions might be different, so I appended the same large diamond.glbmodel in both scenes — this model comes from the three-mesh-bvh library itself. So it seems we can rule out issues caused by the 3D software exports.
The diamond material is based on Demo:// sceneURL: params.load || 'MinDemo_DiamondMat.gltf',//blender export sceneURL: params.load || 'MinDemo_DiamondMat_max.gltf',The only difference between the two pages is the glTF file. After I swapped the files, the diamond material rendered correctly in both cases.
So where exactly is the problem coming from? Could it be related to differences in coordinate systems between the two? But upon inspection, both have
coordSystem: "Z_UP_RIGHT". Perhaps there’s some other property causing the issue?3ds Max uses a left-handed coordinate system by default,
while Blender uses a right-handed coordinate system, which is consistent with glTF.
This means that glTF files exported from 3ds Max may require additional rotation (typically around the Z or Y axis) to appear correctly aligned in glTF-compatible environments.
- You must be logged in to reply to this topic.