3Delight rendering errors when 64-bit & 32-bit studio loaded simultaneously?

genius_3587271

I have both the 32-bit & 64-bit versions of Daz Studio 4.12 installed. The 32-bit for lip-sync; the 64-bit to render 3Delight (the 32-bit crashes whenever I try to render). Until a few days ago I never had both launched simultaneously; but as I've prepared more sequences for render I decided to try editing in the 32-bit version whilst the 64-bit version was rendering. It mostly seemed to work.

But then I noticed a few frames rendered darker than the rest - investigation showed a few frames where point tlights had changed from "on" to "specular" - I assumed I must have done this accidentally; so I corrected, re-rendered - all OK. I also started taking more, and more frequent, backups of the DUF files.

But then it started to happen repeatedly - even though the backup files proved I hadn't orginally selected "specular". 

And since then I've run 100s+ frame renders unattended without problem - so it does seem to be working on both versions simultaneously which is the catalyst.

And just now I had a render which was fine until I launched the 32-bit version; but immediately after launch every frame was rendering very dark, with many assets missing (e.g. all the characters were suddenly bald). Stop the render & re-start - all OK.

As I said above, I've only been trying this over the last couple of days, and I so I haven't done this enough to get statistically reliable data to formally define a bug (if/when I do I will submit). I just wondered if anyone else had seen the same issue?

P.S. I am aware from searching forums that there is talk of not allowing multiple instances of the same executable - but searching those I couldn't find my specific set of observations.

 

genius_3587271

It turns out I was suffering from a coincidence with the point lights issue. I was trying to get steps changes in point light brightness - when I do this, other keyframes were automatically inserted setting the odd frame to "specular". I realised this when the problem showed up again when I been avoiding running more than one Daz Studio instance. And the reason it originally happened more than once is, I think, due to me copying scenes where this had already occured.

The second issue does still repeat when I launch the 32-bit version whilst the 64-bit version is rendering (which assets are impacted seems to vary each time) - but it seems (so far, so good) that editing & saving scenes in the 32-bit version is "safe" whilst the 64-bit version is rendering.