add Moore Threads MTT GPU supported#359
Conversation
xinye0123
commented
Mar 16, 2026
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f1ae2c2621
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8e6e0a32c5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| // ★★★ [新增] 11. 摩尔线程 GPU 回退逻辑 ★★★ | ||
| // 如果 LHM 未检测到 GPU 数据,尝试从摩尔线程 MTML 获取 | ||
| if (result == null && _mttGpuMonitor?.HasMttGpu == true) |
There was a problem hiding this comment.
Prefer MTML metrics when Moore Threads GPU is present
This condition only reads MTML data when result == null, so on systems where LibreHardwareMonitor still returns non-null GPU.* values for another adapter (for example an Intel iGPU), those values are kept even though the UI now uses Moore Threads naming via GetGpuName(). In that hybrid setup the panel can display a Moore Threads GPU label with telemetry from a different GPU, which corrupts reported GPU stats; MTML should be prioritized for GPU keys whenever HasMttGpu is true.
Useful? React with 👍 / 👎.