/3/ - 3DCG

>>936183
What answers are you looking for? That's a top of the line machine. People 10 years ago with 10% of the power of that PC and 10% of resources (both software and documentation) were able to create stunning visuals.
You are not at the level to be worried about this PC bottlenecking your workflow.

Doesn't matter, you can do that on a potato if you use eevee.
If you use cycles a 3090 will do fine with rendering still images, rendering animations will only sort of work if you use lots of denoising, so it doesn't fundamentally change the workflow.
CPU is basically irrelevant because blender is so single thread bottle necked it doesn't make a difference. Only fluid simulation make use of the cpu properly.
Ram is helpful if you use high poly meshes and avoid crashes.

Also you're an idiot for getting a 3090. Cycles isn't that vram hungry (compared to other path tracers) you could have gotten a 4080.

>>936186
16 gigs of vram sounds a bit too low on the other hand. What if you use UE5 with it as well?

>>936188
UE5 (lumen) is even more dependent on gpu speed than vram. You basically never run out (unless you enable the cinematic viewport)
The lewd related software that's so vram hungry is daz (iray render) which basically copies the entire scene 1:1 to the gpu.
Blender does utilize system memory before it runs out with marginal performance loss and unreal as a game engine has so many automatic optimizations you could use a fucking 970 with 3.5gig and be fine.

>>936183
>How far can I go with this setup?
An inch. Very bad specs good luck rendering an utah teapot.

>>936185
well yesterday I was playing fallout 4 and I put everything on ultra in the ini preferences file including tree shadows and I was heartbroken when my game became choppy. Maybe I over did it somehow since my character's own shadows were strangely blurry and blobby

>>936186
You dont know anything about vram. Cycles doesnt even use mipmaps

>>936199
I never claimed that. It does utilize system ram though.