godotengine / godotengine/godot
AMD Radeon "Anti-Lag" feature causes editor stutter
- Dominant language
- C++
- Stars
- 117k
- Forks
- 26.8k
- PR merge metrics
- PR metrics pending
Description
### Tested versions
v4.3.stable.mono.official [77dcf97d8]
v4.4.stable.mono.official [4c311cbee]
### System information
Godot v4.3.stable.mono - Windows 10.0.19044 - Vulkan (Forward+) - dedicated AMD Radeon RX 6950 XT (Advanced Micro Devices, Inc.; 32.0.12033.1030) - AMD Ryzen 7 5700X 8-Core Processor (16 Threads)
### Issue description
I use the default global performance profile on my AMD GPU driver (latest stable release at the time of writing, 24.12.1). This has the feature "Anti-Lag" globaly enabled for all application, and applies it to Godot. (Other default profiles have it also turned on like the Quality Profile). This feature tampers with frame-timing and helps games to run more smooth but it seems to be incompatible with Godot and causes heavy editor stutter on larger scenes. It took me hours to find where the issue is, maybe a warning to the user should be shown, if you think its more of an driver issue than a godot issue?
### Steps to reproduce
* Anti-Lag must be turned on in the driver.
* Any larger scene will start to be choppy and laggy in the editor when moving or zooming. (especially zooming feels like ~10 fps)
* A empty scene or a scene with few objects will not cause this behaviour
Here is a example 144hz recording with a larger scene and turned on&off "anti-lag" where it is visible. (Its only visible on the recoding when you play it on an high refresh rate display!)
https://github.com/user-attachments/assets/9c506112-69b0-4cf3-a0ed-7a32a969479e
### Minimal reproduction project (MRP)
N/A
Contributor guide
Research direction
No source file, test, or entry point is named. Start by reproducing the editor stutter on Windows with Vulkan, a larger scene, and AMD Anti-Lag toggled, then compare behavior while moving or zooming. Done would require identifying whether the cause is in Godot or the driver and defining the appropriate fix or user warning.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100