Thunderhead Engineering
February 04, 2012, 09:39:57 PM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: SMF - Just Installed
 
   Home   Help Search Calendar Login Register  
Pages: [1]
  Print  
Author Topic: Simulation parameter: steering update interval  (Read 539 times)
liu_zhen
New Member
*
Posts: 11


View Profile
« on: March 24, 2009, 11:38:42 PM »

Hi, I have a question about the parameter called steering update interval.

Does it mean that one occupant can re-calculate its path every time step which is specified by this update interval?

Now, the default value is 0.1s; and it seems occupants are quite smart, I mean they can soon find the optimistic route even in some complicated environment. Do you have any recommend to define a reasonable value for this parameter?
 
Logged
Charlie Thornton
Thunderhead
*****
Posts: 368


View Profile Email
« Reply #1 on: March 25, 2009, 08:01:00 AM »

The steering update interval (default: 0.1s) controls how frequently occupants will re-calculate their desired velocity.  The desired velocity is the output of the steering behaviors.  Each simulation time step (default: 0.025s), the occupant will attempt to accelerate to match its velocity with the desired velocity.  Recalculations of the desired velocity are also forced when occupants are bumped off-path or when they reach a waypoint.

The steering calculation is relatively expensive in CPU cycles, so the default parameters should make simulations run about 4x faster than if you put the steering update interval at 0.025s.

As the update interval gets bigger, where you start to see it is in crowds.  Occupants will take turns moving in something like strange coordinated shifts - about half will stop and the other half will angle off for the update interval.  It's not very pretty.  If it gets really big, they'll start to do more corner sliding.  However, the the default settings do a pretty good job of balancing speed with accuracy.  If you have a sparse simulation (no congestion) you can make both values bigger without much of a problem, but it'll already run faster anyway, so there's not much point.

Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.13 | SMF © 2006-2011, Simple Machines LLC Valid XHTML 1.0! Valid CSS!