Life didn't quite co-operate...

I'll see what I can do in the next few weeks.  Writing up an applet for the thing should be a trivial task, because I built the thing with the idea in mind.

I've also got to dig it out of my archives...I've been moving around so much the past couple of months that I haven't worked on it since the semester ended.  Then there's the fact the computer I had been using for developing the project kindof lost it's hard drive to age (thankfully I was able to rescue 98% of my files before it gave up entirely).

I haven't pulled the project out of it's zip archives since then, but I'll see what I can whip together for you...

On a side note, I got an A on the project...

Progress Update:  Gravity works, and collisions do as well, with only mild bugs that I could fix with a little work.  Once those mild bugs are fixed, the only unrealistic thing will be that the numbers are rounded off somewhere around sixteen places to the right of the decimal...

In case anybody is interested, I've finished the collision and gravitational systems in my project.

I may have an applet demonstration soon.

When the scale() (it might also be getScale(), not sure which) method of Object3D is called, it prints the scaling value to the console.

I assume you accidentally left some denug code in, right?

It's really annoying.  It's keeping me from seeing my own debug printouts... (my program scales all objects in universe about 30 times a second)

You could call the method setColor() using a java.awt.Color object as a parameter, under the assumption that the alpha value is a part of the color.

If that's not descriptive enough, perhaps setTransparentColor() would work...

And if you provide both setAdditionalColor() and setTransparentColor(), setTransparentColor() could just call setAdditionalColor() and then set the transparency for the object.

Also, what do you mean by normals?
Remember, you're talking to someone that is illiterate when it comes to 3D rendering terminology...

I hope I'm not annoying you, but I have another idea, one I've actually been meaning to suggest since I looked closely at java.awt.color a couple of months ago.  I've just been forgeting to suggest...

Anyway, I was looking at java.awt.color and I noticed that all color objects have an alpha value associated with them that determines transparency.

I was wondering if setAdditionalColor() supports the alpha value.  If it doesn't use it, why not?  It seems a simple way to set both the color and the transparency of an object in one swoop...

I think it would be cool if it worked like that...

Thanx.

I could use a setSize() method on Object3D.

One that changes it to a particular size instead of having to mess around with changing the object back to it's original size first.

Thanks.

I need a way to iterate over all the Object3D's that are attached to a particular World instance.  I saw no way to do that in jPCT's API.
   I guess for now I'll just have to keep an external LinkedList to do this, but I just thought I'd make the request.  Preferably I would like to have an iterator object to work with.
   In addition, a method to remove all objects from a world would be extremely helpful to me.
On a side note (for curiousity's sake) I was wondering how does jPCT's World class store it's references to Object3D's?

Here is a screen shot of the most current version.  Right now it is just a simulation of real-world gravity.  Normally you would be able to see everything moving, but this is just a screen shot.

I'm doing an undergraduate research project using jPCT.

I'm working on creating a semi-realistic physical environment involoving real-world physics (Gravity, collisions, etc.) in space using only spherical objects (for simplicity's sake).

Once I have the minimum level of physics done (should be in a few weeks) I'll be moving on to inserting objects into the universe that mimic plants (photosynthesis).

I'll also be working on a background process that will mimic the effects of radiation exposure, altering the genetics of the life forms as they live their short lives (about five minutes).  This should allow evolution.

In this project, jPCT is being used just for the rendering of objects and life forms, so you can see them interacting with eachother.  Anything and everything else will be done as much as possible from the project's code, in order to divorce it from the renderer as much as possible.  That way, it could fairly easily be ported to another renderer (like Java3D for example, if you want hardware acceleration), or be left to run with little to no user interface, and a java applet used to view what's going on from another machine.