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

Understanding the D* lite whitepaper

7 posts in this topic

I'm writing a tool for a game I play, and I've found I need a good pathfinding algorithm.

I've already written an A* and a Dijkstra routine, but I've found them to be far too slow. It takes them about 20 and 13 seconds respectively to find the shortest path along the longer routes.

I've come across D* lite as a possible better solution, but there's very little information on the web. Some of what I did find came from here several years ago, so, here's to hoping those members are still around.

I found and read Koenig's 2002 paper about it, ([url="http://www.aaai.org/Papers/AAAI/2002/AAAI02-072.pdf"]this[/url] one), and I understand all of the LPA* pseudo code except for two lines:

- Calculate keys()
In the calculateKeys function, it reads: Return[ min( g(s), rhs(s) ) + h(s, s[sub]goal[/sub]) ; min ( g(s), rhs(s)) ]. What I don't understand is the ; in the middle. Does the function return two values? Does it perform some sort of operation on the results of the two min statements?

- Update vertex and rhs calculation
The other line I had trouble with was this one: min [sub]s' (is element of) pred(s)[/sub] (g(s'), c(s', s)). I don't get that one at all. The s' in pred() with the smallest g or c?

I feel like I'm going to get a lot of blank stares, but, any ideas anyone?
0

Share this post


Link to post
Share on other sites
[quote name='sectrix' timestamp='1339625653' post='4948950']Does the function return two values?[/quote]

It returns a pair or 2D vector; the authors have opted for [a;b] over (a,b) to improve legibility.

[quote]The other line I had trouble with was this one: min [sub]s' (is element of) pred(s)[/sub] (g(s'), c(s', s)). I don't get that one at all. The s' in pred() with the smallest g or c?[/quote]

I don't see this line. I [i]do[/i] see min [sub]s' (is element of) pred(s)[/sub] (g(s') [b]+[/b] c(s', s)) - i.e. the minimum of the expression on the right over all predecessors of s.

EDIT: slightly clearer wording. Edited by TheUnbeliever
2

Share this post


Link to post
Share on other sites
I see. So the second line is basically: the minimum s' in predecessors of u, as calculated by ( g(s') + c (s', u) ).

Excellent, thank you so much for that.

One follow up question then.

When comparing: U.TopKey < calculateKeys, ie: (X1, Y1) < (X2, Y2), is this (X1 < X2) AND (Y1 < Y2), or (X1 < X2) OR (Y1 < Y2), or something else entirely? Edited by sectrix
0

Share this post


Link to post
Share on other sites
[quote name='sectrix' timestamp='1339633003' post='4948990']the minimum s' in predecessors of u, as calculated by ( g(s') + c (s', u) ).[/quote]

Not quite. That would be written 'argmin', whereas we just have 'min'. This is the minimum [i]value of g(s') + c(s',u)[/i] for any predecessor s', not the predecessor itself.

[quote]When comparing: U.TopKey < calculateKeys, ie: (X1, Y1) < (X2, Y2), is this (X1 < X2) AND (Y1 < Y2), or (X1 < X2) OR (Y1 < Y2), or something else entirely?[/quote]

Explained from around the middle of the first paragraph on page 478, starting at 'keys are compared according to a lexicographic ordering.'
2

Share this post


Link to post
Share on other sites
OK, I had it backwards then. It's the minimum of ( g(s') + c(s', u) ) as calculated with all s' in predecessors of u.

And the key comparison is: (X1, Y1) <= (X2, Y2) iff (X1 < X2) OR [X1 = X2 AND Y1 <= Y2].
Have I got it right?


And it seems that everywhere in the pseudo code where there is a < with a dot above it represents this lexicographic comparison, correct?
0

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