Installera Steam
logga in
|
språk
简体中文 (förenklad kinesiska)
繁體中文 (traditionell kinesiska)
日本語 (japanska)
한국어 (koreanska)
ไทย (thailändska)
Български (bulgariska)
Čeština (tjeckiska)
Dansk (danska)
Deutsch (tyska)
English (engelska)
Español - España (Spanska - Spanien)
Español - Latinoamérica (Spanska - Latinamerika)
Ελληνικά (grekiska)
Français (franska)
Italiano (italienska)
Bahasa Indonesia (indonesiska)
Magyar (ungerska)
Nederlands (nederländska)
Norsk (norska)
Polski (polska)
Português (Portugisiska – Portugal)
Português - Brasil (Portugisiska - Brasilien)
Română (rumänska)
Русский (ryska)
Suomi (finska)
Türkçe (turkiska)
Tiếng Việt (vietnamesiska)
Українська (Ukrainska)
Rapportera problem med översättningen
You will need the 3D Vision Driver for it to generate the stereo images, and you can either click the new button on the first dialog, or it will automatically do that job when you first click PlayInVR.
Let me know if that doesn't seem to match what you are seeing.
One other possibility is the DCH driver dialog. You can still run DCH if you want to, but it's a worse experience. That dialog will convert from DCH to Standard, but will still be a regular NVidia driver, downloaded directly from their servers, not from us.
You can say No to the DCH dialog, and it will still work. However you get a 3 second pause on every launch, when 3D is enabled.
I've been using Nvidia 3D Vision for many years now (I'm that pesky drastic00 guy from the HelixMod blog). I did buy HelixVision a few weeks back, and I've had the Rift S since early June. I must admit the first time I tried HelixVision, my 3D Vision configuration went haywire. What I've been using (on Windows 10 version 1809) is a setup using Losti's driver tool, with the 3D Vision bits from 425.31 and graphics driver 441.87. I have been hesitant to further alter anything, as it took no small amount of work to get my rig to this point. As HelixVision appears to do some driver shuffling when starting (unless I did something wrong in the process), I presume that upset the balance, and 3D Vision then quit working for me. I never got HelixVision to work properly, and, sadly, I ended up reinstalling the drivers altogether via Losti's method. Now I'm back to '441.87 with 425.31 bits.'
SOOO, what might I expect now that this update to HelixVision is live? Would it interfere with my driver setup? If so, what is the best way to proceed? I've kept Windows on 1809, and I'm not in a financial position to run a dual-boot setup. I'm kinda scared to try again... If you're unable to respond here, please send a Steam mail. Otherwise, I'll track you down over at the blog LOL.
I'm very hopeful for this project; with the driver ghost busted, this would be triumph, a truly wonderful successor to 3D Vision, and it would allow all of the HelixMod/Shader Hacker community's work to live on!
***UPDATE on this comment: I discovered that there have been significant improvements that greatly simplify running current drivers on an up-to-date Windows 10, while keeping Nvidia 3D Vision functionality. If anyone is interested, check the forums here: https://www.mtbs3d.com/phpbb/viewforum.php?f=105***
The problem you had with HelixVision earlier would presumably still be there, although a lot of changes have happened. Without better details I can't say for sure.
Best bet- make an image backup of your running system using free Macrium Reflect, then if you blow something up, you can revert back to known running state in half an hour. Don't run your system in fear of corruption or breaking it, there's no reason to.
But yeah, I posted over in the forums that I found out that I could do some updating. So now I've done the Windows update to v2004, and used BringBack3DV to update to 451.67 with 3D Vision. All is well on that side of things. I'll be trying HelixVision again here and it sounds like it shouldn't affect anything the way it works. Then when I get a few more moments I'll be putting up a positive review, and I'll leave my troubles out of it.
I really do see HelixVision getting a new infusion of traction, it ought to open up things a lot for gaming in VR. As the tech gets better, cheaper, and more pervasive (I predict SW Squadrons is going to give it another kick in the pants), older games would get a whole new lease on life. Gamers could revisit many of their titles that are gathering dust as fresh experiences. This app could instantly increase the size of VR libraries everywhere. And the Shader Hackers involved would finally get their deserved dues.
Thanks
https://steamcommunity.com/app/582010/discussions/0/1743357605563901479/
Always possible it's related to HelixVision, but Steam and Reddit are full of people having that same error when playing in 2D.
Some suggestions were to roll back drivers to more stable versions. For HelixVision in particular, it would be worth trying 425.31, as that driver requires no driver overrides, and is compatible with all versions of Windows.
Easiest way to do that is in the HelixVision Settings tab, NVidia 3D Settings, Install recommended Gefore Driver. It will download then install the 425.31 Standard driver.
https://steamcommunity.com/sharedfiles/filedetails/?id=1938183170
Our main list when in VR mode is intended to be a known good list, and so we only add stuff there that we are certain is working smoothly. But, in what we are calling hacker-mode/3DVision mode, you can still try anything that you like. Only about 50% of DX9 HelixMod games will work correctly, but about 90% of DX11 games will correctly.