C4D Has a Limit (AKA Windows SUCKS)

[policarpo]

Weird, I have never encountered that problem. Maybe try to reboot and see if it purges the system. :)

[Srek]

Hi,
Open GL as well as Quicktime reserve big chunks of the 2 or 3 GB available to the application (up to several hundred Megabytes). The maximum i was able to use was about 2.8 GB on a windows 2003 server system without OGL graphicscard and QT.
Cheers
Srek

[imashination]

1) How on earth is that scene using so much memory?

2) How much stuff do you have in your task bar? it looks like theres a mountain of stuff down there with even more hidden.

[hundredthirtyseven]

Set virtual memory to system managed size, don't use a certain size. That should solve this problem. I have 2 gigs of ram and I've seen a 1,4 Gb Cinema once so the limit is somewhere else, trust me.

[Hilt]

any particular reason why you have two Cinema's open?
My 3gb machine goes to 'not enough memory'. restarting cinema does the trick. Not sure if windows doesnt free the memory right or what it is.

.hilt

[Didgeroo]

Holy.. seriously rebuild those models!
They're like, solid in wireframe mode. ;o
It's enough geo in there to populate a city heh.

[illmatic]

128 mb of ram and it runs smooth for me. 1.3 processor, radeon 7000 vid card

[Rev9]

:banghead: :banghead: :banghead: This is unbelievable.... Windows is a piece of crap... I mean really, really, really a piece of crap.

I have 2GB of RAM in my system, on XP and yet Windows is STILL limited to approximately 1.2 GB per process..... I know there's the 3GB hack but it's not that trustworthy.

So here I am, and C4D says no memory.... wtf.. :banghead: :banghead: :banghead:

Click for larger view:
http://www.jase.ca/content/forumpost/c4d/cinema_4d_memorylimit_tn.jpg (http://www.jase.ca/content/forumpost/c4d/cinema_4d_memorylimit.jpg)



Took a look at your image....
Looks like you have Sasser worm on your computer, you can see the lsass.exe running as a background process... I might suggest that you grab Ad-Aware from Download.com and see if there's anything else sneaking around taking up memory.

The main problem seems to be your amount of polygons notwithstanding.

Best
BT

[neonghost]

lsass.exe is a windows system process. (http://www.neuber.com/taskmanager/process/lsass.exe.html)

[Hilt]

Took a look at your image....
Looks like you have Sasser worm on your computer, you can see the lsass.exe running as a background process... I might suggest that you grab Ad-Aware from Download.com and see if there's anything else sneaking around taking up memory.

The main problem seems to be your amount of polygons notwithstanding.

Best
BT

not necessary.
As before has been mentioned, a completely innocent system process and a dangerous virus come with the same name. No need for panic but keep your eyes open. Virus removal information can help determining whether you're dealing wtih fake lsass.exe or not. (from http://www.neuber.com/taskmanager/process/lsass.exe.html)

We have lsass.exe running here, at it cant be virus/spy/trojan, cause we're highly paranoid people with highly paranoid virus/spyware apps.

But true, a few less hypernurbs might ease the pain.

.hilt

[Uncle-Ox]

I've started a number of threads about this previously. I have the exact same problem as you. Although your poly-count does look rather severe, I doubt whether it matches some of the poly-counts I've seen on some city scenes.

My problem usually comes when I hit the render button. As soon as it passes the shadow map stage and starts to do the actual render, it pops up the dreaded "Out of memory" error. If you watch the performance meter while it's rendering, it seems as if C4D refuses to use the virtual memory. The physical memory drops to 0MB and out pops the clown.

It's happened to me in the strangest of circumstances as well. For example: I was running a particle system the other day and one would think that the particle count would cause this problem if it's set way high. Uh-uh! Adjusting the speed of the particles fixed the problem.

The last time I had the problem (thank goodness, more than 2 weeks ago) was because of CB Tags which floated invisably around in my scene. Clearing that fixed my problem right up.

The suggestion about not adjusting the virtual memory had also occured to me so what I did was to restore my drive image to get my PC back to its "fail safe" state (No adjustments had been made to the virtual memory there). No joy. This didn't fix the problem at all.

Please let me know if you find a solution or work-around. It seems like my problem has disappeared for the time being but I need to know how to fix the sickness and not just its symtoms. (Hope that my PC isn't to badly infected by that costly virus which is loosely refered to as an operating system :twisted: )

[lllab]

first yes windows sucks. ( buy a mac;-)

second check you modell, it looks way to dense polygons

third if you have to render huge things do boot ini, it is very stable here on my xeons.
you can make it that you can choose to start normal or in 3gb mode.(do a search on this forum and you find what you need)

forth have i said you could "optimize" you modell a bit;-)

cheers

lllab

[AdamT]

Another option would be to render it via NET so you don't have the scene loaded into memory twice--or close the scene as soon as you hit the render button.

And of course do something about that ultra-dense mesh.

[tapaul]

how many polys does that have?

regards
Paul Everett

Nice to see that sniper can render it :)

[Siddhy]

Apart from the obvious whih was mentioned:

- Microsoft Antispyware is Betasoftware. It slows down your computer by random memory hogging with (if you didn't switch it off) incredibly useless and resource blocking "security features".

- Norton Antivirus - sorry i know its widespread - is another big slowdown. Throw it off and use some lightweight Antivirus Scanners like Avast and if needed a PFW.

- Polytrans, Barca, second Instance of C4D, Opera, even a VNC Server and other stuff is running while rendering such a scene. Why?

Anyway here and in the german forums are suspiciously many threads about memory problems since 9.1. Is there a link? Or do people think with the new update they can toture their machines? :)

[thorn3d]

That's probably one of the best examples of over-modeling i've ever seen... you've got at least 800,000 too many polys for this object. Even if it's for hi-res, you have too many... as previously said, your wireframe looks nearly solid.

Windows is what it is... but your scene is problematic to start with.

thorn

[Ernest Burden]

Does this happen consistently?

Yesterday I way working with a medium-dense model and for no damned reason I got that error (9.1). Like you, I uttered the WTF. Then I tried what I was doing again, and it went on like nothing ever happened, same model doing fine today (and getting bigger, and bigger)...

I also am lazy about shutting down other apps unless I start having memory problems, I have Cinema screenrendering (while I type this) with DataCAD and Photoshop sitting open.

XPpro, 2MB

[deljs]

If you are using SPD for the tread on the tire, use a lower "Subdivision Level" since you already have tons of polys.

Also ticking "Round Geometry" for an object in a hyperNURBS is redundant and painful to render (often causing out of memory errors).

Also, something I learned the other day, in Preferences>Common there is an option to change how much RAM is used for SPD. Whatever you specify here is dedicated only to SPD. I had changed mine to 500Mb (as I have 2Gb of RAM). This caused continual out of memory errors in most scenes with SPD. I returned it to 200Mb - no out of memory errors since.

Hope you get it sorted...

[JamesMK]

Aside from what's been said above about the polycount of that model (total mega overkill - and it's also surprising to see no less than 46 processes running in that screencap (I'm on XP as well, but I have only 23 live processes during normal usage)) it's quite useful to use the batch render thingy when dealing with heavy renders. Just set save path and everything, save the scene and close it. The start the render by using the batch render function in the render menu - that way the scene never actually loads into the editor, hence saving a lot of RAM.

[Erik Heyninck]

Thanks, James. I learned something new!

[JDP]

I manage to get between 1.5 and 1.7gb out of XP PRo SP1 by keeping my Cinema machine seperate from the rest of my network, so i don't use antivirus or any services that aren't needed and the minimum of drivers loaded, basicaly as little as possible running in the background, it makes a big difference. Don't install any software that isn't needed, keep your computer as clean as possible. Duderender, I can see from your screen shot that you have 46 processes running in the background and thats going to eat into your memory and performance. If you can afford it you should get another machine for the web and any progs that don't need a lot of oomph, you don't need anything special and you can get quite good machines for little money these days, and then you can use your most powerful machine as a dedicated graphics machine.

[dan22]

( buy a mac;-)



I'll second that.

Slightly OT, would someone like Srek know how much of the maximum 8Gb of memory that you can install on a Mac G5, can be actually used by C4D 9.1? Is there a limit as with Photoshop (2 Gb for now) or can it use the full 8Gb - minus system requirements?

Cheers,

D.

[sketchbook]

i consistantly get this same error on the mac, but i have some really large scenes with lots of geometry, etc. if i switch off hypernurbs it will render fine. turning them hurts.

however, the thread a while back about the 10comm was my problem. i took that out, and i upgraded my memory to 5GB.

now all renders work fine.

[Jonj1611]

Apart from the obvious whih was mentioned:

- Microsoft Antispyware is Betasoftware. It slows down your computer by random memory hogging with (if you didn't switch it off) incredibly useless and resource blocking "security features".

- Norton Antivirus - sorry i know its widespread - is another big slowdown. Throw it off and use some lightweight Antivirus Scanners like Avast and if needed a PFW.

- Polytrans, Barca, second Instance of C4D, Opera, even a VNC Server and other stuff is running while rendering such a scene. Why?

Anyway here and in the german forums are suspiciously many threads about memory problems since 9.1. Is there a link? Or do people think with the new update they can toture their machines? :)

How do you turn off Microsoft Antispyware anyway?

Thanks
Jon

[Jorge Arango]

As far as OS is concerned, Panther can handle up to 4 Gb. Tiger will handle 8 Gb.


Jorge Arango


I'll second that.
Slightly OT, would someone like Srek know how much of the maximum 8Gb of memory that you can install on a Mac G5, can be actually used by C4D 9.1? Is there a limit as with Photoshop (2 Gb for now) or can it use the full 8Gb - minus system requirements?

Cheers,

D.

[dan22]

Gracias, Jorge. So looks like there might actually be something useful to look forward to in Tiger, other than widgets and things.

Even more OT then, though I'm sure most of us here depend on it to some extent, does anyone know when (if?) Photoshop will exceed the 2Gb memory limit. At least on 64bit Macs?

8Gb of Photoshop memory would be fantastic - I have never exceeded memory requirements in C4D on my present computer (2Gb of memory on a G5 at the moment), but I always end up scratching to HD once I get busy in Photoshop on the final renders. That really slows things down, but I hate flattening layers.

(Yes, I know - this is in the wrong forum now..!)

Cheers,

D.

[Simon Wicker]

Even more OT then, though I'm sure most of us here depend on it to some extent, does anyone know when (if?) Photoshop will exceed the 2Gb memory limit. At least on 64bit Macs?

thinksecret mentioned that the next version of ps wouldn't be altered to adjust the 2gb limit. just to clarify, as it has been explained to me, under osx the current version of cinema can utilise a full 4gb of ram (so if you had 8gb of ram you could split that 4gb for the system and 4gb for cinema) so even now you could make use of maxing out the ram in your g5.

cheers, simon w.

[dan22]

Thanks Simon.

That's good to know about C4D - but I am mightily disappointed that PS won't raise the bar on the 2Gb limit in the next version. Whyever not?

(Could it be because their CEO used to be at Microsoft, and doesn't want to give Mac the 64 bit memory advantage till Longhorn is released? Or am I just being paranoid :hmm: )

D.

[duderender]

Hello all!!

Thanks for the interest in this problem.

Regarding polycount: I am well aware of the denseness and I have since down sized the polycount. I am dealing with a CAD model that has almost all curved features so the poly count requires a lot for some zoomed shots and such.

Regarding processes: My bad, I didn't reboot to my "slimline" hardware profiles as I run two. One with default so I can install software, a second that is nuts and bolts only. www.blackviper.com is a good resource.

Regading virtual memory: I don't run managed because when Windows decides to do a big dump or clean it kills everything you're doing. Instead, after a rigourous bout in Windows I'll do a reboot to clean up the pagefile. Also Diskeeper helps with keeping the pagefile in check.

Regarding Sniper Pro: not much that I've thrown at Sniper has killed it yet. Sniper may delay a bit, but no matter what I get a preview! Kudos to Paul.

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.