SitRep on the UDK situation?

"unity2k" wrote:

I feel it's time to get cranky again for an update on UDK progress. You with me HappyHimitsu?

Well, Oculus has been so great to me lately I can't really complain, but given that it's been a couple of weeks since my last post, and a couple of months since Nate's comment, I agree that an update is due.
I apologize for any confusion as I had posted a similar reply prior to this one a couple of weeks ago and deleted it, when I should of just left it here for anybody to read.

:)

I just started doing my coding and I'm pretty cranky. I've overwritten every function mentioning oculus I can find and the Rift still hijacks my camera when it is in Rift mode. Taking a look in class Oculus.uc reveals that they have made everything as difficult as possible for developers. Not a single rotator or quat available in the class. Instead, they throw in a bunch of native functions that hijack the camera for you. At this point I might as well grab a fresh UDK and try to write my own implementation.

DEAR OCULUS:

Your implementation should:
Read sensor data. Store sensor data in accessible variables. Put screen into stereo render with HMDwarp. Include minor rendering optimizations.

Your implementation should not:
Implement controls. Hijack camera. Involve inaccessible native functions except when strictly necessary. Anything else.

Some updates about upcoming new UDK with Oculus support. I know, our current UDK is unacceptably out-of-date and for the last several months we worked hard to make a new UDK. This is a pretty involved process and we need help from Epic guys to make a build of the UDK. (btw, answering on question above: UDK is located in '0.1' tab because it is using OculusSDK 0.1.5; once we have new UDK it will appear under '0.2' tab and '0.1' tab will be gone).
So, we already have a preliminary UDK installation that ALMOST passed QA. In the last minute we got news from Scaleform that their SDK 4.2.24 has a pretty critical crash that might occur if ActionScript 3.0 is used. It is not that critical for UDKGame, since it uses ActionScript 2 only, but I know, a lot of you, guys, switched to ActionScript 3 long time ago. We can't release UDK knowing it has a crash in ActionScript 3.0, therefore we have to delay the release and ask Epic to rebuild it with the fixed Scaleform 4.2.24 (thanks to Scaleform guys for the fix!). I hope, this won't take much longer, we'll keep you posted.

Good to have some news !
Thanks Artyom17, this is a sun ray through the clouds !

Bug hunting, QA, and scaleform on the horizon ! Less than a month I guess, then.
Cool.

Good hunting !

"OlivierJT" wrote:
Good to have some news !
Thanks Artyom17, this is a sun ray through the clouds !

Bug hunting, QA, and scaleform on the horizon ! Less than a month I guess, then.
Cool.

Good hunting !

I wouldn't guess at a time frame, it's taken them almost 6 months since the initial April 1st (inside joke?) release of the OculusUDK to get this far. It was almost 3 months ago that Nate said a couple of weeks (at the earliest, I understand), and it was 3 months before that when we first got 0.1.

I apologize for the pessimistic attitude guys, but this is one of those 'fool me once' kind of scenarios.

Scaleform Isn't even the issue, They keep saying build of UDK. I don't want a build of UDK. Even if the last one had all the 3rd party plugins, it was still utterly useless to developers because they coded everything natively. We have asked time after time for a couple of files to just drop into our UDK folders.

"BlackFang" wrote:
Scaleform Isn't even the issue, They keep saying build of UDK. I don't want a build of UDK. Even if the last one had all the 3rd party plugins, it was still utterly useless to developers because they coded everything natively. We have asked time after time for a couple of files to just drop into our UDK folders.

Do you still feel positive that you'll get there? Did anyone come through with the normal map you were looking for this morning? Any idea when you'll post your next progress video? The work you are doing is exciting, you have some of us on the edge of our seats awaiting your results. Thanks.

I managed to sort of do it with a normal map, but doing it using a texture causes artifacts, even at high resolutions. Looks like I will have to write a custom material expression node, but I have no idea how. I can't find any non-native examples to look at. If I could see a basic explanation of how inputs/outputs work on those nodes, it would help a lot.

It's downloading as I write. I'm ready to sit down with HappyHimitsu and eat some words.

Bink, Simplygon, Speedtree, Scaleform.....it's all there! And the newest Oculus SDK.

You want to talk about happy, thrilled even???