Path-debug is incredibly performance heavy
Open
Nobody has claimed this yet.
Performance
- Dominant language
- C#
- Stars
- 17.4k
- Forks
- 3k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 14
Description
When I click behind these sub pens my FPS more than halfs, (This map is called Ensio Kaivo)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the FPS drop shown in the video on the Ensio Kaivo map with path-debug enabled, then locate the path-debug entry point and profile the slowdown. Done means the reported performance impact is substantially reduced, but the issue names no source file or test, so the affected code and regression coverage still need to be found.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100