Nvidia GPU priority + AMD primary card

[aoktar]

I have tested again to be sure for 4K rendering. We don't have any lags or similar hardness for windows. Are you using R6? Is this occuring on simple scenes or some spesific one?

[bleepurchin]

I have tested again to be sure for 4K rendering. We don't have any lags or similar hardness for windows. Are you using R6? Is this occuring on simple scenes or some spesific one?

I am using a scene file which is 400MB. I am using C4D r16. When I stop a render I can sometimes sit waiting for 2 minutes before my system becomes responsive. It is really not workable even when I have one of my GPUs set to low priority.

[aoktar]

Are you using R6.2(latest)?

[bleepurchin]

I do now.

I had the release before R1. Should that make a difference?

TO further explain my issue - when I activate the live viewer, Cinema freezes for about 30 seconds before I can do anything. This is the same whenever I stop a picture viewer render - Cinema 4D freezes for about 30 seconds.

[aoktar]

Yes. you can read change notes on release thread. That's weird, topic started with priority and come to freeze on LV. I have to ask that: Do you know limitations of plugin+renderer?

1-Max triangle count is about 19 millions
2-Scene is exported to a main nodegraph on Octane side. And it has a limit for total nodes as around 32K. If you don't make much movable meshes there is no problem. But if you make movable meshes with Octane object tags or "Auto" mode. Auto mode will make all resulting objects as movable octane meshes. So i think you have lot of movable meshes if renderer is on stalls. What is the links count number on LV?

3- Btw, are you activated "Sync. geo nodes" on settings->other?

4- Also, don't you make some some tests during scene creation process? This will give some idea how much vram and polygons you have and how are you close to limits. Also would help to optimise your render times.

[bleepurchin]

Ok I see what your saying.

'Links 1000'.

I have 'Synchronisation on geo. updates' - checked.

I have Object tags on my moving meshes only.

Obviously I make tests of my scenes... I had thought that if there was a problem with my scene it would be more obvious in Cinema 4ds Open GL - I can move around that with no issue., so I assumed Octane would be able to handle the scene size.

Where is the polygon limit number? Is is Mesh? To be honest, I watch the video tutorials and at no point has it said where this polygon number count is.

However I have 'resend only updated objects' on.... I thought that would only mean that the meshes that are moving are being sent to Octane anyway.

[aoktar]

Ok, all seems fine. Not too much, 1000 movables. Problem can begin after 10-15k movable objects. Btw, in 3.0 i expect better handling for this situations. If Octane can't provide that i'll add some smart ways to plugin. Clearly i can't see any problem in your info. If you mean completely freezeing the Cinema on start of LV, this is strange. Propably because of very high usage of GPUs. Maybe missed due lot of user post, did you tried to use one gpu for render other for monitor? I'm curious about same thing will happen.

[bleepurchin]

Yes I get the same freeze when I start up the live viewer even with 1GPU... it may be a little shorter but it still happens. The same occurs when delete the live viewer or I stop a render. It's not unworkable though. I've learned today that I can get around somethings by using the priorities more.

I'm going to purchase another GTX card anyway as I need to have more GPU for the other display processes... turning off one of the two I have is not allowing for fast enough render times.

[erase]

I know this thread is old but I was having this same problem and it was really frustrating to work, rendering literally brought my computer to it's knees I couldn't even browse websites. I decided to install Octane 3 Alpha 3.1 c4d plugin and it fixed the problem entirely, hope this helps.