lux 1.6 and reality 4.3
Shagge
Posts: 74
I'm running into a couple of strange issues and i'm party sure i'm doing something stupid.
I'm using Reality 4.3 and Lux 1.6 with open CL.
The character is Gen3 and a genital morph for Gen3 as you can see the skin map does not quite match up and i'm not sure why i've setup the materials, opacity, volumes and modifiers to match the torso for the model but its still lightly off and i'm not sure why.
Another thing i'm running into is when i try to use the gpu's to render with reality lux will crash i'm not sure where the log is for that so i can see why.
This is what i get from windows log.
Log Name: Application
Source: Application Error
Date: 5/21/2017 2:16:03 PM
Description:
Faulting application name: luxrender.exe, version: 0.0.0.0, time stamp: 0x57333caa
Faulting module name: MSVCR120.dll, version: 12.0.21005.1, time stamp: 0x524f83ff
Exception code: 0xc0000409
Fault offset: 0x0000000000074a30
Faulting process id: 0x50bc
Faulting application start time: 0x01d2d26ef8f35ac2
Faulting application path: C:\Program Files\Reality_DS\lux\luxrender.exe
Faulting module path: C:\Program Files\Reality_DS\lux\MSVCR120.dll
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<TimeCreated SystemTime="2017-05-21T20:16:03.338719700Z" />
<EventRecordID>3797</EventRecordID>
<Channel>Application</Channel>
<Data>luxrender.exe</Data>
<Data>C:\Program Files\Reality_DS\lux\luxrender.exe</Data>
<Data>C:\Program Files\Reality_DS\lux\MSVCR120.dll</Data>
This is what I get out of the driver file.
Log Name: System
Source: nvlddmkm
Date: 5/21/2017 2:16:02 PM
Event ID: 13
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Description:
The description for Event ID 13 from source nvlddmkm cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\UVMLiteProcess6
Graphics Exception: ESR 0x50ce48=0xe000e 0x50ce50=0x0 0x50ce44=0xd3eff2 0x50ce4c=0x7f
the message resource is present but the message is not found in the string/message table
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">;
<System>
<Provider Name="nvlddmkm" />
<EventID Qualifiers="49322">13</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-05-21T20:16:02.870769700Z" />
<EventRecordID>3935</EventRecordID>
<Channel>System</Channel>
<Security />
</System>
<EventData>
<Data>\Device\UVMLiteProcess6</Data>
<Data>Graphics Exception: ESR 0x50ce48=0xe000e 0x50ce50=0x0 0x50ce44=0xd3eff2 0x50ce4c=0x7f</Data>
<Binary>0000000002003000000000000D00AAC0000000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>
If I use CPU works fine, and if I use SLI it appears to work but is blank sometimes if I just let it sit it will start to render. I have 2 nvidia 960's.
Daz 3D is part of 
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
Oh no. Genitals on the forum. Try turning SLI off. All 3D rendering applications suggest turning it off. GPU lux still has a lot of work to be done.
I will edit that now. I did not have sli running. But it crashes with both.
Yes, you can tell Reality to point to whatever version of Lux you like. It has been quite a while since I looked at Lux, but there should be a newer version. When was Reality 4.3 released?
I am not sure when it was released I reset my pc and reinstalled everything and saw that was the most recent version of 4 so i snagged it.
I attached a copy of the reality settings to the original post
NO exactly ... the latest versiojn of Reality install it';s own version of LuxRender which you cannot change the path to, however you coudl manually install a different version of LuxRender over the top of that.
Ok thats what I am noticing aswell. Also i tried it with SLI enabled and it does start the render in lux but stays black.
Oh, I'd forgotten that! What I do is rename the current lux folder something like lux-old and then unzip the weekly build or most recent stable into a new lux directory. Like I said, been a while, but I'm pretty sure that works as I can see my old lux folder there. I wouldn't install over the top of an older lux version though. That might create issues. 4.1.1.15288 was the last Reality version I used.
Ok figured out the skin mapping issue. Knew i was missing something silly. The gpu crash not sure yet but i'll keep tinkering and welcome any other suggestions.
How did you fix the skin issue? Glad you got it sorted.
GPU crashes are usually caused by:
- drivers
- texture complexity
- memory limit insufficient for the scene
try updating your drivers first. If that doesn't work the try the other options.
Cheers.
The skin issue is some items would not turn on or pull over the correct top coat since these are iray figures.
I will double check those and see what happens.
For geografts you will likely always need to go in and adjust the material settings in reality.
In general I have to switch things like genital props (or lekkulion head tails, for ex) to skin (from glossy default), then manually enter the gloss and spec to match the main figures torso settings (for ex), then go into the modifiers tab and do the same, make sure the bump/normal settings match and in the case of bump/normal math make sure the bump part of the math amount is set to .0008 (by default if a skin surface is using bump/normal combined reality will read this and set these numbers correctly, but if you manually convert the surface to a different surface type the math defaults to 1 and 1). And sometimes you will have to go in and manually put in textures where they should be as well if reality does not see them automatically.
...so unlike Iray, Lux doesn't default to CPU mode then and the process simply crashes?