- Germany
- https://www.sheepit-renderfarm.com/
-
A Blender lover and admin on SheepIt
- Joined on
2020-01-09
Block a user
Crash: Opening a 3.3 project crashes 3.6/4.0
UI: Can not find Node in the search menu
Change the default Subsurf Viewport Level from 1 to 2
Change the default Subsurf Viewport Level from 1 to 2
Too bad, I would have liked to have seen the levels equated. But I understand if this is not the right place.
macOS: Blender doesn't utilize GPU for background rendering if Metal device type preference is set via script
So, it was a user issue, right? Case closed then :)
macOS: Blender doesn't utilize GPU for background rendering if Metal device type preference is set via script
What about --cycles-device METAL
? Does it work as expected?
https://docs.blender.org/manual/en/latest/advanced/command_line/render.html#cycles
UI: Blender no longer displays a warning for too new .blends
Change the default Subsurf Render Level from 2 to 1
So, change the viewport level to 2? I have a PR for that: #114108 It also seems "industry standard" to have the levels on 2.
Please note that the level difference is only an issue for…
Change the default Subsurf Render Level from 2 to 1
Change the default Subsurf Viewport Level from 1 to 2
I'm okay with that, too. I just want to prevent a rude awakening.
Change the default Subsurf Viewport Level from 1 to 2
Tagging Pable for UI and Campbell and Howard as modeling module.
Change the default Subsurf Render Level from 2 to 1
Nodes: Compositor and Eevee renders skip implicit type conversions in some cases
I can confirm this issue for Blender 3.0-4.0