3Delight Stand-Alone Not Working with DS 4.8.0.55

Morpheon

Now that I've switched over to DS 4.8, I can't get the 3Delight stand-alone renderer to work anymore. I can still compose a scene in DS and then tell it to render it out to an RIB, but when I try to render the RIB file, the stand-alone renderer locks up and I get an error message telling me that "i-display.exe has stopped working".

Up until a few days ago, I was using DS 4.7.0.12 with 3Delight stand-alone 11.0.168 -- I'm currently using DS 4.8.0.55, and I've tried this with both the 11.0.168 and the 12.0.5 versions of the stand-alone renderer, and neither works. I suspect that this new version of DS is not writing the RIB files correctly, causing i-display to crash. FWIW, I've never had an issue with the external renderer prior to this new version of DS.

Anyone else having this issue? And if so, have you found a solution (other than reinstalling the previous version of DS)?

Thanks...

BeeMKay

Just making sure: Whem you render the RIB, are you rendering in 3delight, or Iray?

Morpheon

lee_lhs said:

Just making sure: Whem you render the RIB, are you rendering in 3delight, or Iray?

The engine is set to "3Delight", same as usual. (I checked that out first, just in case). I haven't played with Iray much yet, and I don't even know if it can render out to a RIB file. I'm also using the same old lights and materials as before, and nothing that was made to work in Iray.

mjc1016

It's something on your machine...I've rendered about 5 dozen ribs in the past few days, all exported from 4.8...and that was in both 11.0.164 and 12.0.5.

When you go to render the rib, what is the command you use to start the render?

What operating system?

Specs? Memory, cpu, etc...

Any OS/security software updates? (Even new AV definition files)

Open the RIB file in a text editor and copy the first 3 lines (the ones that start with ##) and paste them here...

Morpheon

mjc1016 said:

It's something on your machine...I've rendered about 5 dozen ribs in the past few days, all exported from 4.8...and that was in both 11.0.164 and 12.0.5.

When you go to render the rib, what is the command you use to start the render?

What operating system?

Specs? Memory, cpu, etc...

Any OS/security software updates? (Even new AV definition files)

Open the RIB file in a text editor and copy the first 3 lines (the ones that start with ##) and paste them here...

Intel i7 3630QM 2.4 GHz
8 GB RAM
nVidia GeForce GT 650M
Windows 7 Home Premium 64-bit (6.1, Build 7601)

##RenderMan RIB-Structure 1.0
##Creator 3Delight 11.0.130 win64 (Jan 8 2015, 89d5e0) "Berto Durante"
##CreationDate Wed Jun 17 20:11:05 2015

As far as AV goes, the only thing I'm running is Malwarebytes. I haven't updated it in the last week or so, so DS 4.8 is using the same profile that the 4.7 version of DS and 3Delight stand-alone was using. Malwarebytes has never interfered with any of my graphics software in the past, and I really don't expect it to start doing so now.

Render Settings >> Advanced >> Engine: 3Delight
Render Settings >> Advanced >> Render to RIB
Select "Render" from the Render menu option
The render window pops up, and DAZ displays its little "Collecting RIB Dependencies" dialog box.
Once it concludes, close the render window, right-click on the RIB file, and select "Render with 3Delight" from the pop-up dialog.
The first window (renderdl.exe) comes up, it starts to process, and then a few seconds later, the "i-display.exe has stopped working" message appears.

One thing I discovered is that the stand-alone won't even run the example RIBs that come with it, so whatever problem there is has to be between the stand-alone itself and some interaction with my machine, and probably not something within DS 4.8 as I first thought.

mjc1016

Go to the folder that it saves the collected rib in...that's the one with the texture files and such. Then, try from the Search/Run on the Start Menu, typing in renderdl.exe .rib, this should, a few seconds/minutes later drop a render.tif in that folder.

If that works, then it's a problem with idisplay.

Morpheon

mjc1016 said:

Go to the folder that it saves the collected rib in...that's the one with the texture files and such. Then, try from the Search/Run on the Start Menu, typing in renderdl.exe .rib, this should, a few seconds/minutes later drop a render.tif in that folder.

If that works, then it's a problem with idisplay.

A TIF file has been created in the same directory the RIB file is located in everytime i-display has crashed, but it's always less than 1 MB in size and unreadable.

mjc1016

Yeah, that's typical for a crash...but if it works without invoking idisplay, the tif should be a bit larger than 1 MB, and readable...one of mine, 2560 x 2048 is around 6.6 MB.

Also, if you run i-display.exe from the command line, does it open and if it does, can you load an image in it?

Morpheon

mjc1016 said:

Yeah, that's typical for a crash...but if it works without invoking idisplay, the tif should be a bit larger than 1 MB, and readable...one of mine, 2560 x 2048 is around 6.6 MB.

Also, if you run i-display.exe from the command line, does it open and if it does, can you load an image in it?

Trying to run i-display.exe manually always leads to a crash, but a few seconds sooner than if it had been called by renderdl.exe.

Thanks for the help, man, but I'm gonna have to go -- I gotta get some sleep (didn't get much the night before, and I paid for it all day today at work -- can't go through that again tomorrow). I'm thinking it might be time to start planning on replacing this machine -- it's a couple of years old, and it's a Dell (which I've always preferred, but to be honest, Dell just ain't what it used to be), and this isn't exactly the first curve ball this thing has thrown at me.

Have a good one...