Thanks Fred  

Hello,

For Java Mobile 3D (JSR84), CLDC 1.1 is needed so MIDP2.1. The floating point dilemma...
OpenGL-ES is kind about that and you could use fixed maths.

I have done a full 3D J2ME engine MEE-J3D : see www.miklabs.com/wip
I will show a keynote  about j2me and 3D at Imagina in France: www.imagina.mc

Mik
Miklabs.com
PS:MEE-J GPL will be released soon  

Yap the win32 demo version freeze my Win2000 Dell Inspiron7500. I need to switch off it.

Duh

and a System.arraycopy instead of the second loop?
like :
for (int i = 0; i < size; i++)
{
  System.arraycopy(source, 0, target, i*size, size);
}

as the source and the target have same type

Duh

Mik

Mojo you are right. (for the milkshape loader not enough time
)

Steve Pavlina writes some good articles about that:
http://www.dexterity.com/articles/

Princec where are you for the j2me edition?

Duh,

Mik

Ya it's messy that we can't subclass Layer class.
In fact The only solution is to rewrite a more powerfull LayerManager that accept ExtraLayer and derived basic Layer.

Duuh

Mik

great job guy  

ok, for the model that you are trying to load, could you give it to me? The best for such a problem, is to use in the same time a hex editor, and find the faulty bytes (and know how little and big endian works)

Ya, you need to rewrite all.I think i will do that,.

I found another bug in loadModelData changed to:

code changed to
     boolean loadModelData(InputStream is, long filesize)
     {
           // wrap a buffer to make reading more efficient (faster)
           DataInputStream dis = new DataInputStream(new BufferedInputStream(is));
           
           int fileSize = (int) filesize;  // Warning! File size trunctuated to 32bits!

           byte[] pBuffer = new byte[fileSize];
           try
           {
                 dis.readFully(pBuffer);
                 dis.close();
           }
           catch (IOException ioe)
           {
                 System.out.println("MilkshapeModel Error: Failed to read file contents.");
                 ioe.printStackTrace();
                 return false;
           }
...

1) A lots, ...

2) A lots, take a look at
forum.nokia.com
wireless.java.sun.com ((http://wireless.java.sun.com/device/index.html for a not so updated devices list)

3) goto 2) for some good examples for gaming
http://jfdoue.free.fr/index.html (a good starting point)

4) Fast graphics ... hum ... No direct pixels access on MIDP1.0, possible with MIDP2.0 Nokia UI, Siemens SDK, and , VSCL, Moto Game API. since MIDP2.0 is not widespreaded making J2ME applis is a bit complex.

I working on a SDK to simplify this process:
mee.dev.java.net

Duh,

Mik

ok, I think I have localize the bug, there is a bug in sully implementation of MS3DMaterial, it assume that the texture name is always 128 bytes long and use a System.arraycopy for copying from the buffer to m_texture.
And because Material Texture loading was the last operation it doesn't bug. But if you continue the process as you do, the pointer is wrong.
To bypass that you need to find the filename length, and change two arraycopy and also the MS3DMaterial sizeof according.
Not enough time to test, but I think it would do the job...

for the high value did you try without the multiply by 1000.

A float is only 4 bytes long   :
dataPointer += 4; // second line  

have you a link where I could see and test your code?

Not finished yet... Not enough time, this WeekEnd I will work on it.

Mik

In fact Eclipse don't integrate J2ME support.  What I do is using Ant and Antenna to bypass this limitation. antenna.sourceforge.net, and It work quit well.
Or use WebSphere Studio Device Developer, based on Eclipse.

Yes as MIDP2 is not really wide spread, J2ME game programming is quite a huge task to deploy on every cellphones.

So what to do?

- only focuses on one phone (like Nokia 70% of the Market)

- use standard MIDP1.0,  but problems are always here. For example PNG transparency on WTK1.04 doesn't work well. On SonyEricsson emulator it works but on the real device T610 not on certain PNG (lower than 256 colors) . Heap size problems are also a classic.

- Or use a SDK that wrap all this nasties problems and so one  code for all devices with optimizations for Nokia Siemens, Moto and soon Sharp GX1. I work on that : MEE http://mee.dev.java.net/

Mik

Duh, I fill stupid    

A new version is upload it checks for uppercase and lowercase, and see if the file exist.

Thx

Mik

ok so i will do that...

Yes that's right.

That's right OpenGL.

For culling:
gl.glCullFace(mode); // where mode could be GL_BACK, GL_FRONT or GL_FRONT_AND_BACK
and etc.

For transparency some methods exists using extensions:
http://developer.nvidia.com/view.asp?IO=Interactive_Order_Transparency

Or as Orangy, by separate opaque and transparent faces

For the skeletal animation, J3D doesn't do that too...

Ok I reply to myself ...

I need to create a sub project of games-games demos rights?

Mik

As I say in other thread, my nehe31 port is here:
miklabs.com/wip/nehe31.zip
I need feedback on Linux box...

Does a file sharing for demos or tutorials would exist to put this kind of stuffs?

I want to build a framework for demos, any suggestions?
As other members told me, a standardized reusable model need to be used. Some sort of Java3D subset?

Mik

No Problemo

Ya vector is hardcore or quit complexe to implements, I have tested some methods using flash or svg format not so smooth.

miklabs.com/wip for a sneak preview  

Mik

Ok I see what you want, a common framework. Not a new engine, but something standardized.

Not reinventing the wheel every time is a good thing. It is what I try to do in my current professionnal project MEE, by completly rewriting the 3D engine to be complaint with standard, like JOGL and JSR184 (JavaMobile3D)

If you want I will completly rewrite the nehe31 and the JOGL framework to a more java3D way... like using vecmaths, and other java3D paradigms. In fact I have already done that with my Quake3 map viewer, a cross over between Java3D and GL4Java.

No Problemo

Mik

Do you use a caterpillar to kill a ant?  

To display a simple cube you don't  need so much stuff  
Transparency and culling are not usefull for only drawing a simple model like Milkshape format.

The framework don't need to be very complex. See my nehe31 port.

I don't understand what you want to say?

But a engine is only some extensions for an API.

To write a 3D loader you need some base classes, like Vector3f, Triangle, Matrix, Joints, ,... to describe infos in the file. This classes are a small engine in fact, specific or not to this loader.

Yap Vector graphics is a cool way when you have direct access to pixeldatas like on MIDP2.0, Nokia, Siemens, GX10 and some Moto. But on pure MIDP1 it is a little harder and slower. Bresenham isn't the fastern a midpoint algo does best for speed.

My Engine MEE uses a wrapping system with Interfaces, and with a good optimizer and obfucator, these interfaces are replaced by classes for each targetted phones, using Ant.

Mik

No Problemo.
miklabs.com/wip/nehe31.zip

I have done a Linux test  of it and texture doesn't show.
I need more feedback for my port  on Linux...

Im working on a base code for other port and demos. So stay tuned.
I have in my folder a old code to compare speed between J3D and GL4Java, which display Quake3 map. Maybe I will work on that too.

But I don't have a lot time my Middleware project MEE, take me a lot of time:
- J2ME support for MIDP1 and MIDP2, Nokia, Moto and Siemens API using an interface wrapping.
- J2SE in the same way
- 2D multiscrolling, Isometric, Raycast.
- XML project description

And MM3D a full 3D for J2ME/J2SE thar I completly rewrite to be compatible with JOGL, and JSR184.

Mik