Ticket #71 (closed enhancement: fixed)

Opened 6 years ago

Last modified 4 years ago

Cached areas should not do collision detection on servers

Reported by: mike Owned by: mike
Priority: normal Milestone: alpha-test
Component: server Version: 0.2
Keywords: Cc:
Estimated Effort: 2 days Platform: All
State: Relative Size:

Description

Problem

In order to speed up the server, it may make sense for cached areas not to do collision detection or to update objects each iteration. Instead they can update objects when the area's master server updates them. This will be in place so that when a server needs to cache an area for the sole purpose of checking collision detection with another area, it won't add too much overhead to the system.

Change History

Changed 6 years ago by mike

Cached objects shouldn't do updates.

Changed 6 years ago by mike

  • status changed from new to closed
  • platform set to All
  • resolution set to fixed

Solution

Just added a couple checks for this case. Nothing fancy.

Changed 4 years ago by mike

  • milestone changed from beta-test to MV3D-0.32

Milestone beta-test deleted

Changed 4 years ago by mike

  • milestone changed from MV3D-0.32 to alpha-test

Setting the milestone back

Note: See TracTickets for help on using tickets.