hedge-dev / hedge-dev/UnleashedRecomp
Dragon Road Act 2-2 physics difference between 30 and 60 fps
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 5.1k
- Forks
- 421
- PR merge metrics
- No merged PRs in 30d
Description
Validation
- I have checked the Issues page to see if my problem has already been reported
- I have confirmed that this bug does not occur in the original game running on original Xbox 360 hardware
Describe the Bug
Physics depends on FPS from the looks of it
Steps to Reproduce
Steps to reproduce the bug:
- Set FPS limit to 60
- Go to Dragon Road Day Act 2-2
- Take the path shown, use only the boost while on the rail, don't touch the analog stick
Expected Behavior
You should hit the spring.
Footage
Bug:
https://github.com/user-attachments/assets/ef7cdb33-6575-4f68-a43c-67a10d030803
Expected (also recorded on the recompiled project. I don't have the means to record 360, but I can record Series X if needed):
https://github.com/user-attachments/assets/2ea2f8d3-6b46-4a64-a7d6-7c9a74fb5961
Specifications
Fill out the following details:
- CPU: Ryzen 7 5800H
- GPU: iGPU (Radeon Vega 8)
- GPU Driver: Mesa 24.3.4-3.fc41
- OS: Fedora 41 KDE Spin
- Version: 1.0.0
Additional Context
When I tested this on Series X, I noticed the same difference between 30fps and 60fps. It does not occur on X360, as it can't hit 60 fps there at all.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce Dragon Road Day Act 2-2 at 30 and 60 FPS using the reported route and boost-only input, comparing the result with the linked footage. Trace the game's physics and frame-update entry points to identify where the behavior diverges. Done means the path reaches the spring at 60 FPS while preserving expected behavior at 30 FPS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100