[1.12pre-4-gfb4763666] Movement is completely broken
Moderator: Raze Developers
Forum rules
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
Please don't bump threads here if you have a problem - it will often be forgotten about if you do. Instead, make a new thread here.
[1.12pre-4-gfb4763666] Movement is completely broken
You can not move in Duke3d, Blood and Redneck Rampage, and in Shadow Warrior you can only move on an axis, not in the direction you're looking at. Additionally none of the entities in either game move (Duke's ride only slowly falls to the ground for example).
-
- Posts: 14
- Joined: Sat Jun 12, 2021 4:29 am
- Preferred Pronouns: No Preference
- Operating System Version (Optional): Windows 11
- Graphics Processor: ATI/AMD with Vulkan/Metal Support
Re: [1.12pre-4-gfb4763666] Movement is completely broken
Happening to me as well, seems every devbuild marked 1.12pre and after is affected, as the one immediately before has working movement. I thought something had gone seriously wrong with my system at first before I fired up Shadow Warrior.
Re: [1.12pre-4-gfb4763666] Movement is completely broken
This is a known issue, it came from the sync'd code from GZDoom when there was a coding QOL feature added that allowed direct assignment of vec3's to their xy components.
It's a bit more complicated to fix because the error comes from conversion from one type to another and back and I am not really sure how Graf wants to tackle this.
It's a bit more complicated to fix because the error comes from conversion from one type to another and back and I am not really sure how Graf wants to tackle this.
Re: [1.12pre-4-gfb4763666] Movement is completely broken
Seems to be fixed in the latest build
-
- Posts: 2
- Joined: Fri Sep 26, 2025 5:37 pm
- Operating System Version (Optional): Windows 10
- Graphics Processor: nVidia with Vulkan support
Re: [1.12pre-4-gfb4763666] Movement is completely broken
Gothic wrote:
> Seems to be fixed in the latest build
I still have it in Redneck Rampage at least, no matter build 1.11 stable or latest 1.12pre-15-g4a8985b4b
> Seems to be fixed in the latest build
I still have it in Redneck Rampage at least, no matter build 1.11 stable or latest 1.12pre-15-g4a8985b4b