hi great engin i love it to bits its so simple to code with it. its a dream to work with but i have used outher engine and say like the BSP demo
same map on orge engin give like nerly 400 fps but is a god dam sone of a %$&$&% to work with.
i can only reach 170 / 200 fps at best on this one
is ther way to speed this engin coz i love it and id like to use this one
will you be doing updates to this engin and maybe speed up in the futre that will just clip in or just change .DLL file.
Engine is Great any speed ups
Well, it really depends on your computer. I tryed ogre, and i got about 40fps on that, and about 300fps using irrlicht! If you change stuff in the source (like change texture to 32bit) you can get better, or worse results, it all just really depends. I'd say stick with irrlicht! Ogre is on the LGPL, meaning you have to also give out the source code to whatever you are making, and with irrlicht, you can keep the source code to yourself. Ogre has a huge mess of a source code, this is because it is an 'open-source' project, meaning other people contribute to it. On irrlicht, however, it is a one-man project, so it has MUCH cleaner and EASYER source code.
"Please do not read this quote. Thank you."
-
Robomaniac
- Posts: 602
- Joined: Sat Aug 23, 2003 2:03 am
- Location: Pottstown, PA
- Contact:
Some corrections to what you've stated:
1) "Ogre is on the LGPL, meaning you have to also give out the source code to whatever you are making, and with irrlicht, you can keep the source code to yourself"
-- This is false. You only have to release the source to your project if it is a derivative of the Ogre Engine, for example a change to the engine, or an addon to the engine, not a project that utilizes the engine itself.
2) "Ogre has a huge mess of a source code, this is because it is an 'open-source' project, meaning other people contribute to it."
-- Every change to ogre, file additions and stuff, has to go through the core development team, which does a very good job at sifting through the changes and not adding anything unneccessary. Its a big source code because its a big project, with lots of parts.
3) "On irrlicht, however, it is a one-man project, so it has MUCH cleaner and EASYER source code."
-- The ogre source is extremely clean, and easy to work with as long as you know the basics of graphics engines
1) "Ogre is on the LGPL, meaning you have to also give out the source code to whatever you are making, and with irrlicht, you can keep the source code to yourself"
-- This is false. You only have to release the source to your project if it is a derivative of the Ogre Engine, for example a change to the engine, or an addon to the engine, not a project that utilizes the engine itself.
2) "Ogre has a huge mess of a source code, this is because it is an 'open-source' project, meaning other people contribute to it."
-- Every change to ogre, file additions and stuff, has to go through the core development team, which does a very good job at sifting through the changes and not adding anything unneccessary. Its a big source code because its a big project, with lots of parts.
3) "On irrlicht, however, it is a one-man project, so it has MUCH cleaner and EASYER source code."
-- The ogre source is extremely clean, and easy to work with as long as you know the basics of graphics engines
I have to follow Robo on this one. Ogre's source is huge but programmed very clean and OO-wise. The fact that there are ten to hundred people working on it, is a big pro if you ask me. Another thing I like about Ogre: everyone's on IRC. You need to talk to the core development team? Join the IRC-channel and ask...
I'm off playing with 1.0RC1
.
I'm off playing with 1.0RC1
.