Hello,
I am here new here to Irrlicht. I last attempted any 'game development' back when Blitz3D was a thing. Since then I have just focused on my professional career which lead me down the Android path. Recently I have wanted to learn another programming language and while doing some research in my area on what is popular I decided to settle with C++. Now I am not one to sit down and watch Udemy videos or create small console applications which have no meaning, I thought I would try create a small game. After browsing the web for an 'easy' solution, Irrlicht kept cropping up, so here I am.
I managed to get everything built in a matter of seconds and have the examples running, so I guess those posts are correct, Irrlicht is easy!
I thought I will run through each example and take the concept and put it into my own project. When it comes to assets I am no artist so I don't mind buying a few models to play around with, could anyone tell me what file format is most common for animated meshes among Irrlicht users?
Mainchip
Hello
Re: Hello
Hello and welcome!
B3d and .X probably work the best. For other formats it might be worth checking out https://github.com/JLouis-B/IrrAssimp
I have no experience with that, but it might allow you to use more modern formats.
Tiny warning about Android... the ogl-es branch is not really maintained too much right now. I try to handle bug-reports, but there are some open problems (especially in Landscape mode). And I plan to release Irrlicht 1.9 before starting to work on that.
I released a game on Android with Irrlicht, so it can be used for that, but it's not tested as much as the PC versions. So some risk you have to dig into engine code once in a while to get things working.
B3d and .X probably work the best. For other formats it might be worth checking out https://github.com/JLouis-B/IrrAssimp
I have no experience with that, but it might allow you to use more modern formats.
Tiny warning about Android... the ogl-es branch is not really maintained too much right now. I try to handle bug-reports, but there are some open problems (especially in Landscape mode). And I plan to release Irrlicht 1.9 before starting to work on that.
I released a game on Android with Irrlicht, so it can be used for that, but it's not tested as much as the PC versions. So some risk you have to dig into engine code once in a while to get things working.
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: Hello
IrrAssimp will come in useful I am sure. The example looked easy to use but I failed to find any information on the formats it can work with.
Thanks for the heads up regarding Android. At the moment I am just interested in building for Linux. Is there a roadmap for 1.9, I would be interested to see what is being worked on.
Thanks for the heads up regarding Android. At the moment I am just interested in building for Linux. Is there a roadmap for 1.9, I would be interested to see what is being worked on.
Re: Hello
1.9 is overdue, so mainly some more bugfixing left.
- I recently broke some behavior of fps-cam in combination with window management on X11 and still try to find a fix (it fixed some other bug so don't want to revert unless I find no other way as camera is far smoother now).
- Only interface change still planned is some changes to IRenderTarget (that got rewritten since 1.8, but have to go over it once more to clean-up some minor stuff).
- One bug left with filename handling (caused by another bugfix, will only matter with stuff like cyrillic filenames on some platforms). While doing that will probably also fix some old bug in CFileList about changing upper/lowercase in filenames (instead of ignoring them in comparisons on Windows).
- Support-libs will be updated (jpeglib, bzip2).
- Could be naming scheme for dll changes before release (to have stuff like platform, compiler info, compiler target etc in the name - So something like Irrlichtx64D for a 64-bit debug version).
- And 2-3 other minor cleanups.
That's pretty much it. But will likely still take a few months (my hope is I manage it around summer...). And could be I decide to put 1-2 more things in it which are on my todo, thought probably that will all be moved to Irrlicht 1.10
- I recently broke some behavior of fps-cam in combination with window management on X11 and still try to find a fix (it fixed some other bug so don't want to revert unless I find no other way as camera is far smoother now).
- Only interface change still planned is some changes to IRenderTarget (that got rewritten since 1.8, but have to go over it once more to clean-up some minor stuff).
- One bug left with filename handling (caused by another bugfix, will only matter with stuff like cyrillic filenames on some platforms). While doing that will probably also fix some old bug in CFileList about changing upper/lowercase in filenames (instead of ignoring them in comparisons on Windows).
- Support-libs will be updated (jpeglib, bzip2).
- Could be naming scheme for dll changes before release (to have stuff like platform, compiler info, compiler target etc in the name - So something like Irrlichtx64D for a 64-bit debug version).
- And 2-3 other minor cleanups.
That's pretty much it. But will likely still take a few months (my hope is I manage it around summer...). And could be I decide to put 1-2 more things in it which are on my todo, thought probably that will all be moved to Irrlicht 1.10
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: Hello
that would be most appreciated! I currently delay load the dll files so that I can copy dll file around based on the build. this would be so much easier.Could be naming scheme for dll changes before release (to have stuff like platform, compiler info, compiler target etc in the name - So something like Irrlichtx64D for a 64-bit debug version).