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.

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

Migrating a project from 3.0 to 3.1 breaks the ability to mark assets as root assets. #442

profan opened this issue May 5, 2019 · 1 comment


Copy link

@profan profan commented May 5, 2019

Release Type: Official Release


Platform(s): All

Describe the bug
Create a project in 3.0, migrate it to 3.1, try to include any asset as a root asset when under the new 3.1 project structure and find it doesn't get included (like a Scene/GraphicsCompositor).

To Reproduce
Steps to reproduce the behavior:

  1. Create a new 3.0 project.
  2. Open it in, upgrading it.
  3. Create a new Scene or GraphicsCompositor/any asset not included in some property in the editor/serialized that way (and mark it as a root asset).
  4. Try to use Content.Load("UrlToAssetHere") and find that the ContentManager does not find the asset, and indeed if you look at the project structure in the actual files, it is not marked as a root asset.

Expected behavior
I expect the upgrade from 3.0 to 3.1 to not break marking things as a root asset.

Additional context
If necessary, I can provide a small repro project..
Also note that this asset has been reported before, but the user closed the issue as they worked around it, but it is still a problem (and I've also personally encountered it now at least twice): #312

@profan profan added the bug label May 5, 2019

This comment has been minimized.

Copy link

@guygodin guygodin commented Aug 19, 2019

Having the same issue here on a project upgraded from to 3.1

@xen2 xen2 self-assigned this Aug 19, 2019
@xen2 xen2 closed this in 1813edc Aug 20, 2019
phr00t added a commit to phr00t/FocusEngine that referenced this issue Aug 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.