OcDS PROBLEMS RESULTING IN CRASHES - read & post here...

[sikotik13]

This scene consistently gives me an nVidia 999 failure using standalone and Poser plugin versions greater than 1.54
At version 1.54 everything works perfectly, and all geometry in the scene is rendered.

Anything greater than 1.54 of the standalone or plugin version is missing scene geometry in the render and crashes to error 999 after a minute or so.

I've been able to save the scene as an 'orbx' (80MB), but it's too big to post here or in other forums for analysis.
So I have included a dropbox link so it can be downloaded and tested by others.

https://www.dropbox.com/s/8gyywhu6y1zsbzo/loft.zip


Thanks for any help.

System:
8 Core 3.50 GHz Intel Core i7-3770K
RAM: 32GB
nVidia Titan 6GB
Windows 7 - Service Pack 1
nVidia Driver Version: 335.32

You should probably post this in the Poser plugin forum, as this is a different developer for a different plugin.

[AtticusBones]

OcDS 1.2 is causing DAZ 4.6 to crash whenever I use Autofit (specifically gen 4 on Genesis).
Is this an issue someone's found a solution to, or do I just need to hold tight for the update?

[t_3]

OcDS 1.2 is causing DAZ 4.6 to crash whenever I use Autofit (specifically gen 4 on Genesis).
Is this an issue someone's found a solution to, or do I just need to hold tight for the update?

what might help is to turn live geometry updates (and/or even auto mats) off during autofit and reload the scene afterwards.

the plugin doesn't get any direct notice from studio that there is autofitting going on, or that it did end, and this hasn't changed. i have of course spent some time in how to make it better for the update, i.e. by watching popup dialogs and parse their titles (probably dirty but the only measure i have found so far) but this still means a good amount of guessing involved...

[Isotemod]

Indeed never ever load an object and have it directly autofit onto a figure whilst auto mats is on. its a lottery with a high chance of crashing.

Best way is either never use auto mats( which is reccomended for new people in my opinion due to the plugin not having a undo button for its material changes) or cancel the autofit procedure on load so the materials are created before Daz attempts any rigging changes to the object and allow it to create the materials then fit to afterwards.

[AtticusBones]

Worked like a charm. Thanks for the speedy reply, and double thanks for all the hard work you put into developing the plugin, t_3.

[garand3d]

Hi all,
Recently I upgraded my GPUs from 2 Asus GTX 660s to 2 Asus GTX Titan BLACKs.
I noticed now that DS is more prone to crashing particularly when I load a new figure, change material type in the NGE or merge two scenes together.
I've been using 1.2 since I had my GTX 660s, and it was working great. The program would crash now and then, especially when I perform the above mentioned operations, but it was nowhere near as frequent as now.

Also on the System tab Octane is showing this message:

12:58:44.769: Unknown Nvidia GPU model found ! ()
12.58.44.766: +++++ Plugin Running

While on the Device settings clearly OCDS recognizes the GPU models as GeForce GTX TITAN Black 1 & 2. (and no, I'm not using SLI)

I wonder if this is responsible for the more frequent crashes.
This is making me sad as the reason I invested in new GPUs is for OCDS. But instead now DS has become unstable at best.
Has anybody had this problem before? If yes could someone please point me to an existing thread on a workaround or solution?

Thanks!

[t_3]

hi garand3d,

the noted line (unknown gpu model) is just because the titan black came out after the last plugin release; the plugin checks card/gpu types against an internal list, merely to point out slow or unsupported cards (is going to be replaced by an online check in future releases to avoid that).

1.2 development was done with titans, and since the titan black is based on the same hardware, that alone should not lead to extra problems.

can you pls. give me some examples what causes problems? in addition it would be helpful if you pm me crash logs from the studio crash reporter tool, that usually pops up if studio quits unexpectedly, as well as the debug.log file from the %HOMEDIR%\OctaneRender folder.

since you had upgraded from 660s - have you also upgraded your psu? e.g. what is the current psu's wattage?
does problems persist if you only activate a single gpu for rendering?

[garand3d]

Hi t_3,

Thank you for your reply.
I've been trying to replicate the errors this morning but to no avail, I was not able to get DS to crash no matter what. Could be that some parameters that are usually a part of my workflow were missing. Will run some more tests and see if I can't reproduce the errors from working on my current project.

In the meantime, allow me to answer your questions,

can you pls. give me some examples what causes problems?

These are the ones that happen almost consistently, and have been plaguing me since the day I got OCDS. Although back then they didn't happen as often as now, as I said before these crashes seem to increase in frequency after I upgraded my GPUs. And they happen regardless whether I have the OCDS render window open or closed.

- Having a figure or a prop already on the scene and loading another one would cause DS to crash. From observation, it almost always happens right after Octane is done converting the DAZ materials.
- Kinda related to the previous one, applying a new texture whether via MAT preset or manually loading it has caused DS to crash, regardless how many distinct figures were on screen.
- Merging two scenes together would cause DS to crash, even when said scenes only had one figure/prop each.
- Changing material types from within NGE or moving a slider in it would crash DS, this has happened numerous times, again regardless how many figures are on scene.

in addition it would be helpful if you pm me crash logs from the studio crash reporter tool, that usually pops up if studio quits unexpectedly, as well as the debug.log file from the %HOMEDIR%\OctaneRender folder.

Will do. I think it's important to be scientific about this, I'll run tests with different parameters and PM you whatever crash logs that I get.

since you had upgraded from 660s - have you also upgraded your psu? e.g. what is the current psu's wattage?

I've been using a Corsair AX1200 (1200 watt) since I had my 660s, could this be a problem? Also I don't know if this could be relevant, my CPU is liquid cooled, I'm using H80i.

does problems persist if you only activate a single gpu for rendering?

Yes. From experience, crashes occur at more or less the same frequency no matter how many GPUs are activated.

[Tugpsx]

The new GeForce Game Ready driver, release 340.52 WHQL, may help with some Video driver issues some people are experiencing.
Also if you have a single video card you may occasionally have video related issues.
It is best to have a separate card for program interface than the render card. Doing this allows Octane to use all the cards memory to load your scene while the other card is used to display interface.
This is a more stable approach and less prone to video issues.

[Hubby72]

- Having a figure or a prop already on the scene and loading another one would cause DS to crash. From observation, it almost always happens right after Octane is done converting the DAZ materials.
- Kinda related to the previous one, applying a new texture whether via MAT preset or manually loading it has caused DS to crash, regardless how many distinct figures were on screen.
- Merging two scenes together would cause DS to crash, even when said scenes only had one figure/prop each.
- Changing material types from within NGE or moving a slider in it would crash DS, this has happened numerous times, again regardless how many figures are on scene.

These are excactly the same things happens often in my installation. I have a GTX780 zotac with 6GB VRAM.

I changed my workflow so that i created a scene completly before i do anything in OCDS.
When i start working in OCDS setup lights, Mats etc. I save very often.

Sometimes it crashed by just changing the material setings in NGE from diffuse to mix or what ever.
Sometimes it add a prop after i did a some rendering. Then it crash.

I got things like that also often.
But usually if you just load a prop into DAZ the plugin only should load the geometry data. I add etxtures always later.

Best Tip save often. Even if you are unsure. If you do one of these listed things from you above save before