VerifiedShow Details
Unknown
Only Xbox Controllers or Steam Input controllers are detected in VR Room. In addition, layout bindings cannot be freely mapped; there are only two layout variants, which simply swap the A, B & C buttons with X & Z.
Local multiplayer is still possible, even if one player is in VR, because the game screen is still copied to the desktop screen. Steam Remote Play is further a possibility, even if host is in VR
To reiterate, the native build is borked, and does not feature the VR Room. One must use the Windows build of the game with Proton.
Test controller in offline Room Hub before launching VR; there's no way to customize bindings or test controllers as nicely as in the desktop hub.
VR hub may not be preferred for those that would rather not use their head to gaze around the menu selections. It's a nice feature, but it's the only way to interact with the VR Room outside of playing games.
Of course, one could always use a Desktop Viewer with a Genesis emulator. This title is more a legal way to obtain a collection of Sega games with a decent room space for the VR user.
Game has a native linux version, but there's only one launch option (the old game hub), and it hangs indefinitely on a black screen after the SEGA logo. It's supposed to show the d3t technology splash video and then the intro video but never does. Force Proton compatibility on this title, then you can choose the launch option.
Gamepad may need to be enabled in Game Room launch option. Use keyboard to go to input options, check that the device shows up on the list, focus it and select, and then its buttons can be mapped to the emulated controllers.
Save states and Favorite Games are lost when switching between Proton versions
Force Steam Input off at first until there's a problem setting up controllers in the game's Input Options, then re-enable Steam Input and try to map to the new Xbox 360 Controller seen in the game's Input Options.
VR mode not yet tested
Only recommend to use the classic launcher. Classic launcher works OOTB with absolutely 0 issues. The "modern" one requires too much work.
Had issues with exiting full screen mode. Dragging windows around caused my system to become unstable.
The modern UI redesign does not launch OOTB. Requires tinkering, as mentioned by other reports.
Frame rate was inconsistent.
The "modern" launcher was already horribly unoptimized on Windows, and it runs significantly worse on Linux. I've experienced several performance degradations & crashes. The launch option vblank_mode=3 %command% helped fix my issues with instability.
But I would still recommend the use of the classic launcher instead, even if that emulator is honestly really bad regardless of what OS you're using.
Used vblank_mode=3 %command% to enable OpenGL vsync and stop the GPU from processing too many frames. With Flatpak you can use this ugly hack globally overriding the envvar just for the Steam package, so that every OpenGL game will use vsync.
Native default does not work well. Switch to Proton and all is fine (including full screen).
Simple launcher requires touch input. Shame since this would be the preferred way for me.
no gameplay on fullscreen, must play from watching "tv screen"
Full screen does not work on deck, do not own a dock yet to test docked
Very enjoyable, if you don't move your windows around too much, lol.
Some tiles disappear but does not seem to happen often. (Games affected, Sonic 3 or Sonic 3-like games.) This maybe just a problem with the emulator, though.
Moving the window around when playing with Simple Launcher seems to freak the game out. Fixes itself when it detects input. Alt-tabbing also has a weird quick speedup than a couple of frames later it also fixes itself. Ditto with the "hub room" other than the focus issue. VR not tested.
(Using the Windows Client with Proton, not native.)
Game froze most of my computer during the d3t logo that plays when starting the game.
Had to shut down my system through the terminal.
This ran flawlessly. I will say that I had not played any of these titles in some time. that said, in game, you're playing the sega games on a 3d virutal tv and console. IDK why, i thought the game might have frozen when launching a game title on this virtual console, but I think the game just requires a few add'l steps to start playing the game that just aren;t intuitive,
I can safely say that this is more a design issue with the game than the steam deck and prton having a comptibility problem or something.
Use Proton-GE and "Simple Launcher"
Make sure to launch in experimental proton, then it's auto pilot from there
Used to work
Tried all proton options too
No longer works. All versions of proton give a direct X error and don't start the game. Native will start the game but locks up on the D3T splash after the SEGA into.
Don't know what happened, used to work fine a few weeks ago and is not unusable
Some of the text is ledgible, but small.
Native port goes to a black screen at launch, switch it to Forced Experimental.
Games work perfectly on steam deck once you force it to use proton (easy change). Default just gives you a black screen.
With the default native or whatever Steam pushes by default, just goes to a black screen. Switching it to force proton latest/exp works perfectly
Genesis Classics boots into its native Linux version by default, which has broken video on all games. Switch to Proton 7.0-1 or higher, and you'll have a perfect experience.
AMD user's will be happy that this proton version is now playable and that you can finally play games in fullscreen
. Linux version with AMD has a problem with fullscreen that has a black screen with sound.
. Videos go by standby mode. Once the standby blinks once, press a button to skip it and it will take you to the title screen and you can play
Native doesn't work and proton is also kinda broken
Latest revisions of GE's Proton seems to work fine, althrough games have input delay on the room thingy. Launching with the Simple Launchers fixes the issue but it streches the screen. It works just be aware of those issues.
The native linux port does not work, so I was force using proton instead and the game work fine no audio issue or graphice issue.
force the game using proton instead for native port
Can run on 4.11-13 with simple launcher. Cannot run on Proton 5.0
Controllers don't seem to work.
I can force-install this game using Proton 4.11-13 using simple launcher but not Proton 5.0 or by using the normal launcher.
You can play it with Proton but I would advise against it. The native version is better, with controllers working.
Works and plays perfectly.
Couldn't get the native port to launch at all but with proton 4.11-12 the simple launcher works flawlessly. No extra tweaks, although still cant get main launcher to run but that's not a big issue as the simple launcher works just fine.
Doesn't work at all with Proton - Loads to black screen
Native version doesn't work when games are fullscreened so I decided to try Proton. However, after trying a multitude of options including disabling esync, using D9VK, and using WINE's OpenGL-based Direct3D renderer, the game seems to be borked under Proton completely. It loads to a blank screen.
The proton version is met with a black screen.
UnknownWorks fine used USB xbone controller
UnknownUnknownSteam controllers don't work; full screen doesn't work; game seems to get random inputs not done by user.
UnknownUnknownGames played in "Fullscreen" Mode seem to black screen. Just back out so the game displays within the virtual CRT TV.
Unknown
