onevent EVENT_PROCESSINPUT seti .avel 0 //has no affect seti .fvel 0 //work properly seti .svel 0 //work properly too endevent
Page 1 of 1
Set input .avel to zero has no affect in r9257
#1 Posted 13 October 2020 - 12:11 AM
Set input .avel to zero has no affect in r9257. Player can still turning.
#2 Posted 16 October 2020 - 04:47 AM
The same applies to the input[].horz struct member.
Caused by r8551, i.e. the mouse input changes.
Caused by r8551, i.e. the mouse input changes.
#3 Posted 10 April 2021 - 09:27 AM
I was searching for reports or logs with the same issue; i declare this as a very important fix to do because some stuff i was developing developing is literally broken.
I have random recalls of this bug occurring before, maybe i can do a better search
I have random recalls of this bug occurring before, maybe i can do a better search
#4 Posted 13 April 2021 - 02:52 AM
The stuct member is updated properly, as I can retrieve the updated values with geti through CON. The internal avel value also gets updated by the TURN LEFT and TURN RIGHT keys, and is subsequently applied to the player's angle value.
The issue stems from the following changes:
pPlayer->q16ang is no longer updated with pPlayer.input->q16avel, which is the value that is update via CON. The same applies for horiz and horz.
It would be necessary for the game to recognize if a CON script is trying to change the avel and horz values, and then applies these changes to q16ang and q16horiz.
The issue stems from the following changes:
pPlayer->q16ang is no longer updated with pPlayer.input->q16avel, which is the value that is update via CON. The same applies for horiz and horz.
It would be necessary for the game to recognize if a CON script is trying to change the avel and horz values, and then applies these changes to q16ang and q16horiz.
This post has been edited by Doom64hunter: 13 April 2021 - 06:32 AM
Share this topic:
Page 1 of 1