Forum Replies Created
-
AuthorPosts
-
Jan 10, 2016 at 10:38am in reply to: So after the Oculus price drama, how's support for OSVR and Vive? #96251
first_emperorParticipantActually they do say that, a lot. Not saying you do, but they really do a lot.
If they had used (real) Full HD, non-plastic lenses etc from the start, sure it would have been more expensive. They did not, one of the reasons being that less developers and indies, which are very important, couldn’t have afforded or decided to get a dev-kit. I doubt we would have many demos and titles to try out VR, if it had been as expensiv as the CV.
Jan 9, 2016 at 3:50pm in reply to: So after the Oculus price drama, how's support for OSVR and Vive? #96219
first_emperorParticipantGlorified Oculus Rift… Imho it’s exactly the other way around and I have to facepalm everytime I read something of the like “The Vive is going to be better priced and more potent”. That’s just not informed, as Ralf said HTC themselves already said that they expect the Vive to be a lot more expensive than the DKs from the Rift and around the 1000 with the controllers and such. Don’t pin me on it since I can’t find the source anymore, but I found multiple where it has been stated that the Vive is going to be a premier VR experience and probable more expensive.
So I have no idea how so many get the impression or conclude that the Vive is going to be cheaper.
On the other hand I also feel like those that are outraged come from the time they didn’t have to afford their own hardware and stuff. Remember what the first Blu-Ray players cost? The first HD or 3D displays? Blu-Ray players were around what the Oculus CV1 costs now, mediocre displays that were outdated a few months later cost a couple of CV1s.
People should stop wishfull thinking and start see some perspective. A rather have an expensive first generation with good hardware that can convince people than a cheapskate version that disappoints. Because that would be the worst that could happen to VR.edit: Oh and also all the surprise that prototypes are cheaper than the finished version. *facepalm*
first_emperorParticipantedit: Although no stereo 3D is supported, renaming any exe didn’t work out either, since the updater fixed the chances immidiatly and you couldn’t start other than with the launcher.
first_emperorParticipantTried it out myself yesterday. At least with the current version it works just fine, starting from the launcher and doing the usual extended/primary workflow.
first_emperorParticipantHi Szabby, I know that I’m not Ralf and so far I didn’t try out any STALKER games with the DK2, however I wanted to try to help you, since the issue sounds very similar to what I experienced with Star Citizen.
Did you try to rename the exe so far? udk.exe seems to work wonders often, even though it’s mainly for unreal engine games. Still other games hook also.
I’ll just asume, that you tried everything from the troubleshoot post (setting Rift to extended view and make it primary etc).
Do you enforce anything in your graphics driver? Like Antialiasing for example? The Stalker Games always had issues with that in my experience, even though they never turned completly black for me. Try to set your drivers to default.Also try out starting Stalker and vorpx as admin.
You could test if Stalker hooked correctly, by starting it and then switching the Rift of, then you should see the at least the vorpx logo on your display.
first_emperorParticipantI finally managed to get it working again, still not sure of what the cause was or what fixed it, might have been an update on CIG, vorpx or even oculus side.
After playing around a bit I reproduced the issue however, and that was when I tried to rename the exe for 3D support. AC didn’t like the changes and I was back at the black screen. Changing the exe back to it’s normal name, fixed it now it works without any problems what so ever.Standard Workflow of setting Rift to Extended and Primary, then just start from the launcher. If the launcher asks for admin permission, you’ll have to set that in the VorpX config too.
My settings are pretty straight forward, but not perfect, might have to tweak a bit. Zoom down to 85% and Letterbox 1. Nothing else.
Now the most important thing however is, that if you want to be able to use “free look” and shoot, you just have to toggle the mouse aim type (default right shift) every time you respawn. Then you can look around freely and aim at the same time, which is great with gimbaled weapons and in general.
You might need to adjust the sensitivity, 0.16 works well for me.
first_emperorParticipantThanks for your guide, tried the same a lot of times before, it worked for some time but at one point it just stopped working. The loading screen and the menues do work, but the actual game itself stays black.
Do you have any suggestions? I tried all the standart things (disabling programs that could interfere, many variants to hook into the game etc).
Did you experience something like this too?
first_emperorParticipant
first_emperorParticipantBlöde Frage (sorry, dass ich das jetzt wirklich stelle), aber ist das Headset überall angeschlossen und eingeschalten? Das ist nämlich genau die Meldung die ich bekomme, wenn ich eben jenes vergessen habe.
first_emperorParticipantTry creating a vorpX shortcut for the game, that helps most of the times. Also make sure you’ve got the Rift in extended mode and as the primary monitor. No other programs should be running that can hook into a game, like fraps, xfire, sweetfx etc.
first_emperorParticipantIf you set it on the ignore list it won’t work, since vorpX will ignore it ;)
A few things you can try:
Try starting the launcher (maybe create a vorpX shortcut for it) and make sure that the Rift is in extended mode with the Rift as primary monitor (that usually does the trick).
Also what worked with Star Citizen once was to start the launcher normally and create a vorpX shortcut for the exe of the game itself (if the launcher is started, you might be able to access the game exe by hand).
Make sure you have no programms running that can show ingame overlays (xfire, overwolf, fraps etc) or sweetfc since this can cause complications or vorpX just won’t be able to hook.
first_emperorParticipantAbout your vorpx not running problem: I had that too, in my case it was an issue with the admin settings. If you set vorpX for Admin and the prompt doesn’t come, you need to restart vorpX manually. If the shortcut links to an exe that has admin privileges, vorpX needs them too. I also think I recall that it’s also the other way around, but I might be wrong.
Did you try to open the config after you got the message? I had an issue where the config would just crash after that message, only reinstalling vorpX fixed this for a few hook ups, than the same issue again. However this issue solved itself magically after some reinstalls Oo Uninstalling/reinstalling (without deleting license information) might have been the fix, instead of just running the setup again.
first_emperorParticipantHi Ralph,
I managed to fix it somehow or vorpX did it itself. Anyways vorpX is now stable again. Only thing to mention: When not using DK2 as primary and instead show on Rift option, black smearing is there and can’t be fixed.
On the negative side Star Citizen does not work anymore. VorpX Loads it as intended and the loading screen plus menues do so too, but whenever I’m actually in the render scene, everything is black (using the vorpX menue works).
Oct 5, 2014 at 11:52am in reply to: VorpX stops working -> reinstall -> works -> stops repeat #18406
first_emperorParticipantHey Ralph, first thing I tried, but it didn’t help. However I think I’m getting at least close to pushing down the frequency of that happening.
It might be, that the error message popping up is a bit confusing, because it’s not the actual problem (when the config isn’t crashing). Can’t say for sure yet, because the last times it popped up in the Rift in Extended mode, so it might have been a different one.
Anyways, I had it at a point, where even though I changed the config, which often caused that issue too, it didn’t crash. The error messages I was getting at that point where caused because set Adminmode in the options, but the Star Citizen EXE was not set to Admin Mode (SC Launcher is btw).I also have the suspicion that setting administrator mode and not restarting vorpX causes the issue. When you apply this, you don’t get the usual request for admin control. So you might want to add an automatic restart for one of the next versions or at least a pop up with the info that a restart is required.
@SC: When it works (and the cursor/menue doesn’t dissappear) it works pretty good. However it’s a pain in the ass to get it working since it’s still a lot of trial and error. I’m getting closer and once I have a workflow, I’ll add a thread about it.
first_emperorParticipantThanks Ralf, I was wondering about this too.
-
AuthorPosts
