hiteshsuthar / rokon

Automatically exported from code.google.com/p/rokon
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

Unable to create engine #38

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Hi,

i just wanted to try Rokon, but i am unable to do it =/ I try to launch 
this short application :

package com.malgon.applecrush;

import com.stickycoding.Rokon.RokonActivity;

public class Main extends RokonActivity {

   public void onCreate() {
       createEngine(480, 320, true);
   }

    public void onRestart() {
            super.onRestart();
            rokon.unpause();
    }
}

But when i try it, I get in the logcat :

V/Rokon   ( 6963): Rokon engine created
V/Rokon   ( 6963): FA=1.5 RA=1.5
D/dalvikvm( 6963): GC freed 1057 objects / 72720 bytes in 95ms
D/dalvikvm( 6963): DexOpt: couldn't find static field
W/dalvikvm( 6963): VFY: unable to resolve static field 8 (SDK_INT) in 
Landroid/os/Build$VERSION;
W/dalvikvm( 6963): VFY:  rejecting opcode 0x60 at 0x01ad
W/dalvikvm( 6963): VFY:  rejected 
Lcom/stickycoding/Rokon/OpenGL/RokonRenderer;.onDrawFrame 
(Ljavax/microedition/khronos/opengles/GL10;)V
W/dalvikvm( 6963): Verifier rejected class 
Lcom/stickycoding/Rokon/OpenGL/RokonRenderer;
D/AndroidRuntime( 6963): Shutting down VM
W/dalvikvm( 6963): threadid=3: thread exiting with uncaught exception 
(group=0x4000fe70)
E/AndroidRuntime( 6963): Uncaught handler: thread main exiting due to 
uncaught exception
E/AndroidRuntime( 6963): java.lang.VerifyError: 
com.stickycoding.Rokon.OpenGL.RokonRenderer
E/AndroidRuntime( 6963):    at 
com.stickycoding.Rokon.OpenGL.RokonSurfaceView.<init>(RokonSurfaceView.java
:15)
E/AndroidRuntime( 6963):    at 
com.stickycoding.Rokon.Rokon.init(Rokon.java:425)
E/AndroidRuntime( 6963):    at 
com.stickycoding.Rokon.RokonActivity.createEngine(RokonActivity.java:212)
E/AndroidRuntime( 6963):    at 
com.stickycoding.Rokon.RokonActivity.createEngine(RokonActivity.java:191)
E/AndroidRuntime( 6963):    at 
com.malgon.applecrush.Main.onCreate(Main.java:9)
E/AndroidRuntime( 6963):    at 
com.stickycoding.Rokon.RokonActivity.onCreate(RokonActivity.java:181)
E/AndroidRuntime( 6963):    at 
android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1123)
E/AndroidRuntime( 6963):    at 
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2231)
E/AndroidRuntime( 6963):    at 
android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2284)
E/AndroidRuntime( 6963):    at 
android.app.ActivityThread.access$1800(ActivityThread.java:112)
E/AndroidRuntime( 6963):    at 
android.app.ActivityThread$H.handleMessage(ActivityThread.java:1692)
E/AndroidRuntime( 6963):    at 
android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 6963):    at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 6963):    at 
android.app.ActivityThread.main(ActivityThread.java:3952)
E/AndroidRuntime( 6963):    at 
java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 6963):    at 
java.lang.reflect.Method.invoke(Method.java:521)
E/AndroidRuntime( 6963):    at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:
782)
E/AndroidRuntime( 6963):    at 
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:540)
E/AndroidRuntime( 6963):    at dalvik.system.NativeStart.main(Native 
Method)

Even the examples don't work...

What version of Rokon are you using?
Rokon 1.1.1

On which version of Android are you experiencing this?
Android 1.5

Original issue reported on code.google.com by Malgo...@gmail.com on 2 Jan 2010 at 3:53

GoogleCodeExporter commented 8 years ago
It seems that it's because i'm under android 1.5 isn't it ?(fucking samsung 
galaxy)

Original comment by Malgo...@gmail.com on 2 Jan 2010 at 4:24

GoogleCodeExporter commented 8 years ago
Yes, it'll get fixed in the trunk pretty soon, its just a bad variable name.

Original comment by rtaylor205@gmail.com on 2 Jan 2010 at 4:31

GoogleCodeExporter commented 8 years ago

Original comment by rtaylor205@gmail.com on 2 Jan 2010 at 4:31

GoogleCodeExporter commented 8 years ago
And will it work under 1.5 or not ?

Original comment by Malgo...@gmail.com on 2 Jan 2010 at 4:36

GoogleCodeExporter commented 8 years ago
Yes, it will.

Original comment by anton.he...@gmail.com on 2 Jan 2010 at 5:16

GoogleCodeExporter commented 8 years ago
ah great news :D Any idea of the time it will take ?

Original comment by Malgo...@gmail.com on 2 Jan 2010 at 5:21

GoogleCodeExporter commented 8 years ago
umm... I'd guess it would take like one or two minutes (it's a really simple 
bug),
but then again, I'm not one of the developers so I can't commit to their SVN :P
But wait an hour or two and Richard will probably have fixed it. :)
In the meantime, you could always run it on a 1.6 emulator.

Original comment by anton.he...@gmail.com on 2 Jan 2010 at 5:40

GoogleCodeExporter commented 8 years ago
Yes but it's not really good to try it on an 1.6 emulator, which is very slow =/
Hope Richard will fix it :D

Original comment by Malgo...@gmail.com on 2 Jan 2010 at 5:46

GoogleCodeExporter commented 8 years ago
You know, if you don't feel like waiting, you could always take a look at issue 
37
where I stated the bug as well as the fix.

Just change all
Build.VERSION.SDK_INT == 3
in the rokon source code to
Build.VERSION.SDK == "3"
and it will work. :)

Original comment by anton.he...@gmail.com on 2 Jan 2010 at 8:49

GoogleCodeExporter commented 8 years ago
Or not :P
It's fixed now, just get the latest trunk.

Original comment by anton.he...@gmail.com on 2 Jan 2010 at 9:02

GoogleCodeExporter commented 8 years ago
Oh yeah it works :D thanks, i will have a look to see if i can't help coding 
rokon :)

Original comment by Malgo...@gmail.com on 2 Jan 2010 at 9:03

GoogleCodeExporter commented 8 years ago
Hello,
I'm trying to use Rokon to develope my game and I'm having the same problem as
Malgon33 had... I've just read all of yours answers but I don't get the point 
of the
solution :S 
I have downloaded the latest version available and I suppose that is updated 
with the
bug that you're talking about fixed... or maybe not? Please help, I don't know 
what to do
thanks

Original comment by jessis...@gmail.com on 7 Apr 2010 at 9:10