Graphics: persisted Vulkan pipeline cache
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- csharp
- Domain
- game-dev, performance
Research direction
Start by reading the Vulkan pipeline creation and cache code in the engine, then trace how device UUID and driver version are obtained. Implement cache persistence with header validation and measure pipeline creation on a second launch. The issue does not name files or tests, so locating the relevant entry points will take project familiarity.
Written by the indexing model from the issue text.
Description
Current State
Pipelines are created from scratch on every launch; mobile drivers make this slow.
Tasks
-
VkPipelineCachepersisted per device UUID and driver version - Validate the header before reuse
Acceptance Criteria
- Second-launch pipeline creation time measured lower
Related
- Android plan task D4 · seniority Mid · mergeable now (.NET 10)
- Platform roadmap: #100
- Dominant language
- C#
- Stars
- 1
- Forks
- 1
- Avg merge
- 1h 45m
- Merged PRs (30d)
- 31
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from MASS4ORG/Turian
-
c:assets p:low size:XS t:task
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
c:engine c:scripting p:medium size:XL t:refactor
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
c:assets c:platform p:low size:M t:feature
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
c:platform c:scripting p:low size:M t:task
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
c:docs good first issue p:low size:S t:docs
Difficulty 3/5 1-2 days Newbie friendliness 67/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
area:re1 bounty help wanted needs-game
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
StackExchange/StackExchange.Redis#3274 ·
Maintainers usually reply within 1 day
-
affected/v17 affected/v18 area/frontend type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
umbraco/Umbraco-CMS#24186 ·
Maintainers usually reply within 2 days