OTOY Forums

glimpse wrote:we'll point this to devs, maybe there is a way to flush things out and keep the full amount under Your disposal.

in any case, thanks for reporting, I guess the hard part (for devs will be) will be to figure out what went wrong..

Thanks man I appreciate it. Something fishy is definitely up with the scene caching on these larger scenes where VRAM is being pushed to the edge. Heres another error below, even though the free VRAM was available (1gb of it)

Also understanding the below, is device 3 referring to my 3rd GPU?

Started logging on 17.10.20 04:58:13

OctaneRender Enterprise 2020.1.4 (8010400)

cannot import a regular grid from an empty voxel buffer.
CUDA error 2 on device 3: out of memory
-> failed to allocate device memory
OptiX error for device 3: [ERROR] "sbt->raygenRecord" is null
OptiX API error for device 3: Invalid value
device 3: RTX picking failed
OptiX error for device 3: [ERROR] "sbt->raygenRecord" is null
OptiX API error for device 3: Invalid value
device 3: path tracing kernel failed

Just an update, opening up older projects that I know with 100% certainty I never got this memory issue....I am now getting a memory issue (see screenshot below for log)

1GB VRAM is free. Im trying to work out what to roll back to as this never used to happen (same machine)

Thanks for any assistance!

AW

Aaron, just an idea to test, could You spin the scene without RTX boost?

glimpse wrote:Aaron, just an idea to test, could You spin the scene without RTX boost?

So working the past 2 days WITHOUT RTX I havnt ran into the issue once, or had a single crash at all (I was running into/needing to restart it every 20 mins prior)

Ive also noticed with RTX ON, rendering to the picture view works perfectly (although sometimes render times were up to 3x longer unless I restarted first)...but its just the live viewer which is crashing, with RTX ON which is having issues.

This isn't the optimal workflow as obviously working with RTX is considerably faster (3min scenes are now > 6) but at least its something for now.

What does all this mean you rekon....a bug with RTX? As I said I never used to have this issue with RTX ON going back a few months...

Thank you SOOO much for the replies....keen on your thoughts.

AW

EDIT: To be clear with RTX OFF my free VRAM is no longer slowly decreasing down to 0 and fluctuating. When I turn off layers, my VRAM comes back (this didnt fully happen before) and It stays steady (moving only up and down by 100mb). This is how it used to work for me with RTX ON and how I imagine it should be working now...?

Another addition, still getting a caching error (NO RTX),

Switching between projects, my VRAM isn't resetting. A restart of C4D fix's this, but just thought to note that that is still present with RTX OFF.

0gb VRAM on crash, 5gb free on restart. Same scene, all the same objects on. Once working everything is fine though (until project switching without closing C4D first)

Thanks for information so far, Aaron.

quick question, actually few (if You would have a minute to reply):

* You mentioned that You did not have same issues before, maybe You remember what version of OctaneRender You were using?
* if You upgraded C4D, maybe You can tell what version You tried now and what versions before? (when You did not have the issue)

did You change anything in Your machine, do You happen to use anything in the background while rendering, that could theoretically require VRAM? Maybe some plugin for C4D? maybe standalone application? I know these question might sound strange to You, but we are trying to figure out what could be causing this so any information would be helpful.

glimpse wrote:Thanks for information so far, Aaron.

quick question, actually few (if You would have a minute to reply):

* You mentioned that You did not have same issues before, maybe You remember what version of OctaneRender You were using?
* if You upgraded C4D, maybe You can tell what version You tried now and what versions before? (when You did not have the issue)

did You change anything in Your machine, do You happen to use anything in the background while rendering, that could theoretically require VRAM? Maybe some plugin for C4D? maybe standalone application? I know these question might sound strange to You, but we are trying to figure out what could be causing this so any information would be helpful.

Thanks for getting back to me! Hoping to get this sorted so ask away any questions you champions might need

- I can’t remember which version exactly. As of July everything was working perfectly (I was up to date with everything then). I never had these issues before (exact same setup) and only started noticing this issue in August/September. I would roll back, but unsure if the conflict is OS, Octane, Nvidia etc

- Been using the same R21 version all this time so no changes there

- Nothing has changed in the machines hardware or software (outside of OS updates). No BG processes, all BG apps closed, fresh restart, all caches are cleared etc.

- I’m not using any other plug-in other than C4D/Octane, and as I mentioned the VRAM consumption is all over the place with RTX on, which is something I only notice in Octane (with NOTHING else open in the BG). Running external benchmarks etc and everything outside of C4D is silky smooth.

Any ideas?

Hi Aaron,

Thank you for your help. I have been testing the scene you shared with Tom Glimps, unfortunately I could not reproduce the issue you describe using the same version of the plugin you shared.

Memory usage looks stable regardless whether RTX is on/off, both used/free VRAM go always back to the same values once the scene is reverted to the original state after removing any layers.

Would you be able to share a list of specific steps to follow in order to be able to see the same behaviour?

Regards.

mojave wrote:Hi Aaron,

Thank you for your help. I have been testing the scene you shared with Tom Glimps, unfortunately I could not reproduce the issue you describe using the same version of the plugin you shared.

Memory usage looks stable regardless whether RTX is on/off, both used/free VRAM go always back to the same values once the scene is reverted to the original state after removing any layers.

Would you be able to share a list of specific steps to follow in order to be able to see the same behaviour?

Regards.

Hi Mojave

As I mentioned to Tom, simply toggling the scatter on and off did the trick and produced the error within a minute or so and I could replicate this every time. If you're not getting that and its all smooth, what does that indicate on my end? I have tried multiple Nvidia drivers, and multiple Octane drivers and am still getting the issues. Hardware checks show my GPU's, memory, VRAM are all running without errors.....so I have no idea what I can try! Any ideas?

Can you share a couple of screenshots of the UI showing exactly what you change to make this happen or a video showing the issue please?
Thank you.