Forum Replies Created
-
AuthorPosts
-
RalfKeymasterYou can activate a single license on two of your own machines. Normally that is meant for desktop/laptop use, but since both machines are yours, this would also apply in your case.
RalfKeymasterI also read widely varying comparisons. My conclusion was that in the end it depends on various factors like system, detail settings and also location in the game world. A 1:1 performance comparison is next to impossible since the detail presets don’t mean the same thing. Also the SE generally has a higher draw distance, grass/clutter are more dense and there are additional effects like volumetric lighting and ambient occlusion. So essentially there is no way to compare both versions with exactly the same workload.
The best course of action is probably checking both. My personal choice would be the original since I like the old color scheme better and G3D performance was also better in tests here, but others may just as well come to the exact opposite conclusion for their taste and setup.
RalfKeymasterIf you see bars at the top and/or bottom, you need to set the Image Zoom value to 1.0 and the aspect ratio mode to “Pixel 1:1” on the image page of the ingame menu. That also requires a high enough field of view (120° horizontal for Vive), otherwise the image will look distorted.
The image is perfectly centered vertically, i.e. you look exactly at the camera center. The bottom bar is larger than the top bar because the Vive uses a slightly asymetric view to account for the human eye being better at looking downwards than upwards. A neat trick that both the Vive and the Oculus CV1 use to gain a few extra pixels where it counts most.
How the FOV can be adjusted varies from game to game. For some games you can do it directly in the game options, for others the vorpX Game Optimizer in the config app can do it or you need an external tool like Flawless Widwscreen . And if absolutely no other option exists, you may have to use a workaround that may involve visible top/bottom bars.
You can find a full list of options you have in this regard in the Essential Hints Guide in the vorpX help, which also explains a few other basics that are worth to read before starting with vorpX.
RalfKeymasterYou can change the button mapping on the gamepad page of the vorpX ingame menu.
BTW: the next vorpX will have a feature that allows native gamepad use in more games that currently do not allow that. I haven’t checked the Special Edition yet, but so far it worked for all Bethesda RPGs, so it’s quite likely that it will also work for the Special Edition.
RalfKeymasterThis doesn’t really have a positive effect when using vorpX. vorpX already supersamples the final image that is sent to the headset. Adding an additional multiplier on top of that only has a small effect on image quality (if at all), and depending on the factor chosen leads to excessively large final eye render textures (up to 6000×8000 per eye).
What does have a profound effect on image quality is running games at a higher resolution. The default suggestion of 1280×1024 is a compromise between quality and performance. 1920×1440 would roughly result in the same quality as native apps, resolutions above that would be supersampled resolutions.
Just keep an eye on performance when changing the game resolution (ALT+F), 45fps+ (game) should be maintained for a comfortable experience.
RalfKeymasterRight now I don’t really have a clear idea about how these games work, but that sounds interesting. I’ll check out Resident Evil 5, and if aiming with the controllers is straight forward to implement, I will definitely consider it. Probably not for the next update, but after that.
RalfKeymasterThe FOVE will likely work out of the box. If I understand it correctly, it works with SteamVR, so it should work with the vorpX configuration for Vive similar to other headsets that use SteamVR.
All headset specific parameters that are used by vorpX like screen resolution for example are read from the runtime, so provided the FOVE sends the right values through the runtime (which almost certainly it does), it should just work.
Whether vorpX may be able to utilize eye tracking in any way remains to be seen. One potential use would be controlling some parameters of the adaptive Z3D algorithm, but that’s just an idea, nothing more.
RalfKeymasterThe next update introduces a new feature that requires additional profiles in itself, which currently are done for about 30 games. Although not its main purpose that will allow Z3D pos tracking for *some* (emphasis on *some*) games.
One of these is Fallout 4 and I can’t help but say that in a game like FO4, that needs every bit of performance, this is a huge win. In practice that means that using Z3D outside where it usually works really well and G3D in interiors is now the best of both worlds without really missing anything anywhere. I dare say maybe even for some of you who really don’t like it until now.
Once all that is done, focus will shift to new 3D profiles.
RalfKeymasterSince you sent the request as screenshot, it had to be processed manually, which may cause delays. You should have received the key in the meantime. Let me know if it didn’t reach you.
To avoid such delays, please send key requests as plain text in the e-mail. This way the system can handle them automatically. You can copy and paste the request code from the dialog for that.
RalfKeymasterYour original idea should also work. The run option can be mapped to the left stick which normally should already be the case unless you changed the key assignment in the game.
The mapping option in the vorpX menu is called “Walk/Run Key”. Depending on whether autorun is enabled or not you may also have to enable “Invert Walk/Run” for that to work correctly. If configured this way, both speeds are mapped to the left stick.
RalfKeymasterDid you try an OpenGL profile? Some sim programs that I’m aware of are based on OpenGL. If the train sim is such a case and happens to use an older OpenGL version, the Quake or Quake 3 profiles might be worth a try. That’s just a guess though, I might be completely wrong here.
RalfKeymasterThe DX9 Skyrim profile won’t work since the Special Edition uses DX11.
There is a preliminary profile for the Special Edition that you can download from this post in the game settings sub forum.
Make sure to follow the instructions! It’s extremely important to run the included gamesettings.cmd, otherwise all you will see is a blurry mess.
RalfKeymasterAs you guessed there corrently is no answer to that question besides “when it’s done”. As soon as I have a pair of Touch controllers here, this will be looked into.
RalfKeymasterJust to be sure: by “dublicate mode” you mean the Direct Mode, yes?
If your Vive does not work in Direct Mode there is definitely something seriously wrong with your setup. I don’t really have any concrete suggestion for such a case unfortunately, since I never heard of Vive not working in direct mode so far.
Just a guess: are you using a laptop with an nVidia mobile GPU? Oculus headsets are incompatible with such laptops due to direct mode not working with them. Might be the same for Vive.
RalfKeymaster1. Please check whether you have “Oculus Rift DK2” selected in the vorpX config app.
2. Make sure that you use the right vorpX version for the runtime you have installed. If you use the latest Oculus Home software, you need the latest vorpX version, otherwise you will see exactly the error you see. Please reinstall vorpX using the web installer that you got when you purchased vorpX, just to be sure.
3. If the integrated graphics of your CPU is active make sure to disable it either in the Windows device manager or better your motherboard’s BIOS (if you are compfortable doing that) to avoid potential issues that can occur if games use another graphics card than the headset.
-
AuthorPosts
