What to do to support DK2 in UDK?

"niksha" wrote:
Not really sure why UDK isn't a priority for Oculus team and Epic.

Is this all because Epic wants to force people to use Unreal 4 if they want to use Rift? People won't just magically give up on using UDK when their whole projects will break and consume more time on moving to U4.

There are so many developers who could have Oculus integrated into their game by now, but nope, it's not really a priority at all (while U4 gets regular updates).


EDIT: Also, developers shouldn't have to go around begging for support to sell someone's product. Jeez. Lets just move on if the company isn't treating UDK users as priority at all. :roll:

I agree with you totally. UDK has been available for years for devs. With no signs from EPIC when u4 would actually be publically available. UDK is quite old now, and understandably EPIC and Oculus need to move (ahead) of the times, and get the best possible product in our hands.

The U4 release was very out of the blue. As most will agree, a welcome out of the blue. But for Devs who have Worked on our projects for years and are at the end of development is not helpful for us. I would have loved to port everything over to u4, but at the end of development, its too late.

I am personally getting asked more and more witch each day which passes, When ? When ? our game is ready for noneVR. Its made for VR. Its works amazing with DK1 and are waiting until we can release it as its meant to be (for DK2). And there is more out there who are wondering why UDK is the last ship to leave the dock?



So another plea to oculus and epic, please give us something to stamp the finished dot on some of our projects and careers :)