Change resolution size and/or visibility of objects without opening a scene? (Preload objects?)

hejjj12hejjj12 Posts: 51
edited August 2023 in Daz Studio Discussion

Hi! Was wondering if there was a way to alter things like visibility of objects and chartchers in a scene without actually opening (opening defult daz3d is okay).

Same with chainging rendeer resolution without opening a scene?

Reason is that opening a scean can take around 10 minutes, while rendering it can take far less and i like to do a render que on them, but if I have to open some before and change things like resolution visibility it will take far longer time. 

I know we have turbo loader, but from what I seen it's more about loading genesis figures into a scean, not loading a scene by itself? Right?

So I wondered if there was a tool or a way to use notepad or something to change minior things in a scene without opening it?

Or if a tool could just pre load objects so daz3d don'r need to reload them everytime I open a scene. (Since I have many scenes with the same figures, enviroment and figures in it, so if I could in some way pre load them so daz3d didn't need to reload them everytime I loaded a new pose version of it, that would also be great.)

Post edited by hejjj12 on

Comments

  • crosswindcrosswind Posts: 6,926
    edited August 2023

    From technical standpoint, yes, you can open DSON User Files ( DUF ) with an Editor software (Notepad++, EmEditor, etc.) , or DSON Editor( https://www.daz3d.com/dson-editor ) to modify sth. like Visibility of objects or whatever, as long as you know well about DSON format / structure and syntax.

    Long loading time might not result from the number of morphs you've installed, remember to check you log first to see if there's any warning like duplicate formulas. Turbo Loader is used for deactivating morph files so as to speed up loading the scene where there're Genesis figures, so they're relevant.

    Finally, if you're talking about sth. like making visual novels or comics that you want one scene file covers multi storyboards, e.g. multi cameras + multi poses, you may wanna check this product -: https://www.daz3d.com/camera-magic and the 2 add-ons, for saving different poses and shapes to different cameras in a single scene file.  Well, at least they're game changers for me.

    Ps: AFAIK, there isn't a way of 'pre-loading' a scene file in DS. When you dbl-click to load a scene file, it'll be fully loaded...

     

    Post edited by crosswind on
  • hejjj12hejjj12 Posts: 51
    edited August 2023

    Thank you for the tips. may need to run a seartch for duplicated files and might look into https://www.daz3d.com/dson-editor if I can't find anything else to lower the speed. 

    Hmm, have considered getting 
    https://www.daz3d.com/camera-magic  but am a bit worried that it may crash with some update or something and then you lose like 20 scenes... :/ Though I'm sure it works well. Might give it a try in the future. Seem to work great togheder with render queue as well since it can render all the cameras in a scene. 

    The errors I seem to get most in the log was apperantly, Formula target property not found and Formula output property not found... Maybe I should look those up then incase that slwos down load time a lot. 

     

    Edit: Oops apperantly I already own camera magic, should really give it a try then xD

    Post edited by hejjj12 on
  • crosswindcrosswind Posts: 6,926

    hejjj12 said:

    Thank you for the tips. may need to run a seartch for duplicated files and might look into https://www.daz3d.com/dson-editor if I can't find anything else to lower the speed. 

    Hmm, have considered getting 
    https://www.daz3d.com/camera-magic  but am a bit worried that it may crash with some update or something and then you lose like 20 scenes... :/ Though I'm sure it works well. Might give it a try in the future. Seem to work great togheder with render queue as well since it can render all the cameras in a scene. 

    The errors I seem to get most in the log was apperantly, Formula target property not found and Formula output property not found... Maybe I should look those up then incase that slwos down load time a lot. 

     

    Edit: Oops apperantly I already own camera magic, should really give it a try then xD

    That's great. Formula target and output warnings are pretty common. That means formula cannot find a dsf file from which it'll get value or to which it'll push value, because you do not own or have not installed the relevant products... Such warnings do not much delay the loading time, appr. 3-5% of the total loading time.

  • barbultbarbult Posts: 24,240
    How would you render the scene at all without opening it first?
  • crosswindcrosswind Posts: 6,926

    OP wanna use Render Queue to batch render scenes, but he wanna first alter render settings and some objects' visibility, etc... For instance, if there're 20 scene files, that'll first take at least 10*20 minutes for him to change the settings before starting Render Queue... The request is understandable.

  • crosswind said:

    hejjj12 said:

    Thank you for the tips. may need to run a seartch for duplicated files and might look into https://www.daz3d.com/dson-editor if I can't find anything else to lower the speed. 

    Hmm, have considered getting 
    https://www.daz3d.com/camera-magic  but am a bit worried that it may crash with some update or something and then you lose like 20 scenes... :/ Though I'm sure it works well. Might give it a try in the future. Seem to work great togheder with render queue as well since it can render all the cameras in a scene. 

    The errors I seem to get most in the log was apperantly, Formula target property not found and Formula output property not found... Maybe I should look those up then incase that slwos down load time a lot. 

     

    Edit: Oops apperantly I already own camera magic, should really give it a try then xD

    That's great. Formula target and output warnings are pretty common. That means formula cannot find a dsf file from which it'll get value or to which it'll push value, because you do not own or have not installed the relevant products... Such warnings do not much delay the loading time, appr. 3-5% of the total loading time.

    Okay must be that I'm just having to many geenesis 8 figures in one seen than and quite a lot of morphs. Since normal scenes with one or two takes less then a minute. 

    Tried out camera magic now on a new scene works great in many ways, but sadly it dosen't work well with render queue (nr 29 at least). For some reason it deecides to move some of the cameras wheile rendering, some stay and some move, it's really strange so a few renders become completly useless. It also can't use cutout plug in so renders take longer, and you have to press yes everytime you load so the whole render queue concept is lost to if I have to guard the computer. 

    Another problem when using camera magic is also if you need to load a new thing in the scene you need to go back to all previous cameras and tell that camera what to do with it. You can't either change textures or similar things that dosen't go with visability or pose. So while the whole thing is a great concept, it could't get me all the way to what i wanted from it. Still though, very usefull for one take were all you might want to alter is a pose or visability, but then there is that yes option that kills it in render queue, maybe render queue 3 could catch that and press yes, but all it says it can preess ok for missing files. 

    Anyway thanks for the tip. Will probobly just neeed to suffer through the slow starts. Or use camera magic first, then save out every camera as it's own scene, then it can go quicker if you need to go back and alter something siple as lights, rendersettings or visability in more then one of them later.
     

  • crosswindcrosswind Posts: 6,926
    edited September 2023
    ...

    Okay must be that I'm just having to many geenesis 8 figures in one seen than and quite a lot of morphs. Since normal scenes with one or two takes less then a minute. 

    Tried out camera magic now on a new scene works great in many ways, but sadly it dosen't work well with render queue (nr 29 at least). For some reason it deecides to move some of the cameras wheile rendering, some stay and some move, it's really strange so a few renders become completly useless. It also can't use cutout plug in so renders take longer, and you have to press yes everytime you load so the whole render queue concept is lost to if I have to guard the computer. 

    Another problem when using camera magic is also if you need to load a new thing in the scene you need to go back to all previous cameras and tell that camera what to do with it. You can't either change textures or similar things that dosen't go with visability or pose. So while the whole thing is a great concept, it could't get me all the way to what i wanted from it. Still though, very usefull for one take were all you might want to alter is a pose or visability, but then there is that yes option that kills it in render queue, maybe render queue 3 could catch that and press yes, but all it says it can preess ok for missing files. 

    Anyway thanks for the tip. Will probobly just neeed to suffer through the slow starts. Or use camera magic first, then save out every camera as it's own scene, then it can go quicker if you need to go back and alter something siple as lights, rendersettings or visability in more then one of them later.
     

    You use Render Q 3? I only own Render Q and rarely use it after upgrading my Nvidia cards... so I'm not sure if Render Q 3 can handle every camera well. With Camera Magic, when switching camera to different poses, there will be some delay for resolving the pose in place and all smoothing iteratijon completed if there's any.  So you may try a simple test - : set 2 cameras for 2 poses and some smoothing on Wearables. Just render with 150x150 resolution, see if there's any problem. Good collaboration between different plugins / scripts really depends....

    As for Camera Magic, a newly-loaded object is visible to all cameras as default. If you want it to be all cameras wide visible, you don't need to do anything. If you want it to be invisible to one camera, switch to that camera, hide the object and click Capture visibility with shortcut. Neat and simple ~ Well, normally placing 3 - 4 cameras in a scene as storyboards might be fairly well or you may not rememeber too many cameras. So it's gonna be pretty smooth to manipulate Camera Magice for 3 - 4 cameras. Besides, you may wisely use Enable / Disable, and Remove functions, then Camera Magic will definitely speed up you workflow.

    Anyway, pls have more experiments, it's gonna be getting better & better. Good luck!

    Post edited by crosswind on
Sign In or Register to comment.