- Brasil
- https://www.linkedin.com/in/germano-cavalcante-77224867/
- Joined on
2012-10-07
In fact it was intentional as it reuses the existing logic of when to calculate occlusion.
But after testing, it really seems to be better to avoid this occlusion.
And in Orthographic view…
Fixed documentation. The changes were:
- Remove note about Incremental Snap's "Default" behavior
- Add description based on the removed Note for the Incremental Snap
- Style and Formatting…
It seems to only happen with the interface editor of a node group. It happens whether with Input, Output or Panel.
This may be an issue with the integrated GPU "Intel(R) UHD Graphics 620"
I don't have similar hardware to test, so before forwarding to the developers, it would be useful to have some…
This is a design issue that has been reported before: #99543: X RAY mode cannot be toggled while in pose mode
Maybe we could remove the "In Front" behavior and have a unique X-Ray type. Or…
For me, this problem would be more expected to happen with global undo OFF.
Just to check if that is the case, @HotKnife, can you try with Factory Settings?
Go to File → Defaults → Load…
Thanks for the report, but this issue is known and has already been reported before. You can find similar reports on the Blender bug tracker:
- #85764: Grease pencil stroke partially invisible…
Tagging @HooglyBoogly as reviewer because:
- reviewed the PR from the mentioned commit
- have worked on this BVHTree Utils code before.
- was involved in creating the loose elements cache API.