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

Archived

This topic is now archived and is closed to further replies.

Hw

Timing in win32

8 posts in this topic

Hmm... You're suggesting an infine loop in main routine? Damn, that's method I used years ago in DOS (before using the PIT)... Somehow, I just don't like the idea...

Oh well. Guess I just have to live with it.

0

Share this post


Link to post
Share on other sites
I think it ultimately becomes an infinite loop, unless you are doing a non-time-dependant stratedgy came. Just don't forget to service the message queue with PeekMessage and PostMessages. Take a look at the DirectX samples..
0

Share this post


Link to post
Share on other sites
GetTickCount works as a backup, but since we are in Windows we might as well check for the existance of a high-resolution timer The following code should work:

int timerFrequency;
if (!QueryPerformanceTimer(&timerFrequency)) {
// Insert fall back code using GetTickCount here
}
else {
// A high resolution timer exists, the number of "ticks" per second is in timerFrequency
int currTime;
QueryPerformanceCounter(&currTime);
// Now we have the current tick count in currTime
}

So, basically you just need QueryPerformanceCounter and Frequency, and both can be included in with "winbase.h" (or i think if you use other WinAPI functions bay already be included)

0

Share this post


Link to post
Share on other sites
In fact, I found multimedia timer, which makes things pretty easy with its 1ms resolution... Now my timer set to 100Hz gives me 110 counts per second... Oh well, guess you can't have everything. Just one question arises; do interrupts overlap in single thread? For example, if I'm doing software rendering called in event handler (slow), do I still get new events to move objects etc?, or should I make scene rendering a thread which is executed whenever needed?
0

Share this post


Link to post
Share on other sites
I'd opt for the multithreaded approach, but then again, that's just how I work. Huge single threaded programs tend to become rather nasty, but ofcourse, you avoid the more curious thread-related bugs...

I personally find seperating the game in 4 threads connected with queues very usefull. One for "AI" (essentially anything complicated that require lots of processing and doesn't need to update with the same frequency as the framerate), one for rendering, one for UI and one for networking.

/Niels

0

Share this post


Link to post
Share on other sites
Well, even though computers are much faster than they used to be, you still must be aware of speed traps. Multithreading for example. Yes, it makes code all nice and neat and logical (that it, until you get into locking/unlocking thread related problems which are hard to debug) but you must understand that for just about any game a single threaded main game loop is just about the optimal way to program it.

The problem with your multithreaded approach is that there are several more threads that you don't even seem. For example, Flip() spawns a thread, async WinSock spawns a thread, etc. At most I could definately see a need for a second thread that handle's non-framerate dependant low priority stuff like AI, but the rest you might as well put into a well-organized main loop that will in the long run save you debugging time, speed up your program, ease portability AND readability issues and just make for a better program

0

Share this post


Link to post
Share on other sites
Ok, fanzy pants, beat this :
http://home.worldonline.dk/~noshit/scrshots.html

(35fps on a 90Mhz pentium with 4Meg VMem, 90fps on a 400 PII (limited by screen refresh rate))..

But you're right - unless you do a proper design, your threads will spend more time waiting for each other, than getting actual work done....

/Niels

[This message has been edited by Niels (edited October 14, 1999).]

0

Share this post


Link to post
Share on other sites
I'm having a problem with timings when doing a d3d app with borland cbuilder 4. It seems that windows' timers can't handle higher frequencies than ~20Hz (even if I set the interval to 1ms!). As directx offers no solution, how am I supposed to get a timer with freq in range of 50-100Hz? Any suggestions?
0

Share this post


Link to post
Share on other sites