Search Results for 'The Void'

[rirath]

Just another Vive owner wanting to mention that I’m looking forward to Vive support, and that I support the choices you’ve made. I know what to expect, and I’ll be buying as soon as the Vive support is available.

In my case, I have a weak stomach for most artificial motion, so I fully expect I’ll get most of my use from the Theater mode. Really looking forward to that, but I’ll give the 3D options a try as well.

Doing room scale in retroactively applied VR would result in you being able to walk through walls and cause a lot of other unwanted issues. The recommendation for all games will be playing seated.

Just for my own $0.02, I know there are a lot of issues to consider, but I’d be absolutely fine with being able to walk through walls. I think most of us roomscale guys know to avoid walking through them unless we basically want to noclip. :)

[alegse]

I have been playing Skyrim a lot with my DK2 (20+ hours) and I have switched my VORPX configuration quite a bit and I have found some things that can trade off but never be perfected. I have some thoughts and a question.

1) Z-fighting in skyrim engine. I can fix this with fneardistance=20-25 (from skyrim.ini) but this messes with the convergence. I can fix that problem with the focal offset but it never feels quite right. Not to mention this also makes huge hands problem worse and has clipping issues. So I guess I will just live with flickering mountains :/ Stereo Shadows are perfect and water is good but slightly odd in Geo3d. Sky looks fine but I notice the clouds don’t have proper convergence only at sunset and sunrise (night stars and daytime clouds are perfectly fine? I simply just avoid sunset so it works fine)

2)framerate. I have used z-depth a lot and found that it actually did not feel smooth even though the framerate was steady 37.5 (Half-refresh async time warp). It always had a bit of a single frame jump/jitter about once per 2-3 seconds and this was worse with full refresh rate.
In Geo 3d it feels a little smoother despite being only 25-30 fps (while the game frame-rate is stated as 75fps. Does this mean that vsync is stuck on despite the fact I disabled it in Nvidia control or is this normal???). Oddly my fps does not seem to change at all weather I set the graphics to very low, med or ultra … always the same 25-30fps outdoors (with no mods running). I believe this is because my video card is so good that graphics details have very little effect and my bottleneck is my cpu.

MY RIG
CPU Athlon x4 860K overclocked to 4.2 Ghz (8Gb DDR3)
GPU EVGA Geforce GTX 980

My main question is… Would a good intel CPU make a huge difference? Is it possible to get a smooth 37.5 or 75 fps in outdoor areas for skyrim or am I already pretty much maxed out already? Also any insight to why I may have the occasional frame jump/skip problem in the z-buffer mode or is this normal too?

[Grumdark]

I have the impression that since Oculus requires the use direct mode,in its last runtimes,injected games with Vorpx,have suffered a loss of performance.
Asincronous timewarp helps a little,but not sufficiently for fix the problem.
Direct mode is very comfortable for the user,but I think,has introduced a performance loss with injected games.

The only thing that has worked well for me,and has managed to alleviate this problem is to lower the internal resolution in games.

Curiously,since the compilation 0.7 / 0.8 runtime Oculus…
Vorpx supports the capacity to change internal resolutions,and therefore other type relations aspect in many games.
In part,this is very good to recover a percentage of gaming performance,avoiding rendering parts that were not visible through the lens,and they were being taken advantage of,and help with other problems Fov in some cases.

But in any case,I am concerned that there should be a performance problem from the obligation of direct modes…
I think that Ralf is aware of this problem,and is working to alleviate this,as far as possible.

This is only a personal opinion,based on my tests,and might change at any time due to possible improvements.
Regards.

[Ralf]

The automatic runtime install will not happen anymore in the future.

This was mainly done to avoid huge amounts of support requests during the Oculus runtime 0.x phase which frequently broke compatibilty with prior runtimes. It will be removed now that things are supposed to be more stable.

[Ralf]

Sorry. The installer does a safety check to avoid things like this, but apparently the registry key that stores the runtime version was removed (or changed) with 1.3, so this check always failed despite a newer version already being installed. One can only foresee so much…

Automatic runtime download is now disabled completely. So this isn’t an issue anymore.

[RagedElimanator]

I keep getting messages about how I gonna be blocked from program because I have installed it on too many pc’s but, that is not true. I have only one pc in my household that only belongs to to me and can run the oculus on it. So I have checks on the system when the system breaks then I have to reset it later. I have ONLY installed VorpX on this computer none other. What I ask is please remove those messages telling me the program will be voided because this program was a gift from my uncle and I honestly cannot buy this program as I don’t have a credit card or the money. After I got this program I actually read all your terms of use and agreements I must comply on.

[Ralf]

Avoiding any “ballpark-estimates”: as soon as possible.

[jhondidfool]

So, everything was fine until I updated to the newest nvidia drivers.
Then, for some reason, my Runtime decided it would not detect my DK2, so I reinstalled and fixed that issue.
Since then I’m getting BSOD about dxgmms2.sys ONLY when using Skyrim with VorpX.

I’ve tried everything I could think of, and it has not served any purpose; on the other hand, I have seen this library has been causing problems in Win 10 (The OS I use, Pro version) since as early as October, maybe before that.

10220 seems to be the Windows build that started it all, but I’ve had a newer version for a while and no problems until that point. “dxgmms2” standing for “DirectX Game Memory Maanagement Service 2”, and being such a widespread issue, one would think either MS would do something about it (they haven’t) or it would affect most games. Oddly enough, in my system, Skyrim + VorpX seems to be the only thing that triggers the BSOD. I can play Skyrim on screen and I can use VorpX with other games, even with FO4, which uses a more modern version of the same engine.

There is one fix, however, that has proven to work completely, and it is to install the last Win8 NV Drivers released before DX12 release. While this would be great if I didn’t use an OR, Runtime 0.8 needs a later version which, I have tested, still has the problem.

This clearly is MS’ fault, not Ralf’s, but, still, I’d like to ask you, Ralf, if you could take a look into it and possibly avoid calling this service since it has proven to be problematic.

Thanks.

[Ralf]

Did you check your spam folder? Anyways: please first try to run vorpX as admin. Should be avoided normally, but may help – for example if you are running Steam or your games as admin for some reason. In such a case vorpX would also require admin rights to hook into the games. There is an option to do this in the vorpX config app.

If that does not help and multiple games are not hooking in a similar manner, there indeed probably is a program on your PC that creates a conflict with vorpX by also hooking into games. Quite a few programs do this, not all are obvious. This may be a virus scanner, a graphics driver add-on (e.g. MSI Afterburner), a CPU tweaking utility, a chat program that can display notifications in games, a video streaming/recording program etc.

The trouble shooting guide in the help lists a few things to look out for. To be sure ideally disable/uninstall all background programs that wouldn’t be running on a fresh, unaltered Windows install.

[raron]

Thanks for replying!

Ah, okay. So no hope for a backwards compatible version, or a runtime version setting then?

I’m ofc aware it’s a prototype and all that, but not everything is updated to work with the latest drivers all the time. So it’s not really worth it to me to update the runtime just yet.

Except maybe to runtime 0.6.0.0 which I suspect works about the same as 0.5.0.1. (haven’t really gotten around to test it). But I have a feeling 0.6.0.1 onwards won’t work, not yet anyway, with the removal of extended desktop mode as I understand it.

My hope was to get Test Drive Unlimited 1 added to a few games I use with the Oculus (and possibly others with vorpX). Not sure about headtracking, I want to avoid using TrackIR at the same time and instead maybe use opentrack (not tried yet). Unless vorpX have some tricks.

Instead of just writing about it, I’ll try it soon :-) Hopefully, vorpX works with 0.6.0.0.

[Ralf]

Unfortunately the mail address you used to register here isn’t in our customer database, so I can’t really check what is going on.

If this hasn’t been resolved already, please make sure that your mail contains the request code that is displayed in the license dialog and also send the mail from the same mail address that you used for purchasing vorpX to avoid delays.

If both conditions are met, and you still did not receive your key, please report back here and/or contact us with a second mail address in case there is an issue with receiving mails from your normal address.

[Nex]

I finally built a powerful computer and am getting back into Rift experimentation. I installed VorpX 0.9.1 in conjunction with Rift SDK 0.8.0.

I then reviewed the official VorpX ‘supported games’ list and tried the first three games in my Steam library that are listed on the VorpX site. The results were disappointing.

– Gone Home: Rift will not come on at all.
– Metro 2033 Redux: Rift will not come on at all.
– HL2: Rift comes on and VorpX is enabled (but presumably worse experience than the native VR now included).

My question is, do the first two games listed above simply not work with VorpX? If not, why are they featured on the Supported Games list?

If 2/3 of the listed games I tried do not work on VorpX, how many others on that list should I avoid?

Otherwise, any suggestions on how to get the first two listed to work with VorpX?

Specs: Windows 10 64-bit, GTX 980 TI, 32GB RAM, Intel 4970k, SSD.

[Ralf]

vorpX requires game specific profiles for games to work in 3D.

Rainbow Six Siege does not have a profile yet, so no 3D as of now. The game is already bought and on the to-do list, so – if possible – a profile will be made available shortly. No promises though, as it hasn’t been tested yet.

You should however be able to play the game in 2D with head tracking normally even without a profile. To make head tracking work, please make sure that mouse input is working in the game. In some games you may have to disable the gamepad for that.

BTW: No double posts please to avoid forum clutter. Your other post containing the same question has been deleted. All future double posts will also get deleted.

[Sticklet]

No luck on un/reinstalling and deleting locals. Same problem.

Like I said, the Oculus official WorldSDK walk-around thing works and so does the demo scene so I’m completely confident the Rift itself is working and there’s no problems with connectivity or sync tracking.

Honestly in the end if there is absolutely nothing that can solve it I’ll try a fresh install but I would like to avoid that at all possible cost.

[Ralf]

Using a custom 8:9 or 1:1 resolution like described above is far superior as 1. no additional downsampling is involved, 2. it also solves FOV issues in many cases, and 3. it avoids rendering overhead, effectively enhancing performance.