Lack of UDK support.

"cybereality" wrote:
Guys, I'm very sorry about this. We are aware of the issue, and are looking into it.

We will have an update soon with more details. Thanks.

Thanks for a response :)

Hey everyone,

Sorry for the delay -- I asked Cyber to let me respond to this post myself.

We haven't had an UDK update recently because the fixes/updates are taking longer than we expected. To be completely transparent, Andrew Reisse, who we lost in late May, was the lead programmer on the Oculus - UDK project. Andrew was a brilliant rendering engineer with almost a decade of Unreal knowledge and expertise. With Andrew's departure, our UDK plans were knocked us off our trajectory and since then, we've been working to get back on track.

That said, the team here is completely committed to the Oculus UDK. We believe the UDK is an awesome developer toolset and some of the best community projects have been developed using it. That's why we (with Andrew's leadership) worked with Epic to build the Oculus UDK in the first place. ;)

One of our best senior software engineers has stepped up and taken the reigns on everything Unreal, including the Oculus UDK, and he's getting up to speed on Unreal technology as quickly as he can. We're making great progress, but we still expect it to take us a few weeks (at the earliest) until we have something ready for release. We're actually searching for a great, lead Unreal developer to join us full time to takeover leadership. If you're interested in the role, please email us at careers@oculus.com!

To answer the question regarding the other middleware technologies: the original Oculus UDK build didn't include other 3rd party middleware because it was a collaboration directly with Epic -- the other middleware companies were not involved, so we didn't have permission to include their technology (it also helped us release it faster so developers could start working quickly). We've reached out to the other middleware studios, and we're in the process of integrating their tech to work with the Oculus SDK (stereo rendering, head tracking, etc...).

We'd like to have an update for UDK developers as soon as possible (with other middleware and a few of the feature requests), but we don't have an ETA yet. We'll let you know as soon as we have an update scheduled. It's coming though!

We really appreciate the community's patience. I'm sorry for the delay (and apparent lack of support). Thanks for bearing with us.

In the meantime, please don't hesitate to let us know if you have any questions or suggestions about the Oculus UDK. Let's make sure we get everyone's changes into the next release. We're here to help!

Thanks again,

-- Nate

Thanks for the response Nate, I'm sure you guys are doing the best you can. The current UDK version is working well enough to tide us over for a few weeks in my opinion!

Agreed. Thank You Nate, that update was like a warm fire bringing hope to a group of campers lost out in the snow.
My concerns have been laid to rest and the response from the Oculus team on the varying issues over the last week has been magnanimous in it's respect for your community.
It is sad to hear about Andrew, and I applaud all of your efforts for pushing on so hard in the face of such difficulties in his honor and for the benefit of all of your supporters.

Thank You again to both you and cybereality for keeping all of us informed with this great news, I will sleep happily tonight knowing I will be able to continue on with my passion in the way I originally intended; and I apologize for the extent of my negativity in some of my earlier posts on the matter.

Take care and Good luck. :)

I'm pretty handy with UDK, but haven't gotten my rift yet. I could probably read the data from the rift without too much trouble, but the rift render mode would be hard for me to replicate on my own in a newer UDK.

Nate,

It's great to see you getting your hands dirty in this thread, and adding some transparency to the situation. This is the kind of attention us devs love to get. It will be a lot easier to wait patiently for the changes now.

Thanks for the transparency Nate. Much appreciated. It is a lot easier to wait when you know the reason for what is going on, and that things are in motion. :)

Thank you for the update, I have been waiting for news like this for quite a while.
Glad you are still making it happens.
I look forward to that.
Merci !

Awesome, great to see UDK is still being processed. I mainly do the programming in UDK, so at this moment the bugs are not hindering me that much so i can still do my work, but yea love to see the integration get even better! Currently still working on Hydra integration after that ill take a shot at some of the bugs and see if i can figure something out in the meanwhile.

"DrSnake" wrote:
Awesome, great to see UDK is still being processed. I mainly do the programming in UDK, so at this moment the bugs are not hindering me that much so i can still do my work, but yea love to see the integration get even better! Currently still working on Hydra integration after that ill take a shot at some of the bugs and see if i can figure something out in the meanwhile.

It is great to know they are still working on a proper UDK build; It really wouldn't be right of them otherwise, they did tell us it would be there and they are making good on their word. :)

If it wasn't for hearing about the Oculus Rift I wouldn't have gotten as far as I have with learning about development, and if it wasn't for the announcement that there would be an official integration for UDK I wouldn't have gone down that route either.

I am very thankful we are part of such a fine community of enthusiasts and developers. Once I got my Rift and realized all the hype was true, the small issues we've been dealing with just seemed to melt away.
Now I am waiting for our UDK to get up to speed (I am still working on demos and testing in the mean time), and when it does I am going to make my (and hopefully your) dreams come true.