What is the difference between version 1.9 and version 1.8.4
What is the difference between version 1.9 and version 1.8.4
What is the difference between version 1.9 and version 1.8.4? And which is better?
Re: What is the difference between version 1.9 and version 1
You have to check changes.txt to see all the differences. 1.9 is still in developement, so there can be problems caused by that sometimes, but mostly it's better (it's the version I'm working with and if you report specific problems with 1.9 I tend to look at them, thought there are 2-3 open troubles I know about and haven't fixed yet).
IRC: #irrlicht on irc.libera.chat
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm
Re: What is the difference between version 1.9 and version 1
What are the flaws in version 1.9? What's left to finish ?
Re: What is the difference between version 1.9 and version 1
Known troubles:
- Demo D3d9 shadows broken since r4794
- rewrite of transparent handling has maybe caused problems. There's right now different isTransparent checks for different nodes and I'm not really sure why it was rewritten in the first place (there had been reasons, but somehow it doesn't look finished to me).
- Filename handling with some unicode characters is currently broken (trouble with certain russion filenames for example which got introduced while fixing another unicode bug)
- IRenderTarget rewrite has all kind of open stuff and needs another rewite. Especially right now we no longer have write access to other mip-map levels. So that interface will change again.
There's several stuff where I don't know yet if it is a problem or not. Like someone added SMaterial.BlendFactor but it's strange to use (expecting users to set MaterialTypeParam and BlendFactor to identical values) and I still have to figure out what that was about anyway. Or RTT's can't disable blendering, thought that was likely the same with 1.8 and maybe can't be avoided. There's reports about quaternion changes having broken something in animation, but no idea yet if that is true.
Lots of open problems with ogl-es branch which was planned to be merged. And original coders not around anymore.
Open todo's ... too many. Don't expect to see 1.9 anytime soon, it won't happen.
If you are evaluating the engine for a new project - right now I'd say - don't use it. Maybe it recovers from all the stuff that got broken with new features again at some point. But right now Irrlicht is stuck. I do what I need for my projects and try to keep up with bug-reports somewhat, but basically don't manage. Always getting more reports than I can handle and nearly all about stuff I didn't write. Unless one of the other coders which produced the changes comes back and helps out with his code it's looking bad for Irrlicht.
- Demo D3d9 shadows broken since r4794
- rewrite of transparent handling has maybe caused problems. There's right now different isTransparent checks for different nodes and I'm not really sure why it was rewritten in the first place (there had been reasons, but somehow it doesn't look finished to me).
- Filename handling with some unicode characters is currently broken (trouble with certain russion filenames for example which got introduced while fixing another unicode bug)
- IRenderTarget rewrite has all kind of open stuff and needs another rewite. Especially right now we no longer have write access to other mip-map levels. So that interface will change again.
There's several stuff where I don't know yet if it is a problem or not. Like someone added SMaterial.BlendFactor but it's strange to use (expecting users to set MaterialTypeParam and BlendFactor to identical values) and I still have to figure out what that was about anyway. Or RTT's can't disable blendering, thought that was likely the same with 1.8 and maybe can't be avoided. There's reports about quaternion changes having broken something in animation, but no idea yet if that is true.
Lots of open problems with ogl-es branch which was planned to be merged. And original coders not around anymore.
Open todo's ... too many. Don't expect to see 1.9 anytime soon, it won't happen.
If you are evaluating the engine for a new project - right now I'd say - don't use it. Maybe it recovers from all the stuff that got broken with new features again at some point. But right now Irrlicht is stuck. I do what I need for my projects and try to keep up with bug-reports somewhat, but basically don't manage. Always getting more reports than I can handle and nearly all about stuff I didn't write. Unless one of the other coders which produced the changes comes back and helps out with his code it's looking bad for Irrlicht.
IRC: #irrlicht on irc.libera.chat
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm
Code snippet repository: https://github.com/mzeilfelder/irr-playground-micha
Free racer made with Irrlicht: http://www.irrgheist.com/hcraftsource.htm
Re: What is the difference between version 1.9 and version 1
Thanks for reply!))CuteAlien wrote:Known troubles:
- Demo D3d9 shadows broken since r4794
- rewrite of transparent handling has maybe caused problems. There's right now different isTransparent checks for different nodes and I'm not really sure why it was rewritten in the first place (there had been reasons, but somehow it doesn't look finished to me).
- Filename handling with some unicode characters is currently broken (trouble with certain russion filenames for example which got introduced while fixing another unicode bug)
- IRenderTarget rewrite has all kind of open stuff and needs another rewite. Especially right now we no longer have write access to other mip-map levels. So that interface will change again.
There's several stuff where I don't know yet if it is a problem or not. Like someone added SMaterial.BlendFactor but it's strange to use (expecting users to set MaterialTypeParam and BlendFactor to identical values) and I still have to figure out what that was about anyway. Or RTT's can't disable blendering, thought that was likely the same with 1.8 and maybe can't be avoided. There's reports about quaternion changes having broken something in animation, but no idea yet if that is true.
Lots of open problems with ogl-es branch which was planned to be merged. And original coders not around anymore.
Open todo's ... too many. Don't expect to see 1.9 anytime soon, it won't happen.
If you are evaluating the engine for a new project - right now I'd say - don't use it. Maybe it recovers from all the stuff that got broken with new features again at some point. But right now Irrlicht is stuck. I do what I need for my projects and try to keep up with bug-reports somewhat, but basically don't manage. Always getting more reports than I can handle and nearly all about stuff I didn't write. Unless one of the other coders which produced the changes comes back and helps out with his code it's looking bad for Irrlicht.