stride3d / stride3d/stride

A Crash Report, Happened When Adjusting The Scene Editor

Open
#2,656 1 comment 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: Stride Version: 4.2.0.2374

Platform(s): PC, In Game Stdio

Describe the bug
While attempting to dock the Scene Editor to the far left of Game Studio to recreate Unity's "2 By 3 Layout," dragging the Scene Editor window triggers a snapping button on the far left. When the Scene Editor is dragged onto this snapping button, the engine crashes.

To Reproduce
Steps to reproduce the behavior:

  1. Create a new project
  2. Find "Main Scene" tab and drag it onto the snapping button on the far left
  3. If the Engine doesn't crush, the Scene Editor will display a blank screen and become non-functional.
  4. Save the change and open Game Studio again, repeat step 2, the Engine will crsh

Expected behavior
The Scene Editor should be on the left side of the Game Studio, like Scene View do in Unity Layout "2 by 3"

Screenshots
The crush Happened ↓

Image

Additional context
A crush report has sent early this day, but I haven't receive any information. I hope developers could see this crush report so I create a new issue

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 crash in Game Studio by creating a project, opening Main Scene, and dragging the Scene Editor onto the far-left snapping button. Check the reported blank-screen and restart behavior, then use the available crash report to identify the failing area. Done means the Scene Editor can be docked on the left, saved, and reopened without crashing or becoming non-functional.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
desktop, game-dev
Issue type
Bug
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.