Config issue

[VaeVictis]

REMOVED

[VaeVictis]

i also see the console message "ALIAS LOOP COUNT" randomly, which i didnt see before adding ammo drops and bfg to those binds... might be the problem...

[ex]

I was gonna say you probably have multiple items bound to the same key, and they're conflicting.  Fine-tooth comb your aliases.

[VaeVictis]

the thing thats weird is it mostly works...

but the alias called at the end for useweps to bind all my weapon keys when the autoexec runs... wont work with GL i have to hit mouse5 and let go which will toggle the bind drops, then letting go calls the SAME alias thats at the end of the config useweps and then it works... but seems to randomly switch back over...

i think there is some limitation in q2... but id like people who know more about the engine to tell me if im correct

[VaeVictis]

bump

alias loop count is the error message that resets my GL bind back to a drop bind rather than switch...

hitting mouse5 fixes the problem until it shows up again.... and its kinda spamming my console showing up quite often :/ not continuous flow of "alias loop count" but it doesnt take long to encounter that error...

i honestly do not see any loops in my config... maybe i accidentally put one in when i added a couple things to my tdm binds?

could some one at least take a look and see if you can notice anything broken? maybe i just have too many going on for r1q2 to handle... engine limitation seems like a logical reason why my config looks fine but im still error'ing

[VaeVictis]

bump AGAIN...

does seriously no one know whats causing this??

its taken apon itself to fire my weapon every time the alias loop error pops up :/

[VaeVictis]

From the lack of the responses in this thread it seems I was the only one to actually copy your config and test it in R1Q2.

Unfortunately I can't reproduce any of the problems that you're having. By default z will switch to using the grenade launcher, and if I hold mouse5 while pressing it then it will drop it instead (I assume this is the way it's suppose to function). I also didn't encounter the alias loop count message while playing a couple maps on dm.

If it were me, I'd start over with a new install of Q2 and then add your config to it before changing anything else and see if the problem still persists.

wouldnt simply deleting all the config.cfg files have the same effect, should load the default.cfg variables from pak0 and then do everything else with the autoexec.cfg... i can try that

really hate to re-install, thats a half assed way of fixing any problem... i guess if all else fails i have no choice and will create a new folder and just archive the old one... only pak files and autoexec.cfg need to be moved over so no big deal