Krzysztof Chalupka

Did this get merged / can I close the issue?

This was fixed a year ago, closing the issue.

Take a look at https://github.com/facebookresearch/pytorch3d/blob/main/pytorch3d/implicitron/dataset/single_sequence_dataset.py#L163 as well as how that is called in [llff_dataset_map_provider.py](https://github.com/facebookresearch/pytorch3d/blob/main/pytorch3d/implicitron/dataset/llff_dataset_map_provider.py), maybe that will help?

Finally got some time to implement this :) Thank you for pointing it out!

This should be already available in Implicitron, please take a look and reopen the issue with more explanation / a concrete use-case if the current functionality is not sufficient.

Hi, long time no update :) But yes we have a VolumeRenderer now, see https://github.com/facebookresearch/pytorch3d/blob/main/pytorch3d/renderer/implicit/renderer.py#L200 The renderer.implicit module has a few raymarchers and raysamplers you can try out. Also, the...

Thanks for reporting and great repro steps! I checked that the seam disappears if you change to `blur_radius=1e-5`. Also, there's no blur if you use the new MeshRasterizerOpenGL (though you...

What's your use-case? It should definitely be faster if: 1) You mesh is reasonably big, and 2) You're doing multiple rendering iterations. If the mesh is very small (hundreds or...

I haven't seen other reports, this would probably be a very rare use-case we will not support in the future. I'm closing the issue.

Can you all confirm whether this is happening on Windows? A few days ago we enabled C++17 features and used some in iou_utils code. The error is complaining because the...