Loading...
> >

4.12 RAM issue

TheKDTheKD Posts: 2,696
in Technical Help (nuts n bolts)

This is a new one for me, as I have 32gb of RAM. I been working on a scene, in the past week using the newest 4.12 I have had it happen at least 10 times. I will get a windows popup saying that I am almost out of RAM, and I must quit programs. Before I can do anything, daz simply crashes. It's not even a scene as big as I have done before with no issues. It fits in my 2080 super and 1070 VRAM just fine, but somehow manages to eat up almost all 32gb RAM on my system. Sometimes even just opening the scene was doing it. Using scene optimizer on it made it a lot more stable, but still DS is using like 20bg RAM.

Comments

  • kenshaw011267kenshaw011267 Posts: 3,805

    are there instances in the scene? Those are fairly massive RAM hogs.

    But you should almost never get that message. There are two possibilities.

    1) The disk your windows swap file (more than likely your boot disk) is almost full so swapping to disk fails.

    2) You've got Windows set to not dynamically grow the size of the file as needed.

  • Richard HaseltineRichard Haseltine Posts: 102,464

    Instances (and Geometry Shells) use less memory than plain duplicates of the given item - but of course there may soemtimes be a lot of them, and they can certainly have an impact on the viewport if they are visible.

  • TheKDTheKD Posts: 2,696
    edited November 2019

    It's fairly simple scene, no instances at all I don't think. Maybe some cinder blocks are instances, but there is not a lot going on in this, some cinder blocks, a few crates. https://www.daz3d.com/abandoned-factory-floor is the scene I was using, had 2 G8 figures, non porn style so they had clothes on lol.

    I have actually had paging off completely since I built the system this spring, I turned that back on to system managed, using my HD with the most free space, a bit over 1tb free space. My SSD I have my OS on, is partitioned down, and not much free space at all there, I also install my games there. See if that helps any.

    Post edited by TheKD on
  • kenshaw011267kenshaw011267 Posts: 3,805

    That was almost certainly at least the cause of the out of memory dialog and maybe the crash. I'm still not sure why you were using up 32Gb if all you had running was DS.

    Did you have something, multiple somethings, with high SubD's set? 

  • TheKDTheKD Posts: 2,696

    I don't think so, it wasn't anything close up, so don't think I would have bumped up the subD past two.

  • kenshaw011267kenshaw011267 Posts: 3,805

    I have had occasion where some props and environments came with SubD's of 4, or higher IIRC, set by default. It would be tedious but add each element one at a time till you get a huge jump in RAM then take a look at that item.

  • PadonePadone Posts: 3,790

    Whenever you buy a new asset, you may just do a test render to see how much ram/vram it takes alone. This is useful to target your scenes in production. Also this way you may return the asset in time if you see it's a memory hog.

  • TheKDTheKD Posts: 2,696

    That's a good point, I never thought to look at scenes/props subd levels before. I will look into it, I am going to have to redo some of the renders from that series of images, stupid ass daz studio turned off my canvas for some of my renders, and didn't notice until after I was done letting them render all night :/  I hate when that happens

     

Sign In or Register to comment.