• 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.


  • Content count

  • Joined

  • Last visited

Community Reputation

488 Neutral

About ThyReaper

  • Rank
  1.   1) It produces native x86 instructions with fallback to the VM under various conditions (some specific types of calls it can't handle natively, script exceptions, and any new ops that might be added since it was last updated).   2) The JIT requests a page from the OS which can be set to be executable. There is a rather simple class, CodePage, which is responsible for this allocation and can easily be changed. The JIT does expect that new code pages can be allocated dynamically, but a single large static page should be sufficient for most purposes. Jumping to the executable page is handled by the JIT instructions in the VM.   3) Native code runs between 2x and 10x faster depending on the exact code being executed and the architecture involved.
  2. That's my limited understanding as well, and I believe the JIT does satisfy that requirement as long as its allocator does as well (though that could be replaced with a suitable allocator if needed).
  3. If it would be possible for you to use our JIT, it would be fairly simple to add a custom line callback to it which caches the line number for each call. I'm not sure exactly what requirements exist for a real time program, but the JIT's behavior is simpler than most of what AngelScript's own compiler has to do.
  4. Here's a brief explanation of the differences:  Foo@ a, b; Foo c; //These compare the value of the referenced instances, typically via opCmp() a == b; a == c; c == b; //These compare handles (pointers) for equality @a == @b; a is b; a is c;
  5. Fixed.
  6. In the future, please report issues with the JIT to the github page. I only check this forum occasionally, while the github page will notify me of new issues.   It looks like the function call being made for the FREE is larger than expected. I'll fix this shortly.
  7.   I'm aware of at least one project on Mac that uses our JIT, though they use GCC. If you use a different compiler it might take a fair amount of work to add support for it.     Looks like that change is simple enough to use a fallback for, at least temporarily. I'll also add native support for power operators at the same time.   Edit: While implementing the power ops, I noticed that overflow isn't detected when constants are resolved (e.g. 500 ** 3000 becomes 0 or #.INF depending, without printing a warning).
  8.   There are relatively few changes to Angelscript that require us to update the JIT. Most changes affect how the bytecode is assembled, rather than what a specific bytecode does. When new bytecodes are added, the JIT also falls back to Angelscript execution so it can continue to work. Most bytecode changes are relatively simple and I can easily keep it up to date.   Due to this, the last updated version is just a guarantee of what version works, not an indicator that other versions don't work.
  9. If you're not using a custom assert(), then lines like assert( pEngine->RegisterObjectType("CScriptComponent2d", 0, asOBJ_REF|asOBJ_NOCOUNT) > -1 ); Turn into something like this in release: (void)0; Asserts are intended to only be run in debug code.   I suggest rewriting your lines like this: { int r= pEngine->RegisterObjectType("CScriptComponent2d", 0, asOBJ_REF|asOBJ_NOCOUNT); assert(r > -1 ); }
  10. If 'myType' needs to be garbage collected, or might need to be garbage collected (not sure of the exact logic for arrays), the array will also be garbage collected. The GC will hold a reference to whatever was added to it until the GC decides it can be deleted.
  11. Array access in Angelscript is fairly slow, as each access is a function call. I believe Angelscript recently added fixed array access which would be a good fit for matrices, and should run much faster.
  12. While the compiler could deduce that aptr[1] is a null pointer access, it is valid to have array handles and to access them in that way.
  13. I discovered a bottleneck in the cleanup process in AngelScript which caused our game to take much longer to shutdown than expected. It seems that all the time was being spent in ClearUnusedTypes() which used a linear search for removing types.   I replaced the vector with a set (emulated with a map, to be able to use the same data structures the library normally uses), removing the bottleneck. We've been using this change for a few weeks without issue.
  14. Your registration is asOBJ_APP_CLASS_CDAK, but it looks like you didn't register an assignment. Any mismatch in these flags tends to cause strange behavior, but I'm not sure if any assignments would be used for this code. The asOBJ_POD flag may also be conflicting here.
  15. I'm not aware of any recent benchmarks compared to LuaJIT, but in the project I work on, using our JIT (https://github.com/BlindMindStudios/AngelScript-JIT-Compiler), we typically achieve performance roughly 2x-3x slower than comparable C++, and at least 2x faster than general AngelScript, with specific tasks going much faster and almost as fast as native C++.