This game runs too slow on my computer

[leileilol]

athlon 950mhz, gffx5200 what is wrong

[Tenn]

Change resolution and minimaze effekts, paricles etc.
I play on 800x600 with 1,2ghz i cant play with 1024x768.. test that

[cyan]

lol nice post

my nexuiz runs too fast now

AMD X2 4800+
2 * GeForce 7800GTX 512mb
4068mb DDRAM 533Mhz Kingstons

had to setup the game to maxfps 300

[Ed]

You're lucky you don't have an Athlon 64 FX-60, then it would surely be so fast it would be unplayable /stupidity

Just go mad with the settings and I'm sure you can find some ways of slowing it down. First put everything on in the menus and use the highest resolution you can. Then go through the config file putting everything else up.

[jaakan]

athlon 950mhz, gffx5200 what is wrong

What OS are u running on?

It's playable on my PIII-666, Win XP home sp2, 512Mb ram, NV GF2-GTS
Realtime lighting and shadows off, all other effects on with paricles set to 1, 800x600 and 32bit color.

[pol pot]

Yeah, just turn off all the effects and lower the resolution, as someone said before.

[esteel]

Generally there are some variables that have to be tested for every system as graphic card, drivers, even driver versions or operation system will influence them and its almost impossible to find the 'perfect' settings for those. I'll mention them as last thing in this post, try them if you need more speed.

I use those configs, the first one for playing (fast), the other for watching demos (slooooow)

n_lo.cfg:

Code: Select all

cl_bobcycle 0
cl_bobmodel 0
cl_itembobheight 0
cl_rollangle 0
v_kicktime 0

cl_decals 0
cl_stainmaps 0

cl_nogibs 0 //1
cl_noplayershadow 1

cl_particles_blood 0
cl_particles_bubbles 0
cl_particles_bulletimpacts 0
cl_particles_explosions_bubbles 0
cl_particles_explosions_shell 0
cl_particles_explosions_smokes 0
cl_particles_explosions_sparks 0
cl_particles_quality .5
cl_particles_rain 0
cl_particles_size .5
cl_particles_smoke 0
cl_particles_snow 0
cl_particles_sparks 0

gl_picmip 2
gl_texture_anisotropy 1
r_detailtextures 0

gl_flashblend 0
gl_polyblend 0

r_shadow_bumpscale_basetexture 0
r_shadow_bumpscale_bumpmap 0

r_sky 0

r_waterscroll 0
r_waterwarp 0

r_bloom 0
r_coronas 0
r_dynamic 0
r_glsl_deluxemapping 0
r_glsl_offsetmapping 0
r_glsl_offsetmapping_reliefmapping 0
r_hdr 0
r_shadow_gloss 0
r_shadow_glsl_offsetmapping 0
r_shadow_realtime_dlight 0
r_shadow_realtime_dlight_shadows 0
r_shadow_realtime_world 0
r_shadow_realtime_world_dlightshadows 0
r_shadow_realtime_world_shadows 0

vid_width 800
vid_height 600

ambient_level 0
bgmvolume 0
snd_staticvolume 0

Also its worth mentioning the the gibs in Nexuiz 1.0 - 1.5 have had very very high-poly count and there spawn six for each frag. You can download this file (made by me) * or this file (made by KadaverJack) * and place it into your Nexuiz/data folder. However please notice that the usage in ladder matches is NOT allowed. Rename the file from .pk3 to .pk3_ then. This will skip the file and you get the original gibs. As ladder matches are only 1on1 they are also not needed there as problems with gibs normaly occur only with more then 4 people.
The new gibs in Nexuiz are easier on the FPS and Nexuiz now also has the settings cl_nogibs to disable gibs. But that setting will remove them totally so they are not even in demos. That looks ugly in demos. That why i still use the pk3 file for NON ladder matches and have that settings commented out in my config files..

* As far as i know both are based on some other file that was posted in the old forum, i have no idea who created that one but as its only 0-sized models there should not be a problem with copyright

Then to enable as much graphic effects as possible:
n_hi.cfg:

Code: Select all

cl_bobcycle 0 //.6
cl_bobmodel 1
cl_itembobheight 10
cl_rollangle 0 //2
v_kicktime 0 //.5

cl_decals 1
cl_stainmaps 1

cl_nogibs 0
cl_noplayershadow 0

cl_particles_blood 1
cl_particles_bubbles 1
cl_particles_bulletimpacts 1
cl_particles_explosions_bubbles 1
cl_particles_explosions_shell 0 //1
cl_particles_explosions_smokes 1
cl_particles_explosions_sparks 1
cl_particles_quality 1
cl_particles_rain 1
cl_particles_size 1
cl_particles_smoke 1
cl_particles_snow 1
cl_particles_sparks 1

gl_picmip 0
gl_texture_anisotropy 16
r_detailtextures 1

gl_flashblend 0
gl_polyblend 1

r_shadow_bumpscale_basetexture 5
r_shadow_bumpscale_bumpmap 4

r_sky 1

r_waterscroll 1
r_waterwarp 1

r_bloom 1
r_coronas 1
r_dynamic 1
r_glsl_deluxemapping 2
r_glsl_offsetmapping 1
r_glsl_offsetmapping_reliefmapping 1
r_hdr 1
r_shadow_gloss 1
r_shadow_glsl_offsetmapping 1
r_shadow_realtime_dlight 1
r_shadow_realtime_dlight_shadows 1
r_shadow_realtime_world 1
r_shadow_realtime_world_dlightshadows 1
r_shadow_realtime_world_shadows 1

vid_width 800 //1280
vid_height 600 //1024

ambient_level .3
bgmvolume 0 //1
snd_staticvolume 1

Variables that will affect performance but are very system dependent. I will list them with their defaults and other possible values. Its best if you run a timedemo via tdem demo1 in the console and compare the fps:
n_xx.cfg:

Code: Select all

set gl_combine 1 //0
set gl_lockarrays 0 //1
set gl_mesh_drawrangeelements 1 //0
set r_batchmode 1 // 0 2
set r_glsl 1 //0
  the following is only for really old versions of Nexuiz.. the name was changed to r_glsl at some point
set r_shadow_glsl 1 //0

WARNING: r_glsl 0 / r_shadow_glsl 0 will disable pixel shaders which is faster on SOME card, MOST are faster with it active (1) BUT DISABLING THIS WILL ALSO DISABLE MOST EYECANDY EFFECTS, so you should only do so in low settings were you will not notice and only if it is an speed increase for you!!!

[tChr]

Save esteels stuff as files in nexuiz/data then do exec filename.cfg in console

[esteel]

Thanks tChr! Thats right but a r_restart afterwards is a good idea too.
Or you can do:
nexuiz.exe +exec n_low.cfg
that will start with those low settings and does not require a r_restart. And you can be sure you always start with the low settings.

[tChr]

Is there an easy way to dump the current config?