Irrlicht Engine

If the __WORDSIZE check remains then the include should remain as well, otherwise it won't be defined under any circumstances unless a previously included header defined it.
Also i know the feeling about wasting time, totally not doing that by dealing with an os i don't even use instead of studying.

Btw, I too up until today didn't know anything about that, i've found it out by looking here https://sourceforge.net/p/predef/wiki/Home/, this page specifically https://sourceforge.net/p/predef/wiki/DataModels/. This piece of wiki is very useful .

For the inclusion, that's up to the compiler/implementation, as in any case__WORDSIZE isn't standard, if you see mac os sdk headers, you can see it clearly https://github.com/phracker/MacOSX-SDKs/blob/041600eda65c6a668f66cb7d56b7d1da3e8bcc93/MacOSX10.11.sdk/usr/include/limits.h this is limits.h of ...

Maybe a not so bad fix could be to make that check for __LP64__ or _LP64 being defined instead of _WORDSIZE, as in that case they would be defined by the compiler directly, rather than being imported by an header. Mac os headers for example check for the existence of __LP64__ to define _WORDSIZE #if ...

I'm building irrlicht 1.9 (even tho the issue shoudl also apply to older irrlicht) with xcode 9.2 on mac os 10.12 and I was having some linking issues when i tried to use utf8ToWchar and wcharToUtf8 inside CIrrDeviceOSX.mm, the issue was about the linker not managing to find the symbol ...

In 1.8 a material with material type of EMT_ONETEXTURE_BLEND was considered to be not transparent, whereas in 1.9 that material is considered transparent.
This breaks (at least from what it happened in my scenario) the usage of the depth buffer to draw those materials, as the drivers when ...

Creating patches - basically make a diff to current version of Irrlicht (or a specific one) and save it as patch. If you use svn you can get it with "svn diff". Then you can add the patch here: https://sourceforge.net/p/irrlicht/_list/tickets
Always good to mention for which revision it is ...

Thanks for answering and for that fix :D. So if I got it right, now the feature is also automatically disabled if the driver doesn't support it, right? In case I coudl try contacting that guy again to see if the check works properly and performances are stable even if ETCF_SUPPORT_VERTEXT_TEXTURE is ...

Hi, recently I released a new update of my application after upgrading it from irrlicht 1.8.4 to irrlicht 1.9 (as of the latest svn). I had encountered no issues with that when testing it out before switching the version but once released, I recieved reports from users that said that noew the game ...