UltraScenery [Commercial]

19091939596100

Comments

  • Oso3DOso3D Posts: 15,011

    Was speedy AF for me; 20 seconds to generate limited to camera + extended forest? Very impressed.

     

    Wading in the Forest.jpg
    1300 x 1000 - 640K
  • dawnbladedawnblade Posts: 1,723

    Just to note that I disabled the Accelerator plugin and USC works as expected, albeit 20 min. to finish  Oaks 11, River 3, Clear Stream, without extended background. No issue closing the dialog when it was done.

  • dawnbladedawnblade Posts: 1,723

    Hm. I did run UltraScenery quite a few times, with various settings, and never experienced a crash or hicup. It runs more stable than the no-plugin version. Running on Apple hardware, so this might not be representative.

    Thanks. I'm on Windows 10, but glad to know it's working for you. smiley

  • the last scene I built (before accelrator) ran the machine up to 63g of ram when starting the render.
    is it possible the scene builder also accesses ram to store data? And if you don't have lots of ram it could be hanging up there? Note ..not cpu cycles ram usage 
    (I monitor on another screen so I can see it. 
    using 63 of 64 gigs of ram has the same effect as using 100% of cpu cycles...  not much can happen. 
     

  • dawnbladedawnblade Posts: 1,723
    edited December 2020

    Accelerator is working now! Octane is conflicting with your Accelerator plugin! That's the culprit (again!), which really stinks because the instances issue with Octane and USC was cleared up, according to a user here. That's why I had Octane active again, plus with the new Octane Kit. So I'll just have to be mindful of which plugin is active.

    @HowieFarkes, if you or a mod want to remove my recent posts regarding this issue so they don't clog up your thread, go ahead. Maybe keep this one in case others using Octane and your new Accelerator run into the same problem.

    Thanks all for testing scenes along with me, much appreciated! smiley

    Post edited by dawnblade on
  • HowieFarkesHowieFarkes Posts: 607
    edited December 2020

    the last scene I built (before accelrator) ran the machine up to 63g of ram when starting the render.
    is it possible the scene builder also accesses ram to store data? And if you don't have lots of ram it could be hanging up there? Note ..not cpu cycles ram usage 
    (I monitor on another screen so I can see it. 
    using 63 of 64 gigs of ram has the same effect as using 100% of cpu cycles...  not much can happen. 
     

    I'm going to guess that you did not have Render Settings -> Instancing Optimization set to "Auto" or "Memory" as this is what can happen if that is set to "Speed". The renderer will attempt to create a copy of the geometry of each instance in memory - which will keep on going until all the instances have been swapped into memory or it runs out of space and crashes your machine.

    Post edited by HowieFarkes on
  • dawnblade said:

    Accelerator is working now! Octane is conflicting with your Accelerator plugin! That's the culprit (again!), which really stinks because the instances issue with Octane and USC was cleared up, according to a user here. That's why I had Octane active again, plus with the new Octane Kit. So I'll just have to be mindful of which plugin is active.

    @HowieFarkes, if you or a mod want to remove my recent posts regarding this issue so they don't clog up your thread, go ahead. Maybe keep this one in case others using Octane and your new Accelerator run into the same problem.

    Thanks all for testing scenes along with me, much appreciated! smiley

    Glad you found out why it was not working - not so glad that Octane still appears to have issues with DzInstanceGroup nodes.

  • davesodaveso Posts: 7,018

    the accelerator install real fast too ... click ..done. 

  • davesodaveso Posts: 7,018

     

    OK --- WOW  ... 23.21 seconds

     

    river 1 woodland 2 extended scenery

     
       



     

  • alan bard newcomeralan bard newcomer Posts: 2,202
    edited December 2020

    the last scene I built (before accelrator) ran the machine up to 63g of ram when starting the render.
    is it possible the scene builder also accesses ram to store data? And if you don't have lots of ram it could be hanging up there? Note ..not cpu cycles ram usage 
    (I monitor on another screen so I can see it. 
    using 63 of 64 gigs of ram has the same effect as using 100% of cpu cycles...  not much can happen. 
     

    I'm going to guess that you did not have Render Settings -> Instancing Optimization set to "Auto" or "Memory" as this is what can happen if that is set to "Speed". The renderer will attempt to create a copy of the geometry of each instance in memory - which will keep on going until all the instances have been swapped into memory or it runs out of space and crashes your machine.

    duh.. yeah forgot to reset that the last time...  
    thanks

    and I was blaming the Aussies and there billabongs

     

    Post edited by alan bard newcomer on
  • GoggerGogger Posts: 2,399
    edited December 2020

    Okay, just to help clarify things for those just tuning in - if your USC hangs after installing the Accelerator AND you have the Octane Render Plugin you do not have to uninstall Octane, but merely DISABLE it by going in DAZ Studio to the Help\About Installed Plugins...\OctaneRender where you will uncheck the box [edited to correct the next statement - thanks @dawnblade] and then you need to restart DAZ Studio.  I saw some vague comments about Octane Render and DREADED having to uninstall it and eliminate any trace files etc - a real chore. But it was as easy as unchecking that box!  And between the two, I'd choose UltraScenery ANY DAY!  Just thought I would try to help clear that up for anyone not quite sure.

    And having gotten it to render in record fast scene-building time, here are a couple of renders.

    Moody Monolith
    Uses the Australian ecosystem and the monolith prop from Muelsfell Elven Monolith that fits this scene and moody Orestes HDRI lighting so perfectly.


    This Autumn Stream scene actually is using TWO generated Ultrascenery scenes (same base, different ecosystems) and both have Render Settings/Matte Fog turned on at about 600 - 800 Matte Fog Visibility (m).  Don't forget to color outside the lines!  It is much more interesting!

    DS_Moody_Monolith_3D_Erik_Pedersen.jpg
    3440 x 1440 - 627K
    DS_Autumn_Stream_3D_Erik_Pedersen.jpg
    3440 x 1440 - 2M
    Post edited by Gogger on
  • dawnbladedawnblade Posts: 1,723

    @Gogger those are great, especially the combination of two USC builds! Barbult had also made them and they turned out great too.

     

    Regarding Octane, you are correct that you don't have to uninstall it to use USC. But restarting DS is required to actually disable plug-ins, as unchecking only changes their state from active to whatever the yellow color represents, I don't remember the name but it isn't disabled yet. Gray is disabled.

     

    Hopefully a future version of DS will set it to disabled w/o the need to restart it. Even better would be that this will be a thing of the past!

  • I bought the Accelerator at the first day. Like all Ultrasceneryproducts ;-)

    Sadly i don´t know, i have to install  the DLL with DIM,

    which isn´t possible for me.

    I wrote DAZ3D a ticket about this. Until now no answer.

    Any chance to help me ??? Please !

     

  • algovincianalgovincian Posts: 2,613

    I bought the Accelerator at the first day. Like all Ultrasceneryproducts ;-)

    Sadly i don´t know, i have to install  the DLL with DIM,

    which isn´t possible for me.

    I wrote DAZ3D a ticket about this. Until now no answer.

    Any chance to help me ??? Please !

    To be clear, you don't have to install with DIM. You do have to download with DIM, but you can install manually once you have download the files. You can use DIM on one machine to download and transfer the downloaded files to a second machine to install manually.

    I am curious to know the reasoning behind not being allowed to download manually, though.

    - Greg

  • GoggerGogger Posts: 2,399
    dawnblade said:
     

    Regarding Octane, you are correct that you don't have to uninstall it to use USC. But restarting DS is required to actually disable plug-ins, as unchecking only changes their state from active to whatever the yellow color represents, I don't remember the name but it isn't disabled yet. Gray is disabled.

    Thanks, @dawnblade, I edited my post in regards to making it sound like you wouldn't have to restart DAZ Studio.

  • I bought the accelerator yesterday and cannot install it due to the missing dll. Because I dont use DIM, I always verify on the product page that the manual download is available.

    Why DAZ write "manual download" if it's not the case?

    I submit a ticket and wait for a response.

     

  • Richard Haseltine said:

    Oh. Dim only download. I have no Dim as my machine is unable to access the net, and I install manually only. That's a bit of a problem then. I suppose I can live with the script version.

    It is mightly clever being able to interface with a program using a dll - I have never succeeded in doing so with my C++ programming.

    Regards,

    Richard.

    As long as you can get the .zip, from another machine with DIM, you can isntall DIM in the offline machine, place the zip in its Pacakage Archive (the downloads folder) and install. You don't need to be online

    Can you you install DIM on a machine that doesn't have DAZ Studio on it?

     

     

     

  • sandmanmax said:

    Richard Haseltine said:

    Oh. Dim only download. I have no Dim as my machine is unable to access the net, and I install manually only. That's a bit of a problem then. I suppose I can live with the script version.

    It is mightly clever being able to interface with a program using a dll - I have never succeeded in doing so with my C++ programming.

    Regards,

    Richard.

    As long as you can get the .zip, from another machine with DIM, you can isntall DIM in the offline machine, place the zip in its Pacakage Archive (the downloads folder) and install. You don't need to be online

    Can you you install DIM on a machine that doesn't have DAZ Studio on it?

    Not sure why but yes.

  • DoctorJellybean said:

    sandmanmax said:

    Richard Haseltine said:

    Oh. Dim only download. I have no Dim as my machine is unable to access the net, and I install manually only. That's a bit of a problem then. I suppose I can live with the script version.

    It is mightly clever being able to interface with a program using a dll - I have never succeeded in doing so with my C++ programming.

    Regards,

    Richard.

    As long as you can get the .zip, from another machine with DIM, you can isntall DIM in the offline machine, place the zip in its Pacakage Archive (the downloads folder) and install. You don't need to be online

    Can you you install DIM on a machine that doesn't have DAZ Studio on it?

    Not sure why but yes.

    I figured if I installed it on my company laptop, then I could manually transfer the DLL over to my desktop without risking anything happening to my DAZ content folders (all 6 or 7 of them).  And as for no DAZ, well, company laptop.  I wouldn't do it if DAZ needed to be installed.  Instead.... sigh.... make sure my Acronis backups had run on all drives for this week, reboot into an Acronis Try & Decide partition, install DIM, download file, abandon all changes to Acronis, and reboot back into my regular system.  In other words, it's a huge pain that take about 2 hours as opposed to popping a flash drive into my company laptop.

     

  • Doc AcmeDoc Acme Posts: 1,153

    Accelerator for UltraScenery prob

    I picked up the Accelerator last night and having an issue that I haven't seen mentioned. See attached screen shot.

    This is with default script settings, Dirt Track01, and Tangy Apple Orchard 10. No extended forest nor restrict instances to Camera, although no camera in scene at time of Build.

    DS 4.14.0.8. DIM shows an update for DS available for 4.14, but doesn't list what version.

    This is on an HP laptop with a whopping 12Gb of RAM.  I normally wouldn't even install USC on it, but thought I'd test. I'm away from my main ThreadRipper system for few more months which is what I'd typically be using.

    Any thoughts?

    USC Accel Prob.jpg
    1920 x 1080 - 292K
  • dawnbladedawnblade Posts: 1,723
    edited December 2020

    Doc Acme said:

    Accelerator for UltraScenery prob

    I picked up the Accelerator last night and having an issue that I haven't seen mentioned. See attached screen shot.

    This is with default script settings, Dirt Track01, and Tangy Apple Orchard 10. No extended forest nor restrict instances to Camera, although no camera in scene at time of Build.

    DS 4.14.0.8. DIM shows an update for DS available for 4.14, but doesn't list what version.

    This is on an HP laptop with a whopping 12Gb of RAM.  I normally wouldn't even install USC on it, but thought I'd test. I'm away from my main ThreadRipper system for few more months which is what I'd typically be using.

    Any thoughts?

    I can confirm that I'm getting that partial layout too. I'm on DS 4.14.0.10, which is probably the version sitting in DIM for you. This is what Tangy 10 is supposed to look like based on the ecology picture. I used Accelerator too, so give me a few as I need to disable the plugin, restart DS.

     

     

    TangyApple10.jpg
    403 x 341 - 45K
    Post edited by dawnblade on
  • NathNath Posts: 2,808

    Doc Acme said:

    Accelerator for UltraScenery prob

    I picked up the Accelerator last night and having an issue that I haven't seen mentioned. See attached screen shot.

    This is with default script settings, Dirt Track01, and Tangy Apple Orchard 10. No extended forest nor restrict instances to Camera, although no camera in scene at time of Build.

    DS 4.14.0.8. DIM shows an update for DS available for 4.14, but doesn't list what version.

    This is on an HP laptop with a whopping 12Gb of RAM.  I normally wouldn't even install USC on it, but thought I'd test. I'm away from my main ThreadRipper system for few more months which is what I'd typically be using.

    Any thoughts?

    I'm seeing the same with this selection.

  • Doc AcmeDoc Acme Posts: 1,153

    I'll give it a test w/ another Ecology.

    Thanks for the quick confirm.

  • NathNath Posts: 2,808
    edited December 2020

    Doc Acme said:

    I'll give it a test w/ another Ecology.

    Thanks for the quick confirm.

    Different terrains with Orchard 10 give the same result for me. Dirt track 1 with Orchard 11 looks to have no problems.

    Correction: Orchard 11 stalls on generating the Young and Sapling Beech trees. Distribution of other trees looks normal.
    Post edited by Nath on
  • dawnbladedawnblade Posts: 1,723

    You're right, Doc. This is the layout without Accelerator. 
    Dirt Track01, and Tangy Apple Orchard 10.

     

    TangyApple10NoAccel.jpg
    1005 x 824 - 444K
  • Doc AcmeDoc Acme Posts: 1,153

    Well, things be gettin' a bit stranger.

    I disabled the Accel plug & restarted DS. I used the same as before except used Pines 7. Had the same issue so restarted system.  Had the same prob, or so I thought.  The Scene panel was showing there were instances, (which zipped through during the build) but not seeing anything UNTIL I went to Left view. All other views, no trees.

    BTW, last night before installing the Accelerator, I did a Tangy Apple scene w/o issue... just took 45 mins.

    I'll try updating to the latest DS later on.

     

    USC Pines + NoAccel.jpg
    1920 x 1080 - 329K
    USC Pines + NoAccel_Left View.jpg
    1920 x 1080 - 168K
    USC Pines + NoAccel_Right View.jpg
    1920 x 1080 - 148K
    DS Render Optimization.jpg
    597 x 1023 - 43K
  • dawnbladedawnblade Posts: 1,723
    edited December 2020

    Doc Acme said:

    Well, things be gettin' a bit stranger.

    I disabled the Accel plug & restarted DS. I used the same as before except used Pines 7. Had the same issue so restarted system.  Had the same prob, or so I thought.  The Scene panel was showing there were instances, (which zipped through during the build) but not seeing anything UNTIL I went to Left view. All other views, no trees.

    BTW, last night before installing the Accelerator, I did a Tangy Apple scene w/o issue... just took 45 mins.

    I'll try updating to the latest DS later on.

     

    A couple of questions: After you restarted DS, did you check the plugin list again to make sure that UltraSceneryAccelerator was disabled? Mine is 2nd from bottom of plugin list. Has to be grey. If yellow then need to restart DS again, and check task manager to see that DS is gone.

    What do your renders look like?

    AccStatus.jpg
    237 x 23 - 2K
    Post edited by dawnblade on
  • barbultbarbult Posts: 24,245
    edited December 2020

    Doc Acme said:

    Accelerator for UltraScenery prob

    I picked up the Accelerator last night and having an issue that I haven't seen mentioned. See attached screen shot.

    This is with default script settings, Dirt Track01, and Tangy Apple Orchard 10. No extended forest nor restrict instances to Camera, although no camera in scene at time of Build.

    DS 4.14.0.8. DIM shows an update for DS available for 4.14, but doesn't list what version.

    This is on an HP laptop with a whopping 12Gb of RAM.  I normally wouldn't even install USC on it, but thought I'd test. I'm away from my main ThreadRipper system for few more months which is what I'd typically be using.

    Any thoughts?

    This is an interesting discovery!!  TAO Apple Orchard 5,6,7,8,9, and 10 all use a distribution type of "square" for the apple trees, and all have the same problem you discovered. I tested with DS 4.14.1.22 Public Build, UltraScenery 1.3.0 and Accelerator 1.0.0.7. It looks like only one half of the square is being populated with trees when the accelerator is used. (I removed the accelerator DLL from the plugins folder to test the non-accelerator version, which is fine.)

    Post edited by barbult on
  • hacsarthacsart Posts: 2,025

    I'm seeing the same thing with this combination, current versions of US and Accelerator Studio 4.12.118..Looks like only half the terrain is populated.

    Doc Acme said:

    Accelerator for UltraScenery prob

    I picked up the Accelerator last night and having an issue that I haven't seen mentioned. See attached screen shot.

    This is with default script settings, Dirt Track01, and Tangy Apple Orchard 10. No extended forest nor restrict instances to Camera, although no camera in scene at time of Build.

    DS 4.14.0.8. DIM shows an update for DS available for 4.14, but doesn't list what version.

    This is on an HP laptop with a whopping 12Gb of RAM.  I normally wouldn't even install USC on it, but thought I'd test. I'm away from my main ThreadRipper system for few more months which is what I'd typically be using.

    Any thoughts?

  • Doc AcmeDoc Acme Posts: 1,153

    dawnblade said:

    Doc Acme said:

    Well, things be gettin' a bit stranger.

    I disabled the Accel plug & restarted DS. I used the same as before except used Pines 7. Had the same issue so restarted system.  Had the same prob, or so I thought.  The Scene panel was showing there were instances, (which zipped through during the build) but not seeing anything UNTIL I went to Left view. All other views, no trees.

    BTW, last night before installing the Accelerator, I did a Tangy Apple scene w/o issue... just took 45 mins.

    I'll try updating to the latest DS later on.

     

    A couple of questions: After you restarted DS, did you check the plugin list again to make sure that UltraSceneryAccelerator was disabled? Mine is 2nd from bottom of plugin list. Has to be grey. If yellow then need to restart DS again, and check task manager to see that DS is gone.

    What do your renders look like?

    Yes, it was still OFF & grayed.  Instance Optimization keeps reverting from Memory to Auto however.

    Didn't do a full on render; just enought to see that Iray was giving the same result.

     

This discussion has been closed.