Environment HDR issue
I'm currently using ManFriday's queue to render a sequence of scenes (I'm working on an animation), so what I'm doing is that I set up my scene and I do the whole animation on the timeline process, then I save every frame as a scene file so I can use the render queue to render the all at night. The problem is that when I come back the next morning I find some of the scenes been rendered with the default enviroment map, not the one I assigned. the problem seem to be random. because when I run the queue again after I made sure every scene has the map I want, and saved them multiple times just to make sure, the problem still appears for a random set of scenes.
I'm not sure if this could help but here are some additional info:
1- the scenes were created in daz studio 4.12 and I'm now currently rendering them on 4.15.
2- The enviroment map that I wanna use is an image, not a .hdr file. Also it's saved on a seperate hard disk, not the disk that I'm running daz from.
EDIT: I've been messing around with other setting now, and I've noticed that sometimes some values refuse to be set. For example the min sample, I've been trying to set it to 500 and it refuses and gets reset to 100. (even thought the default value is 5). even 5 doesnt work.
Comments
You could remove or rename the default HDR map (just untill you finish the project). The default HDR is in the instalation directory "~ Shaders > iray > Resources > "
Clean out all your temp files.
For the "Min Sample" setting. You will need to edit the "Parameter Settings" for that setting (LMB on the little cog icon in the "Min Sample" window) and disable "Use limits" (or change the "Max" setting)
It seems that the problem is general and not affected by one setting. Just now I set up a totally different scene, and I used a render setting preset (hdr map + dome rotation + tone mapping) I got from the store, saved it, went back to it later, then found out all the render settings (all, from general to enviroment) has been reset. the very same render preset is popular and Ive been using it for a long time since 4.12. I only started seeing this problem since 4.15.