Loading...
> >

Older iRay prop crashes latest Studios

PtropePtrope Posts: 682
in The Commons

I bought a Dodge Charger III model from Turbosquid about 4 years ago, broke up the model into components, imported them in Studio, and then applied iRay materials - paint, metal, leather, rubber, etc. I created multiple scenes, rendered them several times, and saved the model with all its parented parts as a scene subset. Starting about a year ago, I found that loading either the saved scenes or the model crashed Studio. My default view is iRay preview, so I changed it to texture shaded, and the model loaded fine, and I could work with it and its parts. But changing the preview iRay crashed Studio again. This doesn't happen with any other models I've worked with, so I assume one of the shaders has a glitch in it, but I have no idea which one. I even tried changing all the surfaces to plain gray, but they're still iRay shaders, and even then, it crashes. Anything I should look for, any change that happened in the last couple versions of Studio that would cause the iRay module to crash based on a shader?

Comments

  • barbultbarbult Posts: 24,244

    Is you NVIDIA graphics driver at least as recent as the minimum version required for your installed Daz Studio version?

  • PtropePtrope Posts: 682

    Yes; the old RTX 2060 6Gb card actually died and I replaced it with an RTX 3060 12Gb, and made sure the right drivers were in place. Even with the new card, the Charger kills Studio.

  • MattymanxMattymanx Posts: 6,908

    Ptrope, 

    Save a new copy of the scene subset with just the default shader applied to the vehicle and props (no mpas) so that everything is just grey.

    quit and relaunch DS, load the new scene subset and try your view ports.  if it crashes, its the model. 

    If it doesnt crash then...

    Create shader presets from all the different surfaces from the car and props

    Make a new scene using a plane primative or cube primative.  Save it with its default shader.

    Apply the first shader, change between regular view port and iray viewport, and if it doesnt crash, save and reload and try again.  Then try the next shader

    If it doesn't crash with the shader test, then its a combo and you would need to figure that out by reloading each piece one at a time and applying its shader to test shats going on.

  • LeanaLeana Posts: 11,715
    edited December 2023

    Could the model be using .tif texture files on some surface settings (like a normal map) that you would have not removed when you tried your "grey test"? I remember recent-ish versions of Iray having problems with some of those.

    Post edited by Leana on
  • TheKDTheKD Posts: 2,691

    It could be the same shader error that was makin certain hairs crash, off the top of my head I forget what needed to be fixed to fix it yourself, was a channel that was taken out of the iray shader or something like that.

  • MattymanxMattymanx Posts: 6,908

    TheKD said:

    It could be the same shader error that was makin certain hairs crash, off the top of my head I forget what needed to be fixed to fix it yourself, was a channel that was taken out of the iray shader or something like that.

    That was a custom shader for OOT hairs that had the issue. 

  • TheKDTheKD Posts: 2,691

    Mattymanx said:

    TheKD said:

    It could be the same shader error that was makin certain hairs crash, off the top of my head I forget what needed to be fixed to fix it yourself, was a channel that was taken out of the iray shader or something like that.

    That was a custom shader for OOT hairs that had the issue. 

    Oh, it was like one OOT made themself? Then nevermind, probably not the same, unless OP used the hair shader as a starting point for the shader, which doesn't seem very likely at all lol.

  • PtropePtrope Posts: 682

    Mattymanx said:

    Ptrope, 

    Save a new copy of the scene subset with just the default shader applied to the vehicle and props (no mpas) so that everything is just grey.

    quit and relaunch DS, load the new scene subset and try your view ports.  if it crashes, its the model. 

    If it doesnt crash then...

    Create shader presets from all the different surfaces from the car and props

    Make a new scene using a plane primative or cube primative.  Save it with its default shader.

    Apply the first shader, change between regular view port and iray viewport, and if it doesnt crash, save and reload and try again.  Then try the next shader

    If it doesn't crash with the shader test, then its a combo and you would need to figure that out by reloading each piece one at a time and applying its shader to test shats going on.

    I think it would probably be a lot easier just redefining the surfaces from scratch. I can create each one, switch to Iray preview, and if it crashes, I know which one did it wink

  • Andrew_CAndrew_C Posts: 105

    Hmm, this reminded me to check if a pair of prop glasses whose shaders crashed the version of iRay in the previous version of Studio still crashes it in the lastest Studio. Looks like they fixed that bug & they added yours.

  • NinefoldNinefold Posts: 256

    Mattymanx said:

    TheKD said:

    It could be the same shader error that was makin certain hairs crash, off the top of my head I forget what needed to be fixed to fix it yourself, was a channel that was taken out of the iray shader or something like that.

    That was a custom shader for OOT hairs that had the issue. 

    Oh, I just ran into this problem myself recently. It's not a huge deal because I render in different software, but do you know the fix? 

  • LeanaLeana Posts: 11,715

    Make sure you install the latest version of the hairs as OOT has fixed quite a few of them.

    If you still have problems, check the surface settings and remove any map from its Transmitted Colour property

  • NinefoldNinefold Posts: 256

    Thanks, Leana! It's an older hair, but I actually just bought it a couple of weeks ago. I'll try your fix.

Sign In or Register to comment.