In fact, I also meet the same bug when I used the API read_triangle_mesh in the Shapenet-v1.

And I think that maybe the .obj file has some problem.

The same issue with 02691156/de45798ef57fe2d131b4f9e586a6d334

How can we solve it? I simply removed that particular data..

It seems the error is with the texture files. If you put the .obj file in a separate folder, it loads in Open3D correctly.

If you need the textures, take a look at this answer: https://blender.stackexchange.com/questions/89010/materials-not-applied-after-importing-obj-shapenet/188192#188192 . You can convert the buggy .obj model from ShapeNet to a .glb model using https://github.com/CesiumGS/obj2gltf.

The same issue with 02691156/31b201b7346e6cd15e9e2656aff7dd5b

For more context on the ShapeNet bug (Stanford url download): it comes from png files having jpg extensions, nothing wrong with the obj file by itself. As mentioned by @Saafke, gets solved by moving to different directory.

In terms of possible fix to o3d: I am able to load the images with matplotlib though. It might be that o3d uses file extensions rather than first bytes to determine file type.

@tomas-aftalion yeah, you are right.

https://gist.github.com/leommoore/f9e57ba2aa4bf197ebc5

0x89 0x50 is png magic number.

And open3d does read based on file extension in the name and not using magic number.