OTOY Forums

Posted: **Thu Jan 12, 2017 9:18 pm**

Where is the rest of my memory? Octane for modo leaves me with more than 6gb in the same scene.

Thanks

Posted: **Thu Jan 12, 2017 10:02 pm**

What I understand is that octane only use 1 Gb Vram here, 4 Gb of your 8 Gb are taken by the sytem and other applications and possibly a lot by Maya viewport, but that's really a lot, that's not a normal situation.
What viewport do you use in Maya ? viewport 2.0 or legacy viewport ? is it possible that you increase too much the level of smooth mesh preview ?

to display VRAM used by viewport 2.0 in Maya use this command:

Code: Select all

ogs -gpu

too flush the memory used by the viewport 2.0 use this command :

Code: Select all

ogs -reset

Posted: **Thu Jan 12, 2017 11:55 pm**

calus wrote:What I understand is that octane only use 1 Gb Vram here, 4 Gb of your 8 Gb are taken by the sytem and other applications and possibly a lot by Maya viewport, but that's really a lot, that's not a normal situation.
What viewport do you use in Maya ? viewport 2.0 or legacy viewport ? is it possible that you increase too much the level of smooth mesh preview ?

to display VRAM used by viewport 2.0 in Maya use this command:
Code: Select all
ogs -gpu
too flush the memory used by the viewport 2.0 use this command :
Code: Select all
ogs -reset

Maya Viewport ogs-gpu is 1770. When I connect one 8k texture it drops to 3200M. When I change to legacy viewport it goes to 4200M again. I think it is to much memory consumption. The same scene in modo left 4700M. Not much difference. Only the programs are open.
I like octane but 8gb memory dont look enough more. =) . Hungry octane.

Posted: **Fri Jan 13, 2017 2:31 am**

there have been very bad memory issues with me, and another user as well, so you aren't the only one.

Posted: **Fri Jan 13, 2017 5:25 am**

@Tharso ,

Lol, almost 2 Gb of VRAM taken by Maya viewport, this is huge, do you know you can limit the resolution of textures displayed in the viewport to avoid this problem ?
there's no point to use the full resolution of a 8k texture for the viewport.
Also maybe there's a problem with the Maya plugin displaying textures and not following Maya viewport preferences for textures or VRAM mismanagement for Octane viewport textures.
Personally I don't trust the Maya plugin for viewport textures (lot of glitches in previous version),
to avoid these kind of problems, I never display textures in the viewport unless I absolutely need it.
so I put my viewport in direct X mode, as the plugin doesn't support direct X at all, no textured are displayed but also no VRAM is taken at all,
and I only override in viewport the Octane Material with a Maya material when I really need to display a texture.
Then I never have this kind of issues.

@itsallgoode9,

I don't think your issue has anything to do with Thalso issue at all, unless this is also a viewport issue and bad flushing of viewport textures ?
but I think your issues are Pascal GPU relatives, and there is some good news on this side !
Octane 3.06 will be more optimized for Pascal GPUs and should solve some of the issues:

abstrax wrote:I basically spent the last month investigating these kind of issues. Unfortunately I couldn't find any actual culprits, but observed various problems with the CUDA 7 / 7.5 and 8 compilers usually resulting in inexplicable kernel crashes which - when debugged - didn't make any sense, i.e. look like compiler problems. I think / hope to have found workarounds for all of these.

I also noticed that most of the CUDA error reports come from users with Pascal hardware and I wonder if there is a general problem with that, but it's really hard to tell. I haven't observed any of the reported sporadic problems with our Pascal hardware yet.

Another thing I have noticed is that the CUDA errors often happen on scenes with very big geometry. In those cases the ray tracing will access the geometry data in a different way than usual. Unfortunately this access method is very unforgiving for invalid memory access. So there may be a chance that there is a problem somewhere in our geometry data structures, but I couldn't find anything yet.

So the plan forward is to release a test build of 3.06 with new features and various changes to address the problems above. This build will also be compiled completely in CUDA 8. Hopefully this will improve things if not I will keep digging.

Posted: **Fri Jan 13, 2017 2:04 pm**

@ calus, yeah I guess that is true. I don't think the issue i'm having is related to viewport. Hopefully you're right that's it's just a pascal issue that will be fixed! up.

Posted: **Sat Jan 14, 2017 1:10 pm**

Hunmn, I am using two 1070.

OTOY Forums

memory problem

memory problem

Re: memory problem

Re: memory problem

Re: memory problem

Re: memory problem

Re: memory problem

Re: memory problem