morgan_423

So, I wanted to share some knowledge and awareness about Nested Desktop. What it is, and if you're interested, how to set it up.

What it is: Nested Desktop allows you to access Desktop Mode functionality while you're still in Gaming Mode / Gamescope, and acts like any other game you'd run from there.

Think of it as your "Desktop Mode emulator for Gaming Mode". It lets you access Desktop Mode files, apps, and functionality just like you were using Desktop Mode natively, WHILE you're already in another game using Gaming Mode (so for instance, you could pull up Nested Desktop to get easier web browser access to look up something for the game you're playing). It's also much faster than rebooting natively into Desktop Mode when you need to use it.

I use Nested Desktop all the time! I find it to be a handy tool to have access to.

How To Set Up: Native Steam Deck screen (800p)

The native app always pulls up in 800p resolution, regardless of your display resolution. If you are on your 800p-screened Deck itself this is perfect; if you're docked or have a different resolution replacement screen, and want a different resolution, I'll cover that later.

Steps:

1. Reboot into native Desktop Mode. Hopefully this will be the last time you have to do that for awhile!

2. Use your application launcher in the bottom left corner. Navigate: All Applications ~ scroll down to N's ~ Highlight Nested Desktop ~ RIGHT click ~ choose menu option "Add to Steam."

3. You're done and can go back to Gaming Mode! You can now run Nested Desktop right out of the non-Steam section of your library. Note: You do NOT have to set any launch properties or Proton options to run this.

When you are done using Nested Desktop, you can close it either with the standard STEAM button menu, or by double clicking the Return to Gaming Mode option on the desktop.

How To Set Up: For Other Resolutions

This was the part that took me forever to find out how to do searching online. I was VERY frustrated figuring this out, so I wanted to share to give others the resource. And sadly no, you can't just pick your preferred resolution from the normal launch options on the regular Nested Desktop app.

Steps:

1. Reboot into native Desktop Mode.

2. Use your application launcher in the bottom left corner. Use it to navigate to and open a new document in your text document writer (the default is KWrite). Copy all the text between START and END below and paste it into your new document:

START

#!/bin/sh unset LD_PRELOAD

rm -rf /tmp/desktop-mode mkdir -p /tmp/desktop-mode cat > /tmp/desktop-mode/kwin_wayland_wrapper << EOF #!/bin/sh $(which kwin_wayland_wrapper) --no-lockscreen --width 2560 --height 1440 --x11-display $DISPLAY $@ EOF chmod +x /tmp/desktop-mode/kwin_wayland_wrapper

kwriteconfig5 --file startkderc --group General --key systemdBoot false PATH=/tmp/desktop-mode:$PATH startplasma-wayland kwriteconfig5 --file startkderc --group General --key systemdBoot --delete

END

NOTE: The height and width numbers in the code above are the resolution that the Nested Desktop will open in. This example is from my 1440p display, but change these to whatever resolution your display is.

3. Save this document under any name that makes sense to you. This will be what you see in your library. For example, I named mine "Nested Desktop 1440" to distinguish it from the regular Nested Desktop I use when I'm handheld.

Also, be sure to save this somewhere that you can easily find it. I recommend the standard Documents folder.

4. Navigate to the file where you saved it. RIGHT click it, choose "Properties" from the menu. Under the Permissions tab, check the "is executable" box, and click OK.

5. Finally, RIGHT click the file again, and pick "Add to Steam."

6. You can now go back to Gaming Mode, and run this whenever you need.

Thanks everyone, I hope you find this useful!

To stay in compliance with weekly Lemmy AI image memes, here this is.

My steps, if anyone has to replicate. I'm not sure if everyone will start from here... it's possible that you already have the prerequisite installed from another game. But I'll give my fix path in case anyone starts from the same place I did.

For me, what I saw to start: When running, a brief spin, and then about ten seconds later, a change back to the green play button. Complete no-go.

My fix path went:

1. Started in Desktop mode, for maximum troubleshooting flexibility.

2. Going to Manage > Properties, I changed BG III compatibility option to Proton Experimental.

3. Tried relaunching game... this time, an error returned that I needed to run the game along with Windows Net Desktop runtime (.net 6.0.20).

This error had its own link button, but in case you don't get the link or error, but still want to see if this is your fix, the link took me here for the download.

4. I added that downloaded file as a non-steam game in Steam, set its compatibility to Proton Experimental, then I ran it and installed it. (Note: For stuff like this, leave it in your Steam library after you're done with these steps... if you delete it later, it takes out the file path and it will stop working, and you'll have to do all this all over again.)

5. Every person is going to get a unique directory number created for them in their file structure for this file. Find it by following the path in your file manager (default file manager is Dolphin): /home/deck/.local/share/Steam/steamapps/compatdata/

Then sort by "last modified," and the file folder you're looking for will pop to the top (it should say something like "last modified two minutes ago," "last modified just now," or something like that... because you just did this, so you know this is the correct one). Write this number down, it's the unique-to-you location id I was talking about earlier.

Finally, go back to Baldur's Gate III and the Manage > Properties. In the launch options, paste exactly this command, except substitute your unique ID number in place of the string of Xs here:

STEAM_COMPAT_DATA_PATH=/home/deck/.local/share/Steam/steamapps/compatdata/XXXXXXX %command%

(Note: there is a space between your ID number and %command%.)

And if your issue was for missing the Net prerequisite, then this should get it running for you. Have fun!