Forum Replies Created
-
Posts
-
No problem is getting ignored, but unfortunately it’s impossible to give specific advice if an issue is not replicable here. There almost certainly is something on your PC that causes a conflict with the 64bit part of vorpX. All I can recommend at this point is what I recommended above already, which is double (and triple) checking for things that may interfere with vorpX.
For inquieries about prices and conditions of professional use editions and hourly rates for custom adjustments please contact info |at| vorpx com. Thanks.
Your web installer always installs the latest version that is available on the server.
The most likely cause of your problem is a conflict with your virus scanner or other security software. For testing purposes please try to disable all such software. In some cases (for example Comodo) these programs aren’t really disabled when you disable them, so uninstalling may be the only option.
Please also try to reinstall both the latest Oculus runtime and vorpX again after uninstalling them and rebooting your PC (important).
Download links were sent to you each time you requested them.
The last four mails sent to you are dated March, 16., April, 7., April, 12. and April, 16. All sent to your satx.rr.com mail address, which is the one we have registered for your purchase, within a few hours after you requested the download.
Please check your spam folder, the mails may have gone there for some reason.
Please contact support |at| vorpx com about registration issues or use the contact form linked above. The forum is not the right place for this. Thanks!
This is a false positive.
Apparently a recent virus signature update for MSE/Windows Defender caused this. The latest from today (1.5.) shouldn’t be affected anymore. Tried with MSE (Win 7) and Defender (Win 8).
I raised the max. value right after we spoke about it, so this will be in the next update. Default stays the same, but you will be able to raise it up to 1:1. Current release date is good old “when it’s done”, but shouldn’t take too long.
I just want to add that “Enable expert settings” has to be checked in the config app to make the EdgePeek options available. With expert settings enabled, the options can be found on the display page of the ingame menu.
Can take a few days from time to time, but it’s also not impossible that something slipped through, of course.
If you checked your spam folder without finding an answer, please resend your request using the contact form linked above. That would at least avoid possible spam filter issues on our end.
This is a false positive.
Apparently a recent virus signature update for MSE/Windows Defender caused this. The latest from today (29.4.) shouldn’t be affected anymore. Tried with MSE (Win 7) and Defender (Win 8).
With a DK2 this should not happen normally. The camera moving out of the tracking volume, like pitt suggests, may be an exception.
In case of a DK1 however that is to be expected, as the DK1 has a fairly high yaw drift. Can be significantly reduced by calibrating the magnetometer in the Oculus Config Utility.
I don’t really have an answer to your question, but to me this sounds more like an issue with the game’s screen resolution. Maybe you set it to something else than 1920×1080 for playing without vorpX?
Might also make sense to restore the game’s profile in the vorpX config app to reset everything to default before completely reinstalling the game. Just to make sure this is not caused by some accidentally changed vorpX settings.
The game has a Game Optimizer profile (vorpX config app) that allows to set the FOV higher than you can in the game option.
If you still think that things look too large after the FOV is set to 120°, you can change the perceived scale with the 3D-Strength/Separation parameter in the vorpX ingame menu. Larger values make the world appear smaller. The default value should work reasonably well in most cases, but might not always be perfect.
Honestly, how many reports of vorpX destroying boot sectors do you see here? When vorpX does not run, it does nothing, and when it runs, all it does in the background is checking whether DirectX programs are started. If you don’t run it as admin, which isn’t necessary, it can’t even hook into system services/programs.