[GZDoom 4.4.2] An odd problem with autoexec.cfg?

Forum rules
Contrary to popular belief, we are not all-knowing-all-seeing magical beings!

If you want help you're going to have to provide lots of info. Like what is your hardware, what is your operating system, what version of GZDoom/LZDoom/whatever you're using, what mods you're loading, how you're loading it, what you've already tried for fixing the problem, and anything else that is even remotely relevant to the problem.

We can't magically figure out what it is if you're going to be vague, and if we feel like you're just wasting our time with guessing games we will act like that's what you're really doing and won't help you.

Post a reply

Smilies
:D :) :( :o :shock: :? 8-) :lol: :x :P :oops: :cry: :evil: :twisted: :roll: :wink: :geek: :ugeek: :!: :?: :idea: :arrow: :| :mrgreen: :3: :wub: >:( :blergh:
View more smilies
BBCode is OFF
Smilies are ON
Topic review
   

Expand view Topic review: [GZDoom 4.4.2] An odd problem with autoexec.cfg?

Re: [GZDoom 4.4.2] An odd problem with autoexec.cfg?

by Bodhisattva » Tue Aug 18, 2020 8:38 am

I did it just like in the example from this page:
alias zoomout "fov 90; eval * $mouse_sensitivity 4.5 mouse_sensitivity; rebind zoomin"
alias zoomin "fov 20; eval / $mouse_sensitivity 4.5 mouse_sensitivity; rebind zoomout"
bind F zoomin
Both cfg-files use the same key, but have slightly different commands inside the quotation marks.

By the way, I tried solving the problem by

  • deleting the old second.ini,
    making a new one from a copy of main.ini,
    putting both cfgs in $PROGDIR, and
    changing the Doom.AutoExec path to $PROGDIR/autoexec.cfg and $PROGDIR/autoexec2.cfg respectively,
and it worked. But now I don't even know which of these things actually solved the issue. :D

Re: [GZDoom 4.4.2] An odd problem with autoexec.cfg?

by Graf Zahl » Sat Aug 15, 2020 2:00 pm

How do you define your bindings in these files? Some bind commands do not override existing bindings. Also keep in mind that bindings bind commands to keys, not keys to commands, so if config A binds a key that config B does not, that binding will persist once set.

[GZDoom 4.4.2] An odd problem with autoexec.cfg?

by Bodhisattva » Fri Aug 14, 2020 3:30 am

So, I've got this main.ini file, which I use for most of my mods, and it has $DOOMWADDIR/AUTOEXECUTABLES/autoexec.cfg as the path to its Doom.AutoExec file that contains several keybindings. It works absolutely fine.
I also have second.ini (which is a copy of the main one), which I use for one specific mod, and I've just changed its Doom.AutoExec path to $DOOMWADDIR/AUTOEXECUTABLES/autoexec2.cfg. The keybindings in this second cfg-file are different.

Now, the problem is that the game keeps using the bindings from autoexec.cfg even when I load the game with second.ini, that uses autoexec2.cfg (and thus should have different actions bound to the same keys). Am I doing something wrong here?

Top