Simula VS Proton

He's _probably_ right that for the majority of people, the Quest would be better.

Towards the end, when he starts talking about the open vs closed model, I find it pretty depressing that meta is the "open" model in this case. I'm pretty sure you still require a Meta account to use the headset. Not sure I consider that "open".

I would love to have a headset that was running Simula (or something similar). I tried Simula with a Valve Index and the resolution was just too low for me. But I could definitely feel like it was "the future".

I travel a lot now and work on one laptop screen. Having a small(ish) headset that I could travel with and then have a VR workspace instead of a single laptop monitor has the potential to be game changing (maybe).

[0] https://github.com/SimulaVR/Simula

>before anyone else did

Not disputing your claim per se, but Google had a project called Daydream back at least as early as 2017 (though seems earlier) and rolled that into Area 120 projects. They canned it at some point in 2021 I believe.

Whereas SimulaVR seems to have started working on this in 2018 per their YC app (but perhaps earlier?) https://github.com/SimulaVR/Simula/wiki/YCW19-Application

That's not rly an os, it's just a different gui, you could probably reuse linux and build it on top of that For example, there's a VR window manager for linux called Simula

That's the dream! I really want to see if I can get it working with a VR compatible desktop env like https://github.com/SimulaVR/Simula; but failing that, just getting the second display surface to be floating instead of fixed would be a huge boon!

That's a clever way of doing it. =) I have considered xrdesktop, Immersed and Simula (SimulaVR's window manager without their headset) as well. Seemingly, Immersed can only create virtual monitors and not separate windows for each application, which leaves xrdesktop and Simula the better options.

You might be interested in looking at SimulaVR - it's a VR desktop built with godot (and haskell), but it uses, iirc, wlroots to handle windows and grab their surfaces to display as textures in godot.

So, you might be interested in https://github.com/SimulaVR/Simula . There have been a few examples of VR windows managers on Linux which don’t require an entire OS rewrite.

Is that the solution Meta will go w/ almost certainly not. But replacing a WM for a different “view” of your OS is a pretty common thing on Linux. (For some distros like Arch, replace isn’t the right word. You have to install whichever one you’d like from the beginning)

The Simula One is a Linux-based, standalone VR headset with compute specs that are comparable to premium laptops (x86 architecture) as well as very high pixel density (35.5 PPD). The software its built over is open-source (https://github.com/SimulaVR/Simula), and its hardware is being built in the open (though not entirely open-source since it would violate many of our NDAs, etc).

The "Metaverse" is a complete joke, and among gamers, Valve has a way better reputation than Meta. Why would they want to dilute that brand?

They already have their own platform (Steam), OS (SteamOS), VR headset (Index), their own Windows translation layer (Proton, https://github.com/ValveSoftware/Proton), their own partnership with cloud gaming (Steam Cloud Play using GeForce Now , https://partner.steamgames.com/doc/features/cloudgaming), etc.

IMO: As someone with thousands of games on Steam, there's no way in hell I'd want that linked to Facebook. I think they eventually removed the requirement to have a FB account to use a Quest, but they still require a Meta account. Yuck.

This reeks of Facebook recognizing the Metaverse as the failure that it was and opening it up because it's no longer relevant...

Or Valve's Proton[0], a tool for playing Windows games on Linux.

https://github.com/ValveSoftware/Proton

Did you mount it with the correct flags?

there is a hack to try and use your existing windows game install from an NTFS drive, but i don't recommend it as steam will try to save file names that are not allowed on NTFS...plus ext4 is faster.

From a quick search, here's what I found. It looks like you're encountering some common issues that can occur with games running on Linux through Proton, especially with the recent updates to games like Satisfactory that might affect compatibility. The log entries you're seeing related to D3DCompile2 failing to compile shader and the issues with Ternary operator and LinearToSrgbBranching not being defined, suggest that there's a problem with shader compilation. This can often be related to the version of Proton or the graphics drivers you are using. Some users have reported that the game does launch with the -vulkan option but with graphical glitches and lower performance, which indicates that the Vulkan renderer is working but possibly not optimally on your setup. From the discussions in the community, users have suggested ensuring that the latest drivers for your graphics card are installed and, if using an Intel GPU, that the Mesa drivers are up to date since Intel XeSS references were found in the logs. If you're using NVIDIA graphics, make sure you have the latest drivers and possibly set the PROTON_ENABLE_NVAPI=1 %command% to enable DLSS if you're under Vulkan. If you're using an Optimus laptop with both Intel and NVIDIA GPUs, make sure your Optimus setup is correctly configured. Some users have found success by specifying DXVK_FILTER_DEVICE_NAMES=GeForce to force the game to use the NVIDIA GPU. It's also worth noting that if you're encountering issues with DirectX 11, you might want to try forcing the game to use DirectX 10 if possible or look into DXVK configurations that could resolve compatibility issues. Lastly, if none of these solutions work, you could try running a trace with apitrace to gather more detailed logs that might point to the specific issue. If you're still stuck, it would be a good idea to report the issue to the Proton GitHub page or seek further assistance in the game's community forums where others might have encountered and solved similar issues. For more information and to find others who might have resolved similar issues, check out the community discussions on GitHub​​, Steam Community​​, and the DXVK GitHub page​​.