Search Results for 'Get Even'

[malospam]

Let me first say that I can run all games made for the oculus in VR mode, my video card has the latest drivers, and also use it in testing games in Unity3d and the unreal engine 4. Also the oculus oculusConfigUtil shows the device is there. However when I try to run VorpX I get the error box saying: “he configured device was not found. Please make sure that you select the correct headset and that your headset is connected to your PC.” I’ve read through the forums and other websites trying to find where I am going wrong but I can’t seem to find away to get this to work. I know this is vague, but I am a bit depressed that I cannot get vorpx to even detect the dk2 oculus. I am even willing to pay if someone can get it to work. If someone could give me guidance, I would be so thankful.
Thanks and warm regards
Max Sal.

[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.

[BuckleBean]

Just want to bring to your attention that performance has massively tanked since the latest version of vorpx, especially when using DX11. Something may be amiss. I did a DX11 playthrough several months back using Z3D, running the game at 4k & was generally able to maintain 75fps. I booted it up today and saw that I was getting around 20-25fps, even at 1080p. I tried DX9 and performance was much better, but even at 1080p, it was dropping into the 60s. I know the latest update, bringing direct mode, comes at a cost, but this seems excessive. I haven’t seen anything like this anywhere else and thought it was worth sharing. I’ve already played through the game on the rift and it was incredible, so it’s no biggie for me, but I was wondering if anyone else had noticed this.

Specs:

GTX 980sc (slight further oc)
i5 2500k @ 4.4gHz
16GB ram
Win 10

[Sticklet]

The last restore point I have was just after the old VorpX/Oculus Runtime, so about a month ago – but I already know for a fact that that works because it was the last time I used it. I think 0.6/7 runtime and 0.7 VorpX.

The Oculus is detected and works, I can do the demo scene even now, but yeah every game just crashes – every 1/10 tries or so Fallout will just barely launch but it’ll just be on the desktop with nothing pointing to the fact it’s using the rift, and the headtracking light disappears once I get past the first few seconds of loading.

This is beyond frustrating ahaha, but I really don’t want to have to roll back my PC to a month beforehand only to have VorpX/Oculus automatically update and then be in the same situation but with a tonne of file loss.

I’ve uninstalled quite a lot of programs I don’t use from the point after I installed SteamVR since that was one of the last things I installed before not using the Rift for few weeks/a month but still doesn’t seem to want to work.

If there’s anything else you can recommend I’ll give it a shot.

[Ralf]

Renaming a game .exe is a hack and usually only works for games that use the same engine. If you know your game uses the Unreal 3 engine for example, you can rename the .exe to UDK.exe and it *might* work,

It does obviously not work for blindly renaming something to anything. It *may* work, but there never is a guarantee. There is a reason why vorpX has game specific profiles.

Even if it does work, you won’t get the game specific adjustments that usually are required for the best possible experience (dealing with shadows, reflections, fx etc.).

Rule of thumb: renaming can (but doesn’t have to) work for games that use the same engine. But even if it does work, it does not provide the same level of quality that individual profiles provide.

BTW: Please start using a language here that is appropriate for speaking publically. Makes reading and answering your posts more pleasent for everyone. If you want to be rude, this is the wrong place for you. Thanks.

[Sticklet]

This has been a bit frustrating.

I’ve only recently gotten VorpX to update and I’ve updated to 0.8 Runtime (the lack of extended desktop mode annoys me), but to the point. No games work.

The one’s I have tried specifically are GTA V and Fallout 4. But even games like Space Engineers doesn’t work, I get a black screen, headtracking light and the sounds of the menu in the background. GTA V and Fallout 4 crash immediately upon opening.

I verified my GTA V game files to have all of my OpenIV mods removed and still to no avail.

Here are things I’ve tried:

Reinstalling Oculus Runtime
Reinstalling VorpX
Verifying game cache
Removing ALL mods/ENB/ReShade/SweetFX files
Disabling AV/Uninstalling AV
Restarting PC after every update
Making sure Windows Update is up to date
Running the bare minimum processes – no media player, Chrome etc. basically just background tasks, the game, oculusconfig and VorpX

Sometimes game’s do start up and I’ll get to the intro, where it’ll be sound for about 3 seconds, then it crashes and says it’s stopped responding. That’s it.

If anyone has had similar problems and knows the workaround I would love to hear it, because I’m sitting on a $600 paperweight at this point.

[bji]

Thank you, that’s all I needed to know. Even if you don’t have an immediate answer to a question, it’s really helpful to provide even minimal feedback. If you had said, “We haven’t tested The Talos Principle recently, it may have broken, we’ll try testing it sometime in the next few days and get back to you”, that would have been sufficient. Anyway, thanks for your response.

[Tony Spaniels]

Im getting this now, black artifacts flickering on my right eye. Weird thing is that it started happening this evening but was fine this morning. Ambient occlusion is turned off already. Oh noes :(

Im not playing in Cinema mode though, z adaptive.

[NipOc]

The watcher was disabled and async rendering on.
I noticed that the framerate problem gets better, when I have vsync enabled an constant 60 fps. But I still have stutters and as soon as the framerate changes the Direct Mode FPS drop even lower than Game FPS.

I use the Desktop Viewer mostly with Tridef, for games that aren’t supported by vorpx yet or dont have a geometry 3D profile, so virtual cinema mode is not an option. (The problem still persists without Tridef)

[Ralf]

Async rendering should always be on. Turning it off actually causes a framerate loss, since all it does is synchronizing the two render threads to work one after the other, which makes things slower. The option is mainly meant for trouble shooting and should be left alone. Will probably get removed soon.

My assumption regarding your framerate issue is that vorpX probably also hooks into the game while you display it in the desktop viewer. Not sure how you even managed to do that :). Normally the desktop viewer should autmatically exit when vorpX hooks into a game.

The better way would be to launch the game without the desktop viewer and switch to Virtual Cinema Mode in the game. If for some reason you really want to play games in the desktop viewer, you have to disable the vorpX watcher (tray icon menu) after starting the desktop viewer.

[Contrabardus]

I’m running Windows 10 64 bit, latest AMD Catalyst Driver, and 0.8 OVR runtime. I’ve had VorpX since it launched and it’s always run fine until now. This latest update is absolutely refusing to do so.

I’ve uninstalled and reinstalled it at least fifteen times, and it refuses to launch after the install process finishes.

It goes through all the dialogue boxes without issue, all the bars fill up and I’m not getting any errors during the actual install. I get to the final screen that asks me if I want to start VorpX immediately, with “Finish” instead of “Next” on the button at the bottom of the box.

After that attempting to launch the program immediately freezes it up. It doesn’t matter if I try to launch it right away, or if I close the dialogue box, restart, and try to launch it separately.

I even went so far as to uninstall the registry stuff, but still no go. It installs everything, tries to launch when it’s finished, and then hangs immediately and stays that way.

I’m running Windows 10 64, I’ve got Oculus Runtime 0.8, and the latest stable AMD driver installed.

The Rift is running and the service is fine. It plays demos and works fine outside of this.

Going into task Manager after it hangs tells me that Setup/Uninstall is not responding.

Attempting to delete VorpX even after ending the hung task tells me that vorpControl.exe is the problem. It’s still being used by the system even after an uninstall and won’t delete. Restarting the computer lets me get rid of it.

I have restarted and run the uninstall program after that, and it gets rid of the file then.

If I let it install, restart, and then try to get it to launch, I just get an unending process that never shows up in task manager. I just get the spinning mouse cursor icon that tells me Windows is trying to do something indefinitely.

Attempting to uninstall VorpX in this state once again leaves vorpControl.exe behind and undeleteable until after a restart.

Something is massively screwed up here and I can no longer get VorpX to run at all. Not even with a completely fresh install.

I’ve tried everything, installing DirectX, putting it in a different directory, and nothing works.

Also, I’m on Windows 10, so reinstalling OVR 0610 isn’t really a viable option to correct this problem, especially with no guarantees it will accomplish anything. I know it’s technically possible for me to install that runtime, but it requires the installation of old drivers and running in compatibility mode, it’s not really an option here.

I have 0.5 installed and the runtime switch. Yes, I’ve tried removing that thinking that it might be getting in the way already. That isn’t the problem here. I’ve also tried hooking it on with the old runtime. None of that worked, so I’ve got no good reason to believe installing 0.6 again will either.

I’m at a bit of a loss here and this is very frustrating. I really wanted to try Fallout 4 in VR, and now I can’t play -anything- with VorpX because the new update has completely cocked itself up on my system and refuses to run.

Any ideas on how to fix this?

[gutang]

Hey man, Vorpx has its quirks and takes some effort to make the most of, but of all the third party 3D drivers it is by far the best available and requires the least amount of hassle. So in that regard I have to agree with OP.. Vorpx is the best and its gets better with every update.

Heack in only 6 hours I’m going to be enjoying fallout 4 is glorious virtual reality, even if its only z3d it will destroy the 2D monitor experience.

[marks]

Spent most of my weekend trying to resolve this issue. Nothing works with vorpx, all the native Rift apps are fine – it is nothing but black screens on vorpx (even the desktop view doesn’t work).

How does one get hold of the old vorpx (pre 0.7/0.8 SDK)?

[ears]

I’m getting a black screen here too. Windows 10 64 bit, Oculus 0.8.

Nothing at all works inside the DK2 – not even pressing delete to bring up the VorpX menu. Mouse control seems to have disappeared – I can see no mouse pointer anywhere.

This is on a pretty vanilla rFactor install – just installed today and only ran once or twice outside the Rift to make sure controls worked etc. Only one extra track – Oran Park – downloaded.

[marks]

I am getting an error in my Windows event logs
“11/07/15 02:01:49: Error: [FirmwareVersions] WARNING: Unable to load the firmware file. Version checking for device firmware will be disabled and will report that firmware data is “not found”.