@brecht , 3.4 is good version. 3.3.4, 3.5 and 3.6 are affected by this issue. I'll bisect this.
@Jeroen-Bakker, GPU subdivision was added in 3.1: https://wiki.blender.org/wiki/Reference/Release_Notes/3.1/Modeling :)
Hi, thanks for the report. Can you share steps to replicate the issue or video showing the problem?
Hi, thanks for the report. I can confirm it locally.
Issue happens when faces are smooth shaded and Auto smooth
is active in object data properties tab.
2.93 is last working version AFAICT.
cc…
Hi, thanks for the report. RCS proposal already exists for this. see: https://blender.community/c/rightclickselect/vJdbbc/?sorting=hot This is not a bug as far as I understand but could be…
Introduced with 133dde41bb5bbbbd083b12723f1ec9053764348a If I understand the reason correctly in #103867, linked data is not stored locally in new file if it is unused (regardless of fake…
Hi, thanks for the report. Can you check again in 3.5-beta?: https://builder.blender.org/download/daily/
Upload system info file if crash persists: Help > Save System Info
Observing crash in intermediate builds so I won't be able to find the exact commit. Suspects are:
- 9d9f2f1a0356d2049ea2ce4820c61fdebbdf50ca
- 342e12d6d92198bba8355562600a2f97bb45fed5
I can confirm when switched between modes.
Issue is only reproducible if armature is added to object property of Armature modifier
in EEVEE
Hi, thanks for the report. Object looks bit broken in object mode. But not sure how it got there. Do you remember exact step that caused the issue. Please check whether issue is reproducible in…
@Melissa-Goon hi, feel free to work on this. Pick any editor from the list mentioned in the report description.
Attached image seems different than the uploaded blend file. Result may vary with every project and depends on how you are passing the normal, height data.
Hi, thanks for the file. Still unable to get the results after merging faces in edit mode. What I've done is:
- Open file
- Change to edit mode
M > by distance
Hi, thanks for reviewing :)
I don't see any particular reason to introduce a new flag here.
I can't tell what the second change does, the if (!recursive) around the addition of TSE_ACTIVE.…