Page 1 of 1

Autoaim properties not saved

Posted: Thu Dec 05, 2013 4:20 am
by WARCHILD_89
Hello,

I just wanted to tell, that in GZDOOM after every single launch I always have to disable the autoaim setting, because I don´t want to use it. Why is the setting not saved like all the other settings I change?

Autoaim HAS TO BE disabled especially when playing brutal doom, otherwise instead of shooting the next enemy, you shoot at the nearest shootable dead corpse, it seems that the port ignores the "+NOAUTOAIM" flag defined in the weapon´s DECORATE code...

:?:

I`m using the latest version provided by the drd Team by the way...

Re: Autoaim properties not saved

Posted: Thu Dec 05, 2013 5:24 am
by Graf Zahl
It is saved but in a very weird way that can't be restored properly. I have no idea why this is done like that. Randi needs to look into this.

Re: Autoaim properties not saved

Posted: Thu Dec 05, 2013 5:42 am
by Gez
If we're talking about autoaim, I'd like this looked into as well.

Re: Autoaim properties not saved

Posted: Thu Dec 05, 2013 7:05 am
by Graf Zahl
That's precisely what I was talking about. The entire setup is stupid.

Re: Autoaim properties not saved

Posted: Thu Dec 05, 2013 1:42 pm
by NeuralStunner
While we're at it, what about SmartAim affecting player crosshair targetting?

Re: Autoaim properties not saved

Posted: Thu Dec 05, 2013 2:05 pm
by Graf Zahl
The crosshair is just a mark in the center of the screen, nothing more. No need to change.

Re: Autoaim properties not saved

Posted: Thu Dec 05, 2013 2:13 pm
by NeuralStunner
I'm talking about the [wiki=A_JumpIfTargetInLOS]line target[/wiki]. Depending on a client's SmartAim setting, you can never do aim checks vs. allies or non-monsters.

Re: Autoaim properties not saved

Posted: Sat Jan 30, 2016 6:47 am
by Graf Zahl
I just checked and this definitely gets saved.

But I never realized how stupid the old menu representation was. It basically had two values of 'no autoaim at all', 3 values of 'horizontal autoaim only' (the minimal vertical autoaim at these settings could well be ignored) and one for 'full autoaim'.
So I decided to replace its menu representation with a slider that can be set to any value between 0 and the maximum of 35. The old default of 5000 was also rather nonsensical since it always got clamped to 35.

All that's missing now is better control of horizontal autoaim, which is still rather poor.

Re: Autoaim properties not saved

Posted: Sat Jan 30, 2016 7:16 am
by Gez
That was basically the point of my thread.

Re: Autoaim properties not saved

Posted: Sat Jan 30, 2016 7:59 am
by Graf Zahl
Yeah, I never realized before HOW stupid this was. The slider represents the settable value range a lot better.