Forum Replies Created
-
Posts
-
Direct driver business is what Oculus needs. It’s the extended mode that Oculus needs to lose, hence 0.7 and above.
My vorpx wasn’t detecting Battlefield 4 or GTA V. Turns out my comodo internet security was killing the vorpx control process needed for 64 bit games. The vorpx control (32) was unaffected. The only way to get the 64 bit vorpx control back was to completely uninstall comodo. Vorpx now works uninhibited.
Switched to a different free firewall: Privatefirewall 0.7
I use runtime 0.7 with vorpx .9
Update:
I had to completely uninstall comodo internet security. I thought I could get away with just uninstalling the AV part and leaving comodo firewall. Wrong.
After completely uninstalling comodo completely… the vorpx control is now resident in memory and GTA V is detected.
Ok, I’ve been looking through this forum and found a few other people had the same issue.
Ralf said: “Without vorpControl64.dat running the game will not hook. Most games are 32bit, hence they work. It’s impossible to tell from here why it does not run in your case unfortunately.
If that is an option for you, you might want to consider a fresh Windows install.”
davidmi58 said: “Ok, I got it finally got it to work. Disabling Comodo was not enough. I had to uninstall the whole program. After that. Vorpx picked right up on it. Now, I just have to figure out what to do about an antivirus program. I hope this helps the others in this thread that are having the same hooking problems.” << I’m using the same antivirus.
I can confirm Vorpx has settled down and runs as it should since I stopped the AV sandbox. Also Vorpx does change the FOV via optimisations page.
Fallout 3 looks very good.
@Ralf:
Although Vorpx hadn’t been sandboxed I think some windows files had and that seems to be the cause. It’s stopped corrupting now.
Still don’t know why vorpx isn’t setting the FOV on games using the optimiser. It’s saying it has but not reflected in the game. I’m setting FOV manually at the moment.
IPD really made a difference with Metro LL but I didn’t realise the FOV wasn’t being set in other games like Arma 3 and Crysis 3. Can only go so far using the vorpx FOV/image zoom so I have to manually edit the FOV for these games. Arma 3 looks correct since manually editing FOV to 120.
My IPD of 67 I got via my Oculus rift profile (after doing the calibration.
Serious Sam 3 looks great on vorpx.
Unless maybe it’s Comodo internet security? Vorpx is “allowed” but nevertheless the sandbox has been active for some windows stuff.
I can’t see an option to completely disable the sandbox.
I might try uninstal comodo.
Vorpx is on C: drive.
Steam is installed on C: but all of the steam games are installed on G: drive (another SSD).I wouldn’t know where to begin with this issue. I was running Vereio perception ok but I understand that’s different software.
Maybe installing vorpx in admin mode would help but I may have tried that already.
I only ever login with one account and that is showing as:
Admin
Password protected.I have windows 8.1 set to automatically login each boot cos I hate that manual sign in that windows has by default.
User account control only shows 1 account existing.
UAC is on default level.
I know what you’re saying makes sense. I have to think more logically about the problem. So it occurs to me that if the FOV is changed to 120 for a particular game that should be very apparent when I play the game without oculus. It would give a very wide angle lens look. So I went into Arma 3 without oculus and the FOV was just default. Even though I’d used the vorpx ingame optimisations.
http://hia3.com/tools/ArmA_3_wide-angle_FOV_calculator_online_by_Hi,A3.htm
I found this FOV calculator for Arma 3 and edited the file myself and the FOV set manually to 120 is correct. I haven’t checked it out with Oculus on yet but it should be good. So the question is why the FOV isn’t being set by ingame optimisations. I’ve tried setting vorpx to admin mode.
There is another problem…
I have to reinstall vorpx numerous times per day. If I close vorpx down to try a game without it, then after exit game and restart vorpx – I am guaranteed vorpx will crash with error code 3. Rebooting windows makes no difference. Once the error code comes it’s permanent until I reinstall vorpx. After reinstall, vorpx works ok again.
Any idea what could be corrupting it?
I’m careful to make sure skype and steam are closed before I start vorpx but this crashing occurs whenever I’ve closed down vorpx and then restart it (without rebooting windows).
It just corrupted again: Error code 5.
I’ve been spending time with Crysis 3, Arma III and other games and all have this zoomed in view that makes them unplayable. Adjusting FOV to 120 doesn’t help here and IPD also doesn’t make any difference.
So it seems like the only way I can play these games is with cinema mode which isn’t as immersive and I can’t look all around me.
I’m really starting to feel like I’m wasting my time with it. Trying to reduce the zoomed in view on every game. I use the game optimisations and in some cases manually edit the game’s FOV but the games still don’t look right.
Does it make a difference which Nvidia graphics driver? I’m using an older one: 350.12
The whole thing is starting to really annoy me because it’s so far removed from the visuals I get with native oculus games.
But the game looks good since I changed IPD in vorpx menu!
:)
IPD is 67 now. Default was lower. Also upped the stereo depth and reduced the vorpx zoom.
Yes and the vorpx optimiser has been taking effect. It worked for Dishonored for example so I know that’s not the issue. Because metro LL was still so zoomed I tried going more extreme with the FOV from user.cfg. That didn’t help. Using vorpx image zoom and increasing vorpx FOV helped a bit but still not enough for correct image.
I think the IPD was wrong for my eyes. Surely the IPD can’t be correct for everyone or else you wouldn’t have adjustment for it in game?
:)
But I was using a combination of modded FOV to 120 and vorpx FOV and image zoom last night. I zoomed out to the point where I could see the bars at top/bottom. The only way metro looked correct in zoom was when Mouse M peek was used or in cinema mode.
So why do you have IPD calibration in vorpx in-game menu if it’s not a factor in setting up correct image?
I tried all the steps u listed and FOV still too zoomed for metro LL. Dishonored looked much better with the steps but not Metro.
I think the default IPD is fine for most eyes but I guess not mine.
But…. maybe it’s a vision thing? If the FOV steps u detailed work for most people.. perhaps my IPD is out of normal range then? After I set my oculus calibration some weeks ago that shows 67 IPD. Default vorpx IPD is lower than this. Upping the FOV using vorpx in-game was dramatic. For the first time the zoomed-in look has gone and it looks pretty good now.
I reckon if I go back to Dishonored with the correct IPD for me then that too will look better.
I did a combination of the steps u listed last night and as I said… didn’t help.
The one step that did work was putting the games in cinema mode but that defeats the purpose. I think cinema mode is great for some games (especially 2d ones) but for any game with 3d support on vorpx I want non-theater mode.