• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.

Archived

This topic is now archived and is closed to further replies.

Whirlwind

Where to put the game engine....

5 posts in this topic

I am logically laying out my game, and am debating where is the best place to put the game engine itself. I am thinking to put it in a DLL and the graphics engine in the main EXE file, since there probably will be a better chance of patches to the EXE itself, and if I want to go to a different engine, I just have to do a new EXE. Kind of a bizzare to look at it, but I hope to make the game modular enough so that I only have to alter the graphics engine and data files to create a new game. Of course then, I''d have to assume that I have embedded the menu options, etc in the graphics engine or in another DLL. The DLL''s I plan on doing alread are: AI, NET, and SOUND. I might add another for just reading data. I might be making this harder than what I should, but I want reusability, and hopefully portability by simply changing the graphics engine and recompilling the DLL''s.
0

Share this post


Link to post
Share on other sites
I think modularity is a great thing. I dont know much about dll''s, but if theyre like .so''s (shared objects) i think it would be cool to have the executable act like a client, and the dll''s like servers.

0

Share this post


Link to post
Share on other sites
I think it''s pretty easy to do DLLs, though I haven''t done it. Pretty useful if you need to patch your game, only have to replace one file.

The major benefit is if you load different DLLs at run-time depending on configuration. Such as a 3D wrapper for OpenGL, Glide, Direct3D and a software-renderer.

Also a nifty way to store AI code for each unit: .dat for graphics and such, .dll for implementation.

---
I personally am going the exact opposite direction. I''m planning to tac a compressed data file to the end of my EXE and make some smaller games that don''t require installation.

- n8








nathany.com
0

Share this post


Link to post
Share on other sites
the best place to put the game engine is in front, under the hood, unless you''re a VW engineer in which case you may consider putting it in the back.


--
Float like a butterfly, bite like a crocodile.

0

Share this post


Link to post
Share on other sites
DLL''s are easy, just do a DLL project under M$ VC++ and make sure that you point your main project to look for the DLL''s .exp and .lib files. When you embed the DLL as a subproject, just make sure that it is compiled before it is needed.

DLL''s are just M$ version of the .so file. I haven''t tried doing shared objects under linux, yet. I''ll do that when I have something tangible to port to it.
0

Share this post


Link to post
Share on other sites
I have been playing around with both ideas (engine in exe or dll) and my conclusion was that it doesn''t make any real difference.

The only thing is that if you keep the exe small and load the dll''s during initialization you are able to other things while the dll''s are loading such as showing a small animation or something like that. To do this the exe should not be anything else than a small file and everything else is put in dll''s.
0

Share this post


Link to post
Share on other sites