Superjer whats low virtual memory???

Superjer whats low virtual memory???

Hammer Mapping — Page [1]

2007 Dec 18 • 18
1 ₧
i get a low virtual memory right bout hte end of the compile whats that mean and how do i fix it?
2007 Dec 20 at 16:10 PST
Rocket Man

2007 Nov 6 • 2525
601 ₧
Buy more memory for your CPU
Free Steam Games
2007 Dec 21 at 02:08 PST
Count Adelaide

Roar Of The Tigress Medal
2007 Jun 24 • 84
68 ₧
I can't even animate an i could have told ya that.
Make awkward sexual advances, not war.
Down Rodeo said:
Dammit, this was the one place that didn't have this, but noooooo, molkman pisses all over that
2007 Dec 21 at 13:57 PST

2007 Dec 18 • 18
1 ₧
i have 2 gigs of ram so i dont think it is that
2007 Dec 25 at 09:06 PST
Down Rodeo
Cap'n Moth of the Firehouse

Find the Hole II Participation Medal
2007 Oct 19 • 5486
57,583 ₧
How big and complex is your map?
Do you have many other programs running at the same time?
Are you on Vista?
:P I am here, and it has died a memory death a couple of times. Mainly due to a program error, I think, but if you have Vista + a lot of programs running that might eat up the memory.
2007 Dec 25 at 18:38 PST

2005 Mar 20 • 6513
You can easily run out of memory compiling even if you have 4 GB of RAM. With a big enough map it could easily take 100 GB to compile. Hint: HL just isn't for making big maps.

But: there are ways to make the HLRAD use less memory, but it will slow down the compile, or make your map look worse. Here are your options:

hlrad -chop 128 yourmapname
This will make your lighting 2 times less detailed and take up 1/4 as much memory. It's also faster.

hlrad -chop 256 yourmapname
This will make your lighting 4 times less detailed and take up 1/16 as much memory. It's a lot faster but looks crappy.

You can crank chop up even higher, like 1024. That is only needed if you have a HUGE (like maximum sized map) with crap everywhere.

hlrad -sparse yourmapname
sparse causes hlrad to use a lot less memory but it is slower.

hlrad -nomatrix yourmapname
nomatrix causes hlrad to use basically NO memory, but it has to do a lot of the same calculations over and over so it's a LOT slower for most maps.
GOOD for multi-core processors. BAD if you have a lot of opaque entities!
2008 Jan 1 at 14:22 PST
Page [1]