Adding to Cart…
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.You currently have no notifications.
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Well it installs and renders (very fast) sometimes.
I suspect VRAM being the issue as a naked figure uses around 2G but when clothed uses 100% of my 6G 1060 card and sits on the geometry step.
I checked the Otoy forums but found nothing on the VRAM requirments for Daz figures (and accessarys).
Has anyone here got recomendations regarding the resources this plugin realy needs as I was considering upgrading to a newer graphics card.
What you need/want to do is enable "out of core" memory in the "Octane Main" window by setting the amount of system RAM ("Out of Core Memory") you want it to use (see attached). Then Octane can use system RAM in addition to GPU RAM to render. You can also set the amount of memory you want to leave free on the GPU in case you want to do something else while rendering.
you can also click on the textures tab and selectively resize materials that reduces the memory footprint. you have options if i remember to reduce up to 1/8 resolution,
Octane 'free' where? With limitations, right?
Only one GPU I believe.
Nice, worked fine although the 32G which was huge when I purchased my PC years ago is only just enough for this;)
Nice, saved ram there just by using the by 1/2 and the image still looked good;)
Must say I'm impressed by the options Octane allows, thanks everyone for aleviating at least some of my ignorance;)
'Freedom of choice is what you want, freedom from choice is what you got' (Devo)
Hmm, I did notice that only the GPU was used during the render but not my CPUs .
The CPUs where used on the initial build but nothing for the render itself.
I have the GPU render priority set to medium, I thought this would split the load between CPU & GPU.
Or am I reading this wrong?
(I always assume I'm doing somthing stupid)
Octane sounds like it's better than iRay. But I have to ask, does it render faster than iRay?
Octane only uses the GPU for rendering. Even when using out of core memory, it still barely uses the CPU (unlike Iray that uses one CPU core per GPU when using GPU only).
As far as features and performance, Octane is definitely better than Iray. It does however require more work from the user, since like any "external" render engine, shaders often need modification by the user to get the best results.
Thanks, I'm still browsing the manual and there are so many options.
If you're interested in faster renders, the AI lighting features can help a lot. The denoiser in Octane is also better than the Iray denoiser, definitely a plus for animations.
The priority setting is for how many GPU cycles it hogs. High basically takes over the GPU and leaves almost nothing for Windows screen refreshes and such, Medium plays nice with other on-screen processes, Low lets everyone else use as much as they need.
Thanks;)
Been running some comparisons and with a 1060 6g vram and not loading too bigger scene the Octan render is aproximatly twice as fast as Iray.
Any speed increase is greatfully accepted;)
CHeck the Octane website. THey should have the correct version of the Cudnn library you will need
Honestly, any increase in render speed is lost in the amount of time it takes to fix the materials. Otoy has also shown virtually no interest in upgraded or updating the Daz plug-in.
Problem with installing Octane Render
The installation doesn't work for me. There is the error message The procedure entry point "cuDeviceGetUuis" was not found in the DLL "C: \ Program Files \ DAZ 3D \ DAZStudio4 \ octane.dll". Can someone help me solve the problem? Thank you !
Is there any automisation or scripting options for the textures?
What would be usful is an option to automaticly rescale textures of a specific size or larger rather than go through clicking all of them manualy.
No I dont work smarter I'm just lazy;)
Edit - Sorry for the grammar, spelling and punctiuation. auto correct has spoiled me.
Glad to see this thread is still alive, I'm the person(HEEHEEdgehog) Mooncraft mentioned in their Octane vs iray review.
Octane can be a bit over whelming at first but it has its own settings you can mess with like Iray does. Only difference is alot of the stuff in iray has the "works right outside the box" feel, removing a lot of the learning and leg work you would have to do.
In simpler terms iray is like an iphone where as octane is like android.
The biggest issue with octane besides its lack of support for daz. There is no documentation that exists or is up to date, the official otoy manual is ancient. Any up to date manuals are for other software such as C4D or Poser.
To add even more problems, the manuals are not exactly the same due to different softwares. A poser octane user suggested i used the beautify denoise feature for octane. I told them it did not exist in the daz plugin, even took a screen shot. to show no option existed.
Instead i discovered octane for daz has a laundry list of beautify featuers rather than a simple "beautify denoise"
Here is a bit of knowledge I'll share for those looking to dive in or give it another chance. This will be stuff to help to get you started. This isn't a do this and you'll get amazing renders like people who have been doing this for years kind of thing.
This is to help you get started on creating your own foundation for octane. I have been able to render a large scene with 4 characters at 4k at 1000 samples in 12-30 mins. (lighting and shadows affect render times) worst case 45 mins.
Octane is fast, REALLY FAST!
Without further a do, here is a the list.
1. Use path tracing Kernal in Octane render settings! ignore the others, seriously DON'T TOUCH THEM! Let me save you time by telling you they look worse off the bat or take longer to render the same image
Mess with it if you want but you'll go back to path tracing because it pretty much does the same as the others except its fatser.
2. 1000 iterations in Iray does not = 1000 samples in Octane. it's like comparing miles to kilometers or gallons to litres. It's a unit of measure ment but both represent diff values.
1200 iray iterations at 1080p can still give me a very noisy render. Octane 500 samples at 1080p can give me a noiseless crisp image
3. Environment tab in Octane, top left you will see "default daylight environment" use this unless you have. Unless you have an HDR you want to use. FYI HDR has its own learning curve as well so stick with Default daylight enviroment until you get familiar with it.
3b. midway in the settings you will see something called daylight model Octane and Nishita daylight models are very similar and do have a slight blue tint to them. This is only noticiable when you select Hosek-wilkie daylight model. This has a more orange/warmer tint.
I use the Hosek-Wilkie one since i do like the warmer feel to it.
4. Daz assets. Not all daz assets work the same and some can be a nightmare to fix when it comes to materials. A good example of working assets would be assets from Stonemason. They work really well with octane and only issue is glass/water objects which i will mention in another point.
Some assets from vendors really dont play nice, espcially if you see a shine on their assets via the promo images.When converted, EVERYTHING IS SHINY! for some reason. This is fixable. i'll mention it in another point.
5. Weird looking materials.
if you see golf ball looking skin. select your character, go to surfaces, skin and turn the bump and normal to 0 and releod your scene. If that doesnt work save your scene then quit daz and reload it and you should see it gone. If you want some detail on the skin adjust the materials in octane and not in daz.
Hair colour- Some work and some don't. If it doesnt work right away do this. apply hair colour again, in the materials tab of octane, select the object right click, select "create as new material" -> select " auto material" and the reload your scene in octane. If that doesnt work. Save, quit daz and reload your scene and the new colour should apply. If it doesnt work still its just how the author of the asset set up the materials. A work around to change the hair colour to anything else is possible but its a whole other lesson.
Pretty much for any material except things like glass or water that isnt working right, just do this -> in the materials tab of octane, select the object right click, select "create as new material" -> select " auto material" and then reload your scene in octane. If that doesnt work. Save, quit daz and reload your scene.
6. Dforcehair- This really depends on how the author set it up. Some work and some don't, anything that is "hidden" from viewport wont render in octane. best case is you get the scalp looking thing.
I have hair assets from the same other and both dforce. One i have no issues and the other I cant figure out how to get it to render. Just be aware. Thisis a current problem I havnt figure out yet.
7. Lighting!- you have to manually create lights in octane, they dont transfer over. Just do this -> in the materials tab of octane, select the object right click, select "create as new light source" -> select " simple" and then reload your scene in octane.
for coloured lighting same thing except choose textured rather than simple. Simple = standard light bulb, textured = every other color.
8. SHINY assets - in the materials tab select the object and increase it's roughness. reload scene.
9. water glass- by default you wont see anything where these should be, maybe a simple outline. You caan use the Live DB octane materials for these or you can just increase the roughness if its like somethign minor, or do both!
10. Ray epsilon - Under render settings make sure "ray epsilon" is set to 0.000003. I cant remember how to lock it but there is a way. octane will keep changing it everytime you change angles on your scene so make sure to set it back. this prevents your character and other assets look like they
arent artifacting or just looking werid. you can play with it and see what it does. I found that setting to work the best.
11. Scene lighting - indirect lighting works amazing in octane, where as the direct evironment lighting looks way too harash. Set up a scene where there are atleast 3 walls and a floor blocking light and you'll see how much better the image looks.
12. Samples- You dont need to crank the sample way high for a nice image, 500-1000 samples should be more than enough. BUT! if you really want to finish that netflix episode crank it to 2000-3000. On my 2080ti a complex 1080p render at 3k samples finishes in about 5-9 minutes.
13. Scene settings - If you gone through and adjust everything to make an image you are satisfied with i reccommend you save your scene delete everything. save it again with a new name. Each time you save, Octane saves any changes you did to its settings for that particular scene. so you can have two differente scenes with two complete different octane settings. This helps you load in assets to render a variety of scenes without having to rework your lighting from scratch.
This is all I can think of off the top of my head. but it shoudl help you get a better footing in Octane. The biggest thing to remember is "Lighting" in Octane this is KEY to making your renders look good.
If you have any question let me know and i'll do my best to answer them.
There are a lot of other settings that can make your renders look nicer or even speed them up but that's a whole other bag of explantion.
I have attached two images I did in octane with a bit of post work done in lightroom for contrast and exposure ( I only use the octaneo ones if I have to)
Cheers!
Octane current works just fine with Daz 4.14
Been testing it just fine since the latest release :)
I've just installed it, no problems and all looks OK in DS, but when I click "Open Viewport" DS (4.14.0.8) crashes with this error. Hardware is pretty old, 8 GB RAM, GTX 1070. Just have a simple cube in the scene.
I have installed it:
1) Install activates at the end of the install process so best to have an otoy account already set up.
a) It also automatically downloads a library needed for nVidia GPUs after the main renderer SW is installed.
2) Installed the the release version of DAZ Studio 4.14.0.8 & it crashed DAZ Studio 1st time I started DAZ Studio.
3) 2nd start of DAZ Studio starts OK.
4) Open the Octane example scene with the lady but it just loads lights & setting not the lady & scene set she is in.
5) so I open the scene that I used to make my forum avatar. A popup for material conversion & it's a little slow going...converting 83...543 materials but not too slow. Super that it's automated though.
6) Docked the Octane Renderer Pane to my DAZ Studio
7) The Octane Pane is certainly impressive in the amount of detail and organization they've done for their renderer. LOL, clearly meant for someone paid 100K plus a year to use in California and not by the likes of me. Anyone wanting to become expert in the ins & outs of professional rendering might do well to learn Octane in & out.
8) So I try & render the scene & Octane renderer tells me it couldn't combine meshes because the scene is using DAZ Instances (the instances are probably from the Ansiko product Mediterranean Seashore)
9) Well, the render isn't doing anthing. I think I should have a 3060 8GB minimal for my GPU card. Correctly I have a 1650 Super 4GB, not slouchy for for a scene like in my icon it's too much for the card & the advanced things the Octane renderer does.
10) I won't uninstall it because it's a good and impressive product but I need to have a better GPU & read the user guide. It's very involved and complex. Oh, also watch the introductory tutorials I got free from DAZ 3D/Octane today.
Big question? If I buy a Big Navi GPU will it run now on them, 6 month later from the original 05 2020 DAZ Studio release of this plugin?
I don't actually think that would help you: I've got a 3080, and I can't enable Octane rendering on it at all. Based on a brief glance at the OTOY forums: In your step 1a, the nVidia library it installs, and which seems to be the only version the plugin recognizes, is version 7.4.1, but Octane support for the 30x0 cards apparently requires version 8.0.4. So in my "OctaneRender devices preferences" window, the "Render," "Use priority," and "Tonemap" options don't have any checkbox at all, and the only thing I can enable for it is "Denoise." That window also just shows a "?" for the "CUDA cores" on the card; I think the 7.x library (and/or the plugin itself) only works with CUDA version 10.x, and the newer cards are based on CUDA 11.1.
Hi people :)
I'm Currently testing Octane with my modest 1660 ti ^^
So pretty much all my scene are bursting out my VRAM... Is there a way to set a limit to textures size (like in Iray), except from going into the material pannel and tweak them one by one :( ?
Scene Optimiser will do that for you (it's still resizing, but it can do a batch and - usefully for stills - will tell you how far away an object is so you can decide how much compression is OK) https://www.daz3d.com/scene-optimizer
Having a slight problem with the octane kit here. The daz supplied skin textures literally turn any figure jet black. What am I doing wrong?