Show Posts
1
Trouble Shooting / Re: Menu_Main error in Q2Pro client.
« on: February 10, 2019, 08:51:59 PM »
No, you did not understand well. I have the source code for Q2pro and I have searched it for Menu_Main and it does not exist. I also have a fully installed Q2pro client and I have inspected the code in q2pro.menu and that string does not exist. Furthermore, using Menu_Main as a client command requires a bound key. The OP has bound “Menu_Main” to a key and on many server mods text that is not a valid client command is transmitted as “say” text to the game.
The OP needs to fix the bind. This can be accomplished in game.
However, if he follows the advice given, to modify config.cfg, he will have problems in future.
I will explain again how Q2 clients work:
(This applies to all Q2 clients, Quake2 from idSoftware, R1q2, Q2pro)
At startup the Q2 file system is initiated and .pak files are inventoried and made ready. The file “default.cfg” is loaded and parsed. This establishes the basic binds as idSoftware intended them.
Next, config.cfg is loaded and parsed, if it exists. (The game WRITES this file whenever you quit the client, each and every time it closes.) It writes it anew every time. Most importantly, it NEVER SAVES ALIASES. This is why you don’t edit config.cfg and why you don’t write protect it. (Q2pro uses q2config.cfg on Windows but config.cfg on non-Windows OS but IMO this is an error.)
Next, autoexec.cfg is loaded and parsed. This allows you to add or change binds by OVERRIDING the previous “default” and “config” binds and to add aliases. Since Q2 never writes to autoexec.cfg you can confidently make your changes permanent without needing to fight Q2 by write protecting any files.
And because you don’t write protect config.cfg the game will save them for you on a normal exit and you don’t need to worry about losing them.
All the OP needs to do is follow Vae's advice and bind escape to "togglemenu".
The OP needs to fix the bind. This can be accomplished in game.
However, if he follows the advice given, to modify config.cfg, he will have problems in future.
I will explain again how Q2 clients work:
(This applies to all Q2 clients, Quake2 from idSoftware, R1q2, Q2pro)
At startup the Q2 file system is initiated and .pak files are inventoried and made ready. The file “default.cfg” is loaded and parsed. This establishes the basic binds as idSoftware intended them.
Next, config.cfg is loaded and parsed, if it exists. (The game WRITES this file whenever you quit the client, each and every time it closes.) It writes it anew every time. Most importantly, it NEVER SAVES ALIASES. This is why you don’t edit config.cfg and why you don’t write protect it. (Q2pro uses q2config.cfg on Windows but config.cfg on non-Windows OS but IMO this is an error.)
Next, autoexec.cfg is loaded and parsed. This allows you to add or change binds by OVERRIDING the previous “default” and “config” binds and to add aliases. Since Q2 never writes to autoexec.cfg you can confidently make your changes permanent without needing to fight Q2 by write protecting any files.
And because you don’t write protect config.cfg the game will save them for you on a normal exit and you don’t need to worry about losing them.
All the OP needs to do is follow Vae's advice and bind escape to "togglemenu".
