Skip to content

Performance Diagnostic Wizard #21

@mdrejhon

Description

@mdrejhon

I suspect it will be useful to have a wizard that applies/unapplies these settings, and/or automatically detects missing tweaks to popup.

  • So maybe a button that launches a wizard?
  • The Performance Diagnostic Wizard will save your tech support time & could include things like a "Save Logs" button.

And it could also be a simple diagnostic indicator: An indicator or the buttton can go red (or flashing) if it detects a major problem in background, or stay green if it is reasonably satisfied. The user can choose to click on the button for extra details.


Performance Diagnostic Wizard Popup Window

"Your system is currently in Balanced mode. It will perform better in Performance mode. Here are instructions."
"Your game is configured at a higher priority than ShaderBeam which will affect reliability of ShaderBeam. ShaderBeam has been unable to reconfigure this. Framedrops in ShaderBeam looks like a malfunctioning CRT, so prioritize framedrops in game to make it look like normal framedrops on a retro CRT. [Link to Wiki HOWTO]".
"You are using and NVIDIA card and your system is missing the NVIDIA power management tweak. We recommend that you apply the following tweak..."
"Diagnostics show your bus bandwidth might possibly be too low for 2560x1440 240Hz between your two GPUs. Try reconfiguring to a lower resolution, lower game framerate, lower display Hz, and/or optimizing for single-GPU operation"
"You may wish to rerun this diagnostic in Administrator mode for additional detection of problems"
"Recommended Registry Tweak: The last activation of ShaderBeam on the last app appeared to show low GPU utilization and highly variable frametimes. This may mean your system/laptop is configured with very aggressive power management. This often has problems with ShaderBeam. This is common with emulators and retro games. Try this DisableDynamicPState tweak: [link to HOWTO]"
etc.

[Close Window]...[Save Logs Button]...[Button to launch browser in Wiki]...[Button to launch browser in github issues]


Could be a separate app, or could be integrated. It stays out of the way, until the user wants it, and it becomes immensely helpful to user: You save future tech support time by programming this up. Heck, even render the lines in WebView's so you can have clickable links to wiki/howto's.

You can start simple (detect only 2 or 3 major issues in a quick job) and add more problem-detections to it later. Start small and expand.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions