AdamsLair/duality

Investigate Bad TilemapCollider Performance in Extreme Cases

Open

#728 opened on Jul 1, 2019

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C# (287 forks)auto 404
BugCoreHelp WantedPerformanceTilemaps

Repository metrics

Stars
 (1,425 stars)
PR merge metrics
 (PR metrics pending)

Description

Summary

Tilemap Collider generation is too slow in "extreme" cases, causing micro-freezes during editing and at runtime when editing tilemaps.

How to reproduce

  • Create a simple tileset with two tiles - one fully passable and one fully blocking.
  • Create a new tilemap that is at least 32x32.
  • Edit the tilemap to create a checkerboard pattern of blocking and passable tiles.
  • Profile and check performance while editing.

ex ex (1)

Reported on the chat by user TBDesignes.

Contributor guide

Research direction
Profile the tilemap collider generation to identify bottlenecks, then implement optimizations such as spatial hashing or reducing redundant operations.
Tech stack
csharp
Domain
game dev
Issue type
Performance
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Duality framework
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60