Closed jloveric closed 4 months ago
One thing I might recall is that when there is not a single pixel rendered on your screen, the program will fail. Maybe for the cube case, a camera accidentally goes inside the cube and get a completely empty view?
I can verify this is not an issue if I change the shape of the cube so if has different dimensions in each direction (now it's a block).
Have you tried to change the scale of the mesh in the config file, perhaps scaling down the cube to for example 0.5 scale will help.
Ok, yes reducing the mesh scale solves the problem. It looked like there was some automatic scaling going on is there (maybe not)? Or in general, are the cameras at a unit distance from the origin or some other distance? For those looking at this I resolved both my cuda errors and "black" results where values go out of range by rescaling the mesh.
By default, it is scaled and centered, before the manual scaling happens, in order to make meshes of different scales to work under a unified setting.
Applying a depth map to a cube (obj generated from default blender) I run into a bunch of cuda errors. I suspect their is some issue with the extents being exactly the same size in each dimension. For me it works in various other cases including the examples provided (but not the perfect cube), at any rate this is the error I'm seeing. Trying to track the problem down on my own...
obj file
and mtl file