Page 1 of 2
Bug / Error
Posted: Tue Mar 31, 2015 7:10 pm
by Refracty
Hi face,
I have an error after reloading the Octane viewport.
Any ideas?
Thanks
Refracty
Re: Bug / Error
Posted: Tue Mar 31, 2015 9:30 pm
by roeland
My guess is the scene is very heavy on geometry. We currently have a limit in how much memory is taken up by geometry, which is 2GB. This limit is there for performance reasons.
--
Roeland
Re: Bug / Error
Posted: Tue Mar 31, 2015 11:35 pm
by Refracty
It is a complex scene but the Graphics Card has 12 GB and should handle it easily.
Why is there a limitation?
I need the scene to run.
Re: Bug / Error
Posted: Wed Apr 01, 2015 12:13 am
by abstrax
Refracty wrote:It is a complex scene but the Graphics Card has 12 GB and should handle it easily.
Why is there a limitation?
I need the scene to run.
As Roeland said, it's there because of performance. If it wouldn't be there everything would render ~10% slower. And no, currently we can't switch between those two modes. Octane 3 will allow larger geometry. Until then you have to reduce scene complexity.
Re: Bug / Error
Posted: Wed Apr 01, 2015 12:16 am
by face_off
You can reduce the number of triangles in the scene by selecting appropriate meshes, and in the Properties->Object window, tick Custom Mesh, click Adjust->Simple Controls, and move the slider towards "Fewer Polygon".
Paul
Re: Bug / Error
Posted: Wed Apr 01, 2015 4:12 pm
by Refracty
Thank you Marcus and Face for the clarification.
Unfortunately I can not reduce the scene much more. It is a big architecture scene and I have already shrinked everything to a minimum.
My client is using VRay at the moment but I am working on bringing this project into Octane to have more instant feedback.
So lets wait for Octane 3...
Re: Bug / Error
Posted: Wed Apr 01, 2015 6:38 pm
by Refracty
So is there any advantage of using a graphics card with more then 6GB VRam in Octane 2 ?
It looks like that the geometry limitation makes a 12GB Card useless.
Re: Bug / Error
Posted: Thu Apr 02, 2015 12:31 am
by face_off
Keep in mind the the render pass outputs (ie. the Viewport) take VRAM too - so if you render very large resolutions, it will take a lot if VRAM. Plus you 12GB can be used to store texturemaps.
Paul
Re: Bug / Error
Posted: Fri Apr 03, 2015 12:17 pm
by Refracty
That is true. On the other side out of core rendering will minimize the VRam consumption for textures with acceptable performance loss.
Hopefully Version 3 will bring the solution for this heavy scene.
Cheers
R
Geometry Limit
Posted: Sat Apr 25, 2015 9:32 am
by Refracty
Using a different scene I am running into the same problem. I have a detailed Car interior with exterior on seperate obj files with more then 20.000 Polys. The TitanX shows only a consumption of 15 percent when I only load one of them. So much headroom.
But I am not able to load them together. That is a pitty because I thought Octane is now ready for Automotive Visualisation (of heavy tesselated cars) when the TitanX came up.
Can the geometry limit be removed easily? I need to work with Octane when doing this kind of renderings.