Forester Problems - can someone help?

[BCres]

Here is the problem: The last version of Forester that worked fine for me was version 121. I still use this version to this day. All versions since then cause my memory to climb to 100% during rendering, where C4D or my system will then lock up.

I traded emails with the developer a while back but he simply kept saying I needed to optimize my scene. But he was ignoring the fact that the very same scene would render fine on 121 (using only about 30% of the system memory), while any version after that would climb until the system ran out of memory. He would never answer that question.

So I can simply swap Forester versions and restart the render to test. 121 always works fine. Anything above crashes. This has happened with all versions of Octane, including the new ver 4 RC4.

And yes, I can optimize the scenes, but then they don't look like what I initially created. Or wanted.

With the new versions of Forester coming out I'm hoping someone here has found a fix for this so I can move on. Thanks in advance.

[BCres]

Oh well, guess I'll figure it out on my own.

[aoktar]

1-Try to use "Render Instances"
2-Try to use "All movable" in render settings. Otherwise RAM usage will climb.

[BCres]

Thank you for responding, Aoktar.

1- I had all the Forester cloners already set to "render instances." I just tried again and actually turned the objects off in the scene. Memory climbed into 90+% before I had to dump out.

2- No change turning on "all movable", memory climbs over 90% and I have to dump out.

It's so weird because all I have to do is replace any newer Forester version at my desktop with the old 121 and I can render the scene without it ever climbing above mid 30% memory use.

Something changed in these newer versions and 3DQuakers keeps telling me my scene needs optimizing. But 121 can render anything I throw at it no problem. And it's behaved that way in all the recent versions of Octane as well. So I honestly don't think it's an Octane problem. Just thought I'd ask here.

I appreciate your help. I know how busy you are with other things.

[aoktar]

Please send me your scene so I can test here! Write what's forester/octane and c4d versions.

[BCres]

Here's what it looks like.

If you need you can drop the tree and the grass if this exceeds your memory.

Forester 121 will render this as is, going up to about 57% memory usage then dropping to 40% during render. Forester 143 uses up all memory and crashes. In fact all versions of Forester past 121 crash.

Tested here on C4D 19.068 Octane 3.08.3. Windows 10 ver1803, 32gigs ram, i7-5960x, 1080ti and 1080 on same system.

But it has been test on all previous versions back to 3.0.6. and all C4d back to version 17. Same problem, along with other video cards and earlier versions of Windows 10.

I password protected it since there are some textures I wasn't sure if I could distribute. Can I dm you the password?

[aoktar]

Please send me the pass by PM from forum messaging system. Thanks!

[BCres]

Just did. Noticed the mail icon and sent it. No hurry. Just something I've been trouble shooting for a long time and never found an answer.

Thank you, aoktar.

[3dquakers]

Hello,

The scene renders fine in the latest Forester, in fact faster than the older version 121.
What I did was reduce the branch segment count from 18 to 10 and branch sides from 8 to 7. Rendering the same scene on the older 121 consumes more memory.
Memory consumption started at around 30% and finished at around 50%

If you wish to discuss this matter further please get in touch with us by email.

[BCres]

I appreciate your reply 3DQuakers, but this is the same thing I went through with your support before. It's very frustrating. It's like you disregard what I am writing.

On my system, if I render this scene with 121 it uses between 35-50% memory and renders fairly quickly. Every other version since then maxes out the memory and I have to dump out of it before it crashes my system.

Honestly, I don't know why your system works and mine doesn't. It must be something on my system and that is why I am asking for some help on these forums. But it doesn't help to keep telling me how it works on yours and how I can optimize the scene. That doesn't answer the question.

To recap...

I run my test by starting a commandline to render a scene, observe the memory usage, stop the render and then swap Forester versions. Then start again and observer what's happening. It has nothing to do with optimizing anything. I'm not even touching the scene.

So if you can tell me why that is happening, I'll solicit your help.

Thanks.