-
Notifications
You must be signed in to change notification settings - Fork 305
opening the project in 2019 #9
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
Comments
I've also found matching the project to the right Unity version and the different package versions challenging as well, especially when trying to upgrade to a new version of Unity. I've been meaning to try this myself and haven't done so, but one suggestion might be to open the project in the Unity version that works (easy if you use Unity Hub), export the scene and dependencies you need into a package, and then import that into a newer version project. The docs say to use: Version: Unity 2018.3.0f2 |
I tried opening the project from unity hub with 2019.1.10 and got a bunch of errors. There are some 200 instances of these two errors:
The approach I suggested worked but many of the materials lost bindings: |
dmalpica, just judging from the error messages, your problem could be coming from the differences between .NET 2.0 and 4.0. Have you tried changing your 2019 project to use 2.0 (Edit->Project Settings->Player->Api Compatibility Level)? |
tried, didnt work |
Did you try upgrading the project to use Version C# .NET 4.6? I think that may solve the issue.@dmalpica |
For anyone who see's this, this project still works fine in 2019.4.
|
Cant seem to open this project in Unity 2019.1.9
everything comes up purple and I cant create a render pipeline asset, even after installing RP core, lrp and shadergraph packages
The text was updated successfully, but these errors were encountered: