Log in or register to post comments

Unity 3.4 beta

June 22, 2011 - 2:55am #1

Hi,

Is QCAR for Android supposed to work with Unity 3.4 (beta)? I get:

  4950               dalvikvm  I  Could not find method com.unity3d.player.UnityPlayer.<init>, referenced from method com.qualcomm.QCARUnityPlayer.QCARUnityPlayer.<init>               
  4950               dalvikvm  W  VFY: unable to resolve direct method 612: Lcom/unity3d/player/UnityPlayer;.<init> (Landroid/content/Context;)V
  4950               dalvikvm  D  VFY: replacing opcode 0x70 at 0x0000
  4950               dalvikvm  D  Making a copy of Lcom/qualcomm/QCARUnityPlayer/QCARUnityPlayer;.<init> code (24 bytes)
  4950         AndroidRuntime  D  Shutting down VM
  4950               dalvikvm  W  threadid=3: thread exiting with uncaught exception (group=0x4001b178)
  4950         AndroidRuntime  E  Uncaught handler: thread main exiting due to uncaught exception
  4950         AndroidRuntime  E  java.lang.NoSuchMethodError: com.unity3d.player.UnityPlayer.<init>
  4950         AndroidRuntime  E  	at com.qualcomm.QCARUnityPlayer.QCARUnityPlayer.<init>(QCARUnityPlayer.java:27)
  4950         AndroidRuntime  E  	at com.qualcomm.QCARUnityPlayer.PlayerActivity.onCreate(PlayerActivity.java:227)
  4950         AndroidRuntime  E  	at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
  4950         AndroidRuntime  E  	at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)
  4950         AndroidRuntime  E  	at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2512)
  4950         AndroidRuntime  E  	at android.app.ActivityThread.access$2200(ActivityThread.java:119)
  4950         AndroidRuntime  E  	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1863)
  4950         AndroidRuntime  E  	at android.os.Handler.dispatchMessage(Handler.java:99)
  4950         AndroidRuntime  E  	at android.os.Looper.loop(Looper.java:123)
  4950         AndroidRuntime  E  	at android.app.ActivityThread.main(ActivityThread.java:4363)
  4950         AndroidRuntime  E  	at java.lang.reflect.Method.invokeNative(Native Method)
  4950         AndroidRuntime  E  	at java.lang.reflect.Method.invoke(Method.java:521)
  4950         AndroidRuntime  E  	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:860)
  4950         AndroidRuntime  E  	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:618)
  4950         AndroidRuntime  E  	at dalvik.system.NativeStart.main(Native Method)

If I build the same project with Unity 3.3 everything works fine. Do you have any ideas? Maybe I'm just doing something wrong...

Thanks,
Paulius

Re: Unity 3.4 beta

August 2, 2011 - 10:23pm #8
UmbertoC wrote:

We just released our iOS Beta extension for Unity and it is compatible with Unity 3.4.

As far as our Android extension for Unity, expect to see a maintenance release that fixes compatibility with Unity 3.4 very soon.

Hi, it is possible to have acces to beta wersion of this ne wersion of QCAR for android, and help You provide this realese sooner?

Support for android 3.x and unity3d 3.4 is very expected by community, nd personaly we have some project with very shord deadline for android 3.x.

Re: Unity 3.4 beta

July 26, 2011 - 12:55pm #7

great to hear that, thank you.
and congratulations to the QCAR iOS beta release!

Re: Unity 3.4 beta

July 26, 2011 - 10:50am #6

We just released our iOS Beta extension for Unity and it is compatible with Unity 3.4.

As far as our Android extension for Unity, expect to see a maintenance release that fixes compatibility with Unity 3.4 very soon.

Re: Unity 3.4 beta

July 26, 2011 - 7:19am #5

hi,
unity 3.4 is out. any news about your QCAR update?

Re: Unity 3.4 beta

July 11, 2011 - 10:54am #4

Any chance this update will include the ability to dynamically import new trackables at runtime?

Re: Unity 3.4 beta

July 11, 2011 - 8:06am #3

Do you have an ETA on the update ? I can't wait to get my hands on it.

Re: Unity 3.4 beta

June 22, 2011 - 3:18pm #2

No, Unity changed a few things with 3.4 and our 1.0.0 release isn't compatible. The good news is that we have an update in the works. We'll keep you posted!

- Kim

Log in or register to post comments