Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Just installed 5.3.5 and went to pre-pop the GPU cache. Menu option it's missing. OK, maybe you removed that? or did you MOVE it?
anyway,
Also, i opened a scene i've been rendering this week at 2K res and now, it is giving me a black render screen, then an error, and it says the GPUs ran out of memory. They didn't when i rendered whole sequences 2 days ago.
i went back to 5.3.4 and the image rendered normal.
Are we needing to update scenes for things like this? Is the existing Optix denoise node no good?
As for the black renders, are you getting a message that says
ERROR | [gpu] CUDA call failed : (712) part or all of the requested memory range is already mapped
If so, that's not running out of memory. That's a known GPU regression that appears on followup renders which we hope to have fixed in the next bug fix release.
i reinstalled 5.3.5 so i could see the error again.
The render gets to 50% (i can see the progress in the render window) then, the image goes black.
the error I get is "# Warning: Cached Playback: Out of memory. Allocated memory limit for caching has been reached so caching has stopped. See the Script Editor for details."
On 2nd attempt, i did get the error you're referencing.
The cached playback message is a surprise to me. I assume you have "Viewport hardware cache" selected, so this is indeed the GPU running out of memory. And you aren't running out of memory with 5.3.4 (note this is a warning, not an error, so rendering will still work regardless)? If the cached playback is indeed only running out of memory on 5.3.5, that suggests maybe 5.3.5 has some additional issue with respect to gpu memory usage.
