Insufficient free RAM Preferences

[Gray_Parrot]

Thanks for confirming this, Funk. How did you manage to resolve this problem? I tried the downgrading of GeForce drives but this did not help, unfortunately. I can confirm that the exact same file exported to Octane standalone from my Mac renders without issue on the windows computer that has the fault with the modo plugin. This is the best confirmation that the issue is not related to sufficient ram. Task manager shows only 40 percent ram usage even when I open up a few other programs.

I would love to be able to use the modo plugin in Windows. Thanks for any help in advance!

[funk]

The cube error was just a random issue a restart fixed, but it's obviously not accurate.

In other cases, I have had to mess around with the preference values to try and find something that worked. I would get one error if the value was too high, then a different error if the value was too low. I found it quite frustrating..

Please give us a way to turn this option off.

[Gray_Parrot]

Ha, yes, this is exactly what I’ve been playing with. I’d like to second what Funk is saying. If there is a way you could make this optional Paul, I’d appreciate it. Perhaps this is not an issue with Mac OS because of how the scratch disks work by default when RAM pages out? Appreciate your comments, everyone. Thanks!

[face_off]

Hi Paul, thanks for your reply. 16 GB is installed on a fresh install of Windows 10 on the Razerblade 15” Nothing else is running on the machine. I’m receiving this error message with Max Verts set to only 500 and a simple low poly cube in the viewport. Just like the gentleman above describes. I have your plug in running at the same time on my 2017 MBP connected to an external GPu 1080ti and it is running fine. The scene that triggered this is relatively large and so could trigger the “too many verts” warning but I simply got this new one instead. So directly comparing the same scene between Very similar hardware the windows install simply does not work.

Clearly you will get the "Too many vertices" error if you set the Maximum Vertices to 500 and have 600 vertices in the scene. With 16GB of RAM, I would recommend a Maximum Vertices setting of 10 million. If you still get the error, can you pls post a screenshot showing the Octane preferences panel and the error, and also the Task Manager Processes windows sorted by Memory.

Thanks

Paul

[Gray_Parrot]

Thanks for your reply, Paul. Well, yes, the too many verts warning is understandable and I’ve learned how to work around that. Yet, reviewing this thread, I do not believe any of the three people commenting have raised an objection to this dialogue box. To reiterate: the problem is with the insufficient ram dialogue that blocks the scene loading from modo into octane even when that scene is tiny and the RAM resources are plentiful. I would love to rap with you about what may be going wrong here in a couple of days—screenshots and all—but at the moment I’m under a deadline and had to switch back to the set up on an older Windows machine. Paul, once again, thanks for your work on this plugin, I’m sure that you don’t get all the praise you deserve for the innumerable features that work perfectly!

[face_off]

OK. There is not much I can do to help you unless you provide the information I requested. Hopefully you can provide it after your deadline.

Paul

[funk]

Paul, until you added this option, I never had any issues.

Please make it optional.

[marchermitte]

I think the error message says it all. Lower the Maximum Vertices in the Preferences, or free up some RAM on your PC by closing other applications.

Paul

Right, when I load my scene, the ram of my video board is almost entirely free, my computer has 20 gigs free (out of the 32 available) and after changing the Nvidia drivers, I get this message only when I refresh the IPR but not when I stop the rendering and restart It.
It feels like this function isn't working properly.

[funk]

marchermitte can you post a screenshot of preferences > rendering > octane?

[Rahll]

I can also confirm this bug. I think in some circumstances it legitimately gets triggered, but then refuses to stop triggering even after you've fixed your scene or opened a new one that doesn't even have any geo, or like someone mentioned, just using a test cube.

It's been a few months since I had the issue, but I noticed when I tried to change my vert count in the preferences, it would frequently refuse to save the new number I put it when I checked again after the issue continued.

Unfortunately I can't entirely recall how I resolved it, but I think it have just been changing the vert count repeatedly until it finally stuck. I think I chopped a zero or two off, closed it, rebooted modo, and then tired to render, then added the zeroes back until it stuck again. I think there's something definitely wrong with how Octane is reading that option, but it's probably a hard issue to replicate

For reference, I'm using 11.2v3.