Oculus-ready UDK Now Available!

"cybereality" wrote:
Correct. There hasn't been an update for UDK to 0.2.2.

Does this mean there is a conflict, or is it still fine to use the old version of the UDK?

Does anyone know if the July 2013 version of UDK from Unreal's site works with the Oculus? If so, any idea how?

I am curious, is the plan to have Oculus fully integrated into UDK so every time there is a new release, the rift users will be able to get latest and move forward?

If so, could you tell the developers if the plan is to have this happen with the next release of UDK?

Thanks!

"AddisonStiles" wrote:
Does anyone know if the July 2013 version of UDK from Unreal's site works with the Oculus? If so, any idea how?

As an over-simplification, my assumption would be that you'd simply need to add the two new classes, Stereo3D and Oculus, and then modify your existing gameplay classes (pawn, playercontroller, gameinfo, etc) to account for head tracking and whatever else you may need. You'd also need to modify your ini files (systemsettings, UDKEngine, etc) to account for all of the Oculuss-specific stuff, including (but not limited to) enabling Stereo3D, hmdwarp, and AA filtering.

There may be a lot more to it, but I really can't say as I've not tried it. And if there's any Oculus-specific stuff in the lower level code, then you're out of luck. But that is an answer I do not have.

Personally, it seems far easier to simply use the official integration, and just port your levels, packages, and code into that version. Unless you already have a huge project going in a different version, or are super serious right this second about speedtrees or scaleform, then I'd suggest sticking with the official integration.

I'm having the same issue as a few other people have had in this thread - the UDK integration documentation still seems to be missing from the documentation page. Any word on when this will be available again?

From what I understand there were a lot of lower level rendering optimizations for the rift so taking vanilla UDK will probably not work nicely.

For the future, we know that unreal 4 engine has native oculus support so this gives us hope that UDK will eventually have the same.

For anyone else struggling to find the documentation or proper integration information, I managed to find it linked elsewhere on this forum.

Unreal Integration Documentation

I have no idea why this link has disappeared from the documentation page, but hopefully this should help some other people out!

I don't get it. First, the Oculus download center is not logical. It has one tab for 0.2 and one for 0.1. This gives an impression that the newest SDK can be downloaded from the 0.2 tab and older SDKs can be downloaded from the 0.1 tab.

It looks, however, that the 0.2 tab is the native Oculus SDK and the 0.1 tab is the UDK with Oculus support. If this is the case the tabs should be renamed to SDK and UDK to not make any confusion.

Also, the Oculus ready UDK seem to be from March if you follow the UDK version naming. And now there is a July UDK. Does the latest UDK from Epic support the Oculus or do I have to download the UDK from this website?

Anyone please enlighten me as this is confusing.

(Edited typo from 2.0 to 0.2 and 1.0 to 0.1)

"AndyK" wrote:
For anyone else struggling to find the documentation or proper integration information, I managed to find it linked elsewhere on this forum.

Unreal Integration Documentation

I have no idea why this link has disappeared from the documentation page, but hopefully this should help some other people out!

Thank you Andy! :DHave been looking for that for an hour now..

Um, where is the download link for the Oculus ready UDK?