• 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

  • Days Won


jpetrie last won the day on July 18

jpetrie had the most liked content!

Community Reputation

13073 Excellent

About jpetrie

  • Rank
    Moderator - For Beginners

Personal Information

  1. I do. The advice is "get a lawyer." It's probably not as expensive as you are assuming, and asking one for information about how much it would cost is free. Be sure to review any legal agreements you have already signed with your school. Often those agreements (which you'd have signed back when you applied or matriculated) encumber any intellectual property you create during your time there, so it's not "just your buddies" that you'd be dealing with legally. And in event approaching things less seriously because it's just a bunch of friends is dangerous anyway.
  2. I couldn't tell you, as I've never done anything beyond launch Unity and quit it on any of my machines. It's possible somebody else may be able to chime in though. I'd still just give it a shot and see.
  3. I'm not sure at all. If you get the low-end model (as far as RAM is concerned), I've have my doubts. If you get as much RAM as you can, I'd be less doubtful. I don't use Unreal outside of work so I don't have first-hand experience with how well it runs on laptop specs. I also work on games that are significantly more complex than the ones you're likely to be building with it, so my experience with how and where it performs poorly even on my work desktops isn't likely to translate well for you. What I'm suggesting is that you just try it for yourself. You don't seem like you're on the "Unreal or nothing else" train so if it doesn't run well, there are plenty of other good options.
  4. This is entirely false. If you are comfortable with using macOS, you will have no more or less difficulty developing games for it than you would anything else. Outside of work, it's all I do, and I greatly prefer it to the experience of working on Windows. Your experience might be different, as might anybody else's but that's just their experience. There's nothing particularly wrong with the platform in that respect. This, however, is more true. The Mac platform has historically not enjoyed nearly the same popularity as Windows, and consequently there have historically been significantly fewer games of the AAA quality you find on Windows. This has improved in recent years, but it's still very likely that <insert upcoming game you want here> isn't going to be available for the Mac. This means it's also not as strong of a market for releasing and selling your games as Windows might be. However, if you're just getting started that's not likely to be a huge concern. And in the long run it's still very possible to make a living selling Mac games... you just might have to work a bit harder at it. At this point I wouldn't consider it too much of an issue for you. Both Unity and Unreal provide ways for you to write your own code. You can do basically as much or as little "drag and drop development" with those engines as you are comfortable with. This makes them good places to start. If they really turn you off, though, Cocos2D is a popular framework that is available for the platform, and Apple's SpriteKit and SceneKit are reasonable things to explore when you're getting started as well. I'd try to run Unity and Unreal, incidentally, if they interest you. You might find them more usable than you think, performance-wise. If not, you can fall back to something like Cocos2D or some other framework you can just manually link into your app in Xcode. If you're buying one without user-upgradable RAM, then absolutely. Starving a macOS machine of RAM is one of the best ways to render it unacceptably slow and the low-end configurations Apple provides are borderline-unethically starved of RAM, especially for serious work like software development. If you are getting an older model you can upgrade, and you are comfortable swapping the RAM yourself, it's cheaper to buy the RAM from a third party. If not, you can't upgrade it later, so get as much as you can up front.
  5. There is no "best" way, really; you should organize it in a fashion that works for you. What you want is for your portfolio to demonstrate the things that show off your skills as a developer, so you will likely want to prioritize the display of projects that are more impressive on some scale or show off something you are particularly proud of. There are no rules for what needs to go into a portfolio. You don't necessarily need "complete" games, for example, if you're a programmer. Portfolios are very subjective things, both in terms of how the author will assemble them and how any potential employers will review and judge them. It's impossible for you to know the latter, usually (and every employer will be different anyhow), so you should focus on structuring it in a way that allows you to show yourself off in the best light you think possible.
  6. It's a good question and I thought about just suggesting this as well instead of what I said in my original post. However, for me it comes down the fact that allowing these necro posts tends to bury new discussion at the end of 5+ page threads from the turn of the century. This makes it less discoverable, because there's a bunch of old crap to wade through first before you necessarily have the context, and wading through that old stuff is potentially totally irrelevant because of how old it is (things may be different now), and it's consequently easy for some posters to then derail the new discussion entirely because they picked up on some statement that was true in 2001 but isn't now, and they post to "correct" that 2001 poster (perhaps because they too didn't notice the date). And that's just for the well-intentioned necro posters, who maybe don't realize they're doing it. There's also the set of posters who reply to these threads just to be jerks and "get the last word in," so it's nice to be able to shut that down.
  7. We have a longstanding policy about avoiding thread necro'ing in year-old (plus or minus some months) topics. Can we just fix this by enabling some option to automatically lock or otherwise disable responding to posts above some threshold? It would eliminate a lot of annoyance for moderators and, especially, users (who I'm sure love getting the silly slap-on-the-wrist warnings from us for something that, it seems, the site could easily just prevent them from doing). It would also eliminate any subjective wiggle-room in "how old is too old" determinations from moderators.
  8. Please do not necro year-old posts.
  9. That's not something we can help you with. If you are unwilling to leave your house, you can try various online resell places like eBay and try to find something you can afford there.
  10. So the "paused" clause is literally for like, "user has paused the game" or otherwise suspended the application and not to pause the loop to throttle down to your target framerate? That does mean the sleep is probably not the cause of your lag, unless you're accidentally flip-flopping the state of the gating variable someplace (breakpoint in the debugger to verify), although the Sleep() is still not the best way to handle that. Neither here nor there, though. You can upload the .exe someplace, although the chance that somebody will download a random .exe is slim (and you'll want to make sure you upload an appropriately self-contained package, e.g., not a debug build etc). You could also upload a .zip of the project and somebody might be willing to build and verify it for you. Or try making a video and sharing that. Something else you might try as a diagnostics technique is to make the shape move back and forth on its own, without mouse input. Then observe the behavior as it runs, keeping your mouse still and your hands off the keyboard. Then, observe the behavior as it runs while you move the mouse frantically over the window. This can help rule out whether the delay is due to a factor of the Win32 message queue size or simply a constant issue.
  11. You might try local thrift shops, or similar second-hand stores, in your area.
  12. The most obvious factor is that the Sleep(100) in your core loop will always halt your application (and thus your updating and rendering of the position of the shape) for at least 100 milliseconds, if not more. The cursor, being driven by the OS, blissfully does not care about that and will update the cursor in realtime. That Sleep() is not needed. It's often seen used to "make sure we don't use 100% of the CPU," but that goal itself is often based on a false premise and even then, sleeping the whole thread for an arbitrary amount of time isn't the solution. If your base class WndProc is doing anything with mouse-moved events that is time-consuming, that can also throttle back your core loop since mouse-moved events are _very_ spammy. Similarly, if the base framework class is trying to force a WM_PAINT, which is a low-priority but spammy (even though it's coelsced) message, and doesn't actually correctly handle that WM_PAINT, that can also throttle back your core loop by causing the branch into the positive case for the PeekMessage check to be taken way, way more frequently than you generally want. I'd verify those.
  13. How are you invoking your actual rendering? Is it in the WM_PAINT handler of your message loop, by chance? (If not, please show the code that invokes it and the code that drives you main loop... and probably your actual window procedure as well; those are the likely culprits).
  14. What exactly is it you're trying to accomplish (if you say you're not rebasing anything yet, why are you running the command)? The "proper" content of that text file depends on your goal, and putting the wrong thing in there (or deleting the wrong stuff) can have unpleasant consequences.
  15. Handle errors how? D3D reports almost all failures using HRESULTs, you don't need dxerr.h's functions to interpret and handle those failures. For the most part the SUCCEEDED() and FAILED() macros will let you make the appropriate determination, and they will be pulled in by simply including Windows.h. The dxerr library is basically dead. All it was useful for, really, was getting formatted error strings from some HRESULTs, and some utility macros. If you really need that functionality you can find various reimplementations (for example, header and source). In practice I've found it more useful to simply write code that interprets the actual HRESULT in the context of the actual failure and propagate a custom error message to users that way, rather than the generic context-free messages produced by the old dxerr functions. You can also use FormatMessage directly.