I have noticed unfortunately that UDK support by the Oculus team seems to be largely lacking; It is rather disconcerting. There have still been no updates for the Oculus UDK build and despite repeat attempts to receive updates to the licensing issues for the 3rd party addons, we have none. I am aware that the majority of new developers lean towards unity for it's ease of use, but many of us here consider UDK as the toolkit of choice for bringing our ideas to life. Could we please receive some more support and perhaps a somewhat regular(ish) update or two on the UDK side of things? It is after all [UDK support] one of the reasons that many of us have chosen the Oculus Rift as a development platform. Thanks guys. :)Edit: The 'thanks guys' above was genuine (as in, I appreciate the help), I just looked at it again and realized it may be taken sardonically given the posts content and I never intended it as such, so I edited in a smiley face so the tone is correct. Is there nobody on these forums using UDK who agrees with me on any of this?

I would agree that the lack of updates is a bit frustrating.I don't want to come across as some whiner looking for everyone to fix my problems. I did buy a Rift specifically because of UDK integration, however, and I'm annoyed that it doesn't work properly and that it basically breaks UDK. My game relies heavily on Scaleform and because Scaleform doesn't work, I basically cannot use the Rift version of UDK.So, I'm not asking for the Rift team to simply fix everything. But an update would be great. Some form of acknowledgement that hey, the UDK version is broken and that it is getting fixed as soon as possible. A general time frame. Something along those lines.I spent over $300 for a product with the expectation of it working. I'd like for their to be some accountability. I know that Oculus isn't responsible for releasing UDK, so why not offer Rift integration as a UDK plugin - just copy and paste into your UDK directory - instead of releasing a special version?Ultimately, I'd just like a response from someone on the team that something is going on and that our investment in their technology is actually appreciated and our needs are being considered.

@BenNadler, I know your post isn't only for me but I appreciate it nonetheless; I was beginning to feel somewhat alone in this whole thing even though I know that many others are hoping for proper UDK support as well. I don't think of it as whining, we were told there would be native UDK integration and it was cited as one of the main selling points of the DevKit. One of the greatest things about UDK is it's 3rd party implementations and although the core features are still there it does feel somewhat 'broken' if those other features are unable to be used. I am also curious as to why Oculus doesn't make the Rift SDK implementation a plugin, rather than trying to base an entire build with the Rift in mind if they can't do it successfully due to licensing constraints.It feels as though this thread and UDK related requests are being largely ignored by Oculus support. Perhaps I am just impatient, or perhaps my recent 'pushiness' to have a Canadian batch of Rifts delivered has put me and my requests in the proverbial 'doghouse' effectively leaving those who stand by me to wallow in my filth collectively. :lol:(Just kidding really, I am sure that at least cybereality knows it isn't personal and I do what I do only to keep momentum flowing in the directions most beneficial to myself and those in a similar position. I Love Oculus just as much as anybody else here!) So hey cyber, can we please have an informative update on all of this UDK stuff and perhaps discuss the direction that UDK support may be going in the future? Thanks in advance. :)

I'm also checking 2-3 times per day for UDK fixes and being disappointed every time...

@HappyHimitsu - yes, that's pretty much it.My biggest frustration is with the lack of information. For example, on the Scaleform thread, cyber mentioned that they are looking into it and that was all they had to say at the time. That's not really a fair way to position what is going on to your customers. No time frame, no recognition of the issue at hand, no explanation of what exactly they are looking into or how they plan on going about fixing it. It's the most vague statement possible, and it's really frustrating to have paid this much money as an indie dev - where every dollar counts, might I add - to be disregarded in this way. $300 would cover both my UDK and Steam Greenlight fees, and more. I made a big investment in Oculus because I think it would not only help my game be even better, but will help elevate a lot of other gaming experiences. I still believe that, but there is only so much I'm willing to take as a consumer. One could argue this counts as a form of false advertising, considering we were promised a functional dev kit and were delivered nothing of the sort. This should have taken a couple weeks to figure out, not MONTHS. I'm very, very disappointed.When someone gives me money for something, I go above and beyond what is expected to make sure they feel they have gotten their moneys worth. I don't feel like we're being treated very professionally at the moment.There hasn't been an update regarding the issues around BIK, Scaleform and SpeedTree in some time. A lot of other UDK functionality remains somewhat broken. We need answers.

While I agree with you BenNader, let's wait to see what Oculus says about the matter this time. They are still a growing team and I would imagine they have a heck of a lot to keep them busy, hopefully our posts here will help spur them into action. I am unsure if you have read through many of my more outspoken posts on this thread, but I am a firm proponent to the rule that if a company promises something and fails to deliver, escalate the situation until they listen. I have personally directed 2 other software companies in the past to action by rallying together a substantial percentage of their user base to speak out publicly about what they [the consumer] believed was owed to them by the company; I made a few enemies in the process but at the end of it all everybody was happy that things had gone the way they did, because their software finally delivered and they discovered how much better it was dealing with thousands of happy customers, rather than pissed off ones. :D I have also had various 'unfair' fees waived in my dealings with UPS, my service provider, my phone company and numerous other businesses that [erroneously] thought they could get a hand up on me by virtue of their size and position.I have no problems putting myself out there and 'taking one for the team' if it gets things done, I also have no problems dragging myself through the mud if that is what it takes to get people to listen.That being said I in no way think that Oculus is that far gone, I just wanted to give an [anecdotal] illustration that it is indeed very much within the consumers power to help maneuver a 'stubborn' company to motion (many consumers believe they are 'helpless' at the hands of the businesses). I believe Oculus are a great team full of good people and they are most likely spread a little thin, and I am sure we will hear some form of reply by tomorrow at the latest; Cyber hasn't posted since Friday so I would imagine he has taken the weekend off, he deserves it!The UDK issue does need resolution. It was Oculus that put such an expectation there in the first place, and those of us using UDK have reason to complain about the lack of updates in it's regard. We made a $300 purchase ($360 CAD in my case with shipping) with the expectation that we would have a fully functioning UDK integration, and escalating the matter until it has been resolved may be our only effective course of action.It has been 6 weeks and we are still behind in the SDK whereas Unity was updated almost right away; and vague answers such as 'we are looking into it' are not going to quell the issue any longer.Come on Oculus. Let's get the UDK Love that you promised and help us UDK devs to make the great content that sells your devices!! :)Edit: It just came to my attention via a friendly PM that perhaps the lack of UDK support is due to the tragic passing of Mr. Reisse. If that is the case then please let us know, as I am sure we will be more than accommodating in regards to such heartbreaking circumstances. Thank You.

Lack of UDK support. | Meta Community Forums

50 Replies

Replies have been turned off for this discussion

Thoth_The3x
MHCP Partner
12 years ago
"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 :)
Anonymous
12 years ago
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
Teddy0k
Explorer
12 years ago
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!
AnotherAtreyu
Expert Protege
12 years ago
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. :)
BlackFang
Honored Guest
12 years ago
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.
boone188
Honored Guest
12 years ago
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.
AgentElrond
Honored Guest
12 years ago
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. :)
OlivierJT
Explorer
12 years ago
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 !
DrSnake
Protege
12 years ago
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.
AnotherAtreyu
Expert Protege
12 years ago
"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.

Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨

Lack of UDK support.

50 Replies

Quick Links

Other Meta Support

Related Content

Quest App Lab rejected due to lack of hand tracking support

Lack of support

Need Support

Support Hours

Contacting Meta Quest Support & Collecting Logs