crashnoww

There are multiple ways of installing Firestorm viewer: On Steam OS (Linux) - install the native linux version, install it from the Discovery store or install the Windows version and run it with Proton compatibility. On Windows - install windows on the Steam Deck in dual boot, then install Firestorm normally. Steam OS native version installation: 1. Using the Discovery store - not safe (for me at least) because the app is wrapped by a 3rd person (not tested). 2. Downloading Firestorm for Linux from their website (tested, seen in video) 2.1. Go to Desktop mode and download the Firestorm Linux version from their website. Make sure it's the Linux version. 2.2. Unarchive it and right click install.sh > execute in Konsole (terminal). You'll get a warning that you're not root, and it will install it in the Home folder. 2.3. Check to see if you have all dependencies: (you might need to set up a password in Linux, see Google on how to do that) Navigate to the newly created Firestorm folder and open Konsole from there with right click. Type this in Konsole "LD_LIBRARY_PATH="./lib:${LD_LIBRARY_PATH}" ldd bin/do-not-directly-run-firestorm-bin | grep not\ found" (w/o quotes). It will tell you the missing dependencies. Google about how to install the missing ones. Disable the write protection on the Steam Deck (Konsole > sudo steamos-readonly disable), Install the dependency, then re-enable the write protection (sudo steamos-readonly enable). 2.4. Double click "firestorm.sh" to see if it starts up. 2.5. Open Steam > Add a game > Add a non-steam game. You should see Firestorm in the list, check it and click Add selected programs. (if it's not in the list, browse for it and add firestorm.sh). 2.6. Add artwork for the grid, hero, icon etc (optional). 2.7. Run Firestorm through Steam to test. 2.8. Return to Gaming mode on the deck and run Firestorm. 2.9. Customize the controller: Steam hardware button, while in Firestorm, to see the menu > slide to the right and Controller configuration. 2.9.1. Here you can make it your own. I've used the left joystick set as directional pad > set as the directional keys on the keyboard (disable WASD as movement in Firestorm). Right joystick set as directional pad and set the commands for the camera (clockwise, counterclockwise, spin over and spin under). You'll have to delete (set as empty) the alternative key bindings in Firestorm, for each command assigned or you'll have conflicts). 2.9.2. Set the other buttons as you see fit. I've set the right trackpad as mouse with left click and the left one as scroll with right click. Bumpers as scroll for fast scrolling. Triggers as ALT and CTRL for camera manipulation (as seen in video). X - Show keyboard, B - Esc, A - Chat, Y - Inventory. You can also set the grip buttons for other functions. You might need to attach a physical keyboard to the deck if you want advanced keys combinations. 2.10. If the resolution or the aspect ration is messed up, enable the developer menu > Set window size > 1280 x 800. You might need to increase the scaling to 1.10 and increase the chat font size. 3. Install the windows version of Firestorm on Linux, using Proton (not tested): 3.1. Download the windows version > add the installer to Steam > Proprieties > Force compatibility > Proton Experimental (or use GE versions if you have them installed). Run the installer from Steam and let it finish. (it might not run). 3.2. Change the target of the already added installer entry in Steam, to the newly installed Firestorm.exe. You'll have to locate it. Run Firestorm through Steam and follow the above for the settings. 4. Install Windows (tested): Follow a tutorial on how to get dual booting on the deck. Install Firestorm on windows normally. 4.1. Install Glossi (for the controller). 4.2. Add Firestorm.exe to Glossi, then add it to Steam through Glossi. Run Firestorm from Steam (or the controls won't work). 4.3. Customize the controls just like described in the 2.9. section. To get the exact same type if interface, run Steam in Big Picture mode. 4.4. Add the Windows touch keyboard to the taskbar for easy access. Issues i've found so far: Linux: Voice doesn't work at all. (it might work with the proton version, i haven't tested it). Native controller support crashes the program. Clicking HUDs is messed up, off target or some HUDs won't show at all if hidden. Windows: Everything works, including voice. I can't remember the HUDs situation. Typing might be a little clunky.

The answer is yes. I've been running SL on the deck for a few months now. It runs pretty well too. On medium I get from 100 fps in empty areas to 25 fps in moderate areas. I'm not sure if I can post links here, but if you want to see my video, showing SL running on the deck, search "Second Life running on the steam deck" by RealEvil ind. on YouTube.