Octane memory problem

Sub forum for bug reports
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.


All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
janmorek
Licensed Customer
Posts: 7
Joined: Fri Nov 10, 2017 5:25 pm

I´m using Octane with Blender for more than 4 years and the following problem is killing me since the beginning.
One year ago I documented it and posted it in Blender+Octane Facebook group, admins acknowledge that it´s a real problem, I think one of the biggest problems, but nothing happened yet.

I´m posting it again, hopefully, Otoy will do something about it and finally fix it.

Please check this document with a detailed explanation:

https://docs.google.com/document/d/1U0s ... llGf4/edit
User avatar
promity
Licensed Customer
Posts: 363
Joined: Sun Dec 19, 2010 7:59 am
Location: Russia

Have you tried out of core option? My scenes traditionally go over 15-20 million polygons and I managed them on much weaker video cards with the help of OOC. Of course, I strongly doubt that two titans of 24 gigabytes each cannot cope with 16 million polygons. But I'm wondering - will anything change in your case when using Out-of-Core?
AMD Threadripper 1950X/64gb ram/RTX 3080 Ti + RTX 2070/Samsung SSD 870 EVO 500 gb/
Lightwave 3d
janmorek
Licensed Customer
Posts: 7
Joined: Fri Nov 10, 2017 5:25 pm

Of course, I tried,

Also, several other users tried it with different cards and have the same problem.

Please try to reproduce the test with spheres.
linograndiotoy
OctaneRender Team
Posts: 1355
Joined: Thu Feb 01, 2018 7:10 pm

janmorek wrote:I´m using Octane with Blender for more than 4 years and the following problem is killing me since the beginning.
One year ago I documented it and posted it in Blender+Octane Facebook group, admins acknowledge that it´s a real problem, I think one of the biggest problems, but nothing happened yet.

I´m posting it again, hopefully, Otoy will do something about it and finally fix it.

Please check this document with a detailed explanation:

https://docs.google.com/document/d/1U0s ... llGf4/edit
Hi Jan, I've tried here with about 18 spheres (31.850.456 total polygons), no problem.
Which version are you using? And which GPU(s)?
Capture.PNG
janmorek
Licensed Customer
Posts: 7
Joined: Fri Nov 10, 2017 5:25 pm

I have 2xRTX Titans
I tried many versions and that problem is everywhere.
In May of 2021, you confirmed on facebook that you notice the same problem.

Please download this file and try to render it: https://drive.google.com/file/d/19EmDwV ... sp=sharing

Thanks
linograndiotoy
OctaneRender Team
Posts: 1355
Joined: Thu Feb 01, 2018 7:10 pm

I remember I confirmed that.
Now I'm getting some similar issue in the current internal version, even if i'm using many polygons.
Needs more investigation for sure.
janmorek
Licensed Customer
Posts: 7
Joined: Fri Nov 10, 2017 5:25 pm

Lino thanks for your help, but I got the same answer "Needs more investigation for sure" almost one year ago and nothing happened.

Could you check if there is the same problem also in Octane for Cinema, or other software?
Berube
Licensed Customer
Posts: 31
Joined: Fri Aug 07, 2020 4:40 am

Hello everyone,

I see the same problem on my side as well.
I would agree this is an important issue.

janmorek Nice work on your documented details.

Best,

-Berube

http://www.johnberube.com

A. MacOS Monterey 12.2
B. AMD Radeon Pro Vega II Duo 32 GB
C. 384 GB 2933 MHz DDR4
D. N/A
G. Octane PR13 Blender
linograndiotoy
OctaneRender Team
Posts: 1355
Joined: Thu Feb 01, 2018 7:10 pm

janmorek wrote:Lino thanks for your help, but I got the same answer "Needs more investigation for sure" almost one year ago and nothing happened.

Could you check if there is the same problem also in Octane for Cinema, or other software?
I did, and it's definitely a Blender only issue.
The developer is working on that.
janmorek
Licensed Customer
Posts: 7
Joined: Fri Nov 10, 2017 5:25 pm

Lino, could you please inform us about the progress? and is there any progress since I reported it 9 months ago?

We are paying for the software that isn´t working properly and at least 9 months (probably more) devs know about that.
It´s great that you are working on new features, but it is all useless for me if I´m not able to render scenes at all.
Or I am able to render but have to optimize everything, waste a lot of time, and then pray so it works.

This isn´t a small bug, for me, and I believe for everybody who´s doing archviz is it the most crucial thing.

One year ago, I´ve started working on tutorials about Blender + Octane, it was quite popular, but then I stopped,
because I realized that I don´t fully believe in that software and I just can´t tell people - use Octane it´s the best what you can have with Blender.

Yes, it´s much better than Cycles when it comes to results, but you will waste tons of time until you will know how to deal with that bug, and even that it bothers you with each big archviz project.

So, please, do something about that.
Post Reply

Return to “Bug Reports”