Unity 4.1.5f1 and Android SDK r22

Ninjapretzel

Are there support for these?

Since unity went free for android with version 4, and the recent updates to the android SDK breaking stuff (and then being fixed by unity), I was hoping that the latest SDK for OUYA would support the latest unity.

I am currently working on porting an android title over to OUYA, and we decided to move the project 'up' from Unity 3.5 to Unity 4.1, and that all went smoothly.

I was even able to build the project right to the ouya without the ODK installed, to test and make sure it would run, which it does.

I cannot for the life of me figure out how to figure out implementing the ODK into unity.

I made a blank project and set everything up as the FAQ had said

Bundle identifiers are synchronized

Min android is set to 16

Set up all paths and latest SDKs (android SDK/NDK, JDK), but there is still one line in the ouya panel that is grayed out: APT Path under android SDK.

There is no aapt.exe under \sdk\platform-tools\

NDK and Plugin compile just fine, but Compile Java spits out the "R.java cannot be found", when my package names are sync'd. I manually verified the OuyaUnityApplication.java and AndroidManafest files, and they have the correct bundle ID.

Is this just a thing where there is no support for it yet?

I would really like to get the ODK integrated so that our game can be on the Ouya market on launch.

Thanks -

Ninjapretzel

As a side note, I did successfully implement an older version (i think the second released update to the unity plugin) in a project when that was just released, and had no problems implementing that into the project.

tgraupmann

The setup documentation has a link to a unity post with a link to Android SDK r21 which works.

https://devs.ouya.tv/developers/docs/setup

Hicsy

I just tested it with the latest updates (Unity 4.1.5f1, ODK 1.0.5.1, SDK 22.01) and it all went gravy, besides Aapt which is now in the new folder build-tools\[version]\

I think I copy+pasted mine from the v17 folder back to platform-tools to get around that bug

Hicsy

@tgraupmann the latest sdk update reorganises the tools+platform-tools again...

 The SDK manager now has separate categories for each tool and added a new cat for build-tools, where it separates out tools such as Aapt.exe for each (new) version

just like the original ADB problem, Aapt.exe is now in a different folder... and in fact probably will be each time a new version is released from now on

tgraupmann

Yeah I'll have to search for those tools each time because they keep moving around. For now R21 works with the OUYA panel. I'll put it on the todo list...

Ninjapretzel

Huh- I still had a r21 version of the Android SDK, so I actually was able to use both alongside eachother to build/push the game to the device.

I was also able to get the game push with the plugins with copying Aapt.exe into the folder it was expected in, and it worked 100% as well.

My only complaint is NGUI being integrated by default with the distribution of the plugins, just for the sake of the examples, when it's not required to actually integrate the plugins.

Can you make a side fork of the project that is just the minimum includes to convert an android game for OUYA? 

tgraupmann

That's why there's the menu option OUYA->Export Core which will only include the OUYA SDK and nothing else...

Ninjapretzel

The contents of that package should be hosted somewhere on the github repository, making it simpler for experienced users to grab the necessary updated files in the future, saving the time of many people exporting that package manually every time an update comes out.

But overall, integrating the SDK has been pretty easy. It's kind of annoying that the examples are so bloated compared to the core necessary files.

tgraupmann

That's the reason behind the export options to just get the files you want.

You are perhaps suggesting that I move the examples to the ouya-sdk-examples/Unity folder on GitHub.

muahahha!

Soon...