Error "out-of-core memory limit exceeded" Tweet

[Lord-Kvento]

In Maya 2018.5 and 2020 I ran into the problem:

I get the message "out-of-core memory limit exceeded"
although Out-of-core was turned on, but for some reason it is not used or does not work.

I tested this on Maya 2018.5 and 2020 on Octane v4.05-13.48 and 2020.1rc2-17.13-beta

PC configuration:
Win 10 x64 (1909) | Geforce 2x GTX 1080ti, 1x RTX 2080ti | i7 4790k | 32GB
At the moment I am using 442.92 studio driver (dch), but I also tried to install other drivers, for example, 445.75 game ready (no dch) (I deleted old drivers using DDU).

I use ORBX to load the environment (the environment is created in C4D and works fine in Standalone), maybe that matters.
At the same time, this scene works great in C4D and there are no errors or messages like "out-of-core memory limit exceeded".

In my case, reproducing the problem is easy enough, I just created many primitives in the scene and assigned them a large OpenSubD level = 5 (or more) to get more polygons.
And I expectedly got the same error.

Is there a solution to this problem, maybe I'm missing something?

[Lord-Kvento]

So, in search of a solution, I noticed that there is a note in the documentation that 'out of core' only works for textures and does not work for geometry.

This information is relevant?

I'm confused because that in Cinema 4D the 'out of core' option works with both textures and geometry.

I thought this was the standard for Standalone and for all plugins. Or is it not so?

[JimStar]

This is not a plugin's issue. The error you see is logged by Octane rendering core, not by the plugin.
There could be many reasons why you don't see it in C4D. For example Maya and C4D themselves may use different amount of CPU memory. I addition Maya itself uses CUDA too, so it may "steal" some amount of GPU memory/resources from Octane...
In any case this is a question for the standalone section of the forum, not for the plugin section... Because as I said - this error is generated by the rendering core, so it is the core development team guys who know what exactly that logged error means...

[Lord-Kvento]

In any case this is a question for the standalone section of the forum, not for the plugin section...

So, should I re-create this topic in the Standalone section?

And what about geometry, 'out of core' works with geometry or only with textures (as written in a note in the documentation)?

[Lord-Kvento]

This is not a plugin's issue. The error you see is logged by Octane rendering core, not by the plugin.
There could be many reasons why you don't see it in C4D. For example Maya and C4D themselves may use different amount of CPU memory. I addition Maya itself uses CUDA too, so it may "steal" some amount of GPU memory/resources from Octane...
In any case this is a question for the standalone section of the forum, not for the plugin section... Because as I said - this error is generated by the rendering core, so it is the core development team guys who know what exactly that logged error means...

But then why when I export the same scene to Standalone does it work without problems?
And out-of-core works fine inside Standalone, also like in Cinema 4D, but not in Maya.
It seems like OOC (mesh) just doesn't work in Maya. In addition, this happens on all versions of Octane. And this problem manifests itself ONLY in Maya. I think that if it were a core error, it would manifest itself in both Cinema 4D and Standalone. This is true?