Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
I am pretty sure that a good portion of the speed comes from having all the assets in the GPU memory. That allows the GPU to process without having to seek it from RAM or the hard drive. That's why I am guessing it is loaded into both, very similar to the way the network rendering works.
Im running a 24G laptop with a 980M just popped a 980 in my 32G tower drivers up to date. iray works great, I like the fact that I dont need to directly light up characters anymore makes things more realistic. According to Paolo's video it should not matter what GPU onse uses. I still need 6 plus hours in some case using GPU boost, I have my lights in one group, I dont get it
I get much better speed with the "Extra Boost" option turned off. I don't know why.
Also check your Luxrender log file to see if there are any clues. Mining the log file helped me tweak my settings both for errors and general processing.
Having all of your lights in one group may be irrelevant since Luxrender depends on how well-lit the scene is, since darkened areas don't received as many photon counts as lit areas. Iray converges so it is independent of how well-lit a scene is.
You can also reduce the number of light paths as well.
@Jason: I think it's partially because Extra Boost for OpenCL has issues with SSS if I'm not mistaken. (edit: Oh and to reference your other reply: There's a copy of it both in main *and* GPU memory, so I'm at a loss as to why it doesn't deallocate from main when it's done compiling the OpenCL code to GPU...)
It does not matter overall its still slow so I am going more iray. Paolo mentioned not to use SSS with GPU boost
@Bobvan: How many samples per second are you getting? My OpenCL renders with GPU only were at 400kS/s and around 700kS/s with CPU+GPU... and that took around 30 minutes under Sobol for a usable render. Was this the same scene you posted last week? I can't remember if you posted what was inside the scene or not...
Its too raunchy to post here. Paolo has said to ignore the stats and judge visuals. Anyhoo im getting killer stuff 15- 20 minute iray. Hence why when my AMD fire pro was accepted as defective under the extended plan on my tower, I popped in a GTX980.. Well worth the few extra hundred dollard diff I had to pay. Using iray draw is just as good as lux on the fly..
Ahhhh the technical person in me twitches when I hear people say to ignore stats. :( I love to help people troubleshoot so feel free to post again if you change your mind...
Thats is very cool. Im asking on the forums too. Before I pack in using Reality I want to absolutly rule out that it will not run faster on my systems..
@bobvan
Come talk to me when you get you content banned from DA tough-guy!
LOL not quite but have had a 2 week ban and also suspended from Youtube LOL I think I didnt completely get punted from D/A due to being a premium member. One can post anything on flickr cause their filters actually mean what they claim.
Okay I relocated my textures to another folder and they render fine now, HOWEVER, I cannot resume the render.
When I want to start rendering again where I left off, I get this error:
[2015-09-28 22:40:47 Error: 14] Static loading of renderer 'luxcore' failed.
Anybody else having this problem?
I have seen very good work with Reality 4 but I always seem to have problems using Reality... always for me using Realoty 4 and now 4.4 is a crap shoot! I never know what's going to happen... sometimes my computer freeze up or most times it just shut down when rendering using reality. My cpu just diea after about half hour. 3D Light and using LuxRender never a problem, even Iray is pretty cool.. But using Reality I get sceard!!!
I've gotten that when the wrong version of Luxrender was loaded with a Reality 4.1 file. The correct version should be in the Luxrender directory under the Reality installation. The easiest way I found to avoid the error was to create a desktop link to the new Luxrender, run that, then do a File > Open if I am not having DS send the file to Luxrender directly.
Reality is a plugin that sends your scene to LuxRender, it is not a rendering engine. How is it shutting down your computer when LuxRender does not?
It isn't that far fetched. I am not saying either of these is what is indeed happening, but there are a couple of possibilities that come immediately to mind.
@Softimage_Graphic_Artist: For you, the best course of action is to open a support ticket with Pret-A-3D (Paolo). I believe the instructions for how to do so are included in the readme.
Finally I find the problem. Fireflies are a problem of sampling Sobol . Metropolis sample produces less noise.
Even if you move the surface tab, that's barely helping it at all, it remains looking quite cluttered. I also did specifically mention the search field as a positive. I've never used Shader Mixer, but if it's so much less easier to work with, I may eventually give it a try.
If you select an item in the Scene pane, then move to the Surfaces pane, you do NOT need to look at everything at once. Using the left hand side of the pane, you can select General, Diffuse, Specular, Ambient, Opacity, Bump, Displacement etc. etc. so that only the parameters relating to these items appear. Very handy imo.
Can you give me a dummies tip, please jason. Using reality 4.1/luxrender and openCL, I get that same error message;RUNTIME ERROR: OpenCL device selection string has the wrong length, must be 3 instead of 2. Can I PLEASE have exact instructions on how to get around this. ie where and how to change the correct file, slave for life if you help me, thanks
No problem. I sent you a private message with the instructions. If they work for you, then I will repost the instructions here in the thread for future reference.
I am so confused.
Because of my setup the most I can use Reality 4.1 is with CPU acceleration, no boost or GPU of any kind. The part that has me confused is the following.
I am trying to render a babe in a bikini. After three hours of trying to get rid of a grey streak that runs down the edges of where the shadows start on her skin, I concluded that maybe it has something to do with SSS and CPU acceleration. I decided not to use acceleration and the grey streaks are gone, but as a bonus, I noticed that even though the image is being rendered, supposedly slower, less samples per pixels at less than three times the speed, the image actually looks cleaner than the same type of render using CPU acceleration.
I kid you not, a render that gets to five hours with CPU acceleration still hasn't cleared noise, yet with CPU and no acceleration and less than one thousand samples per pixel, it looks almost done, in two hours, and no grey streaks to deal with.
I am scratching my head here.
...I still haven't got around to installing 4.1.
After what I have been reading here, wondering if it is even worth it since I have a first generation i7 that does not support AVX which seems to be required to get any significant amount of speed boost.
Okay, a couple of different things going on here...
First, turn off SSS with all skin textures. There is a known issue with Luxrender and SSS settings. That should take care of the line pattern you are describing.
Second, try turning on the "Noise Aware" checkbox to the right of the Sampler in the Scene Configuration tab.
Third, when you are in the Scene Configuration tab do you see anything thay says "Open CL installed?" It should be right around the middle of the window, in white text.
Any other assistance I could provide I would need a screen shot of that Scene Configuration tab or a description of any errors you might be getting.
As promised here is how I fix the "RUNTIME ERROR: OpenCL device selection string has the wrong length, must be 3 instead of 2." error with Reality 4.1 and DS.
This will probably be a little different for each computer, so you are going to have to use some trial and error.
One, when you are in Reality, select "Export Only" under the render tab (just to the right of the Render Frame button). Scene file name, note the name of the file and the directory it is going in. Or, better yet, use the change button to name and put this somewhere easy to get to.
In the scene configuration, make sure you select your GPUs. Select Open CL rendering and then turn the GPUs on.
Hit Render. Most likely it will look like nothing happened. You might see the export of the files occur.
Navigate to the directory from the Scene file name step above. In that directory you should see a [Scene File Name].lxs file. Right click on this and open with Notepad or some other text editor.
In the file look for the section "Renderer "luxcore""
Below that line look for a line that says: "opencl.devices.select = 11"
This is the line that you need to change. But you will probably need to experiment. Start by adding a zero to the start "011".
Save the file. Exit the text editor.
Navigate to your Reality installation directory, probably under your Program Files directory. In the Reality directory there is a lux directory that you are looking for. Specifically look for this: C:\Program Files\Reality_DS\lux
In that directory double click the luxrender.exe file. Or create a desktop shortcut to it (this is what I did to make it easier). When Luxrender starts, go to File > Open and open the LXI file that you just editted. It should begin rendering after a little bit of a pause to load the files.
If you get an error, go back to the LXI file and try a different placement of the zero. I.e. "101" or "110". Where the zero goes all depends on what GPU isn't being counted by Reality.
Thanks for trying to help. I know all about the issues, except that I thought SSS was having issues with OpenCL, it is news to me that simple acceleration with no boost or OpenCL also causes issues.
It seems that the SSS issues are relative, just like the "acceleration", to the scene, some have issues others not. This is the first time I have personally seen it in just CPU acceleration mode.
I did several tests and the non-acceleration CPU mode is working faster in these simple scenes, and maybe in more complex scenes, I will have to test when I work on one. The way I am interpreting this is that, as mentioned before, don't look at the SPP, look at how the image is progressing to get an idea. In this case it is actually faster and cleaner.
I will not even attempt OpenCL, CPU or otherwise, I got very bad results with that. My GPU is not a strong card to even try GPU rendering and only has 1 GB of memory. I can't even use extra boost because it digitizes the image in some areas, some are calling this biased mode (although I am not sure that's true?).
That horrible lines are for ibl lights.
I am not using an IBL light in this particular scene.
I am using lux and iray. Playing with lux more I can see the potential. In the next Reality update some issues and SSS with boosted render modes will be resolved. I am stoked to see what it will do..
That horrible lines are for ibl lights.
Then contact Paolo...