Source code of Bones moved to GitHub.
https://github.com/raftAtGit/Bones.

The latest downloadable zip file can be found at releases page.

Of course this doesnt mean, Bones is moving away from jPCT community. It's a library for jPCT after all

The primary feedback and question medium will still be jPCT forums as mentioned in the feedback section.

This was something I wanted to do since long time, to get rid of the burden of keeping the source code safe. Cloudforge, the previous host of Bones' code is closing, so this looked like the proper time to do that.

Egon, can you please update the links

when jpct.jar is placed in libs folder in Eclipse project, javadoc location is not editable. according to this post in stackoverflow, one workaround is to place javadoc.jar in a proper location and edit a special properties file. unfortunately this does not work for remote (http) javadocs.

so Egon can you please add javadoc.jar to downloads page. unless of course you know an alternative solution?

is it possible to render an object only to depth buffer but not to frame buffer? i want to use this for a kind of masking.

here is my tunnel rendered on top of camera view:


same tunnel with a different camara orientation. obviously looks wrong since the deeper parts of the tunnel should not be actually visible.


if I understand the depth mask thing in unity correct, one way to resolve this issue is, place a plane on top of the tunnel with a hole in it (hole is the entry of the tunnel), render it to only depth buffer and then render the scene (tunnel).

like this, the yellow area will be masked:


is this possible?

I have a default camera at origin looking through z axis. I also have an object in camera's field of view with some rotation and translation. I want to place the object to origin with no transform (identity matrix) and place camera such that what camera sees was identical to before. how to do that?

I'm planning to take the object's world transform, invert it and set as back buffer to camera? not tried yet.

can I suggest adding a new version of ITextureEffect which accepts java.nio.Buffer and channel ordering?

I'm experimenting with the idea of mixing OpenCV with jPCT and making them to render to same GLSurfaceView as I mentioned in this thread. the pipeline is something like:

* take android's camera preview data (byte[]) and put into an OpenCV Mat¹ object
* modify and/or process Mat via OpenCV
* copy final contents of Mat into a jPCT texture via an ITextureEffect
* blit that texture as background
* render 3d content over that

all is fine for now except the fps. some profiling suggests most of the time is spent in ITextureEffect.apply(..) method.

there are two issues:
* jPCT wants texture data in ARGB channel order but OpenCV supports RGBA and BGRA, not ARGB
* jPCT wants all channels embedded into an int but OpenCV gives chanels as different bytes (or float/short/int whatever depth is used)

so I take the byte array from OpenCV, iterate over that, re-arrange the bytes and create an int out of that. jPCT takes that and puts them into a nio.Buffer, quite a waste.

long story short, it may be good idea to add a new version of ITextureEffect which accepts java.nio.Buffer and channel ordering. unless of course there is a better way?

as an implementation detail, this new one can extend from the current ITextureEffect to keep things simple:

interface INioBufferTextureEffect extends ITextureEffect {
    // channel order maybe return type or a setting in Config.
    // if filling in source is costly, it can even be skipped based on a setting in Config
    void apply(java.nio.Buffer dest, java.nio.Buffer source);
}

¹: Mat is an OpenCV matrix like structure which can hold and convert to a matrix of arbitrary depth. pixels of an image or a perspective transform for example.

adding this line to HelloWorld sample before setEGLConfigChooser

mGLView.setEGLContextClientVersion(2);
results in the exception below. any ideas how to fix this?

I/jPCT-AE (24633): Memory usage after compacting: 12335 KB used out of 13447 KB. Max. memory available to the VM is 65536 KB.
I/jPCT-AE (24633): Saving master Activity!
E/libEGL  (24633): called unimplemented OpenGL ES API
E/libEGL  (24633): called unimplemented OpenGL ES API
E/libEGL  (24633): called unimplemented OpenGL ES API
I/jPCT-AE (24633): [ 1387365972966 ] - WARNING: State: 0/0/0/0/0/0/0
W/dalvikvm(24633): threadid=11: thread exiting with uncaught exception (group=0x4199d2a0)
E/AndroidRuntime(24633): FATAL EXCEPTION: GLThread 7949
E/AndroidRuntime(24633): java.lang.ArrayIndexOutOfBoundsException: length=0; index=0
E/AndroidRuntime(24633):        at com.threed.jpct.CompiledInstance._fill(CompiledInstance.java:1206)
E/AndroidRuntime(24633):        at com.threed.jpct.CompiledInstance.fill(CompiledInstance.java:746)
E/AndroidRuntime(24633):        at com.threed.jpct.Object3DCompiler.compile(Object3DCompiler.java:148)
E/AndroidRuntime(24633):        at com.threed.jpct.World.compile(World.java:1951)
E/AndroidRuntime(24633):        at com.threed.jpct.World.renderScene(World.java:1046)
E/AndroidRuntime(24633):        at com.threed.jpct.example.HelloWorld$MyRenderer.onDrawFrame(HelloWorld.java:228)
E/AndroidRuntime(24633):        at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1516)
E/AndroidRuntime(24633):        at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1240)


I've finally received my OUYA. here are first impressions:

It's a cute tiny box. I've known in prior that it's small in size but still it's surprising to see how small it is. slightly bigger then a rubic cube. the console and controller looks good but I suppose the material quality is not that good. battery housing covers tend to open themselves. after a few hours of play, one of the analogue sticks started to screak. I guess there is some extra weight in the controller which makes it fit hand better. the stick sensitivity feels good but that may change in time due to wearing.

anyway, about the subject: I've checked Sky Maze and found that colors look ugly. I dont know how to explain it, they just look unfamiliar and ugly. this does not result from TV settings since other games look good. I dont know the reason yet, maybe extra caution is required for texture colors for TV? (for example, in Android docs, it's suggested to avoid pure white (#FFFFFF) since it may cause vibrancy and image ghosting.)

high resolution (due to relatively small texture sizes) is not also the reason, since I've run desktop version of Sky Maze in my 1080p 24" monitor and never saw such an effect.

may this be relevant with EGLConfigChooser? here is my corresponding code:

glSurfaceView.setEGLConfigChooser(new GLSurfaceView.EGLConfigChooser() {
public EGLConfig chooseConfig(EGL10 egl, EGLDisplay display) {
// Ensure that we get a 16bit framebuffer. Otherwise, we'll fall
// back to Pixelflinger on some device (read: Samsung I7500)
int[] attributes = new int[] { EGL10.EGL_DEPTH_SIZE, 16, EGL10.EGL_NONE };
EGLConfig[] configs = new EGLConfig[1];
int[] result = new int[1];
egl.eglChooseConfig(display, attributes, configs, 1, result);
return configs[0];
}
});

any other ideas?

this exception newer happens on my Nexus 7, my phone or desktop. two Ouya console owners reported this. and it does not always happen. but once happened, level loading fails until application is restarted, possibly because of same exception.

this code runs during level loading in a background thread.

java.lang.ArrayIndexOutOfBoundsException: length=11; index=11
  at com.threed.jpct.Vectors.addVertex(Vectors.java:85)
  at com.threed.jpct.Object3D.setBoundingBox(Object3D.java:2507)
  at com.threed.jpct.Object3D.calcBoundingBox(Object3D.java:1197)
  at com.threed.jpct.Object3D.rotateMesh(Object3D.java:2411)
  at raft.jumpy.view.Particle.<init>(Particle.java:66)
  at raft.jumpy.view.ParticleManager.<init>(ParticleManager.java:43)
  at raft.jumpy.view.GameView.<init>(GameView.java:111)
  at raft.jumpy.android.ouya.JumpyActivity$5.run(JumpyActivity.java:522)

and this is the relavant particle class. taken from Robombs code I suppose:

   public Particle() {
      super(PLANE, true);
      rotateZ((float)Math.random()*6f);
      rotateMesh();
      clearRotation();
      setBillboarding(Object3D.BILLBOARDING_ENABLED);
      setVisibility(Object3D.OBJ_VISIBLE);
      setCulling(Object3D.CULLING_DISABLED);
      setAdditionalColor(RGBColor.WHITE);
      setLighting(Object3D.LIGHTING_NO_LIGHTS);
      enableLazyTransformations();
      reset();
      shareCompiledData(PLANE);
      build();
      texture="particle_blast";
   }

kind of urgent, OUYA will be launched for backers on 28 march