Loading...
> >

[Released] Render Doctor [Commercial]

1234568

Comments

  • tharangarajakarunatharangarajakaruna Posts: 0

    Hi, I just discovered render doctor today and I must say a HUGE thank you for this awesome product. I facing a slight problem though and was wondering if you could help me out. I even watched your YT tutorial and still can't get it to work. I am trying to render 3 camera views at once, I have selected the cameras in the render tab, given a file path, left naming as default, and selected the scene resolution and unchecked simulate render. But every time I render it only renders one camera. How can I fix this and get renderings of all three cameras? 

     

    Thanks

    1.jpg
    1117 x 1243 - 150K
    2.jpg
    1120 x 1247 - 158K
    3.jpg
    1121 x 1247 - 202K
  • mdk_zmdk_z Posts: 3

    Hello, when I attempt to render the displays shows it's producing images but nothing actually get's written out, I've gone through the logs and found a DEBUG level entry as follows - is this critical?

    "2022-09-26 16:02:09.509 [DEBUG] :: ERROR: function text() {

    [native code]

    } Property not found"

    I've tried multiple different scene files and folders however nothing seems to work.

    1.png
    958 x 870 - 67K
    2.png
    1152 x 870 - 66K
  • RiverSoft ArtRiverSoft Art Posts: 6,371

    tharangarajakaruna said:

    Hi, I just discovered render doctor today and I must say a HUGE thank you for this awesome product. I facing a slight problem though and was wondering if you could help me out. I even watched your YT tutorial and still can't get it to work. I am trying to render 3 camera views at once, I have selected the cameras in the render tab, given a file path, left naming as default, and selected the scene resolution and unchecked simulate render. But every time I render it only renders one camera. How can I fix this and get renderings of all three cameras? 

     

    Thanks

    That looks right.  When you click the "Render" button at the bottom of the "Render Cameras" tab, what does the log say?

  • RiverSoft ArtRiverSoft Art Posts: 6,371

    mdk_z said:

    Hello, when I attempt to render the displays shows it's producing images but nothing actually get's written out, I've gone through the logs and found a DEBUG level entry as follows - is this critical?

    "2022-09-26 16:02:09.509 [DEBUG] :: ERROR: function text() {

    [native code]

    } Property not found"

    I've tried multiple different scene files and folders however nothing seems to work.

    First, I think it is very dangerous to set the output directory to the Daz Scenes folder as it might overwrite the icon images for scenes in the directory.  Write out to a temp folder somewhere else. 

    When you click render button, what does the log say?

  • mdk_zmdk_z Posts: 3

    RiverSoftArt said:

    mdk_z said:

    Hello, when I attempt to render the displays shows it's producing images but nothing actually get's written out, I've gone through the logs and found a DEBUG level entry as follows - is this critical?

    "2022-09-26 16:02:09.509 [DEBUG] :: ERROR: function text() {

    [native code]

    } Property not found"

    I've tried multiple different scene files and folders however nothing seems to work.

    First, I think it is very dangerous to set the output directory to the Daz Scenes folder as it might overwrite the icon images for scenes in the directory.  Write out to a temp folder somewhere else. 

    When you click render button, what does the log say?

    Hi, after removing 'simulate renders' it somehow works - I won't touch anything now, seems to be fine :)

    Thanks 

  • RiverSoft ArtRiverSoft Art Posts: 6,371

    mdk_z said:

    RiverSoftArt said:

    mdk_z said:

    Hello, when I attempt to render the displays shows it's producing images but nothing actually get's written out, I've gone through the logs and found a DEBUG level entry as follows - is this critical?

    "2022-09-26 16:02:09.509 [DEBUG] :: ERROR: function text() {

    [native code]

    } Property not found"

    I've tried multiple different scene files and folders however nothing seems to work.

    First, I think it is very dangerous to set the output directory to the Daz Scenes folder as it might overwrite the icon images for scenes in the directory.  Write out to a temp folder somewhere else. 

    When you click render button, what does the log say?

    Hi, after removing 'simulate renders' it somehow works - I won't touch anything now, seems to be fine :)

    Thanks 

    Ah, yes.  "Simulate Renders" is designed for you to see the log of what WOULD HAPPEN, but does not actually write any renders out.  

  • TherewolfTherewolf Posts: 3

    I just recently purched Render Doctor and I'm having a very hard time with it. 

    All my scenes have 3 cameras, a close up, a wide, and a medium shot camera. Labeld Cam1, Cam2, Cam3. I want to batch render all the scenes using only one camera per scene, Such as Scene 1 would use Cam 3, Scene 2 would use Cam1, and so on. Is this possible with Render Doctor? 

  • RiverSoft ArtRiverSoft Art Posts: 6,371

    Therewolf said:

    I just recently purched Render Doctor and I'm having a very hard time with it. 

    All my scenes have 3 cameras, a close up, a wide, and a medium shot camera. Labeld Cam1, Cam2, Cam3. I want to batch render all the scenes using only one camera per scene, Such as Scene 1 would use Cam 3, Scene 2 would use Cam1, and so on. Is this possible with Render Doctor? 

    If the scenes are saved with the camera you want to render as the current camera, it is easy as you can just add all the scenes to the Render Scenes tab and click the "Current Camera" for the Render Scenes Camera.  If you wanted to use ONLY Cam1 (or 2 or 3) for all the scenes, you can use the "Match Labels" option for the Render Scenes Camera and fill in "Cam1" for the label.  You could also fill in "Cam[0-9]" to have it render Cam1 Cam2 and Cam3 for ALL the scenes.

  • vanishvanish Posts: 39

    Product: Render Doctor v1.1

    OS: Windows 11

    DAZ Studio: 4.21.0.5 and 421.1.26

    Issue: This is a long one, so bear with me. I have been trying to render large groups of shader presets using a material ball scene. This sometimes works flawlessly, other times It immediately fails.I don't think the problem is directly the RD script, but I'm hoping explaining what is happening will help you to find a way around the problem.

    How it appears: Select a group (2 or more) shader presets and open Render Doctor. (This happens whether selecting the presets and clicking a custom shortcut, clicking RD in the Scripts menu, or loading the RD script and using Add Files or Add Directory) Upon clicking the Render button, the object in the scene is selected very briefly, and a dialog opens and shuts immediately.No furhter action is seen.

    Here's what is bizaare about it. You have to cancel RD and then you're free to continue using DAZ Studio as you want, including rendering successful groups of presets, BUT as soon as you close DAZ Studio, it throws up the crash reporter. Essentially, when the dialog flashes and does notrhing, Studio has crashed, but continues to function until closed. Neat trick.

    Additional Strangeness: Selecting even a single preset in the failed group and triggering RD has the same issue UNLESS you apply the preset to the object first, then it will apply the prest and render as expected. This can be done one by one just fine. Further, some preset groups only have a subset of presets that go through this failure. I was rendering icons and tips for the nvidia vMaterials 2.0.0 presets. This worked all the way down to the Stone\Polished Granite folder where it fails. The presets after that folder alos render fine. Go figure. I haven't been able to determine what about these presets could be different. Usually, it is whole sets from a single creator that fail, but the nvidia ones threw me a bit.

    Finally: I confess I haven't tried to reproduce this on my Mac. I'd need to reinstall the apps there. (My nvidia card in my Windows box has more support in 3D than Metal on the Mac, so... yeah. Sad but true) If desired I am willing to do that and test. I'm also not afraid to get my hands dirty trying things if needed. I've been a professionla software engineer for 25+ years, so nothing new to me.

  • barbultbarbult Posts: 23,164
    edited December 2022

    @vanish I haven't been able to reproduce this. I'm using Render Doctor v1.1, in DS 4.21.1.26 Public Build, on Windows 10.

    • I created a cylinder primitive and selected it in the Scene pane.
    • Since shader presets are going to be rendered, I selected the Default surface of the cylinder in the Surfaces pane. The cylinder primitive uses the Iray Uber (MDL) shader.
    • I selected four shader presets in the Content Library pane. They were Iray Uber (MDL) presets from the Monochromatic Iray Shaders product.
    • I ran Render Doctor from a custom action icon I added to my tool bar.
    • The Add Presets dialog popped up and I chose Replace.
    • The main Render Doctor dialog opened.
    • I clicked the Render tab on the left and chose Render Presets tab on the top. My four shader presets were shown in the  window and each had the checkmark beside it.
    • In the other tabs along the left, I selected the options I wanted to use.
    • I went back to the Render tab on the left and clicked the Render button near the bottom.
    • All four presets were applied sequentially to the cylinder and the renders were performed as expected.
    • Render Doctor completed and displayed that statistics and log.
    • I clicked the OK button to dismiss the statistics pop up.
    • I clicked Save to close Render Doctor.

    Some thoughts: Are you using some unusual non-MDL shader presets? Are you forgetting to select the object surface in the Surfaces pane?

    Edit: I reread your message. Maybe I misinterpreted it. I thought you were saying it was failing in general when selecting multiple shader presets, and the additional strangeness was just an extra problem. Maybe you meant that it worked fine with multiple shader presets, and only failed with specific Nvidia vMaterials shaders.

    Edit again: So I tried four shader presets from NVIDIA vMaterials 2.0.0 in the Stone/Granite Polished folder. They worked fine, too, and rendered as expected. This is the log:

    16:00:08 GMT-0500 (Eastern Standard Time): Starting Rendering (simulated=false) for 4 images

    16:00:08 GMT-0500 (Eastern Standard Time): Applying preset N:/DAZ 3D/Studio/vMaterials for DazStudio 2.0.0/Shader Presets/NVIDIA vMaterials 2.0.0/Stone/Granite Polished/Polished Granite - Morning Rose.duf

    16:00:13 GMT-0500 (Eastern Standard Time): Queuing nodes for render (group=true):

    16:00:13 GMT-0500 (Eastern Standard Time): pCylinder(11bdoa8_11bdoa8)16_6 (Cylinder)

    16:00:13 GMT-0500 (Eastern Standard Time): Render 256 x 256 Iray Image: N:/DAZ 3D/DAZ Renders/Polished Granite - Morning Rose.tip.png

    16:00:14 GMT-0500 (Eastern Standard Time): Applying preset N:/DAZ 3D/Studio/vMaterials for DazStudio 2.0.0/Shader Presets/NVIDIA vMaterials 2.0.0/Stone/Granite Polished/Polished Granite - Golden Galaxy.duf

    16:00:19 GMT-0500 (Eastern Standard Time): Queuing nodes for render (group=true):

    16:00:19 GMT-0500 (Eastern Standard Time): pCylinder(11bdoa8_11bdoa8)16_6 (Cylinder)

    16:00:19 GMT-0500 (Eastern Standard Time): Render 256 x 256 Iray Image: N:/DAZ 3D/DAZ Renders/Polished Granite - Golden Galaxy.tip.png

    16:00:20 GMT-0500 (Eastern Standard Time): Applying preset N:/DAZ 3D/Studio/vMaterials for DazStudio 2.0.0/Shader Presets/NVIDIA vMaterials 2.0.0/Stone/Granite Polished/Polished Granite - Giallo Fiorito.duf

    16:00:25 GMT-0500 (Eastern Standard Time): Queuing nodes for render (group=true):

    16:00:25 GMT-0500 (Eastern Standard Time): pCylinder(11bdoa8_11bdoa8)16_6 (Cylinder)

    16:00:25 GMT-0500 (Eastern Standard Time): Render 256 x 256 Iray Image: N:/DAZ 3D/DAZ Renders/Polished Granite - Giallo Fiorito.tip.png

    16:00:26 GMT-0500 (Eastern Standard Time): Applying preset N:/DAZ 3D/Studio/vMaterials for DazStudio 2.0.0/Shader Presets/NVIDIA vMaterials 2.0.0/Stone/Granite Polished/Polished Granite - Emerald Pearl.duf

    16:00:31 GMT-0500 (Eastern Standard Time): Queuing nodes for render (group=true):

    16:00:31 GMT-0500 (Eastern Standard Time): pCylinder(11bdoa8_11bdoa8)16_6 (Cylinder)

    16:00:31 GMT-0500 (Eastern Standard Time): Render 256 x 256 Iray Image: N:/DAZ 3D/DAZ Renders/Polished Granite - Emerald Pearl.tip.png

    16:00:32 GMT-0500 (Eastern Standard Time): Rendering Completed in 23 secs 671 msecs.

    Post edited by barbult on
  • vanishvanish Posts: 39
    edited December 2022

    @Barbult Thank you for that detail! So yes, it sometimes works fine and others it crashes Studio. I am intrriguied by your success with the polished granite presets that fail consistenly for me. (All others in the vMaterial set work as expected) Hmm. I wouldn't think the geometry would have anything to do with it, or the HDRI lighting I'm using. I will try the 4 you havfe in that log and see what I get.

    EDIT: I just tried with the 4 you ran successfully selected. It crashed immediately. Here is the log as it stands:

    16:12:56 GMT-0600 (Central Standard Time): Starting Rendering (simulated=false) for 8 images

    16:12:56 GMT-0600 (Central Standard Time): Applying preset D:/3D Graphics/My DAZ 3D Library/Shader Presets/Iray/NVIDIA vMaterials 2.0.0/Stone/Granite Polished/Polished Granite - Golden Galaxy.duf

    So I'm left with my original fear that it is something specific to my setup. Crap.

    Post edited by vanish on
  • barbultbarbult Posts: 23,164
    edited December 2022

    Maybe there is some "order of operations" problem. If you restart Daz Studio and immediately try your granite shaders test does that crash? Or does it only fail after having processed some other presets successfully?

    Are there any significant messages in the Daz Studio log?

    Post edited by barbult on
  • barbultbarbult Posts: 23,164

    I do get this error in the log, even for shader preset renders other than the NVIDIA ones, so it probably isn't significant.They render in spite of the error message.

    2022-12-26 18:03:40.118 [DEBUG] :: ERROR: function text() {
        [native code]
    } Property not found

     

  • barbultbarbult Posts: 23,164

    I have a Post-Load Delay of 5 seconds (set on the Output Options tab). I don't know if that has any impact on my success. Also, I'm rendering to PNG.

    Have you tried simulating the renders (set on the Render Options tab)? That will run through the process without actually doing the rendering. It might help determine whether the problem is in applying the preset or rendering it.

  • vanishvanish Posts: 39

    I tried immediately after starting DAZ Studio, same issue. I created a whole new scene with the same geometery, same issue. I have played with the Post-Load Delay before from 5-15 seconds.I will dig through the DAZ logs as soon as I can remmber where they are. Heh.

  • vanishvanish Posts: 39

    This is the log of my last attempt.

    2022-12-26 17:23:07.735 Iray [INFO] - MDLC:COMPILER ::   1.0   MDLC   comp info : Loading module "::vMaterials_2::Stone::Granite_Polished" from "D:\3D Graphics\My DAZ 3D Library\Runtime\mdl\vMaterials_2\Stone\Granite_Polished.mdl".
    2022-12-26 17:23:07.737 [INFO] :: Applying animations...
    2022-12-26 17:23:07.739 [INFO] :: Finished asset load (merge): 0m 0.29s - /Shader Presets/Iray/NVIDIA vMaterials 2.0.0/Stone/Granite Polished/Polished Granite - Golden Galaxy.duf
    2022-12-26 17:23:07.743 [INFO] :: Unlocking viewport redraw...
    2022-12-26 17:23:07.743 [INFO] :: Viewport redraw unlocked.
    2022-12-26 17:23:07.743 [DEBUG] :: Pausing at least 5000
    2022-12-26 17:23:07.798 [WARNING] :: QWidget::repaint: Recursive repaint detected
    2022-12-26 17:23:07.799 [WARNING] :: QWidget::repaint: Recursive repaint detected

    Not sure what the "applying animations" is all about.

  • vanishvanish Posts: 39
    edited December 2022

    Aha! I got a complete log this last time. Unhandled exception in the script library, according to this, plus that recursive redraw error. Relevant part of the log below:

    2022-12-26 17:28:49.798 [INFO] :: Finished asset load (merge): 0m 0.28s - /Shader Presets/Iray/NVIDIA vMaterials 2.0.0/Stone/Granite Polished/Polished Granite - Baltic Red.duf
    2022-12-26 17:28:49.799 [INFO] :: Unlocking viewport redraw...
    2022-12-26 17:28:49.799 [INFO] :: Viewport redraw unlocked.
    2022-12-26 17:28:49.800 [DEBUG] :: Pausing at least 5000
    2022-12-26 17:28:49.877 [WARNING] :: QWidget::repaint: Recursive repaint detected
    2022-12-26 17:28:49.878 [WARNING] :: QWidget::repaint: Recursive repaint detected
    2022-12-26 17:28:49.899 [INFO] :: Loaded image: baltic_red_diff.png
    2022-12-26 17:28:49.928 [INFO] :: Loaded image: baltic_red_diff.png
    2022-12-26 17:28:49.932 [WARNING] :: ..\..\..\..\..\src\sdksource\general\dzscript.cpp(1189): Unhandled error while executing script.
    2022-12-26 17:28:49.932 [WARNING] :: QScriptEngine::popContext() doesn't match with pushContext()

    Curious that it does appear to be applying the texture twice...

    Post edited by vanish on
  • barbultbarbult Posts: 23,164
    edited December 2022

    It is interesting that things that seem rather catastrophic, like repeated recursive operations,unhandled error, and stack push/pop mismatch are only WARNING, not error. The only real clue to where this trouble is happening is the [WARNING] :: ..\..\..\..\..\src\sdksource\general\dzscript.cpp(1189), but that doesn't even seem to be a line reference in the Render Doctor script, but maybe some generic script function it calls?????

    My log corresponding to the snippet you posted is here:

    2022-12-26 18:03:23.480 [INFO] :: Applying animations...
    2022-12-26 18:03:23.482 [INFO] :: Finished asset load (merge): 0m 0.34s - /Shader Presets/NVIDIA vMaterials 2.0.0/Stone/Granite Polished/Polished Granite - Baltic Red.duf
    2022-12-26 18:03:23.483 [INFO] :: Unlocking viewport redraw...
    2022-12-26 18:03:23.483 [INFO] :: Viewport redraw unlocked.
    2022-12-26 18:03:23.483 [DEBUG] :: Pausing at least 5000
    2022-12-26 18:03:28.478 [DEBUG] :: Finished Pausing
    2022-12-26 18:03:28.478 [DEBUG] :: Queuing nodes for render (group=true):
    2022-12-26 18:03:28.480 [INFO] :: Queuing nodes for render (group=true):
    2022-12-26 18:03:28.480 [DEBUG] ::      NYT-2_Trash_Bag (NYT-2_Trash_Bag-White)
    2022-12-26 18:03:28.483 [INFO] ::      NYT-2_Trash_Bag (NYT-2_Trash_Bag-White)
    2022-12-26 18:03:28.485 [DEBUG] :: ERROR: function text() {
        [native code]
    } Property not found
    2022-12-26 18:03:28.486 [DEBUG] :: Render 256 x 256 Iray Image: N:/DAZ 3D/DAZ Renders/Polished Granite - Baltic Red.tip.png
    2022-12-26 18:03:28.499 [INFO] :: Render 256 x 256 Iray Image: N:/DAZ 3D/DAZ Renders/Polished Granite - Baltic Red.tip.png
    2022-12-26 18:03:28.499 [DEBUG] :: Width x Height 256 256
    2022-12-26 18:03:28.499 [DEBUG] :: 256 256
    2022-12-26 18:03:28.506 [INFO] :: Rendering image

    In that test I tried different geometry (trash bag) to apply the granite prest to and a different lighting HDRI. That made no difference.

    After "Pausing at least 5000", mine says "Finished Pausing". Yours starts getting warning messages. I have my viewport in Texture Shaded mode. How about You? I wonder if using Iray Preview or Filament viewport could have an impact.

    Post edited by barbult on
  • vanishvanish Posts: 39

    I have been in Texture Shaded mostly. but it has also happened in Filament and Iray draw modes.I'm wondering if my daz script library (dzscript) is corrupt.

  • vanishvanish Posts: 39

    Well, I tried a fresh copy of DAZ Studio and the Render Doctor script, still the same problem.

  • barbultbarbult Posts: 23,164

    Hopefully RiverSoftArt will respond with some idea of why that is happening to you.

    You don't have the script installed with Daz Connect inside Daz Studio, do you? That can cause script problems. Do you have plenty of RAM in your computer. I have only 32 GB. I wonder if some installed plugin could be interfering. I can't think of any other suggestions right now.

  • vanishvanish Posts: 39

    I'm in the same boat. I've exhausted what I can think of for now anyway. I used DIM to install. I have 32GB of RAM. I have, well, let's say lots of plugins.Heh. Maybe my next tack will be to unistall al plugins and see what happens. Thanks for all the help Barbult! 

  • barbultbarbult Posts: 23,164

    You probably don't have to uninstall plugins. Help>About installed plug-ins lists those you have installed. You can disable one by unchecking it and restarting Daz Studio.

    I had another thought. RiverSoftArt uses a lot of common helper script files that are used by several products. Sometimes different versions get installed in different folders by different products. Sometimes people have had a problem with the wrong file version getting used. I don't know if that could cause a problem with a specific shader preset, though.

  • vanishvanish Posts: 39

    Hmm. Disabled all of my purchased plugins. Still get the same behavior. :(

  • barbultbarbult Posts: 23,164

    Do you have the Aux Viewport open? I have that pane closed. Do you have multiple viewports? Mine is set to Single.

  • vanishvanish Posts: 39

    Single Viewport and I had Aux open but not visible. I closed it, same behavior. Good thinking though.

  • vanishvanish Posts: 39

    OK, I went to the extreme, backed up my content library then completely uninstalled everything. Reinstalled Studio and CMS with Render Doctor and the nvidia vMaterials 2.0.0. Guess what? Same behavior. I'm left with two things.

    1) Render Doctor somehow, after all the uninstalling, remembered my settings. WTF?

    2) I'm on Windows 11. No idea if that measn anything, but it is a difference between my setup and @barbult setup.

  • barbultbarbult Posts: 23,164

    He posted in another thread and I asked him to check this one, because of your problem that I can't reproduce. I'm sure Render Doctor saves settings some place, because when you Save and run it again, it remembers your saved settings. I don't know where it is saved, though. Deleting the content library files and application may not have removed the saved settings. They could even be in the registry for all I know. It seems more likely that they are in a file someplace, maybe Appdata???

  • vanishvanish Posts: 39

    Well, I got my hopes up. I found entries in the Registry for the script and exported then delted them. Upon opening Studio and selecting presets to render, it was indeed reset, other than favorites for some reason. Still the same behavior though so nothing corrupt in there either.

  • barbultbarbult Posts: 23,164

    With forum notification so hit and miss, he may not even be aware that we are posting here.

Sign In or Register to comment.