Command Line Argument parameter disappears sometimes

[Yakibomb]

v28.6

Description Two bugs:

Command Line Argument parameter (I think for VRAD, not sure about others) disappears from selection in the Parameter Chooser, sometimes.

Sometimes it is there, sometimes it is not. If it is there, I can use Command Line Argument like normal... until it disappears again and deletes all command lines I setup earlier.

Steps to reproduce I'm not really sure. I played around trying to get it to bug, with no luck.

If it helps, these are the command lines I put in:

-final -hdr -ambientocclusion -aoscale 0.5 -LargeDispSampleRadius -softencosine -worldtextureshadows

Expected behavior I would think Command Line Argument would always be there.

Debug.log (I'm currently compiling a map when I grabbed this log) debug.log

Crash logs No crash

Additional context

• The game I'm compiling for is Team Fortress 2 Classic.
• Here is an image of it not existing in VRAD's options:

It would normally be just before Incompatible commands

[HoneyfrostStudio]

The same happened to me for -bumrad_ao, a custom command. I'm using 28.7. It happened after restarting the tool; no real apparent reason for this to happen.

[Exactol]

I rewrote how presets are saved, hopefully this build should make it more stable. https://www.dropbox.com/scl/fi/k43jde7l7mu0jv76kt2zz/Compile-Pal-028.7.zip?rlkey=8h92perdestb0v9lyl2yp6r7j&st=x0laz1z1&dl=0

[Exactol]

Have you had a chance to test the new build?

[Yakibomb]

Ah, no I haven't. I'll give it a shot and update you