Irrlicht Engine

Urrgh, dota, the bane of the map maker

fmx wrote:irrSimplePhysics will be updated, but I can't promise anything for anyone.
(that is if anyone even uses this... besides Pyritie)

Heh, I've moved to ogre, actually.

bitplane wrote:

Pyritie wrote:Urgh, I think you need a better artist. Those dragons look like crap to be honest.

Subjective opinion, some of us actually like programmer art

*points at sig*

:3

g0dsoft always 503's me. :<

Urgh, I think you need a better artist. Those dragons look like crap to be honest.

the integrate terrain system, Built in input handler, Built in official sound library, official importers for the most common format, It uses its own .mesh format but there are exporters for maya, 3ds max, and several others water scene node and stuff like this that are part of the official distrib...

Do you mean you're developing something with jirr using Eclipse as the JDK? Or what do you mean?

Why does irrlicht use the left-handed system anyway? Isn't the right-handed one much more popular?

Jirr's pretty good. It's very fast, much like irrlicht. Unfortunately it's still a version behind irrlicht so some new features in irrlicht aren't available in jirr yet. Hmm, is ogre slow? The .exe demos certainly weren't as fast as irrlicht's were. I tried both of their bsp loader demos. Ogre's had...

At the moment I've been taking a look at a java wrapper for OGRE. I've found several large holes in irrlicht which kinda showed that there are better graphics engines out there.

I've seen it used both ways. Irrlicht and Milkshape, for example, treat Y as "up" but 3ds max, Warcraft 3, and several others use Z as "up".

Seems to mostly be a matter of taste than anything.

It's in java so I dunno how useful this might be. Based on some code vitek posted a while ago. PViewer.receiver = my eventreceiver PViewer.elapsedTime elapsedTime = 1000000 * (timer2 - timer1) * (0.000001f / 30f); // in seconds timer1 = milliseconds before you draw the scene (at the beginning of the...

Almost done here. I'll just add averaging then I'll be done. :3

Mhh, I talked with bitplane over irc and it seems the most feasable way to do this is to stick every triangle in the mesh into a map and then use that to get the mesh triangle from the triangleselector triangle. Urgh.

I'll post the code when I'm done with this, in case anyone else wants it.