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.


Messages - kkl

Pages: [1] 2 3 ... 20
1
Quote
I think that the way we're expected to import models into bones is extremely "hacky."
Agree with u, AGP. I notice even from blender2orge to bones, all the processes are written by different entity, which output different results.

Quote
and why do you need morph animation with Bones?
Hi raft, i checked blender2orge and they always export mesh xml with xml tag "animation" with value "mesh", in which the jme library will return -1 for jointIndex. I tried hacking the blender2orge exporter plugin by changing xml tag from "mesh" to "submesh" and somehow it works in Bones now.

Quote
export to a jPCT supported format (like MD2) and use that
I thought of that too, but the latest Blender seems to not supporting md2 export anymore and I can't find any other similar plugin for it.

2
Bones / Bones using jme library which does not support morph animation
« on: March 27, 2016, 05:13:20 am »
Hi,

I'm using Blender2Ogre to export ogre mesh. It seems like the exporter uses morph animation instead of pose animation (morph animation is similar to pose animation as described by ogre http://www.ogre3d.org/docs/manual/manual_78.html).

It prompts error when attempt to convert mesh.xml to bones
Code: [Select]
        Exception in thread "main" java.lang.IllegalArgumentException: jointIndex: -1
        at raft.jpct.bones.MeshChannel.<init>(MeshChannel.java:39)
        at raft.jpct.bones.MeshChannel.<init>(MeshChannel.java:25)
        at raft.jpct.bones.BonesImporter.convertJMEMeshChannel(BonesImporter.java:609)
        at raft.jpct.bones.BonesImporter.importOgre(BonesImporter.java:259)
        at raft.jpct.bones.util.JMEOgreImporter.loadGroup(JMEOgreImporter.java:112)
        at raft.jpct.bones.util.JMEOgreImporter.loadGroup(JMEOgreImporter.java:88)
        at raft.jpct.bones.util.JMEOgreImporter.run(JMEOgreImporter.java:69)
        at raft.jpct.bones.util.JMEOgreImporter.main(JMEOgreImporter.java:169)

I backtracked the code and notice jme library in Bones does not support morph animation. Do we have a newer jme library which support for that? If we use latest version, does it break anything?

3
Support / Re: NPOTTexture limitation?
« on: March 08, 2016, 01:31:48 pm »
Open source game~ cool. I'll check it out when i got the time. Thanks alot egon

4
Support / Re: NPOTTexture limitation?
« on: March 08, 2016, 11:20:54 am »
Not sure where I saw it in the forum. Just wanna confirm with you if blitting is the correct flow to create depth of field effect by combining depth map (manual color map) and the main scene.

5
Support / Re: NPOTTexture limitation?
« on: March 07, 2016, 04:14:26 pm »
Seems like I misunderstood the doc. Yup ok I'll manually render a color map the depth map and start combining main render with generated color map. By the way, you mentioned if we need to combine 2 textures, we should use blitting from framebuffer class. How is the performance for the blitting? Is it GPU accelerated or just CPU? Do you have any example to apply color map to main render display? I tried finding through the forum but i can find some guidance in verbal form only. Are you planning to put an example in wiki?

6
Support / NPOTTexture limitation?
« on: March 05, 2016, 05:51:15 pm »
Hi Egon,

I would like to make a depth of field effect by using post proccessing. It requires rendering the object z buffer in 1st render pass, then combine with main scene with a custom dof shader set to the framebuffer for post processing. To render the z buffer, we need to render the scene on a texture match with the screen width and height. I'm thinking of using NPOTTexture, but you mentioned in doc saying NPOTTexture is preferred to be in power of 2 as it's not supported in some devices. How should we do in this case? I worry if we create a power of 2 NPOTTexture and it does not match to screen width and height, we might have some texture size ratio problem. Please advise, thanks.

7
Projects / Re: [3D Live Wallpaper] Betta Fish 3D
« on: December 09, 2015, 01:00:02 am »
Lol sure.. Thanks for supporting egon

8
Projects / [3D Live Wallpaper] Betta Fish 3D
« on: December 07, 2015, 04:36:10 pm »
Betta Fish 3D



Inspired by 6S motion wallpaper, Betta Fish 3D is designed to refine the current 6S motion wallpaper, with outstanding and aesthetic graphics, finished with silky smooth animation.

Betta Fish 3D is a 3D live wallpaper that mimics the actual famous betta fish, the Siamese fighting fish. Betta Fish 3D is developed in a way that imitating exquisite photography of famous betta fish in aquarium tank. With 6 different betta fish variations and background color options for customizations, Betta Fish 3D is more lively and exciting for a live wallpaper. Betta Fish 3D is also designed to match fish color and background color, thus creating a phenomenal, state-of-art scene. In addition, Betta Fish 3D features silky smooth animation, while conversing your device battery at the same time.

Unlock all 6 different betta fish and background colors in Betta Fish 3D full version for more customizations. Try it out now!

Download Betta Fish 3D Now!

Betta Fish 3D demo on YouTube

9
Support / Texture virtualize delete
« on: November 07, 2015, 03:58:44 pm »
Hi egon,

Is it possible if you could add delete feature for texture that is virtualized to memory card? Or add delete when textureManager.unload() is called.

Reasons to have this:
1. In live wallpaper, there are occasions where only required textures are loaded, based on user settings in preference.  To avoid loading all textures during app startup (which can be slow),  only one required texture is loaded.
2. Virtualizer.cleanUp() can't be used as it will clean all other textures which are still in use. It also cleans up the shared texture from other Wallpaper instance too.
3. To save storage. Live Wallpaper context is always persistent and never close unless user select other live wallpaper. When new texture is virtualized, it seems like jpct will save another texture in memory card, even if the same texture id but different object is saved before, CMIIW.

10
Bones / Re: "Number of vertices differ" for 2 meshes with one skeleton
« on: October 08, 2015, 10:30:51 am »
Thanks alot raft. Really appreciate ur help. Look forward to supporting pose animation for merging group.

11
Bones / Re: "Number of vertices differ" for 2 meshes with one skeleton
« on: October 08, 2015, 04:06:53 am »
hi raft,

It's working great now! The bones weight should be correct for 2 objects respectively, right? I'll further check on that.

Thanks alot for your help fixing it. It's really helpful :)

12
Bones / Re: "Number of vertices differ" for 2 meshes with one skeleton
« on: October 07, 2015, 03:19:49 pm »
Wow, that's alot useful. I realized there's another method where converting mesh.xml to .mesh using OgreXmlConverter, then view in OrgeMax Viewer. But I'd prefer your way since it's faster :p

13
Bones / Re: "Number of vertices differ" for 2 meshes with one skeleton
« on: October 07, 2015, 03:04:53 pm »
Ok sure. Sent.

Btw, is there any viewer we can use to view the mesh xml so I can verify if it's correct? I tried using OgreMax Viewer and it seems it supports only .mesh file and cant import xml file.

14
Bones / Re: "Number of vertices differ" for 2 meshes with one skeleton
« on: October 07, 2015, 02:00:05 pm »
hi raft, yes they are working when converted to bones individually.

15
Bones / Re: "Number of vertices differ" for 2 meshes with one skeleton
« on: October 07, 2015, 02:11:51 am »
hi raft, i tried with jar u gave me and it actually able to merge 2 objects into 1, but when animating it, only 1 object is working. The other remains still. Am i missing something?


Pages: [1] 2 3 ... 20