- User Since
- Sep 22 2020, 8:59 PM (43 w, 3 d)
Jun 6 2021
I can confirm that the issue is still present in the current 2.93 build.
I confirm that the issue with the current 2.93 build has been resolved and the report can be closed.
I can confirm that the problem regarding cryptomatte in 2.93 is gone. Not sure if the issue remains for other situations, but for me the problem is fixed now.
May 21 2021
May 7 2021
Apr 27 2021
Apr 26 2021
Apr 24 2021
Mar 22 2021
Mar 19 2021
Mar 7 2021
I can confirm, I'm working right now on a project where I'm using an image texture displacement and it's almost impossible to do any action without waiting several seconds. The issue occurs also with working with the Attribute Sample Texture in Geometry Nodes.
Mar 4 2021
Feb 28 2021
Jan 25 2021
Hello, I really like this feature! Just wanted to give a small personal note, I think the percentage indicator should have some sort of visual difference from the static indicators considering they are so close to each other, like having a different background box color.
Jan 23 2021
Jan 22 2021
Jan 18 2021
Jan 14 2021
Did a couple of tries, indeed it happens the same to me. The immediate crash happens with GPU+CPU render.
Jan 11 2021
Is the fix for this coming any time soon? Cryptomatte in 2.91 is currently broken.
Jan 10 2021
Jan 9 2021
Jan 5 2021
Jan 4 2021
Jan 2 2021
Dec 30 2020
Dec 22 2020
We will still be able to disable the confirmation also for X in the keymap?
Dec 17 2020
I always delete with X, it's very fast and intuitive once you get used to it, so I also vote for having the option the disable the confirmation in the keymap like with objects.
Dec 16 2020
Dec 14 2020
Dec 13 2020
Dec 4 2020
Dec 3 2020
The feature is still not present in 2.91, was moved to 2.92. In 2.92, did you activate the feature in Preferences>experimental?
Dec 2 2020
Nov 27 2020
GTX 1080 Ti - driver ver: 457.30
Hi, it's me I had to change account for email reasons. Still an issue for me, I'm on a different computer from the original report but it is still happening.
Nov 26 2020
Just to leave a comment to be sure, I encountered the same problem in 2.91 with a resolution of 1754x2481, not "very high", so I guess the bug regards also smaller resolutions than the one in the first report.
Sorry for not diving a little bit deeper before, I think I actually found out: the regression in 2.91 regards renders with a large resolution.
@YAFU (YAFU) Thanks for pointing out a problem related to subsurf, it's true that regardless of the blender version the file opening and render initializing were slow, but then why in 2.90 the same file renders faster? Might be as @Alaska (Alaska) suggested a regression due to specific CPU architectures?
Nov 25 2020
Did some other tests with the same setup (64x64), same results, this time at the second/fourth render they actually increased from last time, from 2 to 10 seconds.
@Robert Guetzkow (rjg) Thanks for looking into it, hope it will eventually be resolved!
The time measurements I presented weren't the first render after starting the program, but the second/third, anyway I'll do some other tests just to be sure and write them down here.
Not sure if you need to know it, but my CPU is a i9-7900X.
Nov 23 2020
Nov 21 2020
This is not a bug, it's a change in the layout made in 2.90: https://developer.blender.org/D7430
Nov 18 2020
Nov 16 2020
Nov 14 2020
Nov 11 2020
Nov 8 2020
Actually I just found a reported bug that is exactly my same problem: https://developer.blender.org/T82351, guess I should've dug better!
I'd delete this task but I cannot find a way to delete or merge it with the other one.
Nov 7 2020
Nov 6 2020
Nov 4 2020
No problem. Anyway, for the future I'd suggest you to post these observations on devtalk, as here is specifically for bug reporting.
It is because of the new feature "Outliner-Properties syncing", now depending on where you click (object's name, modifier icon, object data icon, material etc.) it will automatically change the properties section. I can understand that it's a big change and can cause some troubles like this, but there are a lot of other situations where this feature actually speeds up a lot the process of dealing with multiple objects, modifiers and constraints. I'd say though that it could be good to have an option to disable it, or at least to add physics and particles icons to the outliner so that the sync happens also for them. For now, what you can do is have the properties panel not sharing an edge with the outliner (basically have the two editors detached), in that case the sync no longer happens.
Oct 31 2020
Oct 22 2020
Oct 20 2020
Oct 14 2020
Also for me, evidently the problem was somehow fixed with a newer release: I don't know how, I just reported the bug I'm not a developer, should I just change the report as closed?