Support us on Patreon
PayPal
First up, if you're looking for my upcoming Vive unboxing video, this isn't it!
When my Vive arrived earlier this month, I'd decided to let it sit in its box for a while. The most recent communication regarding official support was "We are working on it but it's not ready yet," and I had a lot of other work to focus on.
About a month ago, an OSVR contributor had mentioned in the OpenHMD IRC channel that OSVR had a driver that interfaced with Valve's Vive driver and allowed OSVR to support the Vive under Linux. I didn't have time to look into it, but was glad to know that even if Linux support wasn't being advertised as ready by Valve, that there was something tangible to work with.
The Vive's official launch came and went without advertised Linux support and it seemed that those users who did have Vives hadn't managed to jump through the correct hoops to get it functioning on Linux until last night when Linux user and developer SketchStick nudged me to take a look at some successes he'd had.
TMA (Too Many Acronyms)
Before going any further, we're going to need to work through some terms. Here's a rough glossary!
I'd also like to pop a disclaimer here. The stuff contained within this article will not magically give Vive support to Linux apps that weren't compiled with OpenVR support, and it doesn't make doing that any more accessible to developers. The value here is primarily for Linux based developers who are looking for examples to work with, and for F/OSS driver developers who are looking for working examples to observe and learn from.
Getting Things Working
The OpenVR SDK ships with an application called HelloVR. It renders a matrix of cubes around the HMD's camera and demonstrates how to interact with the OpenVR API. This example program has some Linux specific code in it, but needs additional tweaking before it will compile and behave happily on Linux (looking at the issue list in the OpenVR SDK's GitHub repo, it seems that there may be hurdles for other platforms as well).
Last year, in an effort to simplify maintenance of his OpenVR AUR package, Christoph Haag forked the Valve OpenVR repo and attempted to keep Linux support for the example applications behaving by testing with the Oculus Rift DK2 he had at the time. After selling his DK2 (more on that a bit later), Christoph continued to keep his fork in sync with Valve's repo, but didn't have any real opportunity to continue testing it to ensure functionality.
These steps have been adapted from instructions originally written by SketchStick as we were working through this stuff last night. Nice work!
To download Christoph's OpenVR SDK fork and build the HelloVR application, run the following commands (note, that you'll need CMake 3.1.0 or greater, as well as SDL2 and GLEW development packages):
Next, you'll want to plug in all those lovely Vive cables and make sure that the device has appropriate permissions. You can either run chmod like so:
Or set up udev rules for usb devices using the vendor codes 0bb4 and 28de as suggested in the OpenHMD readme (this is persistent and probably not a good idea given how early things are right now):
The next step is to make sure that the hellovr app and OpenVR commands have access to the environment and libraries they expect. If you don't already have it installed, you'll need to install SteamVR. This is done by either installing SteamVR from the VR or Tools category in your Steam library, or by using this URL steam://install/250820. Note that at the time of writing, the SteamVR beta branch does not work.
SketchStick has put together the following shell script which assumes that Christoph's OpenVR fork has been cloned into ~/openvr, that Steam has been installed to ~/.local/share/Steam and that the SteamVR depots have installed to ~/.local/share/Steam/steam/SteamApps/common/OpenVR (this stuff varies! Right click on SteamVR in your Steam library, select Properties, switch to the Local Files tab and click on the Browse Local Files button to see where SteamVR/OpenVR has installed to):
To use this script to set up the environment, run the following command in a terminal (it will allow $steam, $openvr and $steamvr to be used as variables in that terminal until it is closed):
It's not essential to use this script, but for the rest of the document, I will assume that you are (expand out the paths as necessary).
From here, we'll need to verify that the Vive is correctly detected by OpenVR.
This will output information on any detected OpenVR devices. You may see a large number of "ioctl (GFEATURE): Broken pipe" lines being output. For now, these are safe to ignore.
The output we care about should look something like this:
If you see a device and driver line that indicate that a Vive is present, we're ready to move forward with starting up the vrserver process and running the HelloVR app.
Start the vrserver process as a background task.
Open a new terminal and set up the SteamVR environment as we did before.
And finally, run the HelloVR app via a launch script that Christoph has provided.
At this point, we should have a working HelloVR app and be able should see something like this:
On the right is the vrcompositor window, which draws what you'll see through the Vive. The image is duplicated and offset for each eye. On the left is a normal monitor with a preview window that runs at a significantly lower frame rate and resolution that allows you to see what's going on without putting the device on.
Interestingly, the preview window shows significant lens compensation distortion while what's displayed through the device doesn't. This seems to indicate that the compositor isn't quite doing everything that it's meant to be doing.
HelloVR is also meant to use the OpenVR API to retrieve 3D models of the controllers and Lighthouse base stations, which are positioned in 3D space, although at the time of writing, I haven't been able to get this aspect to behave correctly.
Anybody who goes through this is likely to notice that there's a significant amount of latency (my gut says it's input latency, but it's difficult to discern the difference between that and render latency). At this point in time, I'm uncertain whether it's introduced by the HelloVR app, the OpenVR abstraction layer, the Vive driver, or even just launch options for vrserver, but it does suggest to me that there's still a little work left to do before the Vive can be considered "Linux ready".
A Little More Background
As soon as I had a stereoscopic image and headtracking working, I sent an email to Christoph to invite him to offer some comments on his work.
Without a device to test with himself and with the dominant understanding being that the Vive can't run on Linux, Christoph was surprised to learn that his efforts to get an OpenVR sample application allowed myself and SketchStick to demonstrate our Vives running on Linux with the existing OpenVR drivers. Equally surprised at his perseverance with maintaining his fork without a device, I asked Christoph about his interests and motivations with regard to VR.
Looking Forward
Christoph's History of Openness chronicles some details of Oculus' history that I wasn't previously aware of and reflects a level of disappointment that I think we all feel - not only over Oculus' apparent indefinite postponement of Linux support, but also for Valve and HTC's decision to launch the Vive without advertised Linux support.
Oculus dropped Linux support at the time that they shifted towards direct rendering mode. Assuming that there weren't any external factors involved in discouraging Linux support (something I'd rather not entertain in this article), it seems fair to assume that there were hurdles with regards to getting that performant and stable that were large enough to justify shelving Linux support in favour of focusing on a single platform.
The HelloVR app doesn't use direct rendering mode either, and it could be easy to assume that Vive's Linux support is a victim of the same prioritisation that lead to Oculus stepping back from Linux. In this case at least, we can see evidence of continued Linux related updates to OpenVR listed on SteamDB, with the most recent changes to OpenVR and Vive/Lighthouse related drivers happening within the past three weeks (change #1920962).
Looking even farther back, we can see that the Linux OpenVR libaries and binaries have continued to be updated alongside other platforms for the past two years (all the way back to change #395316 when vrserver_linux as added).
I want to sorely and strongly stress again that even though this article is about how to get the Vive to run, and that it highlights continued work on Linux support for the Vive, that now is not the time to run out and order a device or to hassle developers who aren't already shipping OpenVR support in their Linux builds. Both of those are important steps, but can't happen until either official vendor support for the Vive on Linux is announced and promoted as ready and stable, or until there is a feature-complete F/OSS driver available.
In the coming weeks, I'm sure that we'll dig around and discover Linux/Vive compatible apps, better identify the cause of (and possibly resolutions for) the latency issue I mentioned previously, and of course, we'll see progress on OpenHMD's Vive branch as well. Hopefully the proper release of Vive's Linux support is also on the near horizon.
Exciting times are ahead! Article taken from GamingOnLinux.com.
When my Vive arrived earlier this month, I'd decided to let it sit in its box for a while. The most recent communication regarding official support was "We are working on it but it's not ready yet," and I had a lot of other work to focus on.
About a month ago, an OSVR contributor had mentioned in the OpenHMD IRC channel that OSVR had a driver that interfaced with Valve's Vive driver and allowed OSVR to support the Vive under Linux. I didn't have time to look into it, but was glad to know that even if Linux support wasn't being advertised as ready by Valve, that there was something tangible to work with.
The Vive's official launch came and went without advertised Linux support and it seemed that those users who did have Vives hadn't managed to jump through the correct hoops to get it functioning on Linux until last night when Linux user and developer SketchStick nudged me to take a look at some successes he'd had.
TMA (Too Many Acronyms)
Before going any further, we're going to need to work through some terms. Here's a rough glossary!
- API: Application programming interface, a documented way of interacting with a program or library (to allow interaction without necessarily having access to the library or program's source code)
- SDK: Software development kit, a set of tools for creating applications (typically containing a set of libraries, API headers and examples)
- VR: Virtual reality \o/
- HMD: Head mounted display (typically with positional and/or rotational tracking)
- Positional tracking: The detection and capture of real world movement for use in software
- Rotational tracking: The detection and capture of real world rotation for use in software
- Vive: The HTC Vive, a HTC manufactured VR system created in collaboration with Valve
- Lighthouse: The infrared base station system used by the Vive to provide positional tracking, has also been used as a name for the entire Vive system
- Extended mode: Mapping a HMD display as a traditional monitor (derived from "extended desktop")
- Direct mode: A method for drawing graphics directly to a HMD rather than via the window manager
- SteamVR: Valve's collection of Steam and OpenVR libraries, drivers and demos
- Steam VR mode: A VR friendly version of Steam's "Big Picture Mode"
- OpenVR: A proprietary VR driver abstraction layer which supports the HTC Vive, the Oculus Rift, Razr Hydra, typically by interfacing with vendor provided drivers
- OSVR: An open source VR driver abstraction layer by Razer, Sensics and other partners, which supports the HTC Vive, Oculus Rift, Leap Motion and other devices, typically by interfacing with vendor provided drivers
- OpenHMD: A Free/Open Source Software VR input driver which supports the Oculus Rift DK1 and 2 and other devices
- vrcmd: An OpenVR binary providing command line access to information on OpenVR devices (and maybe other things)
- vrserver: An OpenVR binary that can be run as a service to provide access to OpenVR devices
- vrcompositor: An OpenVR binary that is used to render to OpenVR devices and take care of a bunch of VR specific concerns (distortion, etc.)
I'd also like to pop a disclaimer here. The stuff contained within this article will not magically give Vive support to Linux apps that weren't compiled with OpenVR support, and it doesn't make doing that any more accessible to developers. The value here is primarily for Linux based developers who are looking for examples to work with, and for F/OSS driver developers who are looking for working examples to observe and learn from.
Getting Things Working
The OpenVR SDK ships with an application called HelloVR. It renders a matrix of cubes around the HMD's camera and demonstrates how to interact with the OpenVR API. This example program has some Linux specific code in it, but needs additional tweaking before it will compile and behave happily on Linux (looking at the issue list in the OpenVR SDK's GitHub repo, it seems that there may be hurdles for other platforms as well).
Last year, in an effort to simplify maintenance of his OpenVR AUR package, Christoph Haag forked the Valve OpenVR repo and attempted to keep Linux support for the example applications behaving by testing with the Oculus Rift DK2 he had at the time. After selling his DK2 (more on that a bit later), Christoph continued to keep his fork in sync with Valve's repo, but didn't have any real opportunity to continue testing it to ensure functionality.
These steps have been adapted from instructions originally written by SketchStick as we were working through this stuff last night. Nice work!
To download Christoph's OpenVR SDK fork and build the HelloVR application, run the following commands (note, that you'll need CMake 3.1.0 or greater, as well as SDL2 and GLEW development packages):
git clone https://github.com/ChristophHaag/openvr.git
cd openvr
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ../
makeNext, you'll want to plug in all those lovely Vive cables and make sure that the device has appropriate permissions. You can either run chmod like so:
sudo chmod a+rw /dev/hidraw*Or set up udev rules for usb devices using the vendor codes 0bb4 and 28de as suggested in the OpenHMD readme (this is persistent and probably not a good idea given how early things are right now):
echo KERNEL=="hidraw*", ATTRS{idVendor}=="0bb4", MODE="0666"
echo KERNEL=="hidraw*", ATTRS{idVendor}=="28de", MODE="0666"
udevadm control --reload-rulesThe next step is to make sure that the hellovr app and OpenVR commands have access to the environment and libraries they expect. If you don't already have it installed, you'll need to install SteamVR. This is done by either installing SteamVR from the VR or Tools category in your Steam library, or by using this URL steam://install/250820. Note that at the time of writing, the SteamVR beta branch does not work.
SketchStick has put together the following shell script which assumes that Christoph's OpenVR fork has been cloned into ~/openvr, that Steam has been installed to ~/.local/share/Steam and that the SteamVR depots have installed to ~/.local/share/Steam/steam/SteamApps/common/OpenVR (this stuff varies! Right click on SteamVR in your Steam library, select Properties, switch to the Local Files tab and click on the Browse Local Files button to see where SteamVR/OpenVR has installed to):
#!/bin/bash
export openvr=~/openvr
export steam=~/.local/share/Steam
export steamvr=$steam/SteamApps/common/OpenVR
export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:\
/usr/lib/:\
/usr/lib32/:\
$openvr/lib/linux32/:\
$openvr/lib/linux64/:\
$steam/ubuntu12_32/steam-runtime/i386/lib/i386-linux-gnu/:\
$steam/ubuntu12_32/steam-runtime/amd64/lib/x86_64-linux-gnu/:\
$steamvr/bin/linux32/:\
$steamvr/bin/linux64/:\
$steamvr/drivers/lighthouse/bin/linux32/:\
$steamvr/drivers/lighthouse/bin/linux64/To use this script to set up the environment, run the following command in a terminal (it will allow $steam, $openvr and $steamvr to be used as variables in that terminal until it is closed):
source ./steamvr.shIt's not essential to use this script, but for the rest of the document, I will assume that you are (expand out the paths as necessary).
From here, we'll need to verify that the Vive is correctly detected by OpenVR.
$steamvr/bin/linux64/vrcmdThis will output information on any detected OpenVR devices. You may see a large number of "ioctl (GFEATURE): Broken pipe" lines being output. For now, these are safe to ignore.
The output we care about should look something like this:
QuoteDevice 0 - lighthouse.LHR-1F0D0FBC - Vive MV by HTC - HMD - generic_hmd
Left Projection: left=-1.396245, right=1.242144, top=-1.467562, bottom=1.464816
Right Projection: left=-1.251338, right=1.392499, top=-1.474031, bottom=1.464144
Lens Center: (0.546726, 0.499251), (0.457286, 0.497308)
Driver lighthouse : 1 displays
Vive MV (Serial number LHR-1F0D0FBC)
Driver oculus : 0 displays
Driver oculus_legacy : 0 displays
Driver null : 0 displays
If you see a device and driver line that indicate that a Vive is present, we're ready to move forward with starting up the vrserver process and running the HelloVR app.
Start the vrserver process as a background task.
$steamvr/bin/linux64/vrserver --keepaliveOpen a new terminal and set up the SteamVR environment as we did before.
source ./steamvr.shAnd finally, run the HelloVR app via a launch script that Christoph has provided.
$openvr/build/samples/hellovr_opengl/run_hellovr.shAt this point, we should have a working HelloVR app and be able should see something like this:
On the right is the vrcompositor window, which draws what you'll see through the Vive. The image is duplicated and offset for each eye. On the left is a normal monitor with a preview window that runs at a significantly lower frame rate and resolution that allows you to see what's going on without putting the device on.
Interestingly, the preview window shows significant lens compensation distortion while what's displayed through the device doesn't. This seems to indicate that the compositor isn't quite doing everything that it's meant to be doing.
HelloVR is also meant to use the OpenVR API to retrieve 3D models of the controllers and Lighthouse base stations, which are positioned in 3D space, although at the time of writing, I haven't been able to get this aspect to behave correctly.
Anybody who goes through this is likely to notice that there's a significant amount of latency (my gut says it's input latency, but it's difficult to discern the difference between that and render latency). At this point in time, I'm uncertain whether it's introduced by the HelloVR app, the OpenVR abstraction layer, the Vive driver, or even just launch options for vrserver, but it does suggest to me that there's still a little work left to do before the Vive can be considered "Linux ready".
A Little More Background
As soon as I had a stereoscopic image and headtracking working, I sent an email to Christoph to invite him to offer some comments on his work.
Quote"My changes are actually quite small. Valve definitely started porting the sample to linux (some #ifdef __linux__ etc.) but it seems halfway through apparently they stopped. It's weird because this is basically what makes it build and run.
Well, and they have no build system for linux so I threw some cmake stuff together."
Without a device to test with himself and with the dominant understanding being that the Vive can't run on Linux, Christoph was surprised to learn that his efforts to get an OpenVR sample application allowed myself and SketchStick to demonstrate our Vives running on Linux with the existing OpenVR drivers. Equally surprised at his perseverance with maintaining his fork without a device, I asked Christoph about his interests and motivations with regard to VR.
Quote"I personally had preordered an Oculus Rift DK2 because they sorta had linux support and were bought by Facebook so I thought they'd surely deliver and I could play with unity or unreal. Well, they didn't deliver and I sold my DK2 and wrote History of Openness to express my disappointment with oculus. The SteamVR oculus plugin worked more or less, but all of SteamVR's engine integration is only for windows too, so there is that.
As long as all of the interesting stuff is confined to proprietary platforms that are tied to windows I don't really care that much about VR right now.
I am hoping for the next OSVR HDK to have a display that is on par with Vive and Rift though, then I would likely buy one.
Still the trouble remains that while Oculus and Valve only support VR on windows, almost all VR applications will be windows-only too, so stuff like LibreVR/Revive and a cross platform SteamVR would remain pretty useless, at least until wine can really support low latency translation.
My experience with oculus-wine-wrapper was that it works for some unity applications, but not all and that the latency is a bit off...
Well, back when I bought the DK2 I made this subreddit, but there is not a lot of content.
Since I don't like oculus anymore I thought I'd rather have a subreddit name like this, but.. yea, I need to look for some content."
Looking Forward
Christoph's History of Openness chronicles some details of Oculus' history that I wasn't previously aware of and reflects a level of disappointment that I think we all feel - not only over Oculus' apparent indefinite postponement of Linux support, but also for Valve and HTC's decision to launch the Vive without advertised Linux support.
Oculus dropped Linux support at the time that they shifted towards direct rendering mode. Assuming that there weren't any external factors involved in discouraging Linux support (something I'd rather not entertain in this article), it seems fair to assume that there were hurdles with regards to getting that performant and stable that were large enough to justify shelving Linux support in favour of focusing on a single platform.
The HelloVR app doesn't use direct rendering mode either, and it could be easy to assume that Vive's Linux support is a victim of the same prioritisation that lead to Oculus stepping back from Linux. In this case at least, we can see evidence of continued Linux related updates to OpenVR listed on SteamDB, with the most recent changes to OpenVR and Vive/Lighthouse related drivers happening within the past three weeks (change #1920962).
Looking even farther back, we can see that the Linux OpenVR libaries and binaries have continued to be updated alongside other platforms for the past two years (all the way back to change #395316 when vrserver_linux as added).
I want to sorely and strongly stress again that even though this article is about how to get the Vive to run, and that it highlights continued work on Linux support for the Vive, that now is not the time to run out and order a device or to hassle developers who aren't already shipping OpenVR support in their Linux builds. Both of those are important steps, but can't happen until either official vendor support for the Vive on Linux is announced and promoted as ready and stable, or until there is a feature-complete F/OSS driver available.
In the coming weeks, I'm sure that we'll dig around and discover Linux/Vive compatible apps, better identify the cause of (and possibly resolutions for) the latency issue I mentioned previously, and of course, we'll see progress on OpenHMD's Vive branch as well. Hopefully the proper release of Vive's Linux support is also on the near horizon.
Exciting times are ahead! Article taken from GamingOnLinux.com.
0 Likes
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
Omfg I'm so totally sold on Vive. Ever since I tried the first edition of the Rift there was no doubt for me: this is a vagon I'll jump on for sure.
But I NEED Linux support first.
Last edited by Beamboom on 18 May 2016 at 6:52 am UTC
But I NEED Linux support first.
Last edited by Beamboom on 18 May 2016 at 6:52 am UTC
0 Likes
Quoting: slaapliedjeThis kind of reminds me of when 3Dfx cards were first coming out. 3D acceleration used to be laughed off as a niche, and that no one would support it, and initially there were so many different APIs for it, and you only hoped that you had ended up with a card that most games would support.I don't remember anyone saying 3D acceleration was a niche, even if not everyone thought 3D games were their thing. It was all about making those pretty, textured 3D games run at acceptable speeds back when unaccelerated software implementations couldn't do much better than the pseudo-3D of Doom.
VR isn't about enhancement or acceleration, but about a different way to interact with and experience games (and software, the 3D painting stuff seems cool). And it's entirely about making games more immersive. I've found that people generally split into two camps on that issue. Personally I've never thought games need to be more immersive to be more enjoyable. Maybe it's a personality thing?
Quoting: BeamboomEver since I tried the first edition of the Rift there was no doubt for me: this is a vagon I'll jump on for sure.Meh. I'll skip the wagons and wait until they come up with a comfortable and affordable rail service.
0 Likes
VR is the future, whether you like it or not. I think VR sucks right now, but even then I found the HTC vive to be an immersive experience.
0 Likes
Quoting: BillNyeTheBlackGuyI think VR sucks right now, but even then I found the HTC vive to be an immersive experience.
It's mainly the software that sucks (lots of demos and VR tests, few actual fun games), but you get Occulus etc. who spread that "the hardware isn't there yet" for two years. Or rather: "only our $700 headset with <20ms response times is enjoyable at all" etc. Not sure why they do that (scaring people from trying it seems a bad idea), as CardboardVR (the original) is already pretty cool even with a 720p screen. Ok not great, but nothing really horrible about it either and definitely good enough for the WOW effect and some simple, fun games.
I am looking forward to the new Google stuff next week that will be likely much cheaper, and I think the PS4 HMD will be by far the most popular as it is good enough for people to enjoy VR with it, but doesn't cost an arm and a leg (and I have never owned a Playstation nor will I change that, but the current PC HMDs are clearly over-engineered and too expensive).
0 Likes
Quoting: BillNyeTheBlackGuyVR is the future, whether you like it or not.So I hear, but what does that even mean? Please elaborate.
VR is clearly only useful for a subset of (real-time) 3D games and an even smaller subset of non-entertainment software. For other uses it's not the best tool for the job, now matter how cheap or lightweight the hardware becomes. Just like mobile touch-screen interfaces won't displace dedicated input devices and large screens for serious work, even if a persistent mob of hipsters have been declaring traditional computing extinct since the launch of the first iPad.
0 Likes
Quoting: GuestThe only games playable in VR are:Wait what? Hardly. There are tons of other game types that works great. It's all about how you implement it. I've been playing both RPG games and multiplayer fps games that have been an absolute blast.
- flight simulators and space dogfight games
- first person racing games
- stupid minigames where you’re stuck in place
And none of these are of any interest to me.
0 Likes
Mountain Man May 18, 2016
[quote=tuubi]
VR probably won't outright fail, but I think it will ultimately be relegated to the niche of specialized hardware like floor pedals, steering wheels, flight controllers, and articulated chairs.
Quoting: slaapliedjePersonally I've never thought games need to be more immersive to be more enjoyable. Maybe it's a personality thing?This is why I think VR is going to be a (relatively) short-lived novelty, because people are going to be playing essentially the same games that others can play but without cumbersome hardware strapped to their heads. Does VR make games more "immersive"? Possibly. Does that make them more enjoyable? Not necessarily. It's like the old debate of how to get people to upgrade to high definition televisions when the content they would be watching wasn't actually going to be any different than what they already had access to on their standard definition sets. The X-Files was a great show. Would watching it in high definition have meaningfully improved it? No. That's why HD television was dead in the water until the government intervened and forced television stations to abandon standard definition broadcasts. What VR needs to really stand out is a game that can only be played in VR, but is everybody necessarily going to like that kind of game?
VR probably won't outright fail, but I think it will ultimately be relegated to the niche of specialized hardware like floor pedals, steering wheels, flight controllers, and articulated chairs.
0 Likes
Cheeseness May 19, 2016
I think it's a little early to be making determinations about what VR will/won't be. We haven't seen a "typical" VR app and probably won't have things that will be meaningfully reflected on as "definitive experiences" for a couple of years.
I feel pretty confident that in the short term, we'll see prominent VR funtimes coming from unexpected angles. Some examples of current/upcoming VR titles that have potential, but might not be an obvious candidate: Super Mega Mega is a 3D side-on platformer that's looking pretty good (last time I talked to the developer, Linux support was on the roadmap), Ron Gilbert has been considering VR support for Thimbleweed Park, and the Kentucky Route Zero spin-off The Entertainment is one of my favourite VR experiences so far.
I feel pretty confident that in the short term, we'll see prominent VR funtimes coming from unexpected angles. Some examples of current/upcoming VR titles that have potential, but might not be an obvious candidate: Super Mega Mega is a 3D side-on platformer that's looking pretty good (last time I talked to the developer, Linux support was on the roadmap), Ron Gilbert has been considering VR support for Thimbleweed Park, and the Kentucky Route Zero spin-off The Entertainment is one of my favourite VR experiences so far.
0 Likes
Quoting: Mountain ManDoes VR make games more "immersive"? Possibly.
Saying that is obvious you have no idea what you talking. At moment you try VR you will understand the meaning of immersive.
Does VR make games more "immersive"? OMG YES! I'm inside the game!
0 Likes
Cheeseness May 19, 2016
Quoting: bubexelQuoting: Mountain ManDoes VR make games more "immersive"? Possibly.
Saying that is obvious you have no idea what you talking. At moment you try VR you will understand the meaning of immersive.
Does VR make games more "immersive"? OMG YES! I'm inside the game!
I feel that the "immersion" you automatically get from VR hardware is more superficial and less meaningful than the kind of immersion you have can have from a non-VR experience that you are fully engaged with and captivated by.
VR does open a lot of doors for different kinds of immersion that are harder to achieve (or perhaps not even possible) without, but none of that is guaranteed. I'm sure we'll see many VR titles released in the future that don't provide meaningful immersion (and I'm sure that some of those will be intentional and valuable experiences in their own right).
0 Likes
Currently working on Winter's Wake, a first person text adventure thing and its engine Icicle. Also making a little bee themed base builder called Hive Time :)
I do more stuff than could ever fit into a bio.
See more from me