0.14.0
-
- Posts: 142
- Joined: Sat Dec 11, 2004 8:13 am
- Contact:
Some bugs i've posted in the bug forum as well.
Collision response animators are affected by invisible nodes now, which isnt good, and i've got some pretty wacky behavior with getTransformedBoundingBox on my buildings (just scaled cubes, but being very wacky)
http://irrlicht.sourceforge.net/phpBB2/ ... hp?t=10099
http://irrlicht.sourceforge.net/phpBB2/ ... hp?t=10097
Collision response animators are affected by invisible nodes now, which isnt good, and i've got some pretty wacky behavior with getTransformedBoundingBox on my buildings (just scaled cubes, but being very wacky)
http://irrlicht.sourceforge.net/phpBB2/ ... hp?t=10099
http://irrlicht.sourceforge.net/phpBB2/ ... hp?t=10097
patches under:
http://irrlicht.sourceforge.net/phpBB2/ ... hp?t=10107
http://irrlicht.sourceforge.net/phpBB2/ ... hp?t=10105
cheers,
http://irrlicht.sourceforge.net/phpBB2/ ... hp?t=10107
http://irrlicht.sourceforge.net/phpBB2/ ... hp?t=10105
cheers,
terefang
nVidia 7800GT/256, AMD64-X2 4k2, Latest Fedora/CentOS
nVidia 7800GT/256, AMD64-X2 4k2, Latest Fedora/CentOS
The new release sounds very promising and the new features as well (although i think that a software renderer is for the most ppl not so important).
There are still some "low-level" bugs which need to be fixed, like the ones in rect::getWidth and rect::getHight.
Also, many functions need to polished and code-reviewed. Some implementations need to be reworked performance-wise.
Imho "stability" and "performance" are more important than new features.
There are still some "low-level" bugs which need to be fixed, like the ones in rect::getWidth and rect::getHight.
Also, many functions need to polished and code-reviewed. Some implementations need to be reworked performance-wise.
Imho "stability" and "performance" are more important than new features.
oh an Atic - do you think it may be useful for you to start a thread "Important / functional / performance bugs that need fixing" so that they can all be listed in one place.. and a casual reader can see
a.if it is important to their project
b.if they can fix it themselves if needs be (and send code to Niko)
Because I agree that now we really need to squash those bugs and performance problems that are holding it back before looking at any new features
a.if it is important to their project
b.if they can fix it themselves if needs be (and send code to Niko)
Because I agree that now we really need to squash those bugs and performance problems that are holding it back before looking at any new features
Done.. I added two pages to the main page of the wiki for notes about the Irrlicht Releases. Time to start filling them.hybrid wrote:I think I saw such lists comming up from time to time, but usually they disappear quite fast after some days. It'd be probably best to make such an overview in the Irrlicht wiki such that everyone can edit the list and all information stays properly structured.
http://irrforge.org/index.php/Irrlicht0.12Release
http://irrforge.org/index.php/Irrlicht0.14Release
Crud, how do I do this again?
I have an account for the wiki - I wanted to add some (And some custom code /fixes in other areas).. but colour me stupid I just don't know how to "Use" a wiki to edit it - do I really have access to a page?
I know it sounds strange 5+ years with C++ but can't edit a wiki, give me some newb tips here people
I know it sounds strange 5+ years with C++ but can't edit a wiki, give me some newb tips here people
well to be honest i think the new release just sucks :/ terrain is messed up for me (why do i have to scale the terrain 10 times bigger like with irrlicht 0.12? also i get very _heavy_ Z-fighting issues when enabling dynamic lights or fog for the terrain, and without it it looks just bad. i get 20fps less than before and the iterator stuff is dumb too...)
i´ll just stick with irrlicht-012 then for the rest of my project it works without any major problems
i´ll just stick with irrlicht-012 then for the rest of my project it works without any major problems