• 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.
  • entries
  • comments
  • views

Epoch Release 14 Finalization Plan

Sign in to follow this  
Followers 0


Last night at some unholy hour I finished a first pass at marshaling Epoch data back and forth across C-ABI boundaries. In less annoying terminology, this means that Epoch programs can do things like call Windows API functions, C-compatible APIs in other DLLs, and so on. More interestingly, those APIs can be given Epoch functions as callbacks, so there is seamless interoperability between C-compatible programs and Epoch programs.

This marks a great milestone in Epoch Release 14's development. There are now 58 compiler tests in the suite and all of them pass as fully native JIT compiled machine code.

As I mentioned previously, the last piece remaining to get Epoch fully-featured in native code is to implement the garbage collector. There are also some minor bugs related to Win32 interop that mean the raytracer demo is currently non-functional, so I probably have some work to do on the marshaling layer to get that all squared away.

My plan for Release 14 therefore looks something like this:

  • Fix whatever bugs remain in marshaling[/*]
  • Get the realtime raytracer benchmark running as 100% native code[/*]
  • Map out garbage collection implementation (will post on this later)[/*]
  • Implement garbage collection at least in basic form[/*]
  • Final compiler test suite and probably a test harness for ensuring garbage collection works properly[/*]
  • Package and ship R14[/*]

    Of course, if you've followed the Epoch project at all in the past, you probably know as well as I do that I rarely stick to my release plans, so we'll see how it goes :-)

    Once R14 ships, there's a few pieces I need to go back and hit. Here's the gist of what I'd like to do in the future with the language, in no particular order:

    • Better reference semantics for controlling object lifetime and interlinked data structures[/*]
    • Implementation of tasks (green threads)[/*]
    • Implementation of message passing model[/*]
    • Separate compilation and module support[/*]
    • Enhanced template support for better generic programming features[/*]
    • Namespace support[/*]
    • Native support for array types[/*]

      Naturally one of my big goals for the language moving forward is to build a self-hosting compiler and a proper IDE. Most of the above features are geared around making my life easier so I can actually accomplish those two projects. Of course, it may not be worth writing too many compiler features in the current system before moving to the self-hosting model...

      So (with the above caveat of not following my plans very well) I just might wind up working on self-hosting instead. It all kind of depends on how entertaining this stuff is and where my whimsy directs me.

      Another major thing I need to do that I have lamented about repeatedly is build a proper debugging facility for the native code model. Right now any bug in the code leads to lots of hunting through cryptic disassembly listings and requires a lot of painstaking effort. A proper debugger would probably fall under the Era IDE project heading, though, and thereby might wait a while. Even though I really need it.

      Anyways... lots of speculation but as always we'll just have to see what the future brings. I'm super excited about all this and really looking forward to getting the language to a point where I can write hardcore software in it.

      After all, that was kind of the point from day one :-)

Sign in to follow this  
Followers 0


How hard would it be to emit a little DWARF, and use LLDB as a temporary solution?


Writing the IDE prematurely just to get debugger support, seems like putting the cart before the horse...


Share this comment

Link to comment

AFAIK LLDB is not stable yet on Windows, which kind of screws me on that front.


Share this comment

Link to comment
Found and nuked a ton of marshaling and JIT issues tonight. The raytracer now runs as 100% native code, at about 25FPS with a sphere, plane, and shadow-casting all turned on.


Share this comment

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now