Saving Iray render is borked.

FelixFFDS

I've been wracking my addled brain for a few months now.

When using the "regular" Daz Studio program, I can render and save in any mode except Iray.  Upon completing the render (or stopping it), the program freezes then closes out.  This does not happen with any of the other render modes - (Viewport/3Deight, etc). Just Iray.

I have no probelm rendering and saving when using DAZ Studio Beta Public Build.

Note that the problem persists when the Beta Public Build is released to became the release build (4.20.0.17 at this moment).

Reinstalling the release build does not cure it, so I assume it's one of the configuration files that remains.  My question is, which?

I am *almost* to the point of removing the DAZ release completely, wiping out all traces of the build(s) and reloading everything (of course, backing up "My Library", just in case).

Any tips/hints/pointers?

I have the latest Nvidia drivers for my card.

 

Thanks

 

StratDragon

theres a temp folder in users/[your account]/app data/roaming/DAZ3D/[version]/temp

is there any chance it's going in there before it crashes? Its a long shot but it could be an issue with the drive itself. is this an SSD or a rotational drive? if it's not a rotational HDD you might try to defrag it.
BTdubbs never defrag an SSD you're only thrashing it and deprecating it's lifecycle.

FelixFFDS

StratDragon said:

theres a temp folder in users/[your account]/app data/roaming/DAZ3D/[version]/temp

is there any chance it's going in there before it crashes? Its a long shot but it could be an issue with the drive itself. is this an SSD or a rotational drive? if it's not a rotational HDD you might try to defrag it.
BTdubbs never defrag an SSD you're only thrashing it and deprecating it's lifecycle.

Thanks - it doesn't appear to be there.  And the main C: drive where the DAZ temp folder resides IS an SSD drive.

 

Thanks again for the pointer

 

FelixFFDS

Installed a new download of DAZ 4.2 into a separate drive.  Iray render now works.... tempted to copy THOSE files to my "original" 4.20 installation.  What can happen? At least I have two installs working... (Beta build and "new" 4.20)