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

Blogpost about Java for Game Programming

8 posts in this topic

+1. That post about garbage collection and pooling is very informative. Keep adding more!

0

Share this post


Link to post
Share on other sites

Great post.  One thing that you might want to address on it though is the ease with which Java games can be modified through bytecode modification using libraries like ASM.  It certainly is not a deal breaker, and at the end of the day someone who wants to work hard enough will achieve the same results with games written in compiled languages, but might be worth just putting it out there for people who don't know about it.

0

Share this post


Link to post
Share on other sites

You first start worrying about someone hacking your bytecode and then you end up writing your games in some obscure OO framework for plain C.

 

EDIT: One thing, how exactly do you propose to handle FloatBuffers ? Some of them are kinda easy to reuse (ie, matrices, vectors) but the "heaviest" ones, meshes and things like that, aren't kinda what you'd easily set up for another object to use it.

Edited by TheChubu
0

Share this post


Link to post
Share on other sites

You first start worrying about someone hacking your bytecode and then you end up writing your games in some obscure OO framework for plain C.

 

EDIT: One thing, how exactly do you propose to handle FloatBuffers ? Some of them are kinda easy to reuse (ie, matrices, vectors) but the "heaviest" ones, meshes and things like that, aren't kinda what you'd easily set up for another object to use it.

 

Well there are always cases were you do not want the source easily accessible (things like protecting against piracy). But if you care about that, you're going to have to look for obfuscation tools (just like with almost any other language).

 

About the larger float buffers: most of the time you do not have to worry too much about them. Meshes are usually pretty constant during the duration of a level/map and only change during the map reload where the System.gc() usually takes care of the old ones. That is of course, if you do skinning/texture-animations etc in the shaders.

If you do edit meshes/textures/etc a lot on the CPU side of things, make sure you edit the buffers in place and only allocate a new buffer when it needs to grow (or maybe when it you need shrink it a lot).

I can also imagine that is some rare cases it could be useful to have some sort of buffer pool where you return the buffer that is the same size or the one that is the least amount bigger than the data you want to push to OpenGL.

 

Grts!

 

Peter

2

Share this post


Link to post
Share on other sites

All right. Now more on updating data and such... I have a barebones renderer right now, barely able to draw a heightmap, some soft shading, and a few more things. 

 

I have everything that needs to be sent to the GPU duplicated. Once in a regular float[] array and another in a FloatBuffer. So before sending it to the GPU, I update it (ie, grab float[] data, write it on the FloatBuffer) and make my draw call.

 

Now, this is done with a dirty flag. If you manipulate the array in some way, it gets "dirty" so the update call makes the copy to the buffer, otherwise it does nothing. Actually my math stuff is awfully coupled with OpenGL stuff since matrices and vectors contain both an array with the data and a lazily initializated buffer.

 

Anyway, point is, duplicate data. Do you write directly on the Float/Int/etc Buffers always or you have a "frontend" in the way of a regular array and then update it on a buffer?

 

I understand that Buffer objects have backing arrays already, but the direct buffers needed for OpenGL interop aren't guaranteed to have those.

Edited by TheChubu
0

Share this post


Link to post
Share on other sites

Well, we only use the buffers, there really is no need to have a separate array. The only downside is that you're not allowed to change the buffers during rendering (if your game is multi-threaded). If your mesh never changes, you can even forget about the buffer once you've created the VBO (but it is usually easier to have the buffer in memory as well).

2

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