How to configure desktop-like for games #254
|
Hi, In short, I want the same level of game-detection and/or stream experience than with playnite / one app per game, but without moonlight/vibeshine managing how i launch or even close the games I come from reasing Reddit answers but its not entirely clear to me, I understood in a post saying that desktop mode does not enable features like rtss and lossless scaling (also the improvements about FrameGen) And that we must create a profile which just starts a command. Can someone give an example of this? I just created two new applications, one for in-game framegen and one for lossless scaling, both with command empty and with detached command "ping" (aka nothing). Will this work? How does it detect which game I'm playing? (By cpu and memory usage?) Is there a way to verify that the game has been detected? Didn't see anything in stats I dislike playnite etc as I just prefer to connect to my PC and that's it Thanks beforehand! |
Replies: 2 comments
|
A detached ping command will not make Vibeshine identify a game. It is not using CPU or memory heuristics for this; the Windows activity code combines Playnite activity, tracked processes, and foreground/fullscreen detection: https://github.com/Nonary/vibeshine/blob/vibe/src/platform/windows/game_activity.cpp The app examples also describe detached commands as useful for lifecycle cases where a launcher exits but the real long-running process remains, such as Steam. An empty desktop app with no command is the better fit for your connect-first/manual-launch workflow: https://github.com/Nonary/vibeshine/blob/vibe/docs/app_examples.md For game-specific RTSS, Lossless Scaling, or frame-generation setup, create real app entries for the games, or synchronize the games from Playnite and attach the preparation/cleanup commands there. A generic Desktop entry has no reliable per-game identity, so Vibeshine cannot infer which game you manually started just because ping is still running. To verify what it detected, enable debug logging and look for Game activity entries. The useful source labels are fullscreen-foreground, tracked-process, and playnite. If none of those appears, the helper process is not contributing a game signal. |
|
Thanks!! I think I got it. I have removed all commands, just created another app AAGames which is like desktop, no commands. Then I just added the games from playnite (even if I will not use playnite to launch) and I see tracking events you said in the logs for those games |
A detached ping command will not make Vibeshine identify a game. It is not using CPU or memory heuristics for this; the Windows activity code combines Playnite activity, tracked processes, and foreground/fullscreen detection:
https://github.com/Nonary/vibeshine/blob/vibe/src/platform/windows/game_activity.cpp
The app examples also describe detached commands as useful for lifecycle cases where a launcher exits but the real long-running process remains, such as Steam. An empty desktop app with no command is the better fit for your connect-first/manual-launch workflow:
https://github.com/Nonary/vibeshine/blob/vibe/docs/app_examples.md
For game-specific RTSS, Lossless Scaling, or frame-genera…