Page 1 of 2
Testing the demo, but having serious issues.
Posted: Sat Jan 02, 2016 5:16 pm
by ThetaGraphics
So I was looking into DAZ Studio in hopes of adding the Genesis 3 figures and aniblocks to my options, however I have no desire to leave Octane behind (I currently use the Poser Plugin), as Iray doesn't match up.
So I tried downloading the OcDS demo, however, in almost any scene (of complexity levels far lower than what I've managed in Poser) I keep getting this error upon opening the Octane viewport:
I have two GTX 670s, and the Poser plugin works just fine, so it shouldn't be a hardware issue. Is there a way to fix this? I have no intention of buying the full license if I'm just going to keep getting this error.
Re: Testing the demo, but having serious issues.
Posted: Sat Jan 02, 2016 10:59 pm
by face_off
This error occurs when the Octane API detects a render failure. What does the Octane Log say (that is the Messages panel at the bottom of the System tab in the OctaneRender Main window)?
Paul
Re: Testing the demo, but having serious issues.
Posted: Sun Jan 03, 2016 1:48 am
by ThetaGraphics
This is the error log of a simple scene of Genesis 3 with the Dark Storm outfit applied. (No other objects)
Re: Testing the demo, but having serious issues.
Posted: Mon Jan 04, 2016 2:49 am
by face_off
This is the error log of a simple scene of Genesis 3 with the Dark Storm outfit applied. (No other objects)
This error is coming from the Octane engine - so a little hard to determine the exact cause. Are you rendering with both your cards in the Poser plugin or just one? Do you get the same error if you render the basic Genesis 3 figure? If you turn off rendering on one of the cards, do you still get the error?
Paul
Re: Testing the demo, but having serious issues.
Posted: Mon Jan 04, 2016 6:39 am
by ThetaGraphics
Ramping up the Out of Core memory seems to have done the trick. It appears I was exceeding my video card's memory limits.
Now how do I change the inputs for the material nodes?
(such as changing a roughness node from a greyscale color to an image map?)
EDIT: Nevermind, figured out how in the node graph mode. Is NGE the only way or is there a method through the tree mode as well?
Re: Testing the demo, but having serious issues.
Posted: Mon Jan 04, 2016 12:03 pm
by face_off
Is NGE the only way or is there a method through the tree mode as well?
You can change everything via the Material tab - just click the Octane material in the "OctaneRender Materials" listbox, and edit on the right hand panel.
Paul
Re: Testing the demo, but having serious issues.
Posted: Tue Jan 05, 2016 2:44 am
by ThetaGraphics
Pretty impressed with some of the features so far now that its working.
Though there's another odd thing I'm experiencing with the NGE:
This screenshot is as small as I can make the NGE window (which is taller than a standard monitor, have to view it on my 4k to see the whole thing) and seems to be as close as I can zoom up on the node graph, which is too small to read?:
Re: Testing the demo, but having serious issues.
Posted: Tue Jan 05, 2016 3:01 am
by ThetaGraphics
Uh, nevermind, NGE seems to be working fine now. Guess DAZStudio just gets a bit quirky at times. o.O
Re: Testing the demo, but having serious issues.
Posted: Tue Jan 05, 2016 5:16 am
by face_off
Uh, nevermind, NGE seems to be working fine now. Guess DAZStudio just gets a bit quirky at times. o.O
Yes, DAZStudio seems to be a little random with window sizes. If you get in trouble, Window->Workspace->Off Screen Pane (Tab) Groups.
Paul
Re: Testing the demo, but having serious issues.
Posted: Sun Jan 24, 2016 3:55 am
by ThetaGraphics
Still on the demo, but I came across an odd glitch relating to the whole intersecting mesh/ray epsilon = hole glitch (any fixes planned for that by any chance, Otoy?)
Anyway, the hole changes size (and shape) depending on camera angle. The figure is Genesis 3 with Chace Hair. The only difference between the below images is camera angle (no geometry changes):