Welcome to the ZDoom Forums!

Yeah, the initial attempt to fix this did not work. So I had to redo it.

I've noticed over @github that the hackery has been removed and gzdoom will support the "-compatmode" parameter

thank you graf!

It required a bit of hackery but it should work now.

hi graf, sorry to resurrect this discussion BUT...

I'm in the process of setting up a bunch of .bat files and I'm facing the same as OP
it happens either when trying "+set compatmode <value>" using the command line or when adding "compatmode <value>" in autoexec.cfg
I've tried both 4.7.1 and 4.8pre

is this enhancement still something you'd like to implement?

What we have here is the great undefined-ness of order of execution for static C++ constructors. In this case they pretty much mess up each other's values.
Fixing this would require some major refactoring of how CVARs get set up. It has been on my wishlist for some time, but never became urgent.

Maybe after 4.6.0 - it's something that could be useful for Raze as well.

Windows 10, GZDoom v4.5.0
launching via commandline using switches for compatmode i.e

+compatmode 1
+set compatmode 1

changes what is shown as the selected compat mode preset but doesn't appear to change any of the underlying variables
the numbers in the menu under compatflags/compatflags2 don't change either