stride3d / stride3d/stride

Scene.Name = asset name by default

Open
#1,471 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Is your feature request related to a problem? Please describe.
I'm always frustrated when look at the scenes while debugging and always see "Scene Scene" value. This makes hard to determine which scene is which.

Describe the solution you'd like
Set scene's "Name" property to the appropriate asset name by default.

Describe alternatives you've considered
Allow to edit scene's "Name" property like it's already done for entities, but I'm afraid of possible side effects like broken link between the real asset and the added scene to the "Asset editor". It also may not be a problem, I don't really know.

Additional context
SceneNameIssue
RootScene's "Name" should be "RootScene", not "Scene" and debug view for the scene will be automatically updated to "Scene RootScene" instead of "Scene Scene".

Unfortunatelly I'm not familiar with the Game Studio source code, so I don't know how to implement the idea.

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

Start with the referenced ComponentBase.cs value and compare it with the entity naming behavior in Entity.cs. Trace how scenes are created from assets and how their names appear in the debug view, then verify that a scene named RootScene is displayed as "Scene RootScene" without breaking the Asset editor link.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
game-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.