Toony Cam Pro Issue in newest version of Studio
Ghosty12
Posts: 2,065
Found in Studio 4.8 and before that ToonyCam Pro does not work like it used too the Outline ID part of it does not work like it did where you had different coloured sections for skin and eyes and so on during the first pass before the final render.. And it does not like backdrop pictures now I get the grey and white checkerboard bleeding into the backdrop picture during rendering and last but by no means least I get this error:
3Delight message #145 (Severity 1): S2073: 'Min' is not a parameter of shader 'brickyard/{bec77c4a-110f-465a-b648-b4186b0cecae}/shader_Imager'
Not sure how to get it to stop..
Any help please would be greatly appreciated thank you.. :)
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
I reported this problem (two times) to DAZ several month ago since last 4.7 version...Even waiting for a solution.
The trick to use ID is create images in several uniform colors and load in the ID color image parameter. Is tedious but it works. You also can test with image with designs in 2 or more colors and see interesting outlines.
An example of the trick in the attached file
...as I understand from issues that crippled AoA's Atmospheric and Graphic Art Cameras, as well as flagging SSS surfaces with the Advanced Lights, this may have something to do with changes to the Shader Builder that were made in 4.7.
For 4.7 there were changes related to API, I suppose this affect renderman related "objects"
Cool thank you for the info glad to know I am not the only one having this issue.. Would be nice to have a reply of sorts from Daz on the matter as to whether there is likely to be any updates to the affected products..
Thank you that PDF you posted is the exact issue that I get with the plugin very annoying.. :(
Yeah I was wondering what version of Studio it was, was not sure if it was 4.5, 4.6 or 4.7 all I know is that was when the problem had started and I abandoned using ToonyCam which is a shame as it is a good Plugin..
Woah, thanks for the workaround, GiGi_7! I've spent quite a bit of time investigating this and boy is this helpful! For what it's worth, I'm pretty sure this is an issue in the standard Outline renderer script also (which ToonyCam referenced heavily).
Anyway, I'm going to attempt proving out an automated work-around (adjusting the Render script).
It is part that I submitt to DAZ, here is where I think is the problem, it is a simple suspicion, withou true knowledge endorsing it:
"Toonycam pro came in DAZ store in February 2014, for DS4.5 or DS4.6, I don’t remember.
ID was working perfectly in DS 4.7 Public Beta 1. I test camera in this beta in depth. I install all by DIM since the postgre change
I believe (actually not sure) Toonycam ID worked in DS 4.7 Public Beta 2, build number 4.7.0.10.
When general release 4.7.0.12 came, Toonycam ID didn’t work. I tested this too."
Actually, yes, that is least...it's even less than least. Severity 1 'error' messages are NOT errors...they are informational messages, usually of a performance related nature. In this case, the parameter 'Min' is in the UI but NOT in the shader code. If 'Min' is supposed to be a minimum value, then it will default to 0. A negative value won't be able to be set...
More likely than not, this is because the value in the code is 'minimum' and in the UI, the value is "Min" (not just the label, but the actual name of the value).
All Severity 1 and many Severity 2 messages can be safely ignored.
Overall, I haven't looked too deeply into the problem, but I'm of the opinion that it isn't a problem with the way things are NOW, which actually seems to be the correct way, but rather that it was built around an INCORRECT method, before. And if it is the render script, then yes it should be fixable, fairly easily.
This message is not the current error. This message occurs since day one of Toonycam at February 2014. I get a seemed error in one of my SB shaders because I create a user parameter that is not used in the general macro.
To not have that error, when adding a parameter that is not in the macro, the actual parameter name and the name in the user parameters must match, not the labels...and case included...min and Min don't match.
Actually it's the Var AND Name fields that need to match...not just name alone. Label is irrelevant...but it is nice, for a sanity check, if it does match in both the Macro block(s) and the User Parameter blocks.
Yeah, I know where the Scripted renderer Outline & Outline Compositor scripts are failing. It seems to not like the way the outlineColor gets assigned to the outline shader. I am clueless as to the correct syntax.
I have been successful with proving an automated work-around. The gist of the idea is:
1. At render time, for each Color outline ID, generate a 200x200 dummy image file of that solid color. Map that new image file to the Outline ID Image map.
I'm working out the kinks, still but the concept seems solid as a workaround for now.
Hi,
I don't understand all your discussion and I'm not sure that my issue is the same as yours. English is not my language.
When I use toonycam, I launch first "ToonyCam Pro", then I launch "Render outlines on". I get this message : /Application/Daz 3D/DazStudio 4 64-bit/resources/Scripted Renderer/Outline Compositor/Outline Compositor.ds(a b e )
I can't write the tube caracter.
Is it the same problem. I have 4.8 version on a Mac.
Thank you.
It isn't the same problem, but I don't know if the root of these two problems is the same. I don't get any message when I click "Render outlines on", simply render change to render script in the render tab. I have windows 7, no idea about Mac.
Tried that idea and works great thank you.. Now to just get the errors to stop and I will be stoked.. :)
Scripted? Excellent idea...but It is beyond my knowledge
If you'd like to try my script adjustments, you're welcome to. I'm not sure they're 100% bug free, but they've been working for a couple weeks for me now. PM me if you're interested.
PM sent!
Cool thank you and PM sent as well.. :)
I don't know if this is related, but a lot of the additional script files throw dummy error messages for me. (Like "Error reading file, for details see log file" in the actual log file)
BTW, has anyone tried to contact the author about an official update fixing these issues? Successfully? Or is this essentially abandonware?
I could help but I don't have this product, the fix is the same for all other 3Delight cameras created before 4.7. If you feel comfortable browsing by folders and opening/decompressing/editing duf (using a text editor) files I could lead you to correct the issue.
Sounds easy enough. I would be interested.
Ok, then.
Some times the .DUF file does not contain the mentioned lines, that's because the actual camera is defined elsewhere, but referenced on top of the .DUF file with an .DSF extension, if this is the case edit the .DSF instead. If this is the case fix (edit) all .DSF file in the same folder.
HTH
@fornit,
Yes I've tried contacting the author and opened a support case with DAZ also. No action on it for 3 months. I too encountered what seemed like legitimate bugs in the helper scripts provided with ToonyCam. They didn't look incredibly hard to fix or rewrite, but I don't have ToonyCam anymore.
I did a "workaround" fix for the Color Id outline issue, which is broken for the same exact reasons the standard Scripted 3delight > Outline render script is broken (presumably code changes near the end 4.7 broke the acceptance of Color values to the shader being used). My impression is we get to fix this ourselves for now, since DAZ support did not recognize the bug affecting the standard script and claimed it was a ToonyCam specific issue.
That is one thorough walkthrough
Slight problem however: There is no matching string varValue in the toonycam folder or any subfolder. I don't think any of the files are compressed. I opened a few and afterwards just to make sure checked for the string "zigraphix" which was found in 45 files. Of cause the rest of your snippet looks very similar to the text in the top folder main files, unfortunately it does look very similar all over a file with 4796 lines
So unless you can narrow it down a bit i don't think will find it on my own.
@fornit, if I've interpreted @jag11's post correctly, you're on the right track. There are a couple of things I think may be confusing you.
VarValuelines may not exist in the ToonyCam DUF file. If that's the case, it's nothing to worry about (since DAZ save files only save properties which matter).MaxandValuelines. I suggest doing a find/replace function, replacing withI suggest trying this on the "main" ToonyCam camera file (the one you usually load) and see if the changes work and cause the errors to no longer manifest.
There isn't a single occurence of either "value" : [ "i", 39] or "max" : [ "i", 40] in the toonycam folder. I checked all occurences of max/value assignments to account for differences in formatting or whatever could cause a search to miss results and there is nothing even close to 39 or 40 in there.
Looking for a toon solution...I was about to ask if ToonyCam will work with iRay simple shaders, and found this thread instead
Is the issue fixed by DS 4.8?
Render engine are different. If you set iray 3delight doesn't work. Of course, you can render them separately and combine after in photoshop or so. Issue wasn't fixed in 4.8, but it is not a great problem if you work with normal outline. Only ID outline is affected, but workarounds work (the elaborated or the "by hand")
I have and play with both Toonycam and PWToon. I prefer PWToon for being better at drawing fine fiddly details (driven by bump/displacement), but it can be annoying in a big scene where distances mean I'm adjusting line widths constantly.
Whereas Toonycam produces pretty decent lines and images fast... assuming you don't hit a bunch of bugs and can figure out how to get it to make the lines you need.