In the 'Effects' section of the Q2PRO Client Manual there are several relevant console commands.cl_disable_particlesDisables rendering of particles for the following effects. This variable is a bitmask. Default value is 0.1 — grenade explosions2 — grenade trails4 — rocket explosions8 — rocket trailscl_disable_explosionsDisables rendering of animated models for the following effects. This variable is a bitmask. Default value is 0.1 — grenade explosions2 — rocket explosionsTip: BitmasksBitmask cvars allow multiple features to be enabled. To enable the needed set of features, their values need to be summed.I dunno what else is in there but Q2PRO clearly has it covered from the console command angle.
Re: Share autoexec.cfg Code Thread« Reply #7 on: 08-08-2021 03:41:14 »press and hold the key down (N) to see packetloss , eg red lines//Netgraphalias +netgraph "netgraph 1" alias -netgraph "netgraph 0"bind n "+netgraph"this while simple saves a load of typing bind o spectator 1bind p spectator 0« Last Edit: 19-08-2021 23:08:11 by Clippy »
Re: Share autoexec.cfg Code Thread« Reply #8 on: 12-08-2021 16:25:35 »Your default cfg file in the baseq2 folder is autoexec.cfg, if autoexec.cfg is too big then it may fail to load when you connect to a server, if you have this problem then you can create an extra cfg file (pick your own name for said extra cfg file) and then take cfg code from autoexec.cfg and put it into said extra cfg file so that you can keep autoexec.cfg from being too big.1. Create the insertnamehere.cfg file and put it into the baseq2 folder2. Take cfg code from your autoexec.cfg file and put it into the insertnamehere.cfg file3. Put this line of cfg code into your autoexec.cfg file: exec insertnamehere.cfgYou can create more than one extra cfg file by following the same 3-step process.This is a good procedure that everyone would be well-advised to follow. The command buffer size in modern clients is 64k bytes but was originally only 8k in the idSoftware code. The game swallows the entire contents of the config files into the command buffer before it tries to parse the commands so spaces and comments are all put into the command buffer before parsing. Breaking your configs into multiple files exec'd from within the autoexec.cfg is definitely a good way to keep them organized. Executing them as modules from within autoexec.cfg allows greater control of the client startup without a lot of duplication of text.Writing files like grapple.cfg, hook.cfg, zoom.cfg, msgmodes.cfg, etc. allows you to keep all files in your configurations nicely cataloged into single-page, easy to edit modules. Different autoexec's per mod can be customized to call the needed component configs so you don't have to be scrolling through a long file looking for a particular command or bind.« Last Edit: 27-08-2021 16:53:16 by QwazyWabbit »
unbind