Problem with fueldump map

[Quovadis]

It more the contrary , I never heard of anyone capable of connecting NQ fueldump without increasing ram access.

It is probably nq2 an nq3 that uses less ressources than other servers.

Oh and with the specs you have you can only improve your performance if you set it to 512

[daredevil]

But question is FA having more stuff on that map than other clans fueldump ones? If yes then I'll try that 512 (and yes I have more than 1GB mem even my graphics card have 2Gb)

 

Masa_1964

 

512Mb is not needed at all. It's a myth. 256Mb hunk is more then enough.

 

NQ 1.2.3 requires more hunk megs. 1.2.9 B6 way less.

[DFighter]

in jay3 fueldump start also to have some issues specially cause the server is more often full these days so it is pretty laggy this map for most players

is there something there can be done becides removing it ?

Edited November 2, 2012 by DFighter

[daredevil]

in jay3 fueldump start also to have some issues specially cause the server is more often full these days so it is pretty laggy this map for most players

is there something there can be done becides removing it ?

 

No. Fueldump is open space map and hence laggy with 45+ players.

[D..X]

512Mb is not needed at all. It's a myth. 256Mb hunk is more then enough.

 

NQ 1.2.3 requires more hunk megs. 1.2.9 B6 way less.

agreed its a myth indeed like dare say you only need up to 256meg

[Quovadis]

agreed its a myth indeed like dare say you only need up to 256meg

If I am not wrong I saw it in NQ FAQ a few years ago.

Haven't played NQ for more than 2 minutes in over 3 years lol.

Edited November 2, 2012 by QuoVadiS

[D..X]

this is what i found by googling the error

 

"Hunk allocate tempmemory fail on [number]" Error

This means that ET doesn't have enough memory to load a map.

Solution:

- Start ET - don't join any server

- open console (` or ~ key usualy below Esc)

- type "/com_hunkmegs [number]", [number] being 2/3 of your RAM in MB. If you set it to anything from 120 higher you should be alright. Don't set it above 512 tho.

- close ET (you can just type /quit)

- start the ET again (again don't join any server)

- open console

- type "/com_hunkmegs"; the console should say "com_hunkmegs is:[number] default:56". If that [number] is what you entered 4 steps above you're set, if not try doing the last 5 steps again

 

notice it says Don't set it above 512 tho.

Edited November 2, 2012 by captain canada

[Gluecksbaerchi007]

the same error...i open the game with xfire?!....hmmm....

[Quovadis]

 

/vid_restart is not enough to fix it since it needs a full restart so the program can reserve more ram.

1. Right click on you ET shortcut

2. Select Properties

3.Select "Shortcut" tab

4. In path you should have something like that :""C:\Program Files (x86)\Wolfenstein - Enemy Territory\ET.exe"

5. Make it "C:\Program Files (x86)\Wolfenstein - Enemy Territory\ET.exe" +set com_hunkmegs "256"

5. Open ET , should be fixed

Open with ET shortcut

[Gluecksbaerchi007]

everytime with et shortcut?

[Quovadis]

Yes or you need to do an autoexec with com_hunkmegs 256

Is it working with shortcut?

[Gluecksbaerchi007]

yeeees it works...but not with xfire

[Masa_1964]

I think xfire is causing my probs also, I see it occupies 47% prosessor even it not doing anyting.

 

Masa_1964

[Strobel]

I think xfire is causing my probs also, I see it occupies 47% prosessor even it not doing anyting.

 

Masa_1964

Yes, xFire may cause some trouble. Every 2nd-3rd time I start ET via xFire I don't have any sound at all and need to restart my PC.

Guess you're - just as I am - better of with starting ET via shortcut.