Why use a 3D engine
Here are 6 reasons why using a 3D engine is not an option, but a MUST.
1.
{Simple fact}. Every game that is released today has an engine behind it. Developing your own proprietary engine will take years, and then no one guarantees that your engine will be able to compete against the rest.
2.
{There’s no choice}. The engines that come with the hardware APIs don’t deliver good performances. For example, the Direct3D Retained Mode engine is very weak and is not capable of dealing with large worlds efficiently. You won’t see any leading games built on top of it. Glide is just an interface to hardware with no engine behind it.
3.
{There’s no choice (2)}. The market of 3D accelerators and API is undergoing rapid changes. Each month we hear about the new king of 3D accelerators. API wars are causing lots of changes. MiniGL out, ICD in, DirectX 7.0 out, Direct8.1 in. Glide2x out, Glide3x in (though it will be out very shortly), OpenGL 1.2 1.1 etc. …
If you have to spend your time testing your code on dozens of different 3D accelerator cards, you won’t have time to make the game itself. By the time you finish your game, the industry could look completely different. You need someone else to take care of those details. You've got to spend your time on the actual development!!!
4.
Development speed (1) A good 3D engine resolves all the ugly details of 3D API programming without sacrificing performance. Becoming an expert with even just one API takes time and patience. If you are not yet familiar with the 3D APIs, we strongly suggest that you take this informative tour:
Acquaint yourself with Direct3D IUnknown interface and DirectDraw surfaces, IID_IDirect3DTexture2, LPDIRECT3DVIEWPORT3, etc. Try to make some sample code, using Glide, that uses more than 4MB of textures; not to mention the case where some of the textures are bigger than 256*256. Try to make your Glide sample run on Voodoo3, as well as on Voodoo2, and as well as on Voodoo Bunshe (No, it is not just grSstWinOpen() ). Of course don’t forget to print-out OpenGl spec 1.2.1 Make a small mipmapping sample. Make it work with cards that have just the MiniGl drivers and those who have a full ICD driver.
5.
Development speed (2) Even if you are already an expert with the 3D APIs, you still have to develop a smart engine on top of it. That’s exactly what we’ve been doing for the past four years. So take it. It’s debugged and it's working extremely well.
Alternatively, you can take your time and start doing your own research on: binary space algorithms, surface caching, physics and kinematics, texture memory management, software rendering etc …
6.
Development speed (3) A good 3D engine SDK comes with a pack of tools that ensure a smooth development process. GUI based tools can decrease development time significantly. Many programming tasks are replaced with the ease of drag-and-drop functionality. If you try to tailor your own SDK package, i.e. take a 3D engine from vendor X and the World Builder from vendor Y, terrain generation program from vendor Z , you soon discover that you have to spend lots of time on import / export issues, trying to find out why your beautiful models from 3DS look so bad now in DirectX (X files) format etc…
هذا منقول من احد مواقع 3d engine
من ناحيتي اراها مقنعة لني لم اكن مقتنع بها والدليل الرد المقتبس الذي كتبته في احد المواضيع:
اقتباس:
الكريستال:
انا معك في صعوبة التعامل ولاكنها ليس بالصعوبة التي وصفتها
ولا احبذ التعامل مع مكتبات اخرى طالما عندي القدرة على البرمجة والتعامل مع الدايركت اكس مباشرة
فلذلك عملت مكتبة مساعدة خاصة بي وقاعد اعمل عليها
ولمن اخلص من الاشياء الاساسية التي بها راح ارفق امثلة للعمل عليها
والكلام المكتوب بالحمر سبب تحولياقتباس:
prg of rpg:
نعم أنا بعقدت شوي بس المكتبات الأجنبية تدعمها وبالرغم من أنها مجانية
يعني بإختصار سنتين قليلة حتى توصل لمكتبة قادرة على الوقوف أمامها
أنا حاولت أسوي مكتبة خاصة بس مليت أشتغل بلحالي
راح استعمل محرك 3d
ولن اقطع هدفي في عمل محرك 3d عربي الصنع (CGE)
