Forum Replies Created
-
Posts
-
No problem on the server side. Also no other reports like this so far.
Check whether something is blocking the config app from accessing the internet. Might be an overzealous AV scanner, your firewall, your router, your ISP, or just some general network hiccup somewhere.
You could also try to delete the clouduser.ini file in C:\Program Files\Animation Labs\vorpX and login manually again. Just for the unlikely case that the .ini file is somehow corrupted.
vorpX works perfectly file without cloud profiles BTW. All official profiles are already stored locally.
Checked it last week when I saw the thread, but couldn’t replicate the issue.
If you haven’t done so already, trying again with 18.3.1 is worth a shot. It contains a fix for a obscure D3D11 crash issue that happend semi randomly with Fallout 76. With some luck your Metro Redux issue might be the same.
Can’t really recommend anything besides switching the Touch controllers to gamepad mode. That will grant you either native X-Box gamepad support in games where vorpX doesn’t have to override the gamepad or channel the simulated gamepad through vorpX’s gamepad override.
vorpX 18.3.1 has been released. This is a maintenance release that mainly adds support for Fallout 76. The profile is a fully featured DirectVR profile with everything DirectVR can do in the best case including automatic resolution, FOV (two methods) and basic roomscale.
Additionally minor issues with the program itself and other profiles have been fixed.
In case anyone wonders: the Frostbite engine G3D support that sparked a bit of interest recently is still in development and will be made available with the next larger update 19.1.0 before the end of the year.
New profiles:
- Fallout 76: G3D/Z3D, full VR, DirectVR: head tracking, resolution, FOV, tweaks
Changes/Fixes
- Effects that look bad in VR (e.g. DOF blur) can also be disabled with Z3D.
- DirectVR scanner could time out with large scans in low memory situations.
- DirectVR menu page didn’t behave correctly if both memory scan FOV and .ini edit FOV are available.
- FOV scan was run despite .ini edit FOV being selected if both are available.
- Fixed an occasional G3D crash in Fallout 76 (and maybe other DX11 games).
- Arma III: DirectVR FOV was slightly too high.
- The Witcher 3: some objects were rendered at wrong depth.
- Crysis 3: reflections fixed, effect fixes.
- Fallout 4: minor gun decals and fire glitches fixed.
The next larger vorpX update in a month or so will come with a fully working OpenGL version for old CD-ROM builds. Rainy sunday last weekend…
The current BattleNet version used by most who still play the game regularly is DX9 though as far as I’m aware.
Do yourself a favor and wait for the official profile instead of spending time tweaking. That’s what I’m here for.
The official profile (available tomorrow) will have pretty much every possible DirectVR feature, and G3D of course.
Have mercy guys, pleeeaaase! I’d rather get the update/profile done instead of answering forum questions.
If you encounter anything that you consider not the way you want it to be, you can always turn on memory scanner FOV, which will also be available.
Hope that answers all questions in regard to FOV.
I can’t really answer these questions, sorry. If you want my personal opinion: would be rather odd to disallow .ini edits at a later point since they had years to decide that. The risk of using vorpX in online games is the same as it always was with any other game. I’m unaware of anything ever happening in the last five years. Obviously that is no guarantee for the future though.
What I can say is that I’ve been using vorpX with Fallout 76 for several hours now on multiple occasions during the beta and today with the release version. So far without any issues.
Just a heads-up that you will be able to play without using the memory scanner, FOV is now handled semi-officially via ini-edits. Works just as well.
Using the scanner still grants better head tracking, but there will be no need to use it for those who want to be on the safe side.
A minor vorpX update to version 18.3.1 including the completed profile will be made available tomorrow.
There is an issue with recent COD games before it even comes to 3D or not: some odd flicker that looks as if one or two times per second an older frame is displayed instead of the one that actually should be displayed.
Without this glitch there would be official profiles for recent COD games of course. Unfortunately it’s a tough one, resolving it might require an entirely different rendering approach than the one vorpX uses currently, which would consume a lot of time for just 2 or 3 games – with uncertain outcome. I have a few ideas, but so far there always have been more pressing matters on table.
There are many different iterations of the Forostbite engine, might make sense to try another profile as base profile.
I’ll take a closer look at more Frostbite games within the next weeks. No promises though.
‘Official’ tip: Quake 3, map: q3dm17. You probably won’t get more non-stop action anywhere (iron stomach highly recommended).
Crysis and Crysis 3 probably also fall in the non-stop action category. Crysis 3 will get a few fx fixes shortly, so worth to wait a few days. The Metro games might also fit, although I’m not 100% sure whether these really are pure shooters, never played far enough. Far better than its reputation is Aliens: Colonial Marines, absolutely worth a look.
If third person games in immersive screen mode also sound interesting, Vanquish and Bayonetta might be something. Maybe also Psychonauts.