Why wont you change that feature on jpct?

Because it will break all existing code and doesn't really gain you anything except for giving you the gut feeling that it's somehow "better" that way. One thing i really hate about non-commercial software (may it be open source or not) is when the API constantly changes without adding new functionality, i.e. when the only reason for a change is to make the developers of the API feel better.
But i may add such Wrapper as an option and put it into the util-package. I haven't done this until now, because nobody ever complained about it and because such a wrapper is drop dead simple to write by yourself if needed.

I suppose there is a way to redefine this limit but I wasn t able to find it.
How to do that?

Set Config.maxLights to a higher value before instantiating a World.

Glad to see you back in business... :wink: Your planned approach sounds reasonable to me. Just make sure to keep things as complex as needed but as simple as possible. Things will grow in complexity anyway...(for example, Paradroidz proof of concept version started with 4 classes, now i'm at 163 and counting...).

it would be nice though if you could create an applet using the software-based renderer, but have an optional download to plugin a hardware-based renderer, so the the same software runs in either way.

I don't quite understand...you can already do that!

Sorry to hear that Personally, i don't spend days or even weeks drawing UML diagrams and designing stuff to the death. I usually know the goal that i want to achieve and i have a rough idea of how to do it before i start coding.  When i'm thinking too much about design, i usually complicate things more than needed.  For example, Paradroidz first design was overcomplicated. It made sense on paper and it would have done so even in code, if the code would have been used in the way it was planned to...but it wasn't.
Designing too much leads to too much "what if"-thinking IMHO: "What if i want to do this or that in the future or what if my game objects should start cleaning the kitchen or cooking some coffee one day...i should take care of that too...or maybe i want to render them on a line printer one day, so i should introduce another rendering abstraction layer...". That's BS. I like the part of the "Extreme Programming"-philosophy where it says: "Code what's needed, not more. Refactor if needed." That's basically what i'm doing with Paradroidz. That's NOT what i'm doing with jPCT. jPCT's design is years old. It should be refactored for some parts and i would do that, if i were the only person using it. But i'm not and i really don't want to break other people's code (because i HATE it, when this happens to me) justto  make me feel better. In the end, it doesn't matter at all.
However, what works for me doesn't have to work for everybody else and these things lead to very emotional discussions (even more than the great question: "Where to put the brackets?"... :wink: ) most of the time. Do what works for you. If you do and if you finish at least something, you already did a lot better than people who are just talking about things...
About the art department: I'm not very good at art, i.e. drawing textures, making models...i could do better than i'm currently doing with Paradroidz, but i don't want to spend the time needed. A skilled artist would be multiple times faster than me (and with better results) That's why i'm currently looking for an artist to improve the look of the models at least. And to make sure that he delivers, i'll pay him for his work. Not much of course, because Paradroidz is freeware, but anyway...
What else can i say...don't give up just because it isn't fun all the time. There are soooo many abandoned projects on the net...too many if you ask me. The people who are actually getting things done are very very few... :cry:

I've moved this thread to support...anyway: The loader loads polygonal objects only (this is stated somewhere...if not in the javadocs, it may be in the "manual"). That is why straight lines don't show for example. There is simply no matching primitive in jPCT to show them. I don't know about the bevel as i don't know how this works in 3DS Max and what the exporter does with it.
You may want to try to export the model into another format (good old ASC for example, which most likely doesn't support bevel so that it has to be converted to a polygonal representation), reimport it into Max and save it as a 3DS again. Maybe that helps.

BTW: If you are still using the version from Feb. 2004, you should really upgrade. It may not fix the 3DS problem, but it fixes a lot of other stuff...

It was just an example. tempObject3D.setName(nombresMapas ); is better?