I upgraded to Unity 3.3 and it seems that my problems are solved.

It was great seeing QualComm at the GDC, managed to get all the simple problems fixed when I went to the Unity section. Apparently it was just a simply turning off the kinematics and baking animations when porting them from Maya.

I've tried importing the AR plugin, then deleting the tracking scripts from the camera and plane and had the animation issue. I'll try it with a fresh screen and import to see if the plugin problem persists. If it is then I'll send it to support, thanks for the fast response.

If you import the QCAR files and run your app, without dragging any AR prefabs into the scene, do the animations still break? Or do you have to drag the ARCamera into the scene for it to break?

If possible, sending a project that exhibits the problem to

is always the easiest way for us to help.

- Kim

I'm not sure if this a compatibility issue but I can get animations running in Unity, I can get the animations running on the android, but as soon as I port in the AR files, none of the animations will run. Is there an extra step that I'm missing?

I sent my APK to the given email.

I tried reproducing the issue in a smaller project without luck.

As I mentioned I have other issues with Unity 3.2 (unrelated to AR). Unity Android people said it might be a bug related to vertex buffers. No idea if that could be causing problem with video stream too.

Could you possibly send an APK to

? I could test it on an HTC Desire and see if it has the same issue.

I'm not really sure what the problem could be, but I'd also be happy to look over the project if you can share it or a simple example that exhibits the same problems.

Thanks,

- Kim

I'm on GLES 2.0 already (since I couldn't run with 1.1 at all).

I have only NexusOne with Android 2.1 with me at the moment only. I might be able to test on more devices later.

I don't have any screenspace effects and I'm using quite simple shaders (either texture only, or texture + alpha texture).
I use Texture2D.ReadPixels quite a lot (to get a picture from camera).

There were no issues with Unity 3.1 (and old AR SDK jar).

Wow, that's trippy, I've never seen that before :)

Try setting your project to use OpenGL ES 2.0, if you haven't already. That typically takes care of any strange rendering issues. Let me know if this doesn't help.

Also, what device are you using? Are you using any special rendering effects in your Unity project?

Thanks,

- Kim

Hi,

I just started experimenting with the new build and I have experienced some problems with it. I get problems with Video feed. Sometimes it works fine, but sometimes I get single-color-blinking screen, and once I got this weird split (looks like UV coordinates are messed up of video feed).

When I say "sometimes works" I mean it works when I start the game, then I reload scene (in the end of the round) and sometimes it stops working, then reloading fixes the problem again...

Disregard the fact the attached image has weird resolution (I cut the sides of it in order to hide my game).

I have other problems with Unity 3.2 unrelated to AR too...

Regards,
Paulius

The patch is now available! Go to the SDK tab of this site, and look in the Unity section. Let us know if you run into any issues!

- Kim

I was about to ask about Unity 3.2 :)

I'm glad to hear that you're working on it. Moving to Unity 3.2 is very important (once the SDK is compatible), since it reduces main memory occupied by applications significantly (Unity 3.2 stores most of the application on SD card). "Application occupying too much of the main memory on a phone" was one of the main reasons why users would ask for refund for an application bough on Android Market.

Thanks for the heads up!
I've been ignoring the upgrade message precisely due to the fear it'd break something. Sometimes paranoia is a good thing. :)