jzer0

[jzer0]

With the rift I definitely get geometry reconstruction when compared to testing with the default profile. If I had a vive I could confirm whether this is hardware specific. Also since Tesla is not officially supported for g3d I’m surprised it works at all. Still can’t find a working config for everyone’s gone to the rapture, it doesn’t hook at all with alternative profiles, basic stereo output only. I may pick up a vive, especially if the damn CV1 gets delayed again. Can’t believe people are getting their vives before day 1 cv1 preorders. anyway, all I can recommend it to keep messing around with different profiles, may find something that works. Best of luck.

[jzer0]

Sorry for the wait on a reply. The profile I used was from Bioshock, and getting it working is a little tricky. I’ve installed the latest Oculus stuff, so even though the DK2 is unsupported it still loads starts up its own interface in the rift display. The steps I follow are:

– start Oculus software
– start vorpx – will cause rift display to go to this loading grid screen, giving some warning about some crap.
– immediately start Tesla effect while the grid screen is up on the rift, and focus the pointer on the button to accept the warning.

maybe 1-2 tries out of 5 will get it to hook successfully, and you should have all of the same profile options as Bioshock is allowed. I was going to try to upload it to this cloud functionality thing, but vorpx just updated (yay) but seems I’ve lost the profile (boo). Anyway, best of luck. Thanks for the info on Tridef, tried that back when DK1 was out, didn’t know they were keeping it updated with the oculus software changes. I’ll have to check it out.

[jzer0]

Understood Ralph, thank you for your reply and clarification. Yes, G3D is definitely a resource beast. Even the native Oculus rendering hiccups when testing in UE4 and Unity under certain conditions, so I know that this is probably not going to run perfectly until after a few generations of both the hardware and software.

As far as immunity goes, not so much an immunity as it is a long developed tolerance. DK1 and the old software was like having your eyes drilled. Everything has improved 1000% since then, and a super beefy rig can just about handle the load now if things are configured just right.

Anyway, thanks again, this product rocks, keep up the good work!

[jzer0]

Yes, two are available in the dropdown in extended mode, but i usually output only to the rift due to refresh rate issues. Turns out this is due to latest nvidia drivers (anything higher than 350.12). while skyrim is ok with these it turns out fallout is not, tried every trick I could find with no result. after finding multiple reports of the newer drivers causing problems, clean installed the nvidia 350.12 drivers and everything loaded up fine with oculus 0.6.0.1 runtime, but now getting some random in-game crashes. maybe will drop back to 0.5.0.1 and see how this runs. thanks for your help Ralf.

[jzer0]

hi Ralf,

thanks for your reply. tried this, made sure as when set to extended and output only to the rift, there is only one adapter available in the dropdown. set to fullscreen 1080p. keeps freezing, switching back and forth from the game to desktop. rolled back oculus drivers to 0.5.0.1, going to try rolling back nvidia drivers next…

[jzer0]

Wondering if there was any update on this. running 0.8.1, Fallout 3 with no mods as well as trying with the recommended mods for vorpx use (unofficial patch, etc) crashing on startup. No ENB, tried all suggestions, compatibility mode, etc. Music plays, vorpx is putting out in stereo, but the screen loading is extremely slow, input non-responsive. Had it almost working once in windowed mode, but couldn’t get it to happen again when using fake_fullscreen or other workarounds. plays works fine when vorpx is turned off, other games (i.e. skyrim) playing fine with/without vorpx. Oculus utility version 0.6.0.1.

[jzer0]

wooooooooooo hooooooooo!!!!!! Ralf and team Vorpx rocks!!!

[jzer0]

:)

[jzer0]

just checking if the update will be available today, figured this would be better that starting up vorpx every few min. please don’t rush, just checking.

[jzer0]

just to update, rebooting got my camera working again, apologies for jumping the gun reporting this. i guess everything is still a little unstable. gotta say, when it works, skyrim definitely rocks. very much looking forward to more games enabled for geometry/positional tracking.

[jzer0]

HAA HAAAAA!!! RALF YOU GLORIOUS BASTARD!!!!!! Ambient Occlusion was it!!!! Thanks so much, works like a dream now. You’ve made me the happiest boy in all of skyrim.

[jzer0]

Hi,

First just would like to thank Ralf and his efforts, OVR should be kissing your ass for expanding their product’s software library to such a degree.

Now that I’ve kissed a little ass, would ask if there might be a solution to my skyrim problem with head tracking and geometry mode. Only in geometry mode I get this flickering on all of the ground and wall textures whenever there is movement. I have tried all of the following:

– graphics drivers fully updated
– rift extended mode, set to display only on this screen
– various skyrim.ini configurations (deferredShadows, turn off shadows completely, etc)
– happens on a clean skyrim install as well as when modded

I also had this behavior when using Geometry mode with the old vorpx versions and skyrim on DK1. Setting to Adaptive or other modes gets rid of this completely. Unfortunately this also does not allow for the good positional tracking, 3d is not as good. Everything else is running great, good framerate, just can’t resolve this geo mode flickering, last hurdle to full playability.

my rig:
core i7 4960 3.6ghz oc to 4ghz
32gb trident ram oc to 1.4ghz
asus nvidia gtx titan

side question: what determines which 3d modes are made available? is this hardcoded in the vorpx application somewhere or determined based on the target application’s directx implementation?

[Author]

Posts