Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Hi, i'm newbie in jpct.
Is it possible to deform the shape of touched object?
What can I use to achieve this? I was looking for the solution, and I found the bones, but I'm not sure if it is necessary to this task.
I used hello world from wiki to display the object.
It's simple additive blending...yes, you can do this.
No probs. If you want a glow effect as well you could experiment with a simple transparent plane centered near the front-center of the pumpkin with a 32bit (RGBA) texture that fades out from the middle. Beyond that you would need to use shaders, i.e. if you wanted a fancy glow extruding out of the pumpkin.
I must agree it was a battle learning even the basics of Blender.
jPCT doesn't support dual sided polygon textures (which is good in a way, keeps things simple) so you will need to solidify the object as mentioned. Rather than copy the outer texture co-ordinates to the inner faces, you would want to simply apply white to the inside to mimic the light volume. You do this by selecting all the inner faces and either apply a white material from the materials menu on the right, or hop into texture mode, load up your texture, select a portion of the texture that contains white, then wrap that portion to the polygons you have selected. It's not easy to do so I wont go into it in detail, but there are plenty of video guides on youtube that will get you started.
You wont need two pumpkins, 3D modelling programs like blender allow you to select all the vertices and extend them inwards, effectively creating a complete 3D object with both inner and outer walls. Once that is done, apply a white part of the texture to the inner faces.
OpenGL hardware typically have 8 hardware lights you can use. Refer to the "Light" class in jPCT, set it's position to the center of the pumpkin to light it up.
How do you apply a texture to both sides of a mesh using the UV editor ? When you unwrap a mesh it is unwrapped on one side only 
You could cheat and change the texture of the inside of that pumpkin, make the inside colors pure white so it appears lit up.
Additionally, you could separate the inside and outside of the 3D pumpkin object and setAdditionalLighting(200,200,200) to the inner Object3D. Or perhaps pop a small hardware Light in the center.
Something like a...missing image...?
If the memory finally gets freed by the garbage collector, i don't see the actual issue. It's up to VM how to manage the memory and as long as it isn't a real leak (which it doesn't seem to bo or otherwise, the memory won't be freed again), i don't see a problem with that behaviour. You might want to try to call MemoryHelper.compact() in onSurfaceChanged...maybe that helps.
Regarding dispose()...you are meant to call it, if a reference goes out of scope. If it never does, there's no need to call it. Personally, i would simply keep my World and Skybox and don't create new ones all the time, but that's up to you.
Try to load the textures via an InputStream (for example: res.openRawResource(R.raw.texture)) instead and see if that helps.
What's the relation between memory usage and the text on the Activity?
How are you loading your textures? If you load them as Bitmap or Drawable, Android will cache them. Does this increasing memory consumption reaches a limit or does it increase until you get an OutOfMemoryError?
You might want to profile you app (if it's actually possible to profile a wallpaper properly with the means that Eclipse and the Android plugin provide...) to see where the memory goes. Personally, i'm not aware of any existing memory leaks in the engine.
TextureManager tm = TextureManager.getInstance();
String name = "light_" + mLightTex;
int id = res.getIdentifier(name, "drawable", mContext.getPackageName());
if (tm.containsTexture("light")) {
tm.unloadTexture(mFrameBuffer, tm.getTexture("light"));
tm.replaceTexture("light", new Texture(res.getDrawable(id), true));
} else {
tm.addTexture("light", new Texture(res.getDrawable(id), true));
}
if (mFrameBuffer != null) {
mFrameBuffer.dispose();
mFrameBuffer = null;
}
if (mSkyBox != null) {
mSkyBox.dispose();
mSkyBox = null;
}
if (mWorld != null) {
mWorld.dispose();
mWorld = null;
}
TextureManager.getInstance().flush();
That's actually the exact same thing that jPCT-AE does except that jPCT-AE assumes that fov means the field of view in x-direction while this code assumes that fov defines the field of view in y-direction. Personally, i find this highly unintuitive, because nobody defines his field of view in up/down-direction. Anyway, you can get behaviour by setting the fov values for x and y explicitly. To do this, you can do something like:Code: [Select]Camera cam = world.getCamera();
float fov=1.25f;
if (w > h) {
cam.setFOV(fov);
cam.setYFOV(fov * ((float)h / (float)w));
} else {
cam.setFOV(fov * ((float)w / (float)h));
cam.setYFOV(fov);
}
Hope this helps.