Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Moving prefabs with lots of parented meshes in them ends in Editor Crash. #17871

Open
DoItForGrandpa opened this issue May 3, 2024 · 1 comment
Open

Moving prefabs with lots of parented meshes in them ends in Editor Crash. #17871

DoItForGrandpa opened this issue May 3, 2024 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/content Categorizes an issue or PR as relevant to SIG Content.

Comments

@DoItForGrandpa
Copy link
Contributor

Describe the bug
When you try and move a prefab with the Transform component and that prefab has 80+ entities in it, it has a chance to result in a crash.

Steps to reproduce
Steps to reproduce the behavior:

  1. Create a prefab with 80+ textured meshes
  2. Click on the prefab and use the transform component and move it on the Y axis
  3. Editor slows down quite a bit during transform edits and a chance to crash the editor some of the times.

Expected behavior
Moving prefabs no matter what is in them should be a "smooth" process with no crashes

Actual behavior
Moving prefabs with a lot of entities and meshes in it can result in the editor crashing.

Found in Branch
Dev Branch

Desktop/Device (please complete the following information):

  • Device: PC
  • OS: Windows
  • Version 11

Additional context
N/A
@DoItForGrandpa DoItForGrandpa added kind/bug Categorizes issue or PR as related to a bug. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 3, 2024
@michalpelka michalpelka added sig/content Categorizes an issue or PR as relevant to SIG Content. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels May 9, 2024
@michalpelka
Copy link
Contributor

Please check out a similar, resolved issue #17211. Maybe it is again caused by unnecessary overrides?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/content Categorizes an issue or PR as relevant to SIG Content.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@michalpelka @DoItForGrandpa