Page 2 of 3
Re: Plugin Crashing Got strange error message
Posted: Tue Mar 22, 2016 11:27 pm
by morphious2013
well, using G2 characters instead of G3 works, but renders REALLY slow. At .6 ms/sec. With the rolled back driver and the V2.5 Plugin. Does Octane not able to handle the G3 models? And why so slow?
Re: Plugin Crashing Got strange error message
Posted: Tue Mar 22, 2016 11:28 pm
by morphious2013
we posted at same time, see my post. GeForce 690. Multi GPU turned off.
Re: Plugin Crashing Got strange error message
Posted: Wed Mar 23, 2016 3:20 am
by face_off
I just tested this on the latest 3.0.6 TEST release of the plugin.
Genesis2 = 6.2Ms/sec
Genesis3 = 6.7Ms/sec
It could be something specific in your scene causing the issue. Try turning ON the 4 Preferences->Scene Loading checkboxes so you start with a clean scene. Does a standard G3 figure then cause the error in 3.0.6?
Also, make sure you turn ON out-of-core texturemaps. And as suggested a few times, check the clocking on your card.
Paul
Re: Plugin Crashing Got strange error message
Posted: Wed Mar 23, 2016 12:21 pm
by morphious2013
I'm not upgrading to Octane 3 so need to fix this in V2. Yes, rendering a single figure is no problem. Use (2) G3 characters with hair, clothes, Gens attached, and add a scene like a living room or bedroom. That's when I get the error. Doesn't seem to matter what scene or props I use. Why would G2 characters work in this scenario but not G3 Characters? UGH, making me crazy. I tried your suggestions, and still the same result in V2.5 plug.
Re: Plugin Crashing Got strange error message
Posted: Wed Mar 23, 2016 12:51 pm
by face_off
I'm sorry you are frustrated - but I am not able to reproduce these issues, and no one else has reported problems such as these (and I'm sure the majority of users are using G3 with clothes, hair etc). So it's still looking like a hardware issue to me. You are not telling me what you have tried, so it's hard to know if you have covered everything. I got no response to a number of questions, such as are these issues happening in the Poser plugin. As a test, you could start rendering with the 3.0.6 version of the plugin (which gives the 999 cuda error), then try to export to ORBX and try rendering that scene in Octane Standalone - does there problem occur there? If so, upload the ORBX to Otoy so they can take a closer look.
But my best guess is that you have fired graphics card memory - since the more memory you use, the higher the probability of a cuda error 999.
Paul
Re: Plugin Crashing Got strange error message
Posted: Wed Mar 23, 2016 4:05 pm
by morphious2013
You can't get G3 Characters into Poser

(Unless I missed something) Also, I have another lesser card I will try. Just strange that the G3 Characters have problems, not the G2 ones.
Re: Plugin Crashing Got strange error message
Posted: Wed Mar 23, 2016 4:38 pm
by TRRazor
You can't get G3 Characters into Poser
Actually you can - although you have to change the weight mapping from dual quaternions back to TriAx, which half-asses the thing and doesnt really give you the full Genesis 3 in Poser.
More like a Genesis 2.5
http://redspecsss.deviantart.com/journa ... -593180634
Re: Plugin Crashing Got strange error message
Posted: Wed Mar 23, 2016 6:06 pm
by morphious2013
Thanks, but without full functionality, IMOP, what's the point. DAZ finally told me the G3 characters use alot more ram. So, maybe cranking up the out-of-core amount will
Re: Plugin Crashing Got strange error message
Posted: Wed Mar 23, 2016 10:16 pm
by morphious2013
OK, put in my GeForce 650Ti. Set the out of core to just over 13gb. Started with bed prop. The G3F, then her hair, Then G3M, Then his hair, and boom. Rendering after each addition. Got the render engine failure again. Checked the 4 boxes you told me to. Attached is a screen shot. Explain this BS please. I know my 650Ti GPU is good.
Re: Plugin Crashing Got strange error message
Posted: Wed Mar 23, 2016 11:04 pm
by face_off
That is a totally different Octane error to what you reported above. This Octane error is saying you ran out of VRAM. You've got 16GB CPU VAM, but allocated 13GB of that to out-of-core - try dropping out of core to 4GB. Regardess, a 2GB card might simply be too small for a scene that size - given DAZStudio and Windows will use a lot of that 2GB.
Also - you have Displacement mapping on that render. Try removing those maps - if the displacement amount is too high it will cause Cuda errors.
Paul