DirectQ controls configuration annoyance/issue

[Hippox78]

Hey! Nice place.

First I am using DirectQ (v1.9.0) together with Quake 1 v1.9.

Okay, so the issue is that when I change my controls in DirectQ they save -BUT- if I want to leave my "MOUSE2", for example, binded to nothing, then when I restart the client, then the game will just have binded "+forward" to "MOUSE2" automatically. That's part of the default config, I noticed.

The issue is simply that the game/DirectQ WANTS to bind the default config binds to anything left binded to 'nothing', and also if the second default bind is left empty. In practice, I cannot leave my "MOUSE2" binded to nothing, and I cannot have "+attack" binded to only one single key. This is very annoying.

I tired to solve it myself, but the only solution is to make 'directq.cfg' = Read only. Which is kinda a bad solution, still, for me.

Please help....

EDIT: Actually, making the config file 'directq.cfg' set to 'Read only' doesn't even work! Arrrhgh

Not even putting my binds in a 'autoexc.cfg' seems work...

I should be able to bind them to some other keys that I am not going to touch, though, I guess. Like binding "+attack" number two slot to something out of the way. But it still seems like an issue that should be fixed.

[Hippox78]

Okay, so I found a solution that works. If you have the same issue as me then read this:

Step 1: Find a key function that doesn't have any actual function in-game. In my case that's "+speed".

Step 2: Make a 'directq.cfg' by clicking on 'Save currect configuration' in the options, if you don't have one.

Step 3: Open 'directq.cfg' and add "+speed" for any key you do not want to have a bind for (with a function, at least), but only in case if the key you want to bind is part of the default config scheme (Like, 'Ctrl', 'mouse2', 'Z', ect), which mean they HAVE to be binded to something. Or they'll override your configuration. Binding a non-default key will work just fine, of course, without any of this annoyance.

That's it. You can as many keys to "+speed" as you want, to as many keys you want, though, you cannot actaully see more than two binds in the control options.

[Mindf!3ldzX]

Wish I had an actual solution for you, I have had this problem before in Qrack and DirectQ, but I never could find the reproducable problem because I found make a new vanilla quake install / drop in engine , and it would work fine.

Cluttered quake folder is where I always place the blame ,atleast in my own experience with the config fails to save / keeps reverting issue.

[MH]

The default binds are actually coming from default.cfg, in pak0.pak, so theres nothing engine-side can be done. This problem should affect all engines. The solution is to copy your binds to autoexec.cfg and add "unbindall" as the 1st line. Of course that means you wont be able to change binds through the menu anymore, but thats the tradeoff.

[Seven]

Hello Hippox78,

You must know that the config files are read/started in a specific order.
This order is declared inside quake.rc
Just like MH said, all engines will follow it.

If you dont want your "Mouse2" button to contain anything, there is an easy solution.
Knowing from quake.rc, that autoexec.cfg is started last, you only need to add this line into your autoexec:

unbind MOUSE2

So it doesnt matter what any of the config files will do to your mouse2 button.
It will always be deleted/erased !

You do not need to "unbindall" in your autoexec. So you can still bind everything else via in-game menu (except "mouse2").

And this is, as far as I understood your post, what you want.

You may have a good reason for that.
Maybe you are an alien from Planet-Quake with only 2 fingers and cannot use the second mouse button

Have fun,
Seven

[Hippox78]

Okay, thanks a bunch then.

Anyhow, who wants anything binded to MOUSE2? Did I miss something? I use space for jumping, if that's it.

Also, I don't like accidentally hitting a button with a function, like CTRL that then fires the weapon. I keep it tight/simple.

[Mindf!3ldzX]

The default binds are actually coming from default.cfg, in pak0.pak, so theres nothing engine-side can be done. This problem should affect all engines. The solution is to copy your binds to autoexec.cfg and add "unbindall" as the 1st line. Of course that means you wont be able to change binds through the menu anymore, but thats the tradeoff.

Deleting it with PakXplorer ??? Wouldn't this work, or maybe atleast blanking out the entire default.cfg ??

[Syluxguy28O3]

Anyhow, who wants anything binded to MOUSE2? Did I miss something? I use space for jumping, if that's it

actually, in my experience, binding jump to mouse2 makes it alot easier to perform precise rocket jumps. however, i also keep space binded to jump too, becasue out of habit ill use space to just jump around, however i always use mouse2 to rocket jump.

[Syluxguy28O3]

Deleting it with PakXplorer ??? Wouldn't this work, or maybe atleast blanking out the entire default.cfg ??

yeah, cant u just open the pak and edit the .cfg file?

[MH]

It's also an artefact of the fact that Quake was one of the first (if not the first) full 3D games with mouselook support, so they were still working out the best control layout at the time. That's why you see a lot of weird-looking things in configs from back then.