Forum Replies Created
-
Posts
-
For FarCry 3 you have to disable the game overlay in the UPlay options, otherwise the game only displays a black screen unfortunately. You can also try to use the DX9 .exe instead of the default DX11.
BF4 should work by starting it normally through Battlelog. If it doesn’t there are two things you can try: Starting the 32bit version instead of the default 64bit .exe, and go to offline mode in Origin. The latter lets you start the game without Battlelog, which might work better, but disables multiplayer.
ArmA III *should* work. Normally it displays one screen right after startup and switches to the Rift dual view after a few seconds. Sounds like the latter isn’t happening for you. The ‘This game is not officially supported’ message is a small glitch in the game profile, you can ignore it.
Does vorpX show any other message besides this one? In case it displays ‘Rendering API not supported’, your graphics card/driver might not support the full DX11 feature set that vorpX requires. Without knowing your system specs that’s just a guess of course.
The game should work normally. Sounds like this might be either a Windows 8.1 issue, related to the new Radeons or something specific to your PC.
I’ll check it under Win 8.1 and see whether it’s a general problem.
Hi Kitruntlay,
DayZ Standalone needs a game specific profile to run. It’s already working in the current dev build and will be available with the next vorpX update.
The message is most likely just the normal message that always appears when the game starts.
Please write a mail to support |at| vorpx com. The issue sounds really odd, but I’d like to try at least a few individual trouble shooting steps.
ArmA 3 supports separation of head and gun movement itself, that’s why this can be done with OpenTrack.
Most other games (including BF4) don’t allow this, and a driver like vorpX cannot circumvent that unfortunately, it’s always restricted to how the game handles camera movement. Or to be precise: There is a theoretical way to do this, but in almost all games it would lead to massive artifacts in the form of missing geometry depending on where you look at, since the scene geometry gets clipped before the driver comes into play. So that is not practical.
I’m sorry that the above answer is the only one I can give you. Normally using the 3D FOV Enhancement makes weapons look smaller due to the changed perspective, while keeping them in the correct proportion relative to the world.
Not sure why this does not seem to work for you. Could you provide a small video clip that shows what happens when you change the setting? I’d like to take a look at it.
Make sure that Geometry 3D is enabled and use the ‘3D FOV enhancement’. This changes the FOV for the whole picture, including hands and weapon.
If you use Geometry 3D, you can enhance the FOV with the FOV Enhancement setting from the vorpX in-game menu instead the of the Skyrim console command. This also changes the FOV for the payer model. Might make sense to use a combination of both for the best possible settings.
Yes, non-Steam games do also work. vorpX tries to hook into every DX9-DX11 game that you start, regardless how it is started.
Hi rodleach,
Unfortunately I can’t give you any specific advice. GRID should run perfectly fine normally, it’s not at all known as a game that can cause trouble.
The -dx9 switch is not neccessary btw., GRID is DX9 only.
All I have for you is the general trouble shooting sticky on the top of this forum. Maybe it contains something useful for your issue. Your problem sounds very odd though, so it might also be something machine specific.
Hi,
The license includes the full version 1.0 and all following 1.x updates. You get these updates automatically, similar to Steam updates.
Hope that helps.
A real shadow fix would require that it works with the default (deferred) shadows. Everything that requires changing the shadow mode in multiple .ini files – although certainly OK for enthusiasts – is not enough for a large part of the userbase unfortunately.
The nightsky issue is fixed already since mid November. Given the popularity of Skyrim minor game specific fixes aren’t low priority, but they also aren’t a top priortity, so I do not have a specific timeframe for something like that unfortunately.
You can (and always could) use vorpX’s integrated FOV control instead of the Skyrim console to change the player mesh FOV alongside with the game FOV. Shadows will be dealt with when we find a way to do this without requiring users to fiddle with .ini settings.
Hope this helps.
This crash clearly shouldn’t happen, but it can only affect native 64bit applications. So far almost all games also have a 32bit executable, it’s worth a try to check whether these work.
Other than that, please try to temporarily disable anything that might interfere with vorpX. This might be a virus scanner, a chat program that can display content over games, or a special display driver for example. If you have trouble starting anything, it is very likely that something on your system interferes with vorpX.
If you continue to have problems after checking this, please write a mail with some basic information about your system (processor, graphics card etc.) and – most importantly – a list with the games you tried to support |at| vorpx com for individual trouble shooting.