In case someone cannot get Optix to work with an RTX nvidia card, make sure you're on driver version 470 or higher. This will allow you to select Optix and optix denoising. This is fantastic, thanks so much for the video. I'm loving the changes. Your huge volume scene was a good test for how it will do with volumes alone but it's clear it'd be much faster with only part of a scene including volumes, so this is a big speed gain all around no matter what kind of scene you have. Shaving 20% off volume rendering was sorely needed, even if that was all we got.
Oh, I know. I'm stupidly happy about cycles X. I got into blender after the nvidia 30-series dropped and the GPU drought began. I was stuck trying to render animations on a 1070. I had to let renders go as long as 4 min per frame to get useable shots, and I'd let my computer render all weekend for 10 sec of footage. Cycles X was already a godsend for me, but now with the 3060+Optix, and some denoising hacks I came up with (which I'll probably make a video about) I usually don't have to go above 30 sec per frame. I can't believe what's possible on an entry level card now! Thanks for sharing the driver info! That will be helpful for someone watching this.
I tried Cycles X but it crashes (CUDA context error: misaligned address) about a quarter of the way through the render. I did try a different simpler scene which worked fast though
@@chrisfastmedia turns out they fixed the exact thing causing trouble for me just this morning. Misaligned address when using adaptive sampling. Today's new Cycles X works wonders. Render time for a frame of one of my projects down from 22 minutes to just 6 minutes. Only thing is that I don't think Ambient Occlusion is supported yet
Tried it out just after watching your video. I had an error in the preferences that says there are no Optix compatible GPUs while I'm running an RTX 2060 so had to just run on CUDA and the denoising was a bit janky. Did you notice the same??? Other than that works like a charm.
Hmmm weird. Optix is working just fine for me. However, I ran a render on CUDA and it took essentially the same time. That being said I only have volumes in my scene, no diffuse, glossy, etc, so I'm sure there'd be a bigger difference in a more complex scene. I only just got a 3060 so I can't say for sure if the optix denoiser is janky, but it definitely looks like it. I usually use the compositor denoiser and it looked way better. Perhaps try updating your GPU drivers?
@@chrisfastmedia Yeah I guess I'll update the drivers and see. It was a fairly complex scene too. Simple scenes with just volumes etc. render remarkably well.
This is the update I was waiting for. Can't wait to try out the new Cycles X
In case someone cannot get Optix to work with an RTX nvidia card, make sure you're on driver version 470 or higher. This will allow you to select Optix and optix denoising. This is fantastic, thanks so much for the video. I'm loving the changes. Your huge volume scene was a good test for how it will do with volumes alone but it's clear it'd be much faster with only part of a scene including volumes, so this is a big speed gain all around no matter what kind of scene you have. Shaving 20% off volume rendering was sorely needed, even if that was all we got.
Oh, I know. I'm stupidly happy about cycles X. I got into blender after the nvidia 30-series dropped and the GPU drought began. I was stuck trying to render animations on a 1070. I had to let renders go as long as 4 min per frame to get useable shots, and I'd let my computer render all weekend for 10 sec of footage. Cycles X was already a godsend for me, but now with the 3060+Optix, and some denoising hacks I came up with (which I'll probably make a video about) I usually don't have to go above 30 sec per frame. I can't believe what's possible on an entry level card now!
Thanks for sharing the driver info! That will be helpful for someone watching this.
Now the albedo denoise pass works better with volumes.
And in a few weeks volume will render even faster
Wow, good news.
why is your monitor on the ceiling?
I tried Cycles X but it crashes (CUDA context error: misaligned address) about a quarter of the way through the render. I did try a different simpler scene which worked fast though
Hmm, I guess they still have a few kinks to work out. Hopefully they're able to put out a stable release by fall so it can work for ya🤞
@@chrisfastmedia turns out they fixed the exact thing causing trouble for me just this morning. Misaligned address when using adaptive sampling. Today's new Cycles X works wonders. Render time for a frame of one of my projects down from 22 minutes to just 6 minutes. Only thing is that I don't think Ambient Occlusion is supported yet
@@rr24creations Hey that's awesome! What a time improvement!
Tried it out just after watching your video. I had an error in the preferences that says there are no Optix compatible GPUs while I'm running an RTX 2060 so had to just run on CUDA and the denoising was a bit janky. Did you notice the same???
Other than that works like a charm.
Hmmm weird. Optix is working just fine for me. However, I ran a render on CUDA and it took essentially the same time. That being said I only have volumes in my scene, no diffuse, glossy, etc, so I'm sure there'd be a bigger difference in a more complex scene.
I only just got a 3060 so I can't say for sure if the optix denoiser is janky, but it definitely looks like it. I usually use the compositor denoiser and it looked way better.
Perhaps try updating your GPU drivers?
@@chrisfastmedia Yeah I guess I'll update the drivers and see. It was a fairly complex scene too. Simple scenes with just volumes etc. render remarkably well.