Feature: RivaTuner Statistics Server Frame limiter instead of IGCL

[BassemMohsen]

This requires running the Backend as Admin.
We will have to create Task Scheduler to launch it.

We also have to inform users to install RivaTuner Statistics Server from Guru3D
https://www.guru3d.com/download/rtss-rivatuner-statistics-server-download/

Going this route will block any future of publishing over Microsoft Store, since it will violate the store security checks.

[schliemann]

Isn't it a regression to rely on another third party app?

If the Intel launcher app button is removed wouldn't you already fulfill all the requirements from the Microsoft store? And secure a broader adoption.

[BassemMohsen]

Isn't it a regression to rely on another third party app?

If the Intel launcher app button is removed wouldn't you already fulfill all the requirements from the Microsoft store? And secure a broader adoption.

The problem is Intel's IGCL frame limiter doesn't work with backends for Directx 12, some OpenGL, some Vulkan.
Directx 11 seems to respond well to frame limiting. These GL backends represents huge segment of games.
and as you know, Frame limiting is such important aspect of getting quality frame pace.

My intended solution was to rely on RivaTuner if it was found installed, and fallback to Intel IGCL if it's not installed. So that, users are not forced to install anything if they don't want to.

Anyway, I won't be merging this PR anytime soon, due to the security elevation that it requires.
Rivatuner writes its configurations in Program Files, Sandboxed Gamebar widgets are not allowed to write files there.
Gamers also complained about UAC prompts if I try to elevate privilege, it's not the way to go since it causes friction and a security hazard.

Regarding, removing Intel Launcher, it's the long term plans after completing two extra features:

• Retro scaling, GPU scaling, and Display Scaling.
• Color Remaster for vibrancy, contrast and brightness.

Then truly I see no reason to ever launch Intel Graphics software and I will remove the button.
Alternatively, I could just remove it right away, but I do use it myself to adjust the features I mentioned.

[schliemann]

Ah. You obviously have given this a lot of thought. Didn't know frame limit worked so poorly through Intel.

I also thought you kept the Intel launch button to make driver updates accessible through FSE.

I still think you would get the best adoption through the MS store - even if it means you must adhere to their requirements.

[BassemMohsen]

Ah. You obviously have given this a lot of thought. Didn't know frame limit worked so poorly through Intel.

I also thought you kept the Intel launch button to make driver updates accessible through FSE.

I still think you would get the best adoption through the MS store - even if it means you must adhere to their requirements.

I did comment for Intel Issue actually about the FPS limit, I think Endurance Gaming also suffer same issue.
IGCIT/Intel-GPU-Community-Issue-Tracker-IGCIT#958
Unfortunately, I don't control Intel Arc roadmap, and can't influence their prio. I will try to reach through some back channels and ask a bit more.

Release after Next release is planned to go through MS Store, I only have an issue when I upload my package to the store reporting, Do you have some experience how to fix that?

Package acceptance validation error: Duplicate build metadata files were found in the manifest of package Tooth.Package_1.0.56.0_x64.msix: makepri.exe

[schliemann]

I have never tried publishing an app to the MS Store. Did a quick search and found this:

https://learn.microsoft.com/en-us/answers/questions/1132818/windows-store-submission-issue-duplicate-build-met

Don't know if it'll help. Can see you have Microsoft.Windows.SDK.BuildTools as a package.

[BassemMohsen]

Microsoft.Windows.SDK.BuildTools as a package

I do need to use a package project since I'm packaging an App and Backend(Service) in a bundle.
It's a good pointer where to start investigating it.
Thanks a lot. 🙏

Regarding checking for Intel Driver updates, That's a nice feature to add to the project backlog and roadmap. One could just query Intel's server endpoint to check the available latest versions and query IGCL about current installed driver version and match them to notify the user if a new update is available.

[schliemann]

Hehe. Yeah. It was a bit of a shot in the dark. But if you unpackage your msix file do you then see two entries for makepri in your manifest file?

[BassemMohsen]

Hehe. Yeah. It was a bit of a shot in the dark. But if you unpackage your msix file do you then see two entries for makepri in your manifest file?

You must be a marksman, You are a good shot. You actually did help quite a lot,
This fixed the issue

There remaining work is submission of logistics left to publish on the store, such as Languages, logo, which countries, minimum hardware requirements .. etc

I will tackle it after next release.

[schliemann]

That’s great to hear. Do reach out if you run into any problems and need some sparring.