You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The problem is not listed in the hardware support matrix as a known limitation. Examples of known driver-side issues are fans not turning on with a custom curve or inaccurate power limits on RDNA3.
I've included a debug snapshot if the issue is related to hardware configuration
Bug description
Since upgrading to 0.7.0, my 7800XT doesn't go over ~ 2130 MHz, which is close to the the card's "game clock" (can bee seen here for example). It seems to set that as "target clock" regardless of the set "Maximum GPU clock". This results in lower performance (eg. lower fps).
Performance in Kingdom Come Deliverance's main menu, a consistent and reproducible scene:
Performance and clock speed with 0.7.0:
Performance and clock speed with 0.6.0:
(Ignore the RAM/VRAM usage differences, there are some background tasks that are not affecting the difference in clock speed and in game settings are the same)
The card behaves the same in other games/applications.
Screenshot from 0.7.0 (see target clock):
Screenshot from 0.6.0 (target clock behaves normally):
I currently use the 0.6.0 version as a workaround.
System info
- LACT version: 0.7.0-release (commit b818f39)
- GPU model: RX 7800 XT (Sapphire Pulse)
- Kernel version: 6.12.10-zen, 6.12.10, 6.12.9 (behaves the same on all of those)
- Distribution: EndeavourOS
The text was updated successfully, but these errors were encountered:
0.6.0 had broken pstate settings that did not get applied, which was fixed in 0.7.0. The pstates are getting reapplied because you have "performance level" on manual.
Does the issue happen if you choose "automatic" as the performance level?
Checklist
Bug description
Since upgrading to 0.7.0, my 7800XT doesn't go over ~ 2130 MHz, which is close to the the card's "game clock" (can bee seen here for example). It seems to set that as "target clock" regardless of the set "Maximum GPU clock". This results in lower performance (eg. lower fps).
debug snapshot:
LACT-v0.7.0-snapshot-20250122-000245.tar.gz
Performance in Kingdom Come Deliverance's main menu, a consistent and reproducible scene:
Performance and clock speed with 0.7.0:
Performance and clock speed with 0.6.0:
(Ignore the RAM/VRAM usage differences, there are some background tasks that are not affecting the difference in clock speed and in game settings are the same)
The card behaves the same in other games/applications.
Screenshot from 0.7.0 (see target clock):
Screenshot from 0.6.0 (target clock behaves normally):
I currently use the 0.6.0 version as a workaround.
System info
The text was updated successfully, but these errors were encountered: