CS vs Ogre3D, NebulaDevice

[Escorter]

If you a hardcore coder, I think OGRE is the best choice. If you have MSVC, and you looking for a commerical-quality engine, choose The Nebula Device. If you a beginner in game programming, and you want a great engine with lot of features, choose CS.

[jtarbox]

If you a hardcore coder, I think OGRE is the best choice. If you have MSVC, and you looking for a commerical-quality engine, choose The Nebula Device. If you a beginner in game programming, and you want a great engine with lot of features, choose CS.

Actually, OGRE is easier for beginners then CS is.

[Escorter]

It's easier, but it's just a 3D engine, while CS is a complete game engine.

[[SOM]Roberto]

OGRE is a very nice and easy-to-use rendering engine, but if you want to make a game, you need to integrate a sound system, script system, etc. I worked with it, and its a great stuff! The Nebula Device is a professional game engine, but you can't compile it with GNU tools under Windows. I think CS is great, but it has a very annoying "feature": millions of plugin DLLs (the most annoying - why need separate DLLs for Fire, Fountain, and Somke particle system? :S)

Ogre can mesh, texture and bone export only. Cs can bone animation, lightmap, multi shader, emit, hide, skymesh, refelctmask parallax, bump etc. in world file. Very cool. If u want, u using Ogre and u must implement all things etc. in your program. But I click in exporter with CS simpletely. Good luck!

[Escorter]

Yes, OGRE has a very poor Blender exporter. But it has a MUCH BETTER shader and particle system than CS...

[jorrit]

Yes, OGRE has a very poor Blender exporter. But it has a MUCH BETTER shader and particle system than CS...

Beter in what sense?

Greetings,

[Escorter]

OGRE can handle the standard ARB, CG and FX shaders, you don't need to learn a completely different shader system. It has a great particle system: the engine can load the *.particle files created with the particle editor (it's an user-friendly, easy to use, and powerfull editor). You don't need to hard-code the particle system to your world file.

[jorrit]

OGRE can handle the standard ARB, CG and FX shaders, you don't need to learn a completely different shader system.

Same as CS. CS handles ARB, CG, and FX shaders just as well. You just have to wrap them in CS specific XML stubs but the shaders as such are supported.

It has a great particle system: the engine can load the *.particle files created with the particle editor (it's an user-friendly, easy to use, and powerfull editor). You don't need to hard-code the particle system to your world file.

Ok, so you mean OGRE has a better particle editor. Not that the particle system as such is better.

Greetings,

[Escorter]

OGRE's particle system is better, because the *.particle file format. In CS, I can use the hard coded particle systems (fountain, fire, smoke), or I can create it with a ...ehh... not so great editor, then copy-and-paste it to my XML world file.

[jorrit]

OGRE's particle system is better, because the *.particle file format. In CS, you can use the hard coded particle systems (fountain, fire, smoke), or you can create it with a ...ehh... not so great editor, then copy-and-paste it to your XML world file.

Hmm? The 'particles' mesh is also very generic. It is not hardcoded at all. So how is the XML format of that worse then the OGRE particle format?

Greetings,

[Escorter]

So CS supports external particle scripts? E.g.: I make a particle spawn point in Blender, then I can attach a particle file (eg: smoke.xml) to it? And how can I save the particle scripts in partedit?

[jorrit]

So CS supports external particle scripts? E.g.: I make a particle spawn point in Blender, then I can attach a particle file (eg: smoke.xml) to it? And how can I save the particle scripts in partedit?

Yes, a particle system is a mesh like any other. And any mesh you can separate in a different xml file that you can include in a world file or create instances from in code. So basically you make an XML file describing the parameters of the particle system (or genmesh, or thing, or sprcal3d, ...) and then in code you make instances of that.

partedit is unfortunatelly only for the old 'emit' particle system. This is indeed one thing that could be better in CS. We need an editor for the new 'particles' mesh.

Greetings,

[Escorter]

Oh, it's cool! Are you planned to make a new particle editor for the new CS release?

[jorrit]

Oh, it's cool! Are you planned to make a new particle editor for the new CS release?

Well I have no personal plans for that as my todo list is already huge but I sure hope someone else volunteers for this task

Greetings,

[dingobloo]

OGRE can handle the standard ARB, CG and FX shaders, you don't need to learn a completely different shader system.

As jorrit said, CS supports those shader formats just uses an XML format for shader management allowing fallbacks and snippets and templates and conditional attributes to shaders, it makes using shaders more manageable, you can fallback to different shaders for different cards, you can modularise your shader for common features (like CS does with fog, and projected textures) so really, i don't see using JUST cg or ARG as a huge plus. The format isn't that complicated, especially if you do not need to use those extended features.