OctaneRender V4 XB3 Tweet

[arvinmoses0122]

I'm getting same results with displacement. Instant crash when map is plugged in. Running tests right now on workarounds.

[funk]

I wanted to post an update for anyone who read my previous posts in other threads. The denoiser was causing my PC to reboot if I used the 1080 Ti. I thought the PSU may have been the problem.

I had a single PCIE power cable (Y split) from the PSU to the 1080ti. I changed this so 2 separate cables/rails power the 1080 Ti instead. This solved reboot issues when using the 1080 Ti to denoise.

I still got reboots if I used both the 1080 Ti and GTX670 for denoising, but I solved this by using additional drive cables with a molex > 8 pin adapter for the GTX670. I can now denoise with both cards without any issues.

Denoising is actually faster if I use the 1080 Ti alone though. Adding the 670 seems to slow things down a bit.

EDIT: I also complained about denoising being slow. It turns out denoising on the 1080 Ti is actually quite fast (now that I can use it)

[itou31]

Yes, about speed denoising, I use my two 1080ti only. It slow down when combine with my other 980Ti.
I've made some turnable animation with XB3 (4K resolution with 100sp + denoise, between 12s to 18s for each frame for the 2 characters)


Gain speed only on heavy render (denoise is great for animation) over the 3.08, else the 3.08 still faster on some way compared to xb3 + denoise for a same result (about 300sp vs 100sp+denoise)

[gardeler]

First off, I forgot to say Awesome job on the alembic reader! BIG improvement!

found two small issues:
-Enabling the Environment render output almost doubles my render time. Since there is no calculations here, only the HDRI image, I guess something is wrong? (I have no fog or anything else than just a hdri image.)

-If you change anything on the geometry properties after you have loaded an animated alembic, (like un-checkbox "merge materials with the same name"), the time line disappears. You will have to save your file and reopen it and it is back again. This also happens in 3.07. Both on linux and windows.

[coilbook]

Since, I guess, we cannot have the dirt texture locked to one object (no influence by external mesh in close proximity) Can we at least have objects that are set to invisible not to generate dirt on objects with dirt material or please make it where dirt is locked to one mesh only Please!!!!!!!!!

[coilbook]

my master PC only has 2 video cards. One for rendering another one for display. Can I use the third card from the salve for denoising?

[milanm]

@coilbook

Baking dirt to a texture could speedup your renders DRAMATICALLY. Just make a separate scene with the boat isolated and a white diffuse material with dirt, switch the camera to bake and use that render instead of dirt on your model. If the model doesn't have UVs even a basic 5 minute unwrap will do. If you change your mind about the radius, later you can just open up that scene and update the map. I'm saying all this because I had an unpleasant experience on a model with over 6000 elements where Dirt caused a MASSIVE slowdown and it actually makes perfect sense because it's a shader that has to go back and raytrace other pieces of geometry for every pixel in your final render. Same approach is needed for rounded edges and is probably very very hard to make changes to Dirt or introduce features like that without causing a major slow down in Octane.

With all of that said, why the hell are you not complaining to Phoenix FD !!!!???

OFF: Anyway, I'm preparing to post a huge topic about a simple but VERY cool OSL shader(?) that's going to open up a world of possibilities. Like having separate shaders under water, speeding up lights in volumetrics, turning off shadows or AO and hiding objects (nothing Dirt related though, for now).

EDIT: IT'S HERE!

Regards
Milan

[coilbook]

@coilbook

Baking dirt to a texture could speedup your renders DRAMATICALLY. Just make a separate scene with the boat isolated and a white diffuse material with dirt, switch the camera to bake and use that render instead of dirt on your model. If the model doesn't have UVs even a basic 5 minute unwrap will do. If you change your mind about the radius, later you can just open up that scene and update the map. I'm saying all this because I had an unpleasant experience on a model with over 6000 elements where Dirt caused a MASSIVE slowdown and it actually makes perfect sense because it's a shader that has to go back and raytrace other pieces of geometry for every pixel in your final render. Same approach is needed for rounded edges and is probably very very hard to make changes to Dirt or introduce features like that without causing a major slow down in Octane.

With all of that said, why the hell are you not complaining to Phoenix FD !!!!???

OFF: Anyway, I'm preparing to post a huge topic about a simple but VERY cool OSL shader(?) that's going to open up a world of possibilities. Like having separate shaders under water, speeding up lights in volumetrics, turning off shadows or AO and hiding objects (nothing Dirt related though, for now).

SNEAK PEEK

Regards
Milan

Thanks! Hopefully it will work with 3ds max too

[vijay]

my master PC only has 2 video cards. One for rendering another one for display. Can I use the third card from the salve for denoising?

Sorry, Not possible and don't see this coming in near future as well.

[coilbook]

my master PC only has 2 video cards. One for rendering another one for display. Can I use the third card from the salve for denoising?

Sorry, Not possible and don't see this coming in near future as well.

Thanks is one card enough to denoise or more cards is better? Are titans better at it than 1080s?