Added information to ReadMe #70
Conversation
added "Why would I need it?" section to github readme and additional figures for showing how TitleIDs are used and controller profiles work
changed all instances to have MOONDECK as all caps and moonlight as "Moonlight" to emphasize differences and reduce confusion
| - steam game guides for a streamed game cannot be found | ||
|
|
||
|
|
||
| ***MOONDECK*** **fixes this issue by adding a button to each game within the Steamdeck's OS to launch directly into a moonlight stream with ***Steam's specific game title ID #*** associated for the running application in SteamDeck's OS.** |
There was a problem hiding this comment.
I would really like to avoid having this point highlighted as a MoonDeck feature. It is a very hacky solution that apparently no longer works for some users and I have always contemplated about removing it altogether.
| 1. Press ***MOONDECK*** button on game to stream within SteamDeck's OS | ||
| 2. Selected Game is launched via moonlight stream | ||
|
|
||
|  |
There was a problem hiding this comment.
Screenshots should not contain any other plugins in order to avoid confusion as users sometimes start asking pointless question like "why is this missing?"
|
|
||
| - game-specific community controller profiles cannot detect the currently streamed game, preventing them from being downloaded or viewed | ||
| - controller settings are tied to the overall *Moonlight* application, requiring manual reconfiguration when switching between streamed games | ||
| - performance profiles are linked to the *Moonlight* application, also requiring manual reconfiguration when switching between streamed games |
There was a problem hiding this comment.
What are these performance profiles?
|
|
||
|
|
||
|
|
||
| - game-specific community controller profiles cannot detect the currently streamed game, preventing them from being downloaded or viewed |
There was a problem hiding this comment.
Initially I also though this would be a good idea, but I no longer think you should use the controller profiles unless they are for generic controller (which SteamDeck is not). Please read this https://discord.com/channels/960281551428522045/1050462209689518201/1309261646467960884 and a few messages below.
|
|
||
|
|
||
| ***Game Streaming via MOONDECK follows these steps:*** | ||
| 1. Press ***MOONDECK*** button on game to stream within SteamDeck's OS |
There was a problem hiding this comment.
I think we should not use SteamDeck's OS, just Steam or something. This plugin works on other handhelds that use Bazzite.
| ***MOONDECK*** sets configurations ahead of time and skipping many of the steps each time a stream is started. This allows a streamlined experience of selecting a game directly from the steam deck's OS and immediately starting the game stream. | ||
|
|
||
|
|
||
| **More importantly, the ***Moonlight, by DEFAULT,*** method caused SteamDeck's OS to ONLY see *Moonlight* as the running application, rather than *any specific game*.** |
There was a problem hiding this comment.
I find it very hard to read when it's italic and bold, especially when italic is mixed withing bold style sentences.
Please avoid bold sentences and use only bold to empathize something (not bold+italic). For example:
**MOONDECK** sets configurations ahead of time and skipping many of the steps each time a stream is started.
More importantly, the **Moonlight, by DEFAULT,** method caused SteamDeck's OS to ONLY see **Moonlight** as the running application, rather than **any specific game**.
| 3. Select an application to stream, usually steam Big Picture Mode (BPM) | ||
| 5. Select a game via BPM interface | ||
| 6. Selected Game is launched | ||
|
|
There was a problem hiding this comment.
Too many newlines everywhere, please keep to minimum required by MD.
added extra information to readme in a "Why would I need it section"
the added section describes: