• 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.
Sign in to follow this  
Followers 0

[PATCH] POD members in object memory

2 posts in this topic

Inspecting some of the bytecode output from script class constructors one thing I noticed was that application POD classes were being allocated on the heap in their own little chunks of memory. This was mainly an issue for small things like 2d/3d vectors, rectangles, etc. The worst offender of it all being our 'Color' class - a shortcut for representing colors as 32-bit rgba integers which was being allocated into its own heap memory and adding a 64-bit pointer to the class.


The attached patch changes the behaviour of POD application class typed members to be stored directly in the object's allocated memory block instead. It passes angelscript's test suite, and we've been using it in our project for a few weeks now.


Feel free to use/alter if you're interested in using it.





Two small miscellaneous things that I'm going to shoehorn into this thread:


The test suite needs C++11 to compile, so the makefile needs to tell gcc to use it:

Index: sdk/tests/test_feature/projects/gnuc/makefile
--- sdk/tests/test_feature/projects/gnuc/makefile	(revision 1759)
+++ sdk/tests/test_feature/projects/gnuc/makefile	(working copy)
@@ -1,7 +1,7 @@
 # Test Framework GNUC makefile
 CXX = g++
-CXXFLAGS += -ggdb -I../../../../angelscript/include -Wno-missing-field-initializers
+CXXFLAGS += -std=c++11 -ggdb -I../../../../angelscript/include -Wno-missing-field-initializers
 SRCDIR = ../../source
 OBJDIR = obj

Also, there's a problem with the context used in ScriptObjectFactory: if script engine A calls an application function that wants to create a script object in script engine B, ScriptObjectFactory will nest into the context from engine A, creating a crash. This occurred in some of our cross-engine communication functions. We added a check to not use nesting if the active context is from a different engine, but there should probably be a way for the application to provide asIScriptEngine::CreateScriptObject() with the context to use for the call since creating contexts is expensive.

Index: sdk/angelscript/source/as_scriptobject.cpp
--- sdk/angelscript/source/as_scriptobject.cpp	(revision 1759)
+++ sdk/angelscript/source/as_scriptobject.cpp	(working copy)
@@ -53,12 +53,17 @@
 	ctx = asGetActiveContext();
 	if( ctx )
-		r = ctx->PushState();
+		if( ctx->GetEngine() == engine )
+		{
+			r = ctx->PushState();
-		// It may not always be possible to reuse the current context, 
-		// in which case we'll have to create a new one any way.
-		if( r == asSUCCESS )
-			isNested = true;
+			// It may not always be possible to reuse the current context, 
+			// in which case we'll have to create a new one any way.
+			if( r == asSUCCESS )
+				isNested = true;
+			else
+				ctx = 0;
+		}
 			ctx = 0;


Share this post

Link to post
Share on other sites

I haven't even completely integrated your previous patch yet and here you're providing another one. :)


Changing the code to allocate the value types inline has been on my to-do list for quite some time. Thanks a lot for saving this time for me. 


I'll probably not include this for 2.28.0 which is near completion, but I'll definitely look into adding it for the next release after that.


Share this post

Link to post
Share on other sites

I've included this patch in revision 1799.


You seem to have a really good grasp of the internal workings of AngelScript. :)


Share this post

Link to post
Share on other sites

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
Sign in to follow this  
Followers 0