Problem with Batch Render scripts in Studio 4.15
GRFK DSGN Unlimited
Posts: 1,100
To preface what I'm about to post about, I'm using the public beta version of 4.15 and I render in 3delight and I use IBL Master for my light setup.
My workflow is basically, I start a new file, usually have to change the render engine in the render settings to 3delight as sometimes Studio switches to IRay, though I seldom render a final scene. Sometimes I do change the drawing style to iray just to see what it would look like, anyways. I set my scene up, merge into the scene my light file that I set up using IBL Master. I then establish my cameras and then check my render settings and set them to my normals (I turn on the first one under General, starts with a P but can't remember the exact name at the moment), set my pixel samplings to 12 for x an y, turn gamma on and set it to 2.2 (IBL Master recommendation). I set up my cameras and then save the file. If I'm working on my comic then I'll repeat this process 3 more times for the different scenes on the page. After completing the last file, I had been using Draagonstorm's batch render script and setting the files to be rendered while I slept. When I was working in 4.12 I had no issues and things ran smoothly. when I moved up to 4.14, I began having the issue of scenes being switched over to being an iray render instead of 3delight. In the script, you can check so that settings in the scene file are used, which I had been doing. Somehow Studio was overriding the settings when it ran the script. I moved up to 4.15 because of Genesis 8.1. Because I was having issues with Draagonstorm's script, or so I thought, I began using Dimension3D's version. It worked fine for awhile until last night when I used it on one scene file. I started having the same issue of the script doing the scene in Iray even though it was saved as 3delight render settings. I even shut down Studio, opened up again and set-up to try the batch render again. Same results. Finally I just did the scene as a regular render and Studio didn't override and do Iray. Is there something somewhere I'm not doing right? Some box I'm not checking? Or something I've checked that I shouldn't? This seems to be a random problem and I don't know how to solve other than going back to 4.12.
Daz 3D is part of 
Connect
DAZ Productions, Inc.
7533 S Center View Ct #4664
West Jordan, UT 84084
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2025 Daz Productions Inc. All Rights Reserved.
Comments
Gee thanks for the help, guys...
The pa passed away. There won't be updates for this I am afraid unless someone else makes them.
3DL is (obviously) not very widely used these days, and your thread title doesn't make mention of 3DL, so you're unlikely to grab the attention of people who have the experience you need.
Sorry I didn't think I had to be that specific in the title. I may have run across a solution anyways. I did some research into the Environment and Tonemapper options. Seems those are required to be in the scenes these days. They used to be under render settings but aren't anymore. Added them to a few scenes and will test them tonight to see if that solved my issue. And regards to the vendor's passing, are you telling me that both vendors of the products I'm using have passed? I'm not looking for an update on either product. I was just asking if there was a setting that needed to be in the scene file in order to make them behave properly. Gee a guy asks for help for a problem he's having and gets bashed over semantics.
Do. Not. Bump.
Was. Not. My. Intention.
And yes, it seems adding the Environment Options and Tonemapper Options seems to have solved my problem. So if anyone else has this issue, there's at least one solution to try. Older scenes didn't seem to have that issue. Only scenes created in 4.15.
It's not exactly required, but as far as getting attention, specifically noting that it's a 3DL problem is more likely to get the relatively small 3DL userbase to notice it.
Yes, both Dimension3D and Draagonstorm have passed on.