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

Federico Barlotti

Members
  • Content count

    37
  • Joined

  • Last visited

Community Reputation

192 Neutral

About Federico Barlotti

  • Rank
    Member
  1. Yeah, it seems like it's the most stable one out of the 326 I've tried. Thanks for the input though! Still very useful if one can do it that way. :)
  2. Ah, I missed that. Well, as I said earlier I can't do that unfortunately. I can only interpolate the current position over the friction, the destination and the delta. This is because the destination is variable at any point in time.
  3. I don't know, but that's the result I got. Maybe I've implemented it wrong. Here's my function:   void Entity::updatePos(float delta) { float3 distance = this.destination - this.position; float timeNeeded = 3.0f; float increment = delta / timeNeeded; this.X += increment; this.X = clamp(X, 0.0f, 1.0f); this.position += distance * this.X; ... }   I know for a fact the `destination` is updated correctly, so no problem there.
  4. Sorry, I must have misread your post.   But surely this is what you'd want in a game? Shouldn't traveling x distance always take the same amount of time, and not depend on whether your computer is awesome or not? With a varying frame rate, a varying distance moved per frame would have to be the case in order to compensate, in order to keep the total time equal.   It feels like I'm missing something -- care to explain?     Exactly! The way your approach (and my previous attempts) worked, the framerate did nothing to mitigate the wobbling of the movements. In other words, it would abnormally speed up when the framerate increased and slow down when it decreased. This should not happen.
  5.   Your approach doesn't work. The effect is exactly the same I've been getting all along - i.e., speed changing based on the framerate, in fact it seems even worse than a couple of cases I was able to obtain.
  6. Thank you so much! This is much, much better than any of my results. It's still not perfect, probably due to my cheap framerate calculation, but it's barely noticeable. This is more than enough for my needs. :)
  7. I'm assuming `elapsedTime` is my delta time, but what are `t` and `dt`? Is one of them my `X` factor?   There is no origin and no time management in my system, maybe I've not been clear enough. I only have these factors, run on a frame by frame basis, with no "origin" or "time until B" etc.   I just have to put my delta time in the equation I've already got for it to work.
  8. I'm talking about my formula. position = position + (destination - position) * X; It lacks the delta time, and I don't know where to put it.
  9. You're confusing my `X` with the fixed delta time described in the article (which I did read, yet is unhelpful to my more specific problem). X is not the delta time, it's a "friction" factor. It doesn't change over time, but the approach should work for any X.   Also, quoting from the article:     I'm not going for this approach. As I said, the formula should be able to correctly interpret virtually any framerate and factor values between 0.0f and 1.0f.   So asking again, where does my delta time fit in in the operation?
  10. I have a position point that moves towards a destination point by a factor of:  position = position + distance * X; where: distance = destination - position; and `X` is a factor chosen by the code between 0.0f and 1.0f (0 = stopped and 1 = instantaneous motion);   And it all works fine, except the motion speeds up and slows down depending on the framerate. I have access to the delta time of the frames, but I have no idea how to fit it in the formula. I've tried many combinations and failed.   Any help?
  11. That sounds interesting. The VS graphics diagnostics didn't work on VS 2013 so I ditched it and downloaded VS 2015, but since the GPU kept crashing I moved along and started working on the hlsl shaders instead. My card is an Nvidia GTX 970 (latest drivers), maybe it's D3D9 compatible.
  12. Ah, I forgot I had it on; the output says nothing when it works, but when it doesn't or if I pause and continue, it loops that it needs at least one active vertex shader to work and there is currently none set in the context, and then the GPU crashes.
  13. There is no SetShader call active anywhere in the code, so it's most probably the second one.   And I know that isn't the way it's supposed to be done, I was just wondering why it just so happened to work magically like that.
  14. They both return a null pointer, and for some reason now the GPU sometimes crashes when I attempt to start the program or resume it after pausing the debug... I'm not gonna attempt to run it without a shader anymore though, since the GPU apparently can't recover if it crashes a second time (thus requiring me to reboot). Maybe my GPU is just weird, I dunno.   Now, onto new and painful issues, since I just can't get the matrix buffer to be accepted by the shader...
  15. Hmm, is it a general statement or did I do something very bad in my code? I am including the FBX SDK .dll since I would have tried and tackled it in a later time, though I'm not doing anything with it. Could that be the problem?