Forum Replies Created
-
Posts
-
No problem. You can easily absolve yourself by purchasing 10 extra licenses. Just kidding :) . Glad that you finally find vorpX useful and can have fun with it.
Except for the “Stretch” mode the aspect modes pretty much do the same as the “Image Zoom” option, so if you want to have more fine grained control over the image size, you can simply use the zoom instead of the presets.
Did you maybe change the gamma or saturation option (image page of the vorpX menu)? I don’t really recall GTA V to have washed out colors, but regardless whether that actually is the case or you changed it inadvertantly before, adjusting gamma/saturation is what you want to do in such a case.
That sounds extremely odd. Not sure what to recommend, sorry. As said above, vorpX doesn’t interfere with the gamepad in any way once Direct VR is enabled.
I’ll check whether there may be some bug, but I’m 99.9% sure Bioshock works exactly as it should in this regard.
Please check whether the gamepad is activated in the game’s options.
With Direct VR enabled vorpX does not interfere with the game’s native gamepad handling in any way. The vorpX gamepad options aren’t visible in that case because they are not necessarry with Dirct VR.
With Dirct VR the gamepad can be used natively, the vorpX gamepad override is automatically disabled after the scan. You should be able to make any adjustments to the controller mappings in the game’s options normally with Direct VR enabled.
You don’t need to tinker with the FOV anymore in Skyrim. Direct VR takes care of that and adjusts the FOV perfectly. That’s also the reason for the image zoom behaving differently with Direct VR, making it impossible to screw up the calculated FOV with the zoom. If you zoom out the image, the FOV is adjusted dynamically to still be correct regardless of the zoom value. The only reason to use the image zoom with a Direct VR game would be to enhance the image quality (pixel density).
If you for some reason really want to change the FOV, you can do that on the Direct VR page of the vorpX menu. I would *very* *strongly* advise against that though. The automatically calculated FOV is perfectly correct and should not be altered. Any change you make to it will cause image warping when you rotate your head.
Direct VR profiles are very game specific – more than I originally had hoped for. So far there hasn’t been a single case were not at least some per game adjustments had to be made.
@ matteo : following Oliiiiive’s hint should get it working. The game only works when using the DX9 renderer.
@ bankert : That is indeed not how it’s supposed to be. 30fps suspiciously sounds like a somehow locked/v-synced refresh rate. vorpX should take care of VSync, but it’s worth a try to disable it in the graphics driver control panel to be extra sure.
IIRC from my long gone Oblivion modding days there also are mods that artificially cap the frame rate to 30, e.g. the Oblivion Stutter Remover. If you ever used that mod or a similar one, try a totally fresh Oblivion install in case the mod made changes that aren’t reversible by uninstalling it.
Also deleting your Oblivion.ini is worth a shot. The game will create a new one on start.
The general issue here is that, as Cheekyfella correctly assumed, in some games the memory addresses can change on various occasions. E.g. loading levels, save games etc.
Hence the hint about memory scans not being always 100% reliable that is shown during each scan.
While vorpX supports about two dozen tweakable (and rather arcane) parameters for its scan profiles that help to find the right balance between reliablity and unwanted false positives, unfortunately there can’t be a 100% guarantee that the scanner works perfectly all the time in every game on every machine.
Did you check the support FAQ?
If the auto update fails for some reason, you can simply use your web installer to get the latest version.
If you didn’t keep a copy of the installer, you can get a new one here: http://www.vorpx.com/request-new-download/
Disabling FluidSync on the display page of the vorpX ingame menu will unlock the frame rate. It’s still quite possible that ASW auto-limits it to 45fps though afterwards.
I would generally recommend though to leave FluidSync on until you are sure that a game can sustain 90fps (game fps). Between 45 and 90fps either vorpX or the runtime always create interpolated frames. And 45 stable fps often feel better in this scenario than for example fluctuating 50-75.
Multicore CPUs seldomly show 100% usage while gaming, with or without vorpX. Games that fully utilize all cores are still very rare, and Skyrim certainly is not among them. What counts more is the single thread thread performance of a CPU since the main game thread almost always will utilize one full core 100% (which translates to only 25% overall CPU usage shown in the task manager with an i5).