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
Not sure what it is but yeah iray is working for me to as decribed above longer render times using the none map sun vs creating a sun effect with using enviro map & using adding a diffused mesh
I think some of the issues you are seeing are from the Nvidia OpenCL version.The current version of OpenCL is 2.0 and Nvidia packages 1.2 with their drivers.CUDA and OpenCL are competing technologies, so I assume Nvidia is in no hurry to improve OpenCL on their platform.
I read your review, and I too would like to see more of Luxrenders' options exposed in the GUI.Having more materials options would be fantastic as well,,but it doesn't look like very many people are making them unfortunately :( . It would be nice to see opensource projects like Luxrender get some better support for this sort of development work.
Could very well be. Would of been able to confirm this had I swapped out my AMD fire pro w5000 to a 4G current AMD card rather then the GTX980. In any case iray works well due to having the hardware http://fav.me/d9drji4 . If I really need to lux render on occasions using cpu acc none boost with SSS ticked off skin works most stable. I am just disspointed that Paolo said that the issues had been resolved and nothing has changed. Now I am suppose to spend a week to figure out problems that were not there with 4.0 or R2..
I was trying to figure out what OpenCL 2.0 meant for LuxRender. Reading some of the additions it isn't clear, but I'm sure there is stuff in 2.0 that the Lux devs were waiting for. I didn't buy into Nvidia cards before they had OCL 1.2. Aparently that was a pretty unexpected and sudden development, so it could be that Nvidia has begrudgingly found they need to work with it for some emerging tehnologies.
I'm not too concerned about predefined materials so much, but there are a lot of controls Reality could include to make certain materials more flexible, especially in relation to using texture maps.
What do you mean? Are you talking about an HDR/IBL type light and what is a diffused mesh?
I meant the default map lighting I would change the map to a different picture to create day light then add a mesh with emissive shader applied above and angled it, gave it a yellowishtemp. Gave me this effect http://fav.me/d9drjw1 Even though it takes longer I have to admit changing map to none and use the sunlight works better..
So far my experiences with Reality are mixed. I first and foremost am looking for speedup in render times, who does not, this is why I gave Lux a shot, as it can utilize my GPU, which Iray cannot.
The trouble with using Lux is, that you need intermediate software to feed the data to it. It all raises and falls with that intermediate software, which is, in the case of DAZ, Reality.
On the one hand, Reality provides much more than I was expecting, in some cases it provides a pretty good depth of details. For the first hours/days, theres not much to wish for.
On the other hand, it easily gets a hickup, with varying result from corrupted scene files, objects not appearing in the object list, objects on the object list that actually don't exist, or export something that should easily work but makes Lux crash on the first render call. It is unfortunately also a missing some in-depth configuration options to configure all the tonemapping settings that are available in lux.
It also has serious troubles with providing SSS, which is my bigget complaint.
There is this "grey streaks" bug, which funnily does not appear every time. I have quite some accelerated renders which are perfectly okay and where SSS is turned on. Then I have some, which are corrupted. In general it looks like, when adding more than 2 SSS volumes (1 Character + 1 Gen Mesh), it quickly starts to go crazy, crashing most of the time.
Also, what's up with that top coat setting? Why is there a subsurface map loaded into top coat and why is there a pinkish color associated with it? Top coat is above the skin, in which case it is the oily layer, which' specular color is pure white in all cases. I get very strange results with that top coat enabled in all cases.
That SSS map would be needed on the SSS settings instead, but unfortunately you cannot set it there, so you get the same SSS all over the body or none at all.
In the end, I don't get as satisfying results with Reality+Lux on skin as I do with IRay. But this is NOT necessarily true for non-SSS renders; for them, in the end, the material settings are the limiting factor (cloth shader e.g.). A big plus of Reality SSS is the facial map it can create, which prevents rendering of e.g. the eyebrows with SSS, something that, to my understanding, Iray rendering is lacking.
My summary:
As for converting Iray shaders to Lux - this just works on a basic level. I think it cannot do much more, as it is lacking a lot of the material settings Iray has. It can emulate some, but most of them it can't.
As for rendering Skin - mixed result. Sometimes work, sometimes not. More than 1 Figure is a good chance to crash Lux in the version I'm using (which is 1.6dev, not 1.5.1, check Lux forum). SSS not as good as Iray.
As for rendering Architectural - very nice!
As for rendering cloth - Somewhat limited by the available settings. Have to check if I can get more out of it. Results are satisfying overall, though.
As for using any non-GPU mode, accelerated or not - I think it's slower than Iray most of the times, makes no sense to go for the extra hassle when it is not faster by a long shot.
As for loading times - actually I find IRay to be much slower and when you want to play with tonemapping, it gets even slower. So thumbs up for Reality+Lux.
Special mention of the tonemapping in lux is needed - it makes a HUGE difference if you can play around with these while rendering, you can get so much more out of a render with appropriate tonemapping settings. Unfortunately, Iray decides to restart the render each time you change something - you either know which settings you need in advance, or you have some extra lifetime available to restart the render over and over again.
Another short special mention of the save/resume functionality of Lux, it's killer, period. :)
In the end, Reality is a good way to make use of Lux from within DAZ, but, as good as it is already, and it is, it needs some serious improvements on the material settings to make it more fit for PBR.
For the price, it's a no-brainer to get it, in case you have an AMD GPU and want to start making use of it (note that you want to have at least 4GB on your GFX-Card and at the very least 16GB of RAM).
I would really like the improvements. At least in my case, Yes ,LuxRender is 20 times faster (I checked it carefully), but 20 times is not enough,It have to be faster, at least 50 times o more.
I can also confirm that this update SSS problems disappeared. At first I had problems with the preset, and what I did was reinstall everything. Usually, reality does not fit to the first installation. I also had to clean any previous installation, to avoid errors.
I have no issue with the installation and never had to reinstall and still see the grey streaks. See my previous post as well as Bobvan's. We both can't be wrong.
I'm not saying you're wrong in what are you say. I am sharing my experience with Reality 4.1. And the recommendation to reinstall does not only have to do with having installation problems. It is an old advice that works for all types of software, reinstalling sometimes solves problems.
Nahh man I did a fresh install of reality tried deleting R data and re doing reality scene same problem.
Not only that but I rendered 1 character in a scene with SSS so CPU non ac no boost took over 7 hours, iray is coming long just fine..
Hi all,
Going through this thread let me point out some observations ...
I see a lot of comments about how this doesn't work and how Lux and Reality do not function as promised. However looking at what hardware is being used by those who are making these complaints it is obvious it appears most are trying to use gasoline in a diesel engine. In other words, if you do not have the hardware that supports the new features and abilities of Lux and Reality, why would think it would work any better than older versions of the same? It's the hardware that is lacking, not the software.
First off, Intel. If you are using AMD CPU you will not and cannot acquire specific instruction sets needed for the CPU boost. Also in some cases if you use Intel you still may need to download specific instruction sets that may not have been installed by the OS or the BIOS for your machine, even an i7 machine. That being said the minimum requirement is an SSSE3 instruction set, however the most speed increase will be seem with chipsets that support SSE4.2 with AVX2.
Just an observation
I have a CPU that has SSE3 and SSE4A. I can tell I got a boost in CPU mode, and, as I have stated, I don't have a decent GPU or even an NVIDIA card to try with Iray. Except that in reality, it crawls just as much as before (the noise level with boost is much worse which makes a render actually take longer because you have to wait for it to clear, so it is a perception of speed), and the issues with the grey streaks with SSS in accelerated/boost mode are there regardless if you have something better than what I have.
The noise level depends on how your lighting is set. Not everyone is rendering a scene so lighted as to be practically shadow free. I like shadows in my scenes, it is what makes them so dynamic.
Bobvan is a great example, he has all the new hardware, and a CPU that has SSE4.2 with AVX2. Even he sees that he is not getting the speeds he should be.
I can only explain what I am experiencing. I have compared Iray with Reality/Luxrender and both are in par when it comes to the type of objects in a scene. A simple scene with a loaded figure on a stand can render super fast (15- to 19-minutes on average on my hardware). Now add, say, something as simple as grass or a few flowers to cover the ground and the intense calculations kick in making the render take a very, very long time (3- to 4-hours on average). Just like a scene inside an enclosed area (which can take me 9-hours). And I know why, no need for anyone to explain it to me.
Did some light and material tests for these 2 scenes, both of which are enclosed. They ran for an hour each and could probably stand another hour or two
Reality has jumped the shark..
BTW, I also forgot to mention the jagged harsh shadows. I have no idea why that is happening, as well. I even tried using SubD and I got about the same results.
I really did try to stick with Reality/Luxrender but there are way too many issues for me right now.
That's aliasing, an issue along with the tears using SSS was suppose to be fixed in the last update. Have not touched Reality / lux since it yet again did not live to its promises..
I love using Reality, I learned alot about 3D using Reality, transfer over to Iray. Reality/Lux alway's rendered fast on my system, so that was never an issue for me, only I could never get certain materials to work to my advantage, specially water. And I enjoy creating ocean scenes. Would like to upgrade to Reality 4.1, but at the moment appears to be having alot of issues.
...exactly, I have a first generation Nehalem i7 that only supports SSE3 (not SSSE3). so it's still glacial rendering times for me. I could reinstall the dual Radeon 7950 HDs (along with the auxillary power supply they require) if I wanted to save on my heating bill, but that only gives me 3GB of video memory, so if the scene is bigger than that (which is almost a given considering the scnes I create) the process will crash.
But that is not the point. 1. reality does increase the speed (to check this is to make reference your previous render times). 2. The speed increase is not enough, some scenes are still slow for the new Iray standars.
To add insult to injury apparently iray is faster in DS 4.9. I dont do betas so I will see for myself later on. In either case Iray is chugging along nicely. 6 custom renders for a commished project that would of taken a few days with lux took less then 1. I know not everyone has the hardware to run iray to its potential, I myself had originally gone with an AMD fire pro when building my workstation expecting Reality / lux to be faster one day. Hence why I went with a Nvidia this time..
Is there a way to revert back to 4.0? The hybrid rendering mode there worked perfectly fine for me. Now it's been removed, and the other modes don't work nearly as well for me.
Fūrén Lóng Huǒ
Reality 4.1.1 for DS. Took about 8 hours to render on my laptop using only CPU accelerated.
AM's Wolf 2 with LAMH rendered in Luxrender through Reality.
Anyone try to render M7 with Reality 4? I am getting weird red skin and no textures. I'm pretty new at all of this so I dont have any idea why.
Probably because there is no preset for M7 in the reality database yet since it just came out, so you will have to set up the skin materials on your own.
Just remove 4.1 and reinstall 4.0. I had to do this since the new luxrender will not run on my OS
Thanks! :)
Is Reality the one renders until you stop it, or am I confusing it with something else. And if it is the one that renders until you stop it, how do you save the render when you're satified. Do you stop it or pause it and then save it or do you save it while it is still rendering. And what option do you pick to save the image? I looked at the help for the LuxRenderer and read about the menu choices, but I still couldn't find the answers to my questions.
Thanks.
Oh, and what is GPU? I think I saw in this thread that the LuxRender could use that but IRay could not.