Details
-
Task
-
Resolution: Cannot Reproduce
-
Not Evaluated
-
None
-
None
-
None
-
Linux 64bit / nvidia 970
Description
These are the issues I've found so far with the "Mesh" QML type:
1) attached cone-crash.obj fires a segfault. I can correctly open it in Blender and apparently there's nothing wrong with it
2) if the Mesh source property is set to an "external" resource and not a qrc asset, it's not rendered. I tried on deferred rendering using "assets/cone.obj". Using "qrc:/assets/cone.obj" works as expected.
Same thing on forward rendering (tried on shadowmap example)
This is quite important when loading models at runtime.
3) an .obj model with no normals is not rendered properly. By default Blender exports objs without normals.
Now this is the thing: Assimp loaders generate normals for you in case they are not provided by the mesh. I believe Qt3D should do the same for convenience. It surely slows down the mesh loading time but it covers much more cases where people download random models from the internet without knowing anything about 3D normals
4) building Qt3D with the Assimp support still doesn't load a 3DS model. Attached the good old penguin from Qt3D 1.0. No matter if the model is in qrc or not