125 fps

[tooty]

Hi, can anyone help?

Had my max_fps set to 83 for the 'megahealth jump' on q3dm13 4 a while now,so just 4 a laff i retweaked my cfg and tried 4 the optimum '125' fps and tested it on q3dm12/13 megahealth jumps, q3tourney4 gap jump q3dm14 red armour jump etc and managed 2 hit it everytime

added the updated settings 2 my cfg, but when i played q3 again i couldnt do those special jumps all the time like i was b4, which would indicate i wasn't running @ the optimum 125 fps mark, yet i hadn't changed anything in quake3 since i updated my cfg, when i was making those jumps everytime.

is there some kind of variation that only happens occasionally when quake3 loads up that would just tip me over to 125fps if i was on the border? and how do i correct this?

May try O'clocking my Prophet gfx card but am a little unsure as to how much to adjust it to. According to my display properties it's set @ 175mhz. I can OC it here with a little slide panel but it sez my warrantee will b void if i do *gulp* as i've not overclocked anything on my pc b4, i'm a little wary.

any advice/suggestions welcome

 

[Sar]

It sounds as though you're not hitting a CONSTANT 125fps in the situations described.

You'd be better, if your PC doesn't get over say 160fps in a timedemo, to cap your fps lower, back to 72/76 fps.

 

[tooty]

ok thx Sar, I'll try tweaking the 3d optimisation settings on my gfx card panel and if that dont work then i'll cap the fps off lower

 

[Chameleon]

In graphics control panel, turn off vertical sync and full screen anti-aliasing, plus switch to 16 bit colour and select 'best performance' rather than 'best quality'.

In your q3 config, make sure you have

r_swapinterval 0

set. and also try

s_mixahead 0.08

Ch@m

 

[tooty]

thx CH@meleon
btw, i'm having trouble setting my 'com_zonemegs'. i've got 640mb ram. i had my hunkmegs set to 480 and sound megs set to 32, but i cant get my zonemegs to stay set to 32.

I tried entering it directly into my 'q3config.cfg' aswell as entering it in the q3 console but when i type '\com_zonemegs' it says
'\com_zonemegs is "16" default is "16" latched "32" '.

i tried lowering my hunkmegs to 128 but this didnt work. any ideas how to get the zonemegs setting to stay?

btw wot r the correct settings for zone/sound/hunkmegs with 640mb ram, all the q3 guides i've read only go up to 256mb ram

thx 4 helping btw

 

[ShockingAlberto]

If it says "latched" in the console, it means that the correct setting isn't being used. If you add the setting to teh command line, maybe on your shortcut to quake3, it will work. IE:

quake3 +set com_hunkmegs "140" +set com_zonemegs "24" +set com_soundmegs "16" +set r_mode "4"
(that's my command line)

I would guess, for 640megs, you want:
com_hunkmegs "360"
com_zonemegs "110"
com_soundmegs "80"

Or something similar. There's probebrly a limit on how useful a high soundmegs is, however i'm not really sure what zonemegs is...

 

[tooty]

k thx alberto, i'll give that a try. i right-clicked on the quake3 shortcut, and went 2 properties, there r a few places where summit can b written, where abouts do u enter the info?

thx

 

[ShockingAlberto]

I think the bit you want is labled "path" or something...

However, it will point to the quake3 executable, and be in quotes. I believe you need to put the options outside of the quotes.


(Sorry for late reply, but was downloaidng pr0n )

 

[Chameleon]

I have 512mb of 2100 DDR ram and use:

com_hunkMegs "128"
com_soundMegs "32"
com_zoneMegs "32"

You should be fine with that tbh.

You should not really manually edit q3config.cfg
To get a setting to stay in q3config.cfg you need to do the following from the in-game console:

/seta com_hunkMegs "128"

the 'seta' command tells it to set this new setting AND KEEP IT. You can use 'set' but this only keeps it for as long as your playing that session .... once you close and then restart q3, it will forget it, so make sure you use '/seta'

My advice would be this .....

set what you want from within q3, at the console, using '/seta', then quit q3 and browse to the BASEQ3 directory. Then open up 'q3config.cfg' and do FILE ---> SAVE AS and save the file as 'autoexec.cfg' ( be careful. things like notepad have a nasty habit of saving your files as autoexec.cfg.txt ) You can now edit autoexec.cfg to your hearts content and should find that anything you change in there will take effect in q3 (you see there is a .cfg file within pak0.pk3 which contains the line 'exec autoexec.cfg' which means that whenever q3 starts, if you have a file called autoexec.cfg within your baseq3 directory, it will automatically execute it).

I hope that helps

Ch@m

 

[tooty]

Originally posted by ShockingAlberto
(Sorry for late reply, but was downloaidng pr0n )

hehe np m8

Thx 4 the extra info Ch@m. i've got an autoexec file already, which i update when i'm happy with new settings, but i wasn't aware about the point u made about using 'seta' in the quake 3 console, so thx 4 that

 

[throdgrain]

Gamespy has its own autoexec for Q3 I seem to remember, might be worth looking in there too.