Forum Replies Created
-
Posts
-
FWIW, I make positive posts about vorpx all the time on reddit, and I don’t get downvoted. I often get positive, curious responses. The negative posts I see always seem shallow (in the sense that they only tried it once or say something that is demonstrably inaccurate), so they’re easy to respond to. I just try to be honest and detailed and only talk about games I’ve played through in vorpx.
It feels a bit weird saying this about anything, but I also wish there was a way people who purchased vorpx could donate more. I wouldn’t have bought half my steam library if it weren’t for vorpx. I feel like Ralf deserves a chunk out of each of those purchases.
This thread made me go try it too. I’m surprised how cool looking it is in stereo 3d.
(And, it’s a bit cathartic creating a virtual you that can actually leave the house and do stuff. :P)
I remember reading that some games need to be borderless to get a 3d effect, but I didn’t realize fullscreen could cause issues if the 3d was working. I suppose it does make sense. When it’s in windowed mode, the OS just needs to hide a window, but when it’s in full screen, it’s changing a monitor settings, which leads to things needing to be re-initialized.
If it’s not already obvious, your suggestion worked beautifully. After I switched AC settings to bordlerless, I can tab out without it crashing. Thanks!
I would like to have a similar blast. :) I saw you were using SuperDepth 3d or something to play it but had some issues with crashing. Have you found a workaround or have you just learned to live with it? Also, did you try it with Syndicate too?
That’s a shame that they did something unusual that makes it hard/impossible to get vorpx working with it. Odyssey and Origin are so gorgeous in vorpx. Those are the two I use to wow people and turn them on to vorpx.
I ran across several articles that said that the original plan was to have AC Syndicate include native stereoscopic 3d support for PS4. How odd. While it never panned out, it does make me wonder if we can’t get this to work because they did something unusual with their depth buffer when they were trying to pull that off.
https://wccftech.com/assassins-creed-syndicate-stereoscopic-3d-ps4/
I could not get any 3d effect from that user profile. It did load though. I also tried creating profiles based on all the Assassin’s Creeds that came out around that time and the suggested base profiles for unreal 4 dx 11 games. I couldn’t get any 3d from any of them. (Also, several of them would stop the game from loading.)
For what it’s worth, there was one profile that did seem to alter some shaders, but it didn’t do anything good and only had an effect in geometry 3d mode. (When activated, the game dropped do a few fps and several of the shaders for characters turned black or invisible.) I forget which game I based it on, but it was one of the assassin’s creed ones.
I just want to add a positive comment now that I’ve gone through about half the game in vorpx mode. After the recent updates to Vorpx and Cyberpunk, everything has been working like a dream. I rarely get any crashes any more and am getting a very solid 45/90 on my 2080 Super. (I do have to turn of DLSS. It was fine in the starting missions, but started to slow things down too much once they let you loose in more crowded areas.) Vorpx makes the game so much more immersive; Cyberpunk’s first-person perspective makes it feel like it was made for it.
FWIW, I found the readability of the UI in VR could be improved a bit by using one of the mods that changes the UI text/HUD color from red to yellow. (I’m not sure if links are frowned on here, but they’re at nexusmods.com if you want to try it.) And, FYI, adding –launcher-skip to launch options in Steam will skip the Project Red launcher.
To follow up on my previous question about resolution, I think I see a bit more about what’s going on. Originally, I wasn’t seeing any visual difference when switching the resolution in vorpx menu. I think this is because vorpx was always setting the resolution to 1920 after restarting the game, even if my “preferred” resolution was set higher. I’m guessing that means that vorpx decided that 1920 was the closest resolution to my preferred resolution that my specs can pull off reasonably. Is that what’s going on?
If so, does that also mean that switching resolution in vorpx is exactly the same thing as switching the resolution in the game, the only differences being that it won’t occur until you restart and it will consider the custom resolutions we added, which aren’t available in the game’s settings?
(If what I’m guessing is at all accurate, is there any way to force it to try one of the higher resolutions we added that Vorpx might think is too high?)
For those of you who thought something might be wrong with your automatic profile updates, it may be because you never exited Vorpx or rebooted your machine since the update was released. I thought the same thing until I realized that Vorpx only checks for updates upon launch. (It turns out I seldom did either of those things prior to Cyberpunk crashes.)
What’s the relationship between Cyberpunk’s resolution setting and the custom ones you can add amd change to in VorpX? Does the DirectVR resolution setting in VorpX simply override the games resolution at launch? Or is it doing something more complicated where it’s rendering in the headset at a different resolution than what the game renders to your monitor?
I’m a bit confused because I didn’t notice a big visual difference/performance hit after installing the custom resolution and changing the resolution setting in vorpx. Making similar changes in the resolution in Cyberpunk’s settings menu seemed to change things much more drastically on both the screen and in the headset. The text was much clearer than I had seen before but the performance hit was also much higher.
First of all, I’m loving Cyberpunk with Vorpx. I don’t think I’d be able to play it normally now. Overall, it’s working great and far better than I hoped for.
Unfortunately, I am also getting fairly frequent crashes. It’s to the point where I’m having a hard time making progress in the game. (To be fair, the steam discussion for the game has quite a few people who don’t use Vorpx that are also seeing regular, random crashes. Some, or maybe even all, of this may be unrelated to Vorpx.)
Personally, I’m seeing two kinds of crashes. In the first type, vorpx crashes while Cyberpunk continues to run. (In my headset, I’ll get a little window that says it’s waiting for Cyberpunk that never goes away.) This type of crash seems to occur most often if I tab out or switch vorpx settings in the vorpx menu. The second type of crash occurs randomly while playing. In that one, everything dies and I get a Cyberpunk crash report window. (I looked at the crash report a couple times, and it looks like a memory access/null pointer type crash.)
I’m also seeing the previously reported issue where the top (or maybe bottom?) half of the screen is no longer 3d. (I checked the color precision setting, and it is set to high. I’m not sure why the solution that worked for others is not working for me.) The problem seems to always start during cut scenes. I could be wrong, but it seems like it starts specifically when the cut scene force the players view to pan left or right to see something.
(I’m running Windows 10 with a 2080 super, the new nvidia drivers from a few days ago. I am using the base profile. The only thing I changed was adding custom resolutions and switching to one of the slightly higher resolutions in vorpx’s direct3d menu.)