Search Results for 'Rime'

[CaptainKoloth]

I’m been experimenting with VorpX for a bit now and I’m reasonably happy with it from a technical functionality perspective but I’m being driven kind of crazy by the “face gun” aiming in FPS games. I know there is a mod for GTA V that decouples aim and look; are there any other FPSs that do this? Aiming with my head just isn’t working for me.

[Ralf]

Did you try the No Man’s Sky profile from here? That should work by simply importing it into the profile list in the config app.

Your issue sounds more like an injection conflict though, especially OpenGL games like NMS shouldn’t cause problems otherwise, since in contrast to D3D vorpX’s OpenGL injection is not time critical.

Please double and triple check for any potential programs that may also hook into games. Some virus scanners do not allow their users to fully disable them. If you use something like BitDefender, Webroot or Comodo for example, temporarily uninstalling might be worth a try.

Also check for video recording software (e.g. nVidia Shadowplay from Geforce Experience), any GPU/CPU utility and chat programs that can show notifications in games.

Ideally shut down everything that is not required. If that helps, you can easily find the offending program later.

If you can’t solve the problem, please create a trouble shoot data archive in the config app and send it to support |at| vorpx com. I can’t make promises, but I will look into the list of programs you have running and check whether you maybe overlooked something.

[SRBorick]

Doing a bit of experimenting…

Tried Optimizing Arma III and got the following vorpx Config error msg:

Writing config file failed:

The ArmaA3.cfg file is where it’s suppose to be, but vorpX isn’t able to write to it. Checked Properties and there is no indication that the .cfg file is write protected.

[Ralf]

Here is an experimental profile for No Man’s Sky. Simply drag and drop the file into the local profiles list in the vorpX config app. Be aware that with a minimum specs GPU performance won’t be too great with 3D enabled.

Important Hints:

1. The profile uses a low ImageZoom value to compensate for the FOV, 16:9 resolutions minimize bars caused by that (1680×1050 was used here).
2. Set the FOV in the game’s graphics options to 100 (the max. value).
3. Set all quality related graphics options to “Low” for better performance.
4. Set the “Max FPS” option in the game’s graphics options to “Max”.

FOV still isn’t quite right this way. You can enhance it with the 3D FOV Enhancement in the vorpX menu. Be aware that this will cause various glitches though.

Might also be worth a try to disable 3D completely which runs a lot better.

Download: No Man’s Sky (experimental).vpp

Optional: FOV-adjustment for full immersion:

Below you find a preconfigured ini file that raises the FOV above what is possible in the game and sets the resolution to 1280×1024 to regain some performance lost by doing that. 16:9 resolutions like mentioned above aren’t required with a higher FOV.

1. Browse to your [No Man’s Sky Folder]\Binaries\SETTINGS\” folder. For Steam the install folder usually is [Steam]\steamapps\common\No Man’s Sky, for GOG [GOG Game Folder]\No Man’s Sky
2. Replace TKGRAPHICSSETTINGS.MXML with the one below. Make a backup!
3. Optionally write protect the file to prevent the game from resetting values.
4. Raise the Image Zoom in the vorpX menu to match the higher FOV and reduce the bars around the image: ~0.6 slightly depending on your headset.

Download preconfigured ini: TKGRAPHICSSETTINGS.MXML

[Ralf]

Not sure whether that will help with your cursor key issue, but I did an experimental profile that should largely work out of the box. Not ideal, but full Geometry 3D. Make sure to read the hints in the linked post.

http://www.vorpx.com/forums/topic/no-mans-sky-support/#post-110244

[Ralf]

I’m not sure yet whether there will be an official profile since the game has quite a few issues ranging from not so great performance to low FOV. It’s also an OpenGL game, which makes it quite a surprise that it works in 3D, Geometry 3D normally doesn’t for newer OpenGL versions.

Here is an experimental profile though. Simply drag and drop the file into the local profiles list in the vorpX config app.

Important Hints:

1. The profile uses a low ImageZoom value to compensate for the FOV, 16:9 resolutions minimize bars caused by that (1680×1050 was used here).
2. Set the FOV in the game’s graphics options to 100 (the max. value).
3. Set all quality related options in the game to “Low” for better performance.
4. Set the “Max FPS” option in the game’s graphics options to “Max”.

FOV still isn’t quite right this way. You can enhance it with the 3D FOV Enhancement in the vorpX menu. Be aware that this will cause various glitches though.

Might also be worth a try to disable 3D completely which runs a lot better.

Download: No Man’s Sky (experimental).vpp

Optional: FOV-adjustment for full immersion:

Below you find a preconfigured ini file that raises the FOV above what is possible in the game and sets the resolution to 1280×1024 to regain some performance lost by doing that. 16:9 resolutions like mentioned above aren’t required with a higher FOV.

1. Browse to your [No Man’s Sky Folder]\Binaries\SETTINGS\” folder. For Steam the install folder usually is [Steam]\steamapps\common\No Man’s Sky, for GOG [GOG Game Folder]\No Man’s Sky
2. Replace TKGRAPHICSSETTINGS.MXML with the one below. Make a backup first!
3. Optionally write protect the file to prevent the game from resetting values.
4. Raise the Image Zoom in the vorpX menu to match the higher FOV and reduce the bars around the image. ~0.6 slightly depending on your headset should be OK.

Download preconfigured ini: TKGRAPHICSSETTINGS.MXML

[Ralf]

>> the Direct rate shows 89.6 with no fluctuation. Could this be a bug
>> between vorpX and the new Nvidia drivers?

That’s how it’s supposed to be. On Vive the Direct Mode frame rate should always be the headset’s refresh rate (90). A higher rate wouldn’t help and a lower will cause issues (flicker) on Vive.

The important one is the game frame rate. If you want, you can experiment with disabling Fluid Sync, which will allow the game frame rate to go higher than 45, but at the same time raises the burden on your GPU and may cause a worse experience than having Fluid Sync enabled. In general it’s better to leave it enabled on Vive unless you can reach something close to 90/90,

No need to worry about the missing 0.4 BTW , that’s just the counter not being entirely precise.

[Ralf]

The official recommendatation are 1280 (width) x 1024 (height).

There are mainly two reasons for recommending 4:3/5:4 aspect ratios:

1. They are available per default, so inexperienced users don’t need to add resolutions to Windows.
2. They provide a few extra pixels for vorpX’s async timewarp.

You can still experiment with other aspect ratios, of course. The performance gain usually isn’t worth the extra hassle campared to 5:4/4:3 though.

[maurice]

j ai résolu mon problème votre copier coller c’est faux il cree des espaces entre les parenthésés et l adresse mail.Il faut supprimer les espaces
je m’excuse de m être impatienté mais on se sent seul par moment
bonne nuit et merci

[Ralf]

You can remap gamepad buttons on the gamepad page of the vorpX ingame menu.

Alternatively you can enable the *experimental* Direct Head Tracking on the head tracking page of the ingame menu, which currently is avalilable for Skyrim and Fallout 4. This enables native gamepad support. Be aware though that this is truly experimental. It might or might not work on your PC.

[lipplog]

Thanks Ralf! I’ll be doing some experimenting.

[Ralf]

That is a more complex issue than you probably think (and I originally thought too). vorpX actually had the ability to change the vertical position of the image in the first CV1 specific release to help with a certain feature of the CV1 optics. There is a severe drawback when doing this though that makes it *very* *absolutely* *completely* useless: since your eyes aren’t centered at the perspective center of the rendered image anymore, you get heavy perspective distortion when you rotate your head. So this was removed again after a short experimentation phase.

Whatever issue you may want to solve with such a feature, unfortunately it won’t work because of the distortion it introduces.

[Ralf]

The sync options are related to how the actual game render thread and the direct mode render thread, which does async timewarp and sends the final image to the headset, work together.

In the majority of games “Fast” or “Safer” will cause issues like dropped frames and other even more undesirable artifacts. There are a few exceptions, so you may experiment. But only “Safe” ensures that everything is synced correctly at any time.

[kandor]

Hi everyone

I noticed something very interesting today while I was setting up CSGO with vorpx

The game play has been so so, without vorpx running I get about 250-290fps / s on max settings in 2560×1080 resolution
As soon as I run vorpx with geometry 3d it would go to a shitty framerate the game, even at low resolution like 960×1080

Anyway I was experimenting today with command line switches and saw there is -refresh setting

I set this to 90

Ohh my god, everything is as fluid as on regular monitor screen, could even run the game in full monitor resolution and it was going every bit as good as he monitor

As I can not run 90hz on my screen I need to run it in windowsed mode and not full screen

But this works perfectly, have not tried any other games but my guess is the results would be very similiar

We need to be able to control the refresh rate inside games to get full effect

Only issue I still have is that I get double crosshair in geometry 3d, everything else works perfect and I have gotten used to pretty much use the space between my crosshair as aiming point

Anyway hope this will help some people out

this might help people interested in CSGO

-w 1280 -h 1024 -novid -refresh 90 -windowed

I know max res I can get geometry 3d in is 1920×1080

Best,
Kandor

[Ai]

There has been some recent (backwards) movement on this with Linden Lab withdrawing their latest Oculus viewer… which did not work well at all, and was not as good as their earlier viewer for DK2/Oculus Runtimes before the CV1/1.3 versions. It did not support the Vive though anyway. See this blog post for a review and various links to the information sources…

http://blog.inf.ed.ac.uk/atate/2016/07/04/testing-second-life-oculus-rift-viewer-4-1-0-313313/

I was also wondering if anyone had 3experimented to see if VorpX will work with Second Life/OpenSim viewers like Firestorm? Is it even possible Ralf? Or would that be a no go?