Irrlicht 1.5 released!

Discuss about anything related to the Irrlicht Engine, or read announcements about any significant features or usage changes.
GameDude
Posts: 498
Joined: Thu May 24, 2007 12:24 am

Post by GameDude »

Nice Job. I just realized that there were quite a bit of changes, and I like the new and clean code. I also like how the tutorioals on the main page were updated, but I noticed that in the download package they weren't. Are they going to be updated for the next release? The tutorials I'm talking about.
hybrid
Admin
Posts: 14143
Joined: Wed Apr 19, 2006 9:20 pm
Location: Oldenburg(Oldb), Germany
Contact:

Post by hybrid »

Oh :oops: Could be that I forgot to copy those files to the repositories :lol:
Mirror
Posts: 218
Joined: Sat Dec 01, 2007 4:09 pm

Post by Mirror »

well done! Thank you all guys for the hard work and the efforts!
MasterGod
Posts: 2061
Joined: Fri May 25, 2007 8:06 pm
Location: Israel
Contact:

Post by MasterGod »

Great Job! Never cease to amaze us with your wonderful work.

I'm very glad to be part of this awesome community.

Good job everyone!
Image
Dev State: Abandoned (For now..)
Requirements Analysis Doc: ~87%
UML: ~0.5%
xsinick
Posts: 18
Joined: Fri Aug 10, 2007 12:05 am

Post by xsinick »

Joystick! :lol:
Revan1985
Posts: 89
Joined: Tue May 08, 2007 4:11 pm
Location: Italy

Post by Revan1985 »

little question...
the "# 32bit indices for large meshes" means that now we can use meshes larger than 65535, it's true?
CPU: AMD PHENOMII X6 1090T BE 3,2GHZ
RAM : OCZ 8GB 2*4GB DDR3 LOW VOLTAGE 1333
VGA: GeForce GTX680 2GB
HD : 500GB + 500GB + 2x1TB Raid Edition + 500GB External
Motherboard: ASUS CROSSHAIR FORMULA 4 890FX AM3
PSU: Corsair 750W
CPU Cooling: Katana 2
Mirror
Posts: 218
Joined: Sat Dec 01, 2007 4:09 pm

Post by Mirror »

Revan1985 wrote:little question...
the "# 32bit indices for large meshes" means that now we can use meshes larger than 65535, it's true?
yes! finally we can :D, actually AFAIK it is some kind of automatic, luke so called them "dynamic" meshbuffers, meaning that it automatically detects if it has less than 64k polys it uses 16bit if it has more it uses 32bit. correct me if i'm mistaken pls.
hybrid
Admin
Posts: 14143
Joined: Wed Apr 19, 2006 9:20 pm
Location: Oldenburg(Oldb), Germany
Contact:

Post by hybrid »

Well, it can be switched between those two modes, but as of now we only use this meshbuffer type in terrain scene node - with several bugs already showing up. So be aware that you can only use those meshes when builcing geometry manually, and you might face incompatibilites and previously unfound bugs...
Mirror
Posts: 218
Joined: Sat Dec 01, 2007 4:09 pm

Post by Mirror »

hybrid wrote:Well, it can be switched between those two modes, but as of now we only use this meshbuffer type in terrain scene node - with several bugs already showing up. So be aware that you can only use those meshes when builcing geometry manually, and you might face incompatibilites and previously unfound bugs...
hybrid, would moving to strictly 32bit without this dual approach iron out most [if not all] of these bugs ?
hybrid
Admin
Posts: 14143
Joined: Wed Apr 19, 2006 9:20 pm
Location: Oldenburg(Oldb), Germany
Contact:

Post by hybrid »

No, not at all, because the problems don't show up because of type mismatches, but due to lack of support of 32bit indices on some hardware etc. Moreover, using 32bit indices everywhere kills performance, as I've shown several times already. Not even thinking about our embedded and mobile system targets here...
Mel
Competition winner
Posts: 2292
Joined: Wed May 07, 2008 11:40 am
Location: Granada, Spain

Post by Mel »

65536 vertices can give quite a lot of polygons too. I really doubt that a mesh buffer, out of a particle system, would even use such amount.
"There is nothing truly useless, it always serves as a bad example". Arthur A. Schmitt
matgaw
Posts: 45
Joined: Sat Oct 06, 2007 11:33 am

Post by matgaw »

Mel wrote:65536 vertices can give quite a lot of polygons too. I really doubt that a mesh buffer, out of a particle system, would even use such amount.
Actually the terrain scene nodes use them frequently. 65k vertices bounds us to max (in practice) of 129x129 heightmaps. This is unsatisfying very frequently, as we would like to use 513x513 or even 1025x1025 almost all the time. So this has been an awaited feature.
Dorth
Posts: 931
Joined: Sat May 26, 2007 11:03 pm

Post by Dorth »

Why do I always feel as if I was the only one to think that small terrain patches are better? To split them up is a joke and it permits you to more easily do LOD, hide stuff, alter them, etc. There's just no real reasons to use a huge terrain unless someone else already did all the hiding, lod, etc. for you. But since there's no guarantee it'll match your needs, you're better off coding that yourself anyway.
cdrwolfe
Posts: 100
Joined: Thu Nov 15, 2007 5:38 pm
Location: Cranfield University

Post by cdrwolfe »

Now if only someone could port it over to Irrlicht.NET ;)

:D

Regards Wolfe
christianclavet
Posts: 1638
Joined: Mon Apr 30, 2007 3:24 am
Location: Montreal, CANADA
Contact:

Post by christianclavet »

Wow! Great!

I've just tested the demos one by one on my OS (Vista 64). Everything work perfectly. I didnt see any display errors!

I find that great that you updated the demos and added new ones (too few but its a very good start). The Shader demo didnt gave me error this time (Because MS removed support for old shaders)

Also great that we can have the tools already compiled (font, GUI and model viewer) compiled so we can check theses right away.

For Vista user, that's the most compatible version I've seen so far!
You've done a great job!
Post Reply