Forum Replies Created
-
AuthorPosts
-
Aug 28, 2015 at 5:33pm in reply to: Will vorpx ever work with the newer Direct Display driver? #89567
bcozier
ParticipantAh cool then…I had thought it maybe impossible…so it’s just a matter of time then, that’s great.
Jan 15, 2015 at 1:28am in reply to: VorpX 0.75 massive performance drop in Borderlands 1 confirmed #28532bcozier
ParticipantWith options on and high there is definitely a significant drop, would be useful to have a fps display for 0.71 also. It dips to 29/30fps with 0.75 checked with Alt-F and ultra smooth with 0.71, especially at the place where the shadow from the windmill is on the ground in front of you.
bcozier
ParticipantThanks for responding and letting me know.
Jan 12, 2015 at 3:19pm in reply to: My Bioshock Infinite is showing double image in each rift eye #27205bcozier
ParticipantOk I found the culprit. The latest NVIDIA driver version 347.09 has a problem not only with Bioshock Infinite in VorpX producing double image in each eye, but also same thing happens with the Oculus Config utility desk scene, it shows double image ONLY when Rift is in extended mode. Strange that no other games gave any problems in Vorpx except for Bioshock Infinite. I confirmed the new driver is the problem by reverting back to the old driver and everything works fine. Re-installed new driver 347.09 again and problem re-appeared both in Bioshock Infinite Vorpx and Oculus Demo desk scene.
Does anyone also have an NVIDIA card with driver 347.09 that they can test with? I am also using Win 7 64-bit and GTX 670 FYI. My next test is to try Win 8 with latest driver and see if getting same problem. Will post back results here later.
Sep 7, 2014 at 11:49pm in reply to: Skyrim and other games work super sampled at 2650×1440 on DK2 + vorpx #17453bcozier
ParticipantInteresting…I will give a try for MW3 and Borderlands 1, since they are buttery smooth at 75hz already..so should we then turn off any aliasing options in the game settings?
bcozier
ParticipantThat fix, as another user noted could be related to GPU or CPU overheating…get a utility to monitor your temperatures while running the game too.
bcozier
ParticipantI was able to find a fix for Fallout crashes…sounds quite feasable…you might want to try it and let us know if it solved your problem.
bcozier
ParticipantFallout 3 – Game of the Year edition. Can you please add support to that, it keeps crashing on me while in DK2. Thanks!
I remember I used to get crashing on that game often too without vorpx. It was on an AMD CPU with AMD GPU. I now have intel i5 and nvidia GPU and I tried it with vorpx and it works fine for me. If you are overclocking anything turn off all overclocking and try that first, otherise the game just might be favoring either intel cpu or nvidia gpu. I don’t think there’s much ralph can do because I can play it without issues and the 3D is sxcellent btw.
bcozier
ParticipantOk, it was IPD. I set it to 61 in game with VorpX and everything is scaled correctly now. It was as simple as that… nobody even thought about it… :P. VorpX is using completely different IPD. Don’t ask me why.
I guess we should try to remember that when someone is having problems…you are correct my dk2 config util sets my ipd at 69.1mm however in vorpx I use 63.5 which is less by about 5.5mm tell us what is your dk2 util ipd after doing the 4 green lines thing…
bcozier
ParticipantWhat Oculus runtime are u using 0.41 or 0.42? You should use 0.41 since that’s what the current vorpx was made for…although I’ve tried 0.42 with borderlands and it works fine with vorpx.
bcozier
ParticipantAlso make sure you UNcheck “Enable Personalized Rendering for this eye position” in the dk2 config utility advanced..
bcozier
ParticipantMake sure you choose “Do not use an oculus profile” in the vorpx config. That causes double image if you try to use a profile. I know because I tried to see if the new .42 runtime fixed that problem with vorpx but it did not, vorpx will need to be updated with the new .42 sdk and then it might work but for now definitely choose no profile.
bcozier
ParticipantThe new 4.2 is supported I just tried it. Make sure and select “Do not use an oculus profile” in the vorpx config.
Also, you should select “Show only on Rift DK2” not “system settings” and make sure your games have configured resolution for 1920×1080.
Try and see if that works, if not then you should configure vorpx as “use system settings” AND then make your rift the primary display. You’ll need to close one eye and launch your games from the rift display after that but should work fine.
bcozier
ParticipantI hear ya…but I’m not sure a direct to rift mode would be possible with vorpx because of the nature of the non-native games. I’m glad I found that util so it’s no longer a pain in the A55 to pull up nvidia display panel to switch primary and disable secondary and all that crapola. I manage to launch games a whole lot quicker now.
bcozier
ParticipantAnother way to circumvent the annoying rift when set as primary display mode would be to get a utility to map hotkeys to launch your games/apps…its not perfect but an option.
Here you will find a hotkey utility to make it easier to toggle primary display between rift and regular monitor and another hotkey to toggle disabling and re-enabling your secondary display.
I personally still use the peek into rift display to launch my games after.
-
AuthorPosts