[BUG] Nothing can move around

[Talon1024]

Raze version

Raze git (commit 940e53a)

Which game are you running with Raze?

Duke Nukem 3D

What Operating System are you using?

Linux x86_64

Please describe your specific OS version

SteamOS 3.6.24

Relevant hardware info

Steam Deck LCD

Have you checked that no other similar issue already exists?

• I have searched and not found similar issues.

A clear and concise description of what the bug is.

Everything seems to be frozen in place, and nothing can move around, except if it's moving up or down. This not only applies to the player, but also to the damaged ship at the start of Duke Nukem 3D, and the ship that's flying around (and shoots rockets at you) on Duke Nukem 3D E2L1.

I did a bisect, and found out that commit 940e53a is the problematic commit.

Steps to reproduce the behaviour.

Explain how to reproduce

1. Start any game supported by Raze. (I've found this bug in Duke Nukem 3D and Blood)
2. Try to move around.
3. The only way you can move around is by jumping.

Your configuration

Provide a Log

No response

[madame-rachelle]

Does this happen with Raze via Wine?

I am suspecting compiler shenanigans here. It could even be a difference between GCC and Clang here.

[Talon1024]

Does this happen with Raze via Wine?

Yes, unfortunately.

I made a symbolic link to my DUKE3D.GRP, put it in the 'data' folder, and launched the latest Windows build of Raze from devbuilds with Bottles.

[madame-rachelle]

Alright so it's not compiler shenanigans - more likely it's the conversions between fix and float and back that might be incompatible with the change in that commit.

[inf78]

I suppose this is related to SW as well, where NPCs are stuck in place and player can move only in fixed directions?
First I thought that it can be the compiler, but no, 1.11 is perfectly fine.
Unplayable, but, quite funny ;)

[sinisterseed]

Fast forward over a month later, and it looks like the problem was traced back by a contributor - #1156 .

It likely originated from 940e53a which sought to eliminate the use of type-punning in vectors.h, but there were a lot more placed that needed to be adjusted for it to work.

Bonus, a fix for a bug in Blood that went unnoticed for over 3yrs.