Haven Park locks up Studio

Petercat

I've returned Haven Park for a refund,, but Tire and Swing is doing the same thing, and it was free.

Both work fine in 4.10, which I don't use because it has too many issues.
They lock 4.9.2.70 up when I try to render.
I get the checkerboard screen, nothing else.
Memory usage climbs until it gets kicked off my 980Ti, then system memory climbs until it hits the full 64 gigs, goes into swap mode, and I get the "Studio has failed" message.
Can anyone help me figure this out?

So far this has happened with Toon Forest, Haven Park, and Tire and Swing.
The scripts in Scene Optimizer and Crowd Billboards don't work in 4.9, either.
Am I just going to have to quit buying new products?

SixDs

Well, something there seems to be amiss, Petercat. I know that some of those landscape environments have a lot of maps and big ones, but if you have 64 GB of Ram and your scene is blowing right through that, I have to believe that something else is wrong here. The fact that you have seen this happening with three different sets and they all worked fine on 4.10, would seem to reinforce this. I don't have those sets and I'm not running 4.9 unfortunately, so I can't think of why you are seeing this behaviour. Not helpful, I know, but hopefully someone else might have some insights. 64 GB should be more than enough RAM to handle those scenes, and if it isn't, then most of us are in trouble.

BTW, something just occured to me. Are you running both 4.10 and 4.9 concurrently, or did you uninstall 4.10 and re-install 4.9? If running both, is one of them a Beta?

Petercat

SixDs said:

BTW, something just occured to me. Are you running both 4.10 and 4.9 concurrently, or did you uninstall 4.10 and re-install 4.9? If running both, is one of them a Beta?

I have 4.9.2.70 and 4.10 beta installed, not running both at once.
The scene stays on the GPU with 4.10.
What I don't understand is why, in 4.9, it starts on the GPU then slowly increases memory usage until it transfers to system ram, slowly uses more of that until about 15-20 minutes later it's using all 64G of that, then goes into swap mode and fails.

SixDs

Yeah, it was just a thought, since DAZ "strongly recommends" that two versions of DAZ Studio 4.x not be installed at the same time as it can cause unpredictable issues. But, since the 4.10 is a Beta, that shouldn't cause a problem. Running a Beta and a general release is considered OK.

Have you looked at the DAZ Studio log file to see if there is some clue there as to what might be happening? Its a bit of a long shot, but worth looking at.

WendyLuvsCatz

could it be instances and can you change the settings for them collapsing like groups and using memory rather than speed in render optimisation?

Jeromelevaiath

I have 24GB memory/RAM on my machine which works great with most complicated scenes.

Sure enough, Haven Park grouped objects would not show in Iray preview and will not render under 4.10 pro. It'd render as black screen.
Eliminating some of the objects (I just randomly deleted the fence, walls and the smaller part next to the path) in the group solved the problem.
Logically, there are too many heavily detailed objects in the group; yet, if it failed on a 64GB system as well then my guess would be a single faulty object which causes this mess to begin with.