Data-Stacking!- What is 'Octane Scene Render Data'? Why is it...mutating scene memory?

Data-Stacking- That is what I have been calling it, for lack of a better term.

It started, recently- a month or so, ago.

Normally-Low kilobyte figures or props, begin growing into 5, and then, 6-figure megabyte figures (or props), until they become gigobyte figures (or props).  'Gigobyte hogs!', you might say.  

Really!  My 2 Terabyte drive is filled to capacity, now, after only a limited number of scenes.

Saved figures (and props) that should be a few thousand KBs are 168,000!  Into the megs!  A gig!

HAS THIS HAPPENED TO ANYONE ELSE?  (And 'Select All', once again (for me, anyway), is useless!

I will click on a...shall we call it...a mutated 'hog figure' (or prop), which was small (in memory), but is now huge, and here is the message I get: 'Octane Render Scene Data 194390' ...for example.

I can only delete a piece of data, one digit at a time.  I would spend ALL DAY deleting scene-data digits!  There appears to be no way to select all the data, and delete it, at once.  ...that I know of.

I have reconstructed scenes and figures, many times.  But it just keeps happening again.  

Does anyone know what is happening?  Is the figure (or prop) corrupted?  Or can it be reduced to its normal memory size, again?

Is there a way to batch-delete this...'octane scene render data'?       

I am only assuming that this is related to the problem, because I don't remember encountering messages like this, before this happened.

Comments

  • cridgitcridgit Posts: 1,757
    edited May 2022

    Redacted

    Post edited by cridgit on
  • Richard HaseltineRichard Haseltine Posts: 102,218

    Try File>Save As>Scene Subset and check only the items you want to keep, rather than trying to delete the rogue Octane nodes. The Octane issue should be reported to the developer of the Octane plug-in, assuming you are following their recommendations for workflow.

  • dash2128dash2128 Posts: 714

    cridgit said:

    Screenshot? This shouldn't be happening and definitely some bug.

    Hello, 

    Whenever I try to take a screenshot of the 'Octane Render Scene Data' message, it disappears.  And I sometimes have to shut down the computer, when the 'Select All' issue happens, which- I'm guessing- may be related, in some way.  I'm not sure, since that issue has gotten much worse, lately.  ...but has been around for quite a while,actually.  But the huge memory problem...what shall I call it?...An 'M-Class black hole!'?...  may be causing 'Select All' to run and run (the computer hangs up) until I have to (sometimes) shut it down (in the middle of operations) and restart it.  Because SDaz will not close out until it spends 15 minutes- or perhaps hours- selecting all (or everything) in the scene.  One night, I let it run all night, and found it still hung on the 'Select All' operation, in the morning!

    But I don't want to confuse the S.A. issue with the 'Octane Render Scene Data' issue.  ...which has already filled up my onece-empty 2-terrabyte drive, until I am now running off a 4-terrabyte external drive.  If I could just batch-select the scene data (one of them is  presently '194390'- that is how many delete operations, I would have to perform with the mouse, the get rid of it!), perhaps I could reducde the scene (or figure/prop) memory.

    I wonder what is causing this, in the first place?  Some Daz sets are a gig, now.  But that shouldn't be making figures and props increase, should it?

    (Thanks for replying!)            

     

  • dash2128dash2128 Posts: 714

    Richard Haseltine said:

    Try File>Save As>Scene Subset and check only the items you want to keep, rather than trying to delete the rogue Octane nodes. The Octane issue should be reported to the developer of the Octane plug-in, assuming you are following their recommendations for workflow.

  • dash2128dash2128 Posts: 714

    Hello, that is a very interesting remark!  'rogue octane nodes'.  Yes!  They do seem to be nodes.  And they stack up into the gigs, sometimes!  I cannot say that I am following the recommendations of the developer, since...I don't know what they are, actually.

    I wouldn't know who to report it to, either.

    But I definitely would like to prevent those...'rogue nodes'...from piling up.  

    'Check only the items I wish to keep, when I save?  Using 'Scene Subset'?

    I can give that a try.  I will, and see what happens.

    Thank you for replying!  

  • dash2128dash2128 Posts: 714
    edited June 2021

     

     

    Post edited by dash2128 on
  • dash2128dash2128 Posts: 714

    dash2128 said:

    Richard Haseltine said:

    Try File>Save As>Scene Subset and check only the items you want to keep, rather than trying to delete the rogue Octane nodes. The Octane issue should be reported to the developer of the Octane plug-in, assuming you are following their recommendations for workflow.

    Wow!  That reduced the size of the scene!

    Does that mean that the figures and props will also be reduced?  Figures, for example, are stacking up 'rogue nodes', also.  If I save them, using 'Scene Subset', and that restores them, that will be great!  

  • DustRiderDustRider Posts: 2,785

    Have you installed the Octane Render plugin from Otoy? If so, then the developer Richard referred to would be Otoy. If you don't have the Octane Render plugin, then something is really wrong,  because without the plugin, DAZ Studio "knows" nothing about Octane Scene Render Data, therefore can not generate it on it`s own.

    It sounds as if you have the plugin installed, and you have it set to auto-generate Octane Materials for all assets added to the scene. Going into the Octane settings and disabling this will stop Octane from generating materials until you tell it to (this is the default setting, so you probably enabled it while using the Octane plugin, not realizing it would auto-generate the materials even when you don't render with Octane).

  • cridgitcridgit Posts: 1,757
    edited May 2022

    Redacted

    Post edited by cridgit on
  • DustRiderDustRider Posts: 2,785
    edited June 2021

    In the Octane Main window, go to the materials tab, select the object/node you want to create/referesh the materials for, then click on the missing drop down and select "Create as Auto Materials" (see below).

    Octane Materials.jpg
    629 x 935 - 164K
    Post edited by DustRider on
  • cridgitcridgit Posts: 1,757
    edited May 2022

    Redacted

    Post edited by cridgit on
  • UHFUHF Posts: 515

    dash2128 said:

    Data-Stacking- That is what I have been calling it, for lack of a better term.

    It started, recently- a month or so, ago.

    Normally-Low kilobyte figures or props, begin growing into 5, and then, 6-figure megabyte figures (or props), until they become gigobyte figures (or props).  'Gigobyte hogs!', you might say.  

    Really!  My 2 Terabyte drive is filled to capacity, now, after only a limited number of scenes.

    Saved figures (and props) that should be a few thousand KBs are 168,000!  Into the megs!  A gig!

    HAS THIS HAPPENED TO ANYONE ELSE?  (And 'Select All', once again (for me, anyway), is useless!

    I will click on a...shall we call it...a mutated 'hog figure' (or prop), which was small (in memory), but is now huge, and here is the message I get: 'Octane Render Scene Data 194390' ...for example.

    I can only delete a piece of data, one digit at a time.  I would spend ALL DAY deleting scene-data digits!  There appears to be no way to select all the data, and delete it, at once.  ...that I know of.

    I have reconstructed scenes and figures, many times.  But it just keeps happening again.  

    Does anyone know what is happening?  Is the figure (or prop) corrupted?  Or can it be reduced to its normal memory size, again?

    Is there a way to batch-delete this...'octane scene render data'?       

    I am only assuming that this is related to the problem, because I don't remember encountering messages like this, before this happened.

    I have tons of ready to go characters, and scenes all translated to Octane.  Very few have bloat as you describe.  I've only seen that with hair fibers as geometry, but I'll know, Daz will bog down.

     

Sign In or Register to comment.