Vray 1.48.66 will not take more that 300.000K of memory

[dwanimations]

Hi

I am using the new vray and I have 4gb ram... but vray only uses 300mb...
When I set the Dynamic Memory Limit to 4000mb. It still stays at 300mb max... And the rendering takes a very long time
Is this maybe a known bug?

And I want to say that I know you guys are working hard to fix all the problems.. If you need more details form this problem I am having pleas say so.

Thanks and good luck

[-Keith]

Re: Vray 1.48.66 will not take more that 300.000K of memory

Hey,

This is a Microsoft thing
http://www.microsoft.com/whdc/system...AE/PAEmem.mspx

All 32bit applications behave like this.

[dwanimations]

Re: Vray 1.48.66 will not take more that 300.000K of memory

But I am not working on a 32x platform I am using 64x vista (sorry forgot to say that) Hope you can give some advice?

And I only was able to use 300mb. of memory while I should be able to use more than that Even if I was working on a 32 bit machine. I should than also use 3.000mb insted of 300mb max.

[-Keith]

Re: Vray 1.48.66 will not take more that 300.000K of memory

Sorry I was not clear.

V-Ray is a 32 bit program just like its host programs SketchUp and Rhino. It will behave as a 32bit program regardless of the OS and machine it is installed on. Once we have 64bit versions of Rhino and SketchUp we can begin developing a 64bit V-Ray for them. So far Google has not announced any intention of creating a 64bit version of SketchUp, and McNeel is working on a 64bit Rhino.

[thomthom]

Re: Vray 1.48.66 will not take more that 300.000K of memory

64bit SketchUp? That'd be the day. :

[dwanimations]

Re: Vray 1.48.66 will not take more that 300.000K of memory

I understand. but still why is it not using more that 300mb (when I chek with my taskmanager) of memory It can go up to 3.000mb. whit 32bit apps. whit My old vray for us it used normaly about 1.400mb. of memory not just 300...

I was wondering why it is this low

[-Keith]

Re: Vray 1.48.66 will not take more that 300.000K of memory

300 ohh I thought that had been a typo and that you meant 3000.

Is this any scene? even new ones?

[dkendig]

Re: Vray 1.48.66 will not take more that 300.000K of memory

Just to help clear things up, here in the US, we use commas to separate the thousands place in numbers, and periods to separate between whole numbers and decimals. So your 3.000 would mean 3 in the US, and we would actually write that number as 3,000. Or... I'm completely wrong and I should go away.

[dwanimations]

Re: Vray 1.48.66 will not take more that 300.000K of memory

Ow haha..

Over in the EU we have a different way. excuse me for the confusion. let’s put it this way.
when I render in (the new) Vray the max ram the render uses is just 300MBm regardless of what I put in the "Dynamic Memory Limit" I was looking for a solution to get a larger usage... Whit my old version could use about 1400MB of ram.

Is there someone that knows how to get this ram usage up end increase the speed of my render because a ram usage of only300mb makes my renders (“vray tests”) take very long.

[dwanimations]

Re: Vray 1.48.66 will not take more that 300.000K of memory

Is thare somone that understands my problem???? and knows how to handle it

[thomthom]

Re: Vray 1.48.66 will not take more that 300.000K of memory

Does it happen to every model that it takes a long time?
Do you have a picture of your scene?

Why are you so sure it needs to consume more RAM?

[dkendig]

Re: Vray 1.48.66 will not take more that 300.000K of memory

Yeah, memory shouldn't be an issue unless you run out of it. It sounds to me like there's something else going on. I'm kind of busy with the latest beta, so I can't really play with any scenes just yet, but I hope to be able to help you out soon.

[dwanimations]

Re: Vray 1.48.66 will not take more that 300.000K of memory

ok... great. When you are able to do that you can contact me via mail..?

hope to hear from you soon.. Good luck

[dkendig]

Re: Vray 1.48.66 will not take more that 300.000K of memory

I created a ticket about this issue. I hope to resolve this bug soon. Also, I guess I missed this earlier, but the Dynamic Memory setting you're referring to should have nothing to do with this issue as far as I know. If that number actually dictated how much ram VfS was allowed to use, everyone would be able to render enormous scenes with no problems, same with VfR users. Unfortunately this is not the case. I did a google search for some more information on this setting, beyond the textbook definition which pops up as a tooltip when you hover over the control.

http://forums.cgarchitect.com/28336-...ory-limit.html

So the only dynamic geometry that we support at the moment, would be displacement. So unless you're using a lot of displacement in your scene, I don't think that setting will effect anything at all.