Open SBCV opened 3 years ago
The background images of the animated camera are currently only visible if viewport shading
is set to wireframe
, solid
or material preview
(i.e. it does not work for rendered
). interestingly, the background images of single (non-animated) cameras are shown correctly with viewport shading
set to rendered
.
EDIT: See https://developer.blender.org/T85750
Currently the addon uses something like windows/path/to/blender/python -m pip uninstall package_name
to remove the dependencies of the addon. On windows it may be possible that this command does not completely remove the previously installed folders and files.
Blender crashes when deleting point clouds drawn with OpenGL. Due to the non-deterministic appearance of this bug, it is (potentially) caused by the memory management of Blender / Python. Further investigations are necessary to identify the cause.
~~EDIT: Currently, the addon can not properly delete the drawing callbacks without causing a crash in Blender. To avoid a crash, the callbacks are not removed when the corresponding point clouds are deleted. Since these callbacks are not longer drawing anything, they become very cheap and produce only a marginal overhead. A restart of Blender will remove the callbacks.~~
EDIT: This bug has been fixed (see https://developer.blender.org/T86106). In the latest version of the addon the drawing callbacks are correctly deleted.
bgl.glEnable(bgl.GL_DEPTH_TEST)
is broken in Blender 2.90. Thus, the occlusion handling of point clouds in the 3D viewport with OpenGL does not work properlybgl.glEnable(bgl.GL_DEPTH_TEST)
causes strange artifacts underWindows
. Saving images of point clouds using the photogrammetry importer panel (in the 3D view) might result in black images. Dependending on your use case consider to uncomment the corresponding lineNote: Blender is currently switching fromOpenGL
toVulkan
, i.e. thebgl module
will be deprecated! This could resolve the current rendering issues.EDIT: See https://developer.blender.org/T85709EDIT: This bug has been fixed in the latest version of the addon using the new api of Blender 3.0