@hornpub You have been asked several times now not to tag developers in your reports. It's up to the triaging team to tag reports with corresponding module labels and tag developers directly…
I have left the original report un-modified for moderation to take a look at.
wdym 😑 everything u need to know is in the video 🤨 i keep it nice and short and straight to the point 🙃
Hi, thanks for the report. Can you attach the affected .blend file?
sure here it is 🙂
Also @hornpub please follow the bug report template for future bug reports. That includes providing a working verison of Blender (if there is one and you have the time to test for it), a short…
This is the same issue as #86787, so closing the issue as a duplicate.
@hornpub , please don't tag a developer in a report unless it is neccesary or helpful (E.g. Tagging a developer…
Seems to have been fixed already. Please reopen if that's not the case.
now its work 😃
btw i cant find bloom in this version
Hi, thanks for the report. I think this is intentional. Similar results can be achieved through viewport compositor (glare node).
how can i find…
@sean-kim r u interesting in this one 😊 BTW thanx for fixing this issue #121008
This doesn't appear to be an issue with the actual vertex colors, it's something on the rendering side. Reselecting the active vertex color attribute fixes the view
![](/attachments/92a39e…
I guess this only happens in non "object" mode, right? That's due to two different undo systems.
camera navigation
uses memfile undo. But inside sculpt mode, their own undo system is used. …
Hi, thanks for the report. Generating undo step when transforming in "locked camera view" is an intentional change I made in befe38fe1d Not a bug, closing 🙂
no this wasnt my point 😁…