After reading through the threads for a week before I received my DK2 I have seen thread after thread of problems, headaches and errors people are having with their DK2 ' S. Thankful there are also threads about how great it Is for those lucky or skilled enough to get it working.
I received my DK2 and have been trying to get it working with my Macbook Pro for hours upon hours last night. (I know, I am in the process of locking down specs to build my own PC for DK2/CV1 PC)
But seriously, not even one email or thread from Oculus letting Mac users know Mac wouldn't be supported?
Oh well, I guess ill just wait until I shell out another $1,200-$1,500 on a PC that will run the DK2, and even then, with all the bugs and problems I am worried that whatever processor or video card I select will somehow give me error telling me they are not compatible with my DK2 for some weird, technical reason.
Why Is DK2 littered with thousands of more problems than the DK1? This is supposed to be version 2. But It feels like a step backwards aa far as software and support.
Nicely worded Chaoss. I'm certainly no expert, but all of that made sense to me. I know there's nothing wrong with my rig and I know the sdk is working as I can run Tuscany and the demo scene perfectly, so it's the content people are making that's the issue and will no doubt take some time to get the hang of and figure out how to get the ideal performance. I love what Oculus has done with the sdk and how it works with the dk2. Now, we just need to figure out an easy way to get our content to properly work with it.
I am pretty sure I saw a post a week or 2 ago from one of the SDK developers specifically stating that the SDK will not work on a MAC, however, they are working on converting it so that it can be used.
And the DK1 was a PITFA to set up btw.
Current WIPs using Unreal Engine 4:Agrona - Tales of an Era: Medieval Fantasy MORPG
I cannot figure out how to update the firmware to make dk2 work. I got to the tools and to where it says firmware but when I go to "open" it flashes something in the background and then nothing.
"knutsi" wrote: I found it very easy to set up on my PC. The demo scene and OculusWorld demo worked much better than any DK1 content ever did. It was so easy that this could be like CV1 (plus maybe a first-run wizard) and people would manage.
(The point is that software made for SDK 0.4 is very user friendly due to the lack of extended/mirrored desktop, while all other software struggles because it was made for previous iterations of the SDK)
"andyr123" wrote: It wont work on any mac yet though - the SDK isnt available, correct ?
PC only at the moment.
Not that i can get mine to work on a PC either. The oculus device driver seems to conflict with my graphics driver.
See! That's what I'm scared of when I build my PC. You aren't the only person that's had graphics drivers problems. What kind of graphics card do you have?
"knutsi" wrote: I found it very easy to set up on my PC. The demo scene and OculusWorld demo worked much better than any DK1 content ever did. It was so easy that this could be like CV1 (plus maybe a first-run wizard) and people would manage.
(The point is that software made for SDK 0.4 is very user friendly due to the lack of extended/mirrored desktop, while all other software struggles because it was made for previous iterations of the SDK)
What kind of processor and graphics card do you have ?
