• 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

471 Neutral

About jbb

  • Rank
  1. As I posted already I don't really care about layout oriented standards. There are some i like better than others but I'll adopt whatever I'm required to with minor grumbling. More important are standards for the code itsself. Consistent ways of allocating memory. Consistent ways of using threads (Do we use queues, do we "ban" shared data?) Consistent ways of passing data. Do we prefer pass by pointer? Or reference? Do we prefer to allocate memory and pass it into a function to use like in C or do we let objects handle their own memory? Do we like shared pointers or do we prefer other ways to manage things? I find all of that matters more than layout but again, as long as it's not insane I don't much care the details. And then standards for accepting code? Do we insist on actual proper code reviews? Do we properly document what the changes are _for_ in source control and do we have one functional change per commit so we can manage them? How is code deployed? Do we need to write a backout plan for each change in case it fails to work in production... These things matter more than the detail
  2. > (this applies to everyone posting here, as many have explained what they like to do but not how they would be bothered going against that)   I think it's difficult to answer that as an abstract question. Generally I'm not that bothered, there are things way more important than where braces and upper case letters go. But it depends on the specifics. Mostly I don't like the coding standards where I work but I accept them and it doesn't really bother me. But there are just a couple of things I find very hard to comply with :P I do though, and don't get upset about it.
  3. These things used to matter to me. Now I got older and worked in more places i find myself caring less and less about the details. As long as the rules are somewhat consistent and applied properly i don't really care. The are more important things to worry about like writing correct elegant performant code to be bothered how we have to spell class names this week. I don't really care about brace placement as long as we have a scheme. I prefer not to have a C prefix on classes because its ugly and doesn't tell you much you can't infer from the code without it. I slightly like m_ because it tells you at a glance if the thing you updated is a temporary local thing or if it will persist... but none of them are deal breakers
  4. Thanks again all. ?Based on the comments I'm not going to try to support multiple windows :) My project doesn't need them anyway. My problem is that I identified 'Window' as being a good abstraction of something I'd need my application to have and a common one. And once I did that it because natural to ask does it make sense to have more than one window in an application.... Yes, it makes sense. And then the issue of how to implement it nagged and nagged at me leading to complete coding paralysis!   I have decided that I have no need to implement multiple windows/contexts in my project so I will not do. ?Having decided that it seems natural to merge window and context management into my 'Game' class as they don't really need their own identity and it's natural to have a single "Game" object created in a program but not so much a 'Window'
  5. Thanks everyone. I don't actually need this at all. As they say, I'm trying to make a game, not a general purpose engine, but it's always nice to separate components where possible and effective, so it seemed right to make a Window class which naturally lead to thinking what if the user makes more than one. Well my game isn't going to, and it looks tricky, so I'll probably come up with an alternative interface that assumes only one "window", precluding the question even arising. Still a useful discussion for me anyway, as it's lead to me looking into and understanding renderbuffers and fbo's and why I might use one :)
  6. Thanks, i looked into it now :) That makes a lot of sense and makes things very much easier as I can basically pick a single pixel format and use that for all my windows and hard code it and forget about all this. Hmm, does that mean I need a depth buffer on my render buffer and don't need to create my window with one...
  7. If I want to use multsampling on the output, don't I have to create a multisampled pixel format? Or are you saying I can create a multisampled render-to-texture and render to that, and then somehow copy that to the display? Won't that be slow?
  8. How do people manage multiple opengl contexts, if in fact they do? My code has a 'Window' class, so, in theory at least, you can create two or more windows. Each window can have it's own pixel format and opengl context due to the way it works. Now the problem is that before making *every* call to opengl I have to check that the current gl context is the correct one, and if not do wglMakeCurrent to switch to it. Or else I have to make a function on 'Window' called something like 'makeActive' before I do any opengl operations on it. And be sure to always remember to do this. My question is how do people cope with this? Is doing this very slow? Or do people generally not support more than one context in a program? Secondly, it seems that on windows at least, you have to call opengl functions via function pointers obtained from wglGetProcAddress and those pointers can be *different* for each context if they have different pixel formats. I am using multisampled output window in my main window and intend in a debug mode to have a separate window that doesn't need to have that so I *will* be having different pixel formats. So I can't just slap them into a lot of global variables. How do people cope with this? Or do people in general decide that supporting multiple windows is more effort than it's worth and find alternative solutions?
  9. OpenGL

    Will it be possible to build a reasonably good version of opengl interface implemented on top of vulkan? I'm thinking that vulkan is supposed to be easier and smaller to implement than opengl so is less likely to have subtle bugs, and then if opengl can be implemented on top of it then the same opengl library can be shared across different hardware providers meaning that they are more likely to have the same bugs & features.  
  10. Ah yes, that makes a great deal more sense. So I can just keep a "pool" of buffers for each constant buffer and reuse them as the API finished with them. I guess D3D11 is doing this behind the scenes for me anyway
  11. My understanding then is that I need to create all buffers in my DX11 code fully initialized at create time and never overwrite them then? That if I want to charge the value I create a new buffer with the new contents? If that's correct how do I handle constant buffers that I need to change every frame? Create a new one every frame? That seems expensive?
  12. Thanks! Ok thanks for the comments on resources too. I can likely change my d3d11 code to work closer to that way too without any great loss.  
  13. Although I'm a professional C++ program my 3d stuff is strictly hobby only so I'm doing mostly what I enjoy rather than what makes sense commercially :) 1) Although I'm working with directx11 at the moment I keep an eye on opengl and I'm ensuring that I could fairly easily port my drawing code to opengl if I wish in future. I would like to port to directx12 when it's practical to do so. So I want to make sure I structure my code is such as way as to make it easy/efficient to do so. My understanding is that the main difference is that direct3d12 is stateless. That I need to submit all the render states, all the buffer mappings, all the texture mapping etc. in each rendering command at least conceptually. So I ought to organize my code that way now and ensure that my rending commands contain everything needed for the draw call (Buffers to map, Constants to set, Which render state set to use etc). Is this correct and is it sufficient? Basically is there anything else I need to do in organizing my code to facilitate later porting to D3D12? I don't mean detail of using the API as much as how to organize the higher level code to facilitate it 2) I see some slightly older graphics cards only advertise directx 11 support even now. Are these still usable through the directx 12 API in the same way that you can use directx 9 cards through the directx11 api with a reduced feature set? Or will they not work and I'll have to have a separate directx11 interface if I want to support them? (This all assumes that relevent driver support is still available for them of course). Thanks!
  14. After considering this some more I realized there isn't a code issue here, the issue is that I'm trying to design my game too much "bottom up" without considering how the low level compents will be used. it's clear now that I'll have some kind of "Level" class which represents one game level or world and that will load all of the ressources that items within it need when it is created and release them when it is destroyed. No real need to reference count or track usage. Just create everything on startup and release it on destruction. Other subsystems such as UI do similar with their own lifetimes. I guess the issue here is the one that people mention. Trying to build an "engine" rather than a game without having the previoius experience to understant how the engine will be used. (Not building an engine on purpose, its just how it works out if you do bottom up design only).
  15. Well, std::shared_ptr generally uses a mutex when you copy or destuct them which never is going to be fast. But point taken...