Forum Replies Created
-
Posts
-
That sounds strange. The Game Optimizer is the only thing that adjusts settings in the UserSettings.txt, so any change it makes should be visible directly after applying it. Specifically the Optimizer changes the graphics driver ro DX9, sets the resolution and fullscreen state, and disables frame smoothing. Nothing that even remotely sounds like it could cause blue haze, especially not the second time after the changes are made.
Completely random guess: sometimes positional tracking can cause odd artifacts, so disabling that may be worth a try. Haven’t heard of anything like this in regard to ESO though.
It’s on the nice-to-have-list, but without a date set. Realistically not something you can expect before the consumer Rift release.
Windows 10 is the main dev platform since shortly after it was relased and is also used widely by users. Not all but many of the games in your list have been at least shortly tested here since then. OpenGL support (Amnesia, Penumbra) was even almost entirely developed on Windows 10.
More importantly: the hooking mechanism hasn’t changed at all since 0.8. vorpX 0.9 hooks into games the exact same that vorpX 0.8 did.
To prevent vorpX from updating, you can disallow internet access for vorpControl.exe using your firewall.
You will need the Oculus runtime 0.7/0.8 for vorpX 0.9, no way around that. Earlier runtimes are already more or less obsolete and will soon be entirely forgotten. It’s impossible to support older versions of the runtime, sorry.
Regarding Direct To HMD: personally I’m not too happy with the direct to hmd only decision either. It surely has many advantages in regard to easier setup, but there also are a few technical drawbacks, especially in regard to Non-DX11 games. So it would have been nice to still have extended mode as fallback.
Star Citzen never has been officially supported by vorpX and won’t while it is in alpha.
It *may* work again normally at some point in the future, until then you can use the desktop viewer like described above.
Issues like these most of the time are caused by conflicts between vorpX and other programs that also try to hook into games. A lot of programs do this, not all of them are obvious unfortunately. Typical candidates are virus scanners, graphics driver add-ons (e.g. MSI Afterburner), many chat programs (which display notifications in games), video recording and streaming apps etc. The trouble shooting guide in the help lists the most ususal types of programs that may cause such issues.
If the game allows you to look around with a gamepad thumbstick, you can configure the head tracking as gamepad axis in the vorpX ingame menu and then change the ingame gamepad binding accordingly. In many Codemasters recing games this allows you to get head tracking working (quite laggy usually though).
Another workaround would be to play in Virtual Cinema Mode (ambience scene) and then move the screen closer until the image fills the whole view. That doesn’t give real headtracking, but works surprisingly well for racing games od all kinds.
Just a guess: did you activate the DX9 renderer (required for proper 3D)? Normally the Game Optimizer should take care of that, but it may fail in some cases.
To do it manually, locate your UserSettings.txt and change
SET GraphicsDriver.7 “D3D11” to SET GraphicsDriver.7 “D3D9”
The UserSettings.txt file is located at [Documents]\Elder Scrolls Online\liveeu
“liveeu” may also be just “live”, “liveus” or maybe something else depending on your location.
That looks quite normal. The desktop viewer opens an invisible window which displays as black in the taskbar preview. So nothing wrong with this screenshot.
Are you by any chance have multiple monitors connected? That might cause an issue. Also please check for any programs that hook into games similar to vorpX. The trouble shooting guide in the help has a few hints in this regard.
Judging from your forum registration mail address you should have received your key in the meantime. if not, please report back here.
Please guys. I wasn’t sure whether this is serious or not, so I left it open in case someone wants to add something useful. Otherwise it’s probably better not to comment.
Will be fixed in the next version. Sorry for mentioning the date which unfortunately will be missed. As always in software development, giving dates can be a bit problematic. The issue is fixed in the latest internal build, and you will be able to play rFactor 2 again with vorpX when the next version is released.