Forum Replies Created
-
Posts
-
Still no fix on this yet in the latest version (.9.1) – looks like DK1 will not be getting anymore support as ralf has not had any luck fixing it – so DK1 you will have to use older versions of VorpX (.5 I think is the one I got working)
It definitely occurs when VorpX hooks and is swapping eyes.
That’s a shame :( Guess will have to uninstall and wait til next year til I can get the CV1.
Thanks for your help though.
Hi Ralf, have you fixed the eye swap issue on the DK1 at all? or will you be abandoning the DK1 completely?
Hi Guys – It is a problem with VorpX and the DK1 (Ralf is working on it)
We have to wait til the next update to correct this, in the mean time roll back to an older version (of VorpX) until it is corrected.
Changing about your SDK or runtimes wont have any effect
Hey Abowling,
So far it looks as though we need an update on VorpX to get it working with DK1 – as its swapping left and right eye for some reason.
Though I myself have not had much luck getting this to work on DK1, the level of communication from the developer (here and on reddit) has been amazing.
I wish more developers were this active and helpful.
Not even close to being able to focus unfortunately – your on a DK2 right?
DK1, It’s definitely flipped right and left eye.
DK2, everything as it should be.
Appreciate all the help guys, Ralf – thanks again, your support is great – once there is an update will let you know if it corrects things as I think it’s there that the issue is happening when it’s hooking in via VorpX as it seems to be only isolated to VorpX.
again keep up the good work, you guys are doing a stellar job.
It’s very weird – almost like its negative IPD (is that even possible?) as left eye is right eye and the right eye is where the left eye should be.
All of the apps/demos etc all work as they should, anything hooking with VorpX is whats doing the problem.
Kind of wishing left at least one machine here on windows 7.
LOL – just realised we are having this exact discussion on reddit.
*Ralf – Windows 10, so I am stuck with .7 or .8 – the older versions (below .7) give me a boot loop and just don’t work with windows 10.
I know some people have had luck with getting it work but not me (this could be because I did not perform an upgrade and did a fresh install).
I rolled it back to .7 still same problems as .8.
with the DK2 – I have not had any problems whatsoever, same hardware in both machines. AMD 15.10 beta drivers on both – the only difference is the RAM.
have swapped both over and tested both but yeah same problem happening on DK1 – just a hea
*Castane – I have had a look at the Netserver.cfg – it looks like this.
{ “LoggingMask”: 256, “RSWakeupMins”: 5, “DebugHMDType”: 3, “DK1LensSeparationOverride”: 0, “LowerReportIntervalWhileIdle”: true, “DK2LensSeparationOverride”: 0, “HASWLastDisplayedTime:default”: 1445138985, “HardwareCollectionLevel”: 65535, “AllowFirmwareMismatch”: false }
I have heard some people setting theirs back to Zero has fixed or alleviated the issue (myself I have not changed it).
Ah yeah, sorry – I just now twigged what you meant.
Likewise – After upgrading to win10 and now VorpX .9 – not having much luck with my VR experience (except for the few games suporting .7/.8 runtime)
Hopefully an update rolls through soon.
I have had no luck getting the earlier runtimes working on win10 as they lock my PC into a boot loop.
hit Del and middle mouse button – hold one eye closed.
you should be able to use the keyboard now to navigate through the menus to be able to output to your screen as well.
bit of a pain (the image swap) and it seems to do it on everything atm with Vorpx (leaving it unusable for me).
I am getting the exact same issues a above.
DK1, .9 with AMD 5.10 beta drivers.
All apps and occulus config files work correctly with no issue – but anything VorpX (once it hooks) gives me eye swap from the looks of it.
Exactly like this: http://puu.sh/kV4Cv/4e1d7d84fe.jpg
