Tue, Dec 24, 10:29 PM CST

Renderosity Forums / Vue



Welcome to the Vue Forum

Forum Moderators: wheatpenny, TheBryster

Vue F.A.Q (Last Updated: 2024 Dec 13 6:58 am)



Subject: Vue 8 System resources usage are unacceptable


Tubbritt ( ) posted Fri, 06 November 2009 at 6:02 PM · edited Mon, 09 December 2024 at 10:12 PM

Hi all.

I have to say that I'm trying my hardest to be positive with the upgrade to vue8 but man, this is by far the the most disappointing upgrade for me yet.

The bugs I can workaround, but the system resource usage of vue8 is totally ridiculous. A scene that uses 10% of my resources in Vue7 will use 70% in Vue8 and display a warning telling me my resources have dropped to a critical level.

In all fairness....   that's unacceptable in my opinion and I can't see how e-on can see this as an improvment.

Regards
James


Rutra ( ) posted Fri, 06 November 2009 at 6:05 PM

Hi James. :-)

What system do you have?


Tubbritt ( ) posted Fri, 06 November 2009 at 6:14 PM

Right now I'm on my Laptop.
2.2Ghz Dual Core, 512MB Gforce 9600m GT, 4GB RAM and Vista 32.

I have a Quad Core desktop for doing my rendering, but I always create my scenes on my laptop because my desktop PC is in my Recording Studio and not my home.

Regards
James


Rutra ( ) posted Fri, 06 November 2009 at 6:20 PM

32 bits. That's your problem. That limits Vue to use only 2GB of the 4GB you have. Every new software release (not just from e-on's) demands from the hardware. That happens with Microsoft Office, with 3DS Max, you name it. Vue is no exception.

64 bits systems (and a good amount of RAM) are more and more required for doing any serious work in Vue (or many other 3D apps). You should seriously think about upgrading your hardware.


Tubbritt ( ) posted Fri, 06 November 2009 at 6:36 PM

Hmmm... I understand but it's hard to get away from the maths on this one.
How can a scene that uses only 10% of my resources in Vue 7.51 all of a sudden need 70% in Vue8.

That's a pretty freaking big difference.

If I launch Vue 7.5 and 8 one at a time to see how much resources I have free when no scenes are loaded, there is only an increase of 9% for vue 8.

Regards
James


Tubbritt ( ) posted Fri, 06 November 2009 at 6:43 PM

I don't believe it, ...... I found the cause by pure accident just now. It's OpenGL 2.1

If I switch back over to OpenGL hardware the scene only uses 10% of my resources. Turn it back onto OpenGL 2.1 and the scene will take 70% of my resources and display critical memory errors.

Ok... I lived without that “feature” this long, I'm switching it off until e-on sort this out.

Regards
James.


Rutra ( ) posted Fri, 06 November 2009 at 6:46 PM

We saw the same from Vue6 to Vue7. There were many threads here with the same situation as you describe now. Vue7 has a bigger memory profile than Vue6. Vue8 has a bigger memory profile than Vue7. Vue9 will have a bigger memory profile than Vue8.

Instead of looking at resources (which may be deceiving), look at the amount of RAM. Open your task manager and in the processes page look at the amount of RAM that Vue uses in each case. I never saw the numbers from "resources" explained in a satisfactory manner. There seems to be some non linearities with these numbers. If you want to have a concrete feeling of what's happening, the amount of used RAM is a better indication, IMO.


Rutra ( ) posted Fri, 06 November 2009 at 6:48 PM

We cross-posted. I'm glad you found a workaround. :-)


nruddock ( ) posted Fri, 06 November 2009 at 6:55 PM

The resources number almost certainly takes into account other things besides main memory usage, e.g. various OpenGL related things, the amount of which will depend on your graphics card and drivers.

Try turning off (or otherwise adjusting) some of the display features.


Tubbritt ( ) posted Fri, 06 November 2009 at 7:02 PM

Thanks guys.
I'm going to open a ticket with e-on on this and let them know. OpenGL 2.1 surly shouldn't be eating that much memory.

Regards
James


Tubbritt ( ) posted Fri, 06 November 2009 at 7:21 PM

Thanks guys.
I've opened that ticked with e-on and when they get back to me I'll let you know what they say.

I can't see it being right that OpenGL 2.1 would cause scenes to use 6 times more memory.

Regards
James


bruno021 ( ) posted Sat, 07 November 2009 at 3:24 AM

On my system, using the Shader4 model, I start at 67% resources free. If I use the standard ardware accelerated OpenGL, I start at 84%.
So the difference is quite important, but not as much as on your system. BUt I'm 64bit with 8 gigs of ram.



ShawnDriscoll ( ) posted Sat, 07 November 2009 at 4:18 AM · edited Sat, 07 November 2009 at 4:19 AM

Quote - Hmmm... I understand but it's hard to get away from the maths on this one.
How can a scene that uses only 10% of my resources in Vue 7.51 all of a sudden need 70% in Vue8.

Vue 8 Infinite turns on displacement for any materials that had bump maps used in 7.51.  I had to turn displacement off on such materials in Vue 8 (via the Function Editor) until I got back all my resources that were available in 7.51 with the same scene.  Crazyness.

www.youtube.com/user/ShawnDriscollCG


bruno021 ( ) posted Sat, 07 November 2009 at 5:19 AM

What is important here is not the Ram amount on your system, but the video memory present on your graphic card.
And according to Shawn, displacement is on on many materials (hadn't seen this myself), and memory reqirement for displacement can be quite high, both graphic and system ram. There is an amount limit for for displacment display and ecosystem display in the display options box. This is the max amount Vue will use. You can either lower or up this value according to your graphic card's memory amount, with a limit at 1 gig.



Tubbritt ( ) posted Sat, 07 November 2009 at 8:38 AM

Hi Guys.
I'm not sure I understand what you mean about displacement in this situation.

If I turn off OpenGL 2.1 in Vue 8, my scene will only use 10% of my resources. If I turn it back on the same scene will use up 70% of my resources and give me warnings about my memory being at a critical level.

So same scene, same program, only difference is OpenGL 2.1 turned on vs off.

Kind Regards
James


Tubbritt ( ) posted Sat, 07 November 2009 at 9:06 AM

Sorry I can't edit my post and that should say that if I turn OpenGL 2.1 off, same scene will use up 70% of my resources.


Tubbritt ( ) posted Sat, 07 November 2009 at 9:28 AM

Damn copy and paste... my post is wrong again.

Never mind.... I know the problem is the OpenGL 2.1 anyway and I have a ticket open with e-on


bruno021 ( ) posted Sat, 07 November 2009 at 11:48 AM

Yes, openGL201, shader model4 is your problem, what is your graphic card and how much ram doe sit have? This is I think the biggest problem.



blaineak ( ) posted Sat, 07 November 2009 at 1:20 PM

That sounds like a bug you should report.

You won't be happy until you go to 64 bit. Most issues evaporate.


Tubbritt ( ) posted Sat, 07 November 2009 at 1:26 PM

It's a G Force 9600m GT Cuda with 512MB dedicated video memory

I've spent the entire day working away with OpenGL 2.1 turned off and the experience has been very good. I've loaded up some of my very complex scenes and the systems resources usage is been really good. Almost identical to Vue 7 usage.

The second I turn OpenGL 2.1 back on, the resources usage goes through straight the roof. Everything seems roughly 6 or 7 times larger when OpenGL 2.1 is switched on in Vue 8.

With nothing loaded at all it even uses an additional 10% of my resources.

Regards
James


skavan ( ) posted Tue, 01 June 2010 at 10:52 AM

**Tubbritt - you are a life saver. I have been pulling my hair out trying to do anywork:
Windows 7 (32-bit) 4GB Ram. Quadro FX 5600...!! and I couldn't import any consequential files into the environment without running out of RAM. System reources would start at 32% -- until I imp;emented the switch you described...and VOILA!!!

All i good...THANK YOU!**


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.