stride3d / stride3d/stride

Sprite Sheet Asset Doesn’t Update After Modifying Source PNG

Open
#3,003 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
7.8k
Forks
1.2k
Avg merge
2d 17h
Merged PRs (30d)
49

Description

Release Type: Official Release

Version: 4.3.0.2507

Platform(s): Windows

Describe the bug
I’m having a problem with updating a Sprite Sheet when I change the source texture (image). First, I draw the image in PNG format. Then I create a Sprite Sheet asset that contains the individual sprites. When I build and run the game, everything displays and works correctly.

However, once I modify the source PNG image, the editor still shows an outdated thumbnail for the Sprite Sheet asset, and if I build and run the game again, the change isn’t reflected there either — the game still shows the original image. The only place where the updated image appears correctly is when I open the Sprite Sheet asset directly in Game Studio Editor, the editor shows the new image properly.

Sprite parameter change, deleting the obj folders or using Clean Solution in Visual Studio helps.

Expected behavior
The expected behavior would be automatic updating of the Sprite Sheet asset whenever its source files change.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue in Game Studio Editor on Windows by changing a source PNG after creating its Sprite Sheet, then build and run the game again. Compare the stale asset thumbnail and runtime result with the refreshed image shown when opening the Sprite Sheet directly; done means source changes update automatically without changing sprite parameters, deleting obj folders, or using Clean Solution.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
build-system, game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.