[...] Android and Me Related Posts:Android 将在三年内具备 PS3 的图形处理能力Facebook正式登陆Android [...]

[...] Fonte AKPC_IDS += "9003,";Popularity: 2% [?] [...]

[...] for his work on the Unreal Engine. We have been following Epic Games because they showed off the Unreal Engine on an iPod Touch and then an Nvidia Tegra 2 tablet. Epic had hinted they would support another mobile platform [...]

Ahhhhh. Sorry, that was me pissing on your Android phone as I’m playing Need For Speed in all its full 3D glory on my Palm Pre. You can have your clunky Droid phone, but the Palm faithful will prevail! Go Palm!

I find it easier to imagine its going on the PSP, with the Minis functionality. But I’m sure it’ll port to android once its a likelyhood.

Agreed, that would be awesome!

freakin’ awesome. ’bout m.f. time, what what!

Ahh.. I didn’t hear about the UDK, but on checking up on it is a binary only release, so not applicable for porting. I’d be surprised if U3 engine had source available at those costs. Yearly per seat fee and 25% royalty is somewhat high for a binary only release, but it does get the tech out there for alternative usage as promoted on the UDK page.

If there are GL2 bindings in NDK for Eclair; I’d expect to see them in the SDK unless someone is being lazy.

Also a port wouldn’t be a matter of hours for something like UDK even if it was in source. There are so many components to U3 that have no alternative on Android devices; for instance NVidia PhysX engine usage, but there are probably many other constraints including that U3 is a combination of 3rd party libraries like SpeedTree and other 3rd party libraries too. I’d like to see them get the outdoor terrain part of the engine working well for instance on the IPhone 3GS, but something tells me U3 for iPhone may be an indoor only engine ala Q3 with a reduced outdoor / terrain rendering capability, etc. It’s slightly misleading giving the impression that the full U3 is coming to iPhone (or Android); though one can be hopeful. By 3rd or 4th generation Android devices we’re going to really have some fun!

So, well have to wait and see what is actually supported on the mobile version of U3.

I’m really interested in Java source level engines using the GL bindings in the SDK as compared to the NDK. That is what I think will definitely be a ways off to seeing brand new commercial game engines or ports of existing engines at the Java source level. I’ll have Auriga3D / Q3 stuff out soon, but it’s just a demo of how to do 3D programming at Java source level though games easily can be made with it though it’s not a one stop full game engine suite of tools like U3. I guess the cool thing with my effort is that it runs on the desktop and Android from one shared source code base and can use the LWJGL, JOGL, or Android GL ES bindings.

and If their engine is a pure C/C++ one, the Android port is a matter of hours, not days or weeks

There’s OpenGL 2.0 bindings in the 2.0 NDK (check the eclair snapshot in AOSP)