well I got Fallout3 to work with dk2....using the tridef 3d it wasn't
built for dk2 support....but alas no head tracking....used my oculus as
the primary and set on this screen only.....so when hit the power button
it jumps to the occulus. and shuts ...
fallout 3 is working with the tridef 3d ignition drivers.....well done,
for 50 buckos I cant complain...only one problem I am having if I use my
360 controller it deactivates part of the oculus head tracking....the
yaw works but the look part is gone...
once i mapped for unreal way back with many a maps.........but now i am
designing a full map pack for Oculus......hopefully 20 maps.......since
i haven't received my oculus i cant dimension the maps yet....or set up
or game type.......newest ones wil...
my 660 worked fine....so I suspect your 680 will work.....then again I
just sold my dk2.....bought a house so very little time to use it, and
prefer someone else have fun with it....
just tried half life 2......very nice....very playable.....with the
graphics.....far better then the dk1.....the commercial version will
blow the socks off the consumer with 4k screens.....yep....still need a
smooth transaction about screen order set...
dk2 is a step up in improved graphics and head tracking then dk1....and
the consumer version can only benefit from the feedback of the dk2, if
they custom built a screen with the pixels prescrunched into the shape
of modified software view(saving pro...
I guess we will have to wait for tridef 3d to do a dk2 update....Fallout
3 looks great with the improved graphics the dk2 provides, just that the
head tracking is not working.
I just set the oculus as primary.....set it as screen 2 only.....then
power off oculus then the main screen comes on.and when I get a game
playing split on my main screen....I turn the oculus on and it turns off
the main and jumps to the oculus.