Repository navigation
Axes3D voxels is rendered incorrectly with plot_surface, plot_wireframe, or plot #13580
Description
Bug report
Bug summary
When using the voxels rendering for Axes3D, surfaces and lines are not stacked correctly in the visual perspective of the axes.
Code for reproduction
Adding the following lines to the example from matplotlib's example https://matplotlib.org/gallery/mplot3d/voxels.html produces the glitch:
(xx, yy) = np.meshgrid(x, x, indexing='ij')
zz = np.ones_like(xx) * 4
ax.plot_surface(xx, yy, zz)
or
ax.plot_wireframe(xx, yy, zz)
before the line
plt.show()
Actual outcome
Expected outcome
The plane should be rendered below the green voxels and some of the red voxels.
When rotating, some of the voxels become visible.
Matplotlib version
Using matplotlib from a miniconda distribution:
- Operating system: linux64
- Matplotlib version: 3.0.2
- Matplotlib backend : Qt5Agg
- Python version: 3.6
Thank you in advance!
Cheers,
Nicola
Activity
ImportanceOfBeingErnest commented on Mar 3, 2019
This is essentially what the My 3D plot doesn't look right at certain viewing angles paragraph of the mplot3d FAQ tells us about.
Obi-Wan commented on Mar 4, 2019
Thank you for pointing this out! I did my research before submitting the bug, but apparently I missed it, or didn't look for the right thing :)
Anyway, do I read this correctly:
in the sense that some of the backends might give the correct output?? Or simply it means that it won't be fixed until the "reduction of 3D data down to 2D + z-order scalar" won't be removed?
ImportanceOfBeingErnest commented on Mar 4, 2019
Solving this is indeed only possible when having a true 3D renderer. This would require a major rework of the complete mplot3d module and/or a true 3D backend.
An intermediate solution, where each face of a collection is treated independently across different artists within the "2D + z-order" framework would be possible though. Still no-one has implemented anything alike as of now.
Obi-Wan commented on Mar 4, 2019
Ok, thank you very much for the explanation!
What should I then do with this issue? Close it, or leave it open indefinitely until this gets fixed?
timhoffm commented on Jan 9, 2022
Closing as "won't or can't fix" because there are no concrete plans to rewrite with a true 3D renderer.