- User Since
- Dec 9 2018, 11:17 PM (102 w, 5 d)
Jun 22 2020
Apr 15 2020
I can't make anything look like a pro with Eevee. I guess it's caused by lacking of this antialiasing node and Eevee motion vector pass (Or Velocity Pass as it was named there https://developer.blender.org/rBSe2613e4051d501c8b553d781cb63d06735968f91)
Mar 30 2020
My current scene has many heavy procedural textured walls and my viewport works slow with all of that. Wire view mode isn't convenient because I need to see the wall in close look. And in the same time I need to work in Eevee render view to see the smoke and other animations as it is. This feature would be helpful.
Mar 24 2020
I faced this in 2.82a. As for Cycles so for Eevee. I don't know how to add a tag here. And I made proxies for everything.
Jan 6 2020
Probably it's a duplicate of this bug https://developer.blender.org/T61093. I have two amd cards and I tried to bake irradiance volume with DRI_PRIME=1 and with active render view and seems it works without crashing.
Aug 19 2019
("Task"... I feel like a boss. It's not a task it's a bug. "Bugs" are just ok, "Tasks" leads to overheating and so on. Sorry, someone should say it.)
Aug 18 2019
Obviously any redesign should increase the work efficiency, not the buttons pressing amount. Currently, for me, the trade off roughly sounds like "you get Eevee but you need twice as many pressed buttons for the same operation". How many hours Blender developers could save if they just didn't bother about the UI redesign? How many hours addon developers could save without tricking with the new UI? And how many hours users could save after release? (What do we do with our lives?:'|) It's measurable. Blender needs some kind of standardized testing scene to compare the amount of user actions needed to reproduce the scene with old UI and with the new one. And an official statistic addon in the future. It's for UI Design bugs objectivation. (I hope the idea will not look bad only because it's said by me. I didn't do anything for Blender, I don't even have an avatar... But please, in the name of world efficiency and technological singularity and so on.)
Hello, Brecht. I think it's not a user feedback it's a UI design regression bug, because anyone can measure it. So it's not a subjective user feedback it's an objective reality. With this in mind, I found here the "Regressions" category, then I set "Design" in the bug report tunables and then posted it. And I still think I was right. Bugs are objective, measurable things, user feedbacks are subjective and not measurable things. Is this wrong? Is there an another criteria for bug/feedback differentiation? Thank you.
Aug 17 2019
Martin, thank you. Your solution does work.
Mar 12 2019
I was wrong. My example contains non-manifold objects so it's not suitable for bmesh/carve comparison, as I read there https://developer.blender.org/T59357. I've made manifold objects from that non-manifolds and it works. Previously I thought there is no any way to make that kind of non-destructive cuts in Blender newer than 2.79b.