Daz3D Crashed with Plugin 2.10

[3dmania]

Hi,

I just reinstalled everything. I have the licence and everything. When I load up a G2F model DAZ crashes to the desktop. If I disable the plugin, everything works.

The crash however only happens if I load up a character model. If I just load up a scene model, everything is fine. The crash happens when Octane loads up the materials

Here is a SS of my preferences

Please help, thanks

[Tugpsx]

Which GPU do you have?
How much ram on GPU?
Can you load any other model like V4 or G1?
Do you use separate GPU for display and rendering?

[3dmania]

This is the error I get

DAZStudio.exe caused ACCESS_VIOLATION in module "C:\Program Files\DAZ 3D\DAZStudio4\QtCore4.dll" at 0033:0000000062C03CC5, QMetaObject::cast()+37 byte(s)

I have 3 GTX 680s with 4GB VRAM. I used these for a year before with version 1.2x without a problem.

My Render GPUs are seperate from my display GPU. I can load some models. like V4.2,V6 and G2F and also props. But whenever I load A6,L6,G6 or other newer models it crashes when octane processes materials. I already tried reinstalling the plugin to no effect.

[SimonJM]

Could the causal link be AoA SSS shaders on the loaded characters?

[3dmania]

could be,

is there an easy way of disabling the AoF shader from the models?

[sikotik13]

The simplest would be to change them to a different character, or selecting a different shader, then applying that, if you're trying to use a particular skin.

Example: Select all surfaces, hold [Control] while double clicking the Daz default shader, and selecting ignore images. Leaves current maps in place, but switches the shader to the Daz default.

[SimonJM]

About the only way is as sikotik says, or to load a full texture set that is not AoA SSS-based, as you would do normally.

[3dmania]

well, thats a big tend in my workflow, especially its something that can be easily forgotten, and then boom crash, start all over. I think I will stick with 1.2 until sometime in the next century when 2.x becomes stable

[sikotik13]

Out of curiosity, since I've only managed to crash it trying to do anything from a .duf load, or trying to open an old preset in NGE, is it only AoA SSS based skins? I haven't found any that crashed me yet, but if you know of a particular one that crashes for you every single time, I could try it out tonight to see if I have the same issue at least. If you have more than one, I can check to see which ones I have and test them, then, if I don't have the same issue, we can see what the difference between your system and mine is that might be a problem. If you feel like it, anyway. Figured I'd offer to help try to pin down the issue.

[SimonJM]

I suspect it might be any shader that 'diverges' from having standard labels or values for some of the properties - not sure what it was but there's one (at least) that OcDS 1.2 passes through with an opacity of -1 (quite cunning with a scale of 0 to 1). I'd guess there's something that comes over as a 'bad value' that later causes OcDS to choke.