Forum Replies Created
-
Posts
-
The HD project, while it does a lot, doesn’t change the game engine so the existing profile should still work fine.
I think I remember something about someone getting a Windows Store game to work by creating an empty text file on the desktop and renaming it to the game’s executable (i.e. blank.txt -> game.exe), which got vorpx to hook. I don’t remember if that was a fluke of some sort or if it actually works, but it might be worth a try.
Echoing apollon01’s order of operation, always start the MR portal first. It takes the longest to get going and if you try to do start something in VR (even native VR games/apps) before it’s ready, things usually go wrong. The most common problem being the game simply doesn’t display anything in the headset. This is the “is the computer plugged in?” tech support of WMR.
Aside from that, there are a few things about WMR in general that aren’t specific to vorpx, but still worth mentioning. Unplug the headset when you’re not using it. The MR Portal has an annoying habit of randomly starting on its own if it “senses” that the headset is in use, even if it’s just sitting there doing nothing. Maybe the rotation of the earth convinced Windows that the headset was being put on. Who knows. A small warning on this though, I’ve seen people on forums that have said hot unplugging the USB caused damage to their headsets (probably a power spike). The reports are sporadic (usually cheap USB add-in cards or headsets with known low quality cables) and I’ve never had this issue in the few years I’ve been using WMR (Samsung O then later O+), but I’m mentioning it just in case.
In the Windows Mixed Reality settings tab (open Windows Settings, MR is [usually] the bottom option), there are a few options worth looking at. Some of them have the “Let Windows decide” option, which is generally a bad idea. You need to manually set the framerate to 90 hz or it will stick with the lower 60hz most of the time (even if you have the GPU power to go up to 90). It’s also (to me) worth setting input switching to manual; automatic can and will cause problems if you’re going back and forth between the headset and your normal desktop.
Also, if you don’t use the WMR Home much, it might be worth changing those to the lowest settings to reduce the overall WMR overhead. I haven’t done extensive testing on that one, so I’m not sure if it actually makes any difference, though. The rest of the settings are pretty much user preference and shouldn’t impact vorpx in any way. They probably do, but they shouldn’t. But they probably do.
No actual reviews yet, but nvidia is claiming the 3080 will be double the performance of a 2080, and the 3070 will be better than a 2080 ti. We’ll find out in a couple weeks how close any of that is to reality.
I’d wait until aftermarket/custom pcb cards start coming out.
Have you tried running it with dgvoodoo2? From a cursory search about the game all I could find out about it’s graphics was that it was 3dfx compatable; nothing about directx or opengl.
Ars has a decent vr hw guide: https://arstechnica.com/gaming/2020/03/the-ultimate-half-life-vr-hardware-guide-from-frugal-to-fantastic/
I’ve been using an Odyssey+ and my only complaint is the WMR portal is stupid and annoying. If I had to pick something new and money was no object, it’d be the Index, mostly because it has the least amount of overhead required to use (you need steamvr to use just about any vr program these days anyway).
It shouldn’t really matter in which order you start the apps.
It shouldn’t, but I rarely have luck getting stuff to work correctly if I don’t start the Mixed Reality Portal first.
The “safest” way I’ve found is to start Mixed Reality Portal, then Steam VR, and once both of those are working start the game. Whether you start vorpx before or after Steam VR doesn’t matter.
I’ve been wondering about the plausability of getting vorpx to work with some emulators. I’m not sure there are enough 3d ps1/n64 games to make looking into those worthwhile, plus there are way too many of them to try and support all of them. But…
PCSX2 is in it’s “final” 1.6.0 prep stages, would be nice to see an update of the profile once that’s released.
RPCS3, I know it’s main renderer is vulkan, but it’d be pretty neat.
CEMU, the opengl renderer seems pretty stable now that he’s working on a vulkan option. Not sure that makes any difference, though.
I know they all still have work being done on their video backends, which makes writing profiles for them a whack-a-mole game at best, but hey, this is a wishlist (also why I suggested waiting for the “stable” release of PCSX2). I didn’t mention Dolphin since it’s got its own built in 3d option with some of the devs working on openvr support.
Just an FYI, NVidia’s Low Latency Mode is the same thing as AMD’s Anti-Lag option. Both reduce the number of pre-rendered frames on the CPU before that information gets sent to the GPU. It’s basically just a fancy name for the (now removed) maximum pre-rendered frames option that used to be in the driver.
The main purpose of the option is to cut down on input lag, but it has the added benefit of increasing the framerate in a lot of cases (not all), especially when you have a high end CPU and a mid-range GPU. On a high end GPU you’ll definitely get better response times, you just might not get as much of a framerate boost. The major downside is because there’s little to no buffer with the option turned on, you can end up with stuttering in the game if the CPU isn’t able to get frames to the GPU fast enough.
I’d recommend turning the option on on a game by game basis, turning it on globally is probably a bad idea (really, turning any driver option on globally is a bad idea).
The VR pre-rendered option works much in the same way, but I’m not sure how vorpx interacts with that part of the driver (if at all). Generally speaking though, you want the option set as low as possible.
That’s the id tech 3 engine, you can check out all the games using it on the wikipedia page.
https://en.wikipedia.org/wiki/Id_Tech_3#Games_using_the_engine
If you’re running it using G3D, you might be able to get what you want yourself using the current shader tool (default ctrl+end, have to enable it in the vorpx options). Just cycle through the shaders until you get to the offending one and set it to disabled (or something like that, haven’t used it in a while so I don’t remember the exact wording).
Getting back to the original questrion, there are no specific features from either AMD or nvidia that give you better performance in VR vs. normal rendering.
The PC version of Arkham Asylum uses UE3 as well, it was updated to UE4 for the PS4/Xbone releases only.
Going through the UE4 list on wikipedia, very few games have native vorpx support (read: not user profiles). Hellblade and Life is Strange 2 are probably your best bets if you want to go off an official profile.