-
Search Results
-
Not with vorpX alone, but at least for SteamVR there are tools that can display a desktop window in VR. Forgot the names unfortunately…
Dear Ralf, you are absolutely right. In fact, I’ve been using Desktop+ (free tool on Steam) to achieve this. I play SteamVR games such as Eleven table tennis, SkyrimVR etc. while having a second window pop up with my browser so I can watch YT or netflix and everything works flawlessly. Even Oculus games work without any problems.
It’s only when I start vorpx (in the vorpx config tool I changed back to Steam VR since I use a WMR headset) the second window which I created with Desktop+ for this purpose freezes as soon as I start a game. It’s still there where I put it but unfortunately it’s frozen so it becomes unusable and I have not found a way to make it work with vorpx.
In reply to: Cyberpunk VR Update Thread
Thanks for the update!
Out of curiosity, is there any way I can get this working in Cyberpunk v1.23? I keep noticing new visual ‘glitches’ only to discover that what I’m seeing is just the visual downgrades that occurred between v1.23 and v1.31. Most impacted are draw-distances, which have gone from “kinda crappy” to “unbelievably awful.” I clean-installed the game just to be sure, and even completely vanilla it does this. It’s so bad it’s kind of funny. Makes the draw distances in Skyrim and Fallout 4 look good, and those were awful at time of release.
I’ve tried everything I can find to fix the issue, and it’s so baked into the engine that nothing seems to actually touch it. Only way I know around it is to revert to v1.23, which was bad, but no where near this bad.
In reply to: Cyberpunk VR Update Thread
For reference I’m currently managing the following on my 3080-Ti:
Native game res: 3325×1871 (one of my easily-accessed DSR factors as my primary screen is a Sony Playstation 3D display, which is only 1080p).
Graphics: Close to maxed across the board, but with all features that are actually handled by RT turned all the way down. That should not matter, but I’m paranoid that the game engine doesn’t really know that (for example) shadows are being handled by RT and may be wasting cycles drawing non-RT shadows anyway.
DLSS: Quality
RT: ON -> UltraThe is providing an extremely crisp display for me in Cinema or Immersive mode. It’s not enough for full VR mode. But I’m very happy with those results. I’m getting 50+ fps, with the average right around 60. That’s also not sufficient for VR, as Brainwarp’s motion-smoothing is basically unusable in this title (it’s really great where it works well; such as Skyrim VR, but in some titles it’s just awful.) The nice thing is, with the HMD SYNC settings I mentioned above in anther post, there is zero stuttering or other issues. It just pushes my GPU to about 98% and pegs it there, smoothing rendering as many frames per second as it can without problem. It’s some of the smoothest performance I’ve ever seen out of vorpX.
In reply to: Amnesia: The Dark Descent
Hi,
just wanted to know, whether there is ANY other/new way to play Amnesia TDD with Radeon GPU (RX6700XT with HP Reverb G2), since it’s been a few years.
The (basically) immersive screen variant is nice, but is there a fix for the “eye switching” and stutter to play it in Geometry 3D, yet?
I basically got the same problem as quoted below, but sometimes one eye goes just dark and another shows (part of) the image.(anyway, Happy New Year everyone!)
I cannot play Amnesia Dark Descent at all. Both eyes get flashing flickering of the game and the frame rates is so low it would be less than 1 frame per second. Im running win 10 64 bit. AMD fx-8350 Black edition and an R9 390x video card. Quake 2 does the exact same thing. I have tried many settings to no avail. Games like Skyrim and fallout 4 run just fine. It seems to be a possible issue with Open GL not really sure. Any help would be greatly appreciated.
I was trying to play Observer today (original not Redux) with Vorpx and my Xbox One gamepad and it was just an absolute exercise in frustration. Sometimes the gamepad would seem to work fine. And then–without me changing anything at all–all the buttons on my gamepad would just stop working. I could move with the joysticks but couldn’t interact with anything. Then other times, the joysticks would also stop working, and I couldn’t even move. I was just completely stuck.
I understand that this is probably related to the fact Vorpx uses mouse controls for headtracking and sometimes games get confused between m/keyboard input and gamepad input … but what is the solution for me as a Vorpx user? How am I supposed to get around this problem? Do I just need to disable head tracking completely or is there another way to fix it?
Whether there is or is not a solution, I feel like there should be a stickie in the forum about this issue because it seems to be a long standing one that isn’t limited to just me. A google search for “vorpx gamepad controls seem broken” will get you an endless series of hits like those below:
Etc.
Ralph can we get a stickie on potential work arounds for this problem?
In reply to: Cyberpunk 2077
back in 2016 fullvr mode was G3D with headtracking, 6dof, automated fov with directvr scan, looks like things changed.
full VR mode cant be with Z3D when you dont have 6dof.
there are plenty of full VR enabled game, like skyrim, fallout 3, bioshock 1,2, infinite and many more but i have hard time understand why some games are listed as full Vr mode while they arent, i know for sure cp2077 is not, as defined since 2016 was fullVr mode was and is supposed to be.
In reply to: What are your TOP VorpX experiences?
Shadow Warrior 1 & 2. Intense, need Good VR legs.
Skyrim (played as mini g.i joe mode..Fantastic) Seriously try it. https://www.youtube.com/watch?v=a11VBm7ux44&t=2s
Half Life 2
Dark Messiah of Might and Magic.
In reply to: HP Reverb G2?
Controller issues with the G2 are greatly exaggerated. Personally i have about 300hrs playing the likes of No Mans Sky, The Forest, Fallout 4, Skyrim, and numerous smaller titles with zero issues.
The only thing that’s actually bad about them is the awful haptics, which pretty much requires you to turn the feature off. FOV is tricky, more is better obviously, but it’s something very dependent on the game experience. I find it limiting and extremely obvious in flight sims, but not obvious at all when bearing down a race track in the cockpit of a car. General games where you on the centre of the screen you probably won’t notice it, or at least become accustom to it.
It probably is worth waiting on the next iteration though, certainly if you’re routed to a AMD system, or need that extra inside out tracking camera they’re adding to solve generic problems with inside out tracking.
Absolutely a great device for VorpX though. If you have the ability (a 3090) you can crank it up to 3k per eye in steamVR, which makes games that looked poor in VR previously much much better.
In reply to: Is it impossible to use sweetfx/enb files?
It is possible but only g3d, z3d will be overridden by other shaders.
This however has more impact on performance than desktop use and you will need the vr hacked reshade dll to use (I only know reshade works, though there was vr enb for skyrim)
As for d3d9 conflict sometimes vorpx complains about it but works, sometimes it makes a game crash, sometimes you are able to rename it to any other dll to work. There is a list of dll names that windows applications load by default and with these post effect tools you can use those to make game hook post fx tool while not having vorpx complain.
All in all you have to try it yourself and success can vary per application and your dedication on trying to make it work.
In reply to: Tip: Fallout 3 with VorpX
Fallout 3 is definitely one of my top, if not my very top vorpX game. It just looks great and it runs very well in G3D at high resolutions. Thanks for the tip about the multicore fix. I’ll take a look at that. I’ve got a thread here somewhere that covers using the Fallout stutter remover etc, which may be necessary for many (Fallout 3 and NV had major stuttering issues when run at frame-rates other than 60 or 30, if I remember correctly). Other issues to avoid are frame-rates greater than 60, which will break the physics and can cause all kinds of problems (this issue persist through at least Skyrim and FO4). So you’ll want to use motion smoothing to double your frame-rate and lock your actual fps to 45/90, or 60/120 (for example). I lock it to 45/90 and that’s plenty smooth enough for me even in full VR mode (and it allows me to use UGRIDS=7, as that makes a HUGE difference to FO3’s otherwise extremely short draw distance.)
In reply to: vorpX 21.3.5 Available Now
Glad you like it. Setting the option to full enables a hack that AMD recommends game developers to implement in addition to the upscale/sharpen shaders. Didn’t cause a problem for me in Bioshock Infinite, but whether the hack is an actual improvement or not in general depends a bit on the game and the resolution it runs with.
The hack basically tells the GPU to load a more detailed version of a texture from memory than it normally would for the current pixel. When game devs implement FidelityFX they are supposed to do that in addition to the upscale/sharpening. vorpX can enforce the hack for every texture read (if available for a game). In some cases it doesn’t make much of difference at all or even introduces some shimmering instead of improving anything, but in other cases it does actual improve things. Easily spottable examples that probably everyone has available to try are trees/shrubs/gras in Fallout 4 or Skyrim.
I spent the last three days replicating what the AMD shaders do within the vorpX image processing pipeline. For the most part that meant adding a higher quality sampling algorithm that replaces the default GPU sampling for the headset render stage of vorpX. The sharpening kernel used on top of that is the same as before. It’s absolutely competetive, spent days finetuning its paramaters back then… AMDs dirty little mipmap trick, which normally only is available if game devs implement it in addition to the FSR shaders, can be forced by vorpX.
Long story short: turned out noticably better than sharpening only as currently available in the vorpX menu. Also better than adding AMD’s method as an extra step in between, since adding an extra processing step would partially negate the prior gain in clarity later when the image has to be resampled again.
But see for yourself. Skyrim SE is an ideal test case due to its super blurry antialiasing. Looks almost like being rendered at twice the resolution in the headset. I.e. at 1440p the image will look similarly crisp as 4K does without any processing, although (just like AMD’s method) in truth it’s really just traditional upscaling+sharpening. Unlike AMD I don’t have to compete with nVidia, so I don’t have to pretend it’s a direct substitute for their DLSS. ;)
No enhancement vs. vorpX “Super Resolution”:
CAVEAT: Note that this will only be available in the actual headset modes (Oculus, SteamVR, OpenXR). ‘Generic 3D-Display’ and ‘Generic Headset’ don’t involve any upscaling that could be utilzed for these improvements.
In reply to: Fallout 4 on Oculus Rift S
Bethesda games traditionally are well suited for the different things vorpX can do ranging from 3D to the memory scanner stuff, so both Skyrim and Fallout 4 are still being used here for dev work quite often. Surprisingly they also both still seem to be fairly popular among users despite VR versions being available, probably for the same reasons as yours.
Anyway: did you run the DirectVR scan (either ALT-L or from the vorpX menu)? After a successful scan there should be positional tracking for both G3D and Z3D since that let’s vorpX access the game’s camera position/rotation values in memory. Without running the scanner positional tracking is only available for G3D.
In reply to: Skyrim SE xbox360 controller disconnecting
Well, at this point I feel like a total idiot. My initial assessment was correct – it was the Oculus Client messing things up, not Vorpx. I realized this after the problem occurred again last night and I tried to repair it with the game console, which failed miserably because it was already gamepad-enabled.
For some reason the Oculus client was hiding the controller and sending keystrokes and mouse inputs (sounds a bit far-fetched on the keystrokes, but I opened up the console, moved the left stick around, and saw it fill up with WASD’s). I checked some other games (Bioshock Infinite for example) and they also had the same problem, while other’s didn’t (Borderlands 3 and Witcher 3). Even some native VR apps had this problem, whereas Virtual Desktop was unscathed.
Anyway, I had to re-install the Oculus software 3 times and re-pair the controller a gazillion times before it took, so I’ll be getting a new hmd soon. If you’ve got any recommendations for anything that doesn’t have Oculus or Facebook written on it…
So…I was really having fun in Skyrim – I’d lost interest in the game before Vorpx, but now I’m back at it again. Vorpx was what I got my headset for, I just didn’t realize it at the time, so thank you very much (I found that with few exceptions that native VR games are {expletive deleted}, IMO).
In reply to: Skyrim SE xbox360 controller disconnecting
vorpX doesn’t touch this setting at all. Skyrim is being played that way for years without anyone ever bringing up such an issue. As mentioned above, I also played it myself many hours. Plus the game actually still is one of my regular test titles. I’d love to tell you something else if I could, but this is not an issue that occurs under normal circumstances.
