OTOY Forums

aoktar wrote:It's working but not as should be. It destroy the lighting and environment. So C4D's solo is much better in case.

just lock the "visible in Renderer" option of lights and octaneSky in the AM then its the same.

aoktar wrote:Also I can't be agree with that should be just for viewport. It's very well on complex scenes to edit some objects. And with ASync update mechanisms, you shouldn't be breaked to work on viewport.

in a scene with 11.5 mil Tris i have to wait about 1 minute until i see my objects again in the viewport after i deactivate the viewportsolo. its like i would hit the send scene and render button. also the cpu is on 100% during this time.

fuchsundvogel wrote:

aoktar wrote:It's working but not as should be. It destroy the lighting and environment. So C4D's solo is much better in case.

just lock the "visible in Renderer" option of lights and octaneSky in the AM then its the same.

aoktar wrote:Also I can't be agree with that should be just for viewport. It's very well on complex scenes to edit some objects. And with ASync update mechanisms, you shouldn't be breaked to work on viewport.

in a scene with 11.5 mil Tris i have to wait about 1 minute until i see my objects again in the viewport after i deactivate the viewportsolo. its like i would hit the send scene and render button. also the cpu is on 100% during this time.

Yes it can take long time to appear, but you can work while waiting. Waiting occurs on Octane Core not in plugin side. There should not be any lock in viewport, isn't?

exact. there is no lock in viewport.
its just a bummer that you have to wait for the liveviewer. and if you used the solobuttonplugin and locked the octanesky visibility its now just the same. before i had the choice if i want solo affect the liveviewer. now i don´t.

Just curious, how's the stability on this thing coming along. I've been holding off from messing with it because all I do is commercial work that I live off of, but have been interested in trying it out.

Pretty good. Although I find that I get 'Render Failure' with really big scenes – like Forester trees – which is odd as I've upgraded to a 6GB card (I did have over 22 million tris in the live viewer which was amazing).. With smaller scenes it's been pretty good, although it does eventually conk out after a while. NOTE: I am using the 2.24.2 test version which is obviously still a work-in-progress..

Weezer wrote:Pretty good. Although I find that I get 'Render Failure' with really big scenes – like Forester trees – which is odd as I've upgraded to a 6GB card (I did have over 22 million tris in the live viewer which was amazing).. With smaller scenes it's been pretty good, although it does eventually conk out after a while. NOTE: I am using the 2.24.2 test version which is obviously still a work-in-progress..

I has some 'Render Failure' with really complex materials, mostly SSS stuff. Never had this before.

Weezer wrote:Pretty good. Although I find that I get 'Render Failure' with really big scenes – like Forester trees – which is odd as I've upgraded to a 6GB card (I did have over 22 million tris in the live viewer which was amazing).. With smaller scenes it's been pretty good, although it does eventually conk out after a while. NOTE: I am using the 2.24.2 test version which is obviously still a work-in-progress..

I suppose TRIANGLE LIMIT is around 19Millions. How did you rendered 22M? RENDER FAILURE and any CUDA errors is not related with plugin. So i cannot do anythings. You may export a standalone scene and send me to share with OTOY guys. But they cannot do anythings for TRIANGLE limits on 2.x.

Yambo wrote:

Weezer wrote:Pretty good. Although I find that I get 'Render Failure' with really big scenes – like Forester trees – which is odd as I've upgraded to a 6GB card (I did have over 22 million tris in the live viewer which was amazing).. With smaller scenes it's been pretty good, although it does eventually conk out after a while. NOTE: I am using the 2.24.2 test version which is obviously still a work-in-progress..

I has some 'Render Failure' with really complex materials, mostly SSS stuff. Never had this before.

Also same as wrote. Please share a C4D or SA scene to see.

So would you guys say that it's more or less stable than the official. It's not like that one is completely crash free. Or to put it another way, are the advantages worth it to use this as daily driver?

aoktar wrote:I suppose TRIANGLE LIMIT is around 19Millions. How did you rendered 22M? RENDER FAILURE and any CUDA errors is not related with plugin. So i cannot do anythings. You may export a standalone scene and send me to share with OTOY guys. But they cannot do anythings for TRIANGLE limits on 2.x.

This was the figure displayed in the LV as it was updating. For example, I have four SpeedTree objects (one tree duplicated three times) In C4D it says 6 million polys, but in the LV it says Tri:108.061m – I assumed this was the triangle count.

So is the limitation 19 million triangles (or polygons) in C4D?