Search Issue Tracker

Fixed in 7.1.3

Fixed in 7.1.5

Votes

75

Found in [Package]

7.1.2

Issue ID

1194975

Regression

Yes

[HDRP] When installing or upgrading to package version 7.1.2 type or namespace 'SerializedScalableSetting' can not be found

Package: Scriptable Render Pipeline HD

-

When installing or upgrading to HDRP package version 7.1.2 type or namespace 'SerializedScalableSetting' can not be found. This prevents building or compiling the project.

1. Create a new project.
2. Download HDRP version 7.1.2 in the Package Manager. (Window -> Package Manager)

Expected outcome: The package installs with no errors.
Actual outcome: Errors in console. When you clear, three errors remain that prevent build and compilation.
(Error messages detailed below.)

Note:
- This also occurs when you upgrade an HDRP project to package version 7.1.2
- This was tested primarily on Mac but is reproducible on Windows.

Reproducible in 2019.3.0b9
Not reproducible in 2019.3.0b5, 2019.3.0b8, 2020.1.0a9

Errors shown in editor:
Library/PackageCache/com.unity.render-pipelines.high-definition@7.1.2/Editor/RenderPipeline/Settings/SerializedRenderPipelineSettings.cs(58,16): error CS0246: The type or namespace name 'SerializedScalableSetting' could not be found (are you missing a using directive or an assembly reference?)
Library/PackageCache/com.unity.render-pipelines.high-definition@7.1.2/Editor/RenderPipeline/Settings/SerializedRenderPipelineSettings.cs(59,16): error CS0246: The type or namespace name 'SerializedScalableSetting' could not be found (are you missing a using directive or an assembly reference?)
Library/PackageCache/com.unity.render-pipelines.high-definition@7.1.2/Editor/RenderPipeline/Settings/SerializedRenderPipelineSettings.cs(8,16): error CS0246: The type or namespace name 'SerializedScalableSetting' could not be found (are you missing a using directive or an assembly reference?)

License type: Pro

Comments (27)

  1. 0c506abf7b399c2947485603557143b6?d=mm

    denisgarifullin159

    Dec 16, 2019 15:32

    A meta data file (.meta) exists but its asset 'Packages/com.unity.visualeffectgraph/Editor/Models/Contexts/Implementations/HDRP' can't be found. When moving or deleting files outside of Unity, please ensure that the corresponding .meta file is moved or deleted along with it.
    UnityEditor.GenericMenu:CatchMenu(Object, String[], Int32)

    IVery disappointed. That's just funny

  2. 318654a786700455b96049d8ac9beb11?d=mm

    ilyaryzhenkov

    Nov 19, 2019 13:45

    My bad. Should've upgraded shadergraph as well. So if you change your `manifest.json` file like this:
    "com.unity.render-pipelines.high-definition": "7.1.5",
    "com.unity.shadergraph": "7.1.5",

    it seems to work in 2019.3.0b11

  3. 318654a786700455b96049d8ac9beb11?d=mm

    ilyaryzhenkov

    Nov 19, 2019 13:27

    I've just tried Unity 19.30b11 with HDRP 7.1.5. A different problem, but still no luck :(

    Library/PackageCache/com.unity.render-pipelines.high-definition@7.1.5/Editor/ShaderGraph/HDSubShaderUtilities.cs(378,30): error CS1061: 'ShaderGraphRequirements' does not contain a definition for 'requiresVertexSkinning' and no accessible extension method 'requiresVertexSkinning' accepting a first argument of type 'ShaderGraphRequirements' could be found (are you missing a using directive or an assembly reference?)

  4. 63ca35ccc0a541c1dbac59ed4f103aca?d=mm

    Meatgrind

    Nov 18, 2019 08:26

    Anxious to see when this is fixed I browsed through ScriptableRendererPipeline GitHub again; they seem to have the approppriate meta files in the folder in 7.1.x development branch and it would seem the meta file has never been missing in the versions where the error occurs.

    Also, they seem to have internally (in GitHub, not yet in Package Manager) marked 7.1.3 and 7.1.4 already in changelog with release dates (both in the past at the time of writing).

    These and the total lack of any commits or changelog fix lines mentioning anything about this issue or related files makes it sound like HDRP works and they're furthering development normally, meanwhile there's something broken with how Package Manager packages are put together, published and/or distributed.

    Or at least that would explain why the GitHub version seems like this issue should be nonexistent, but they'd still have an unresolved issue with Package Manager or making packages that blocks them from publishing new releases and fix for this issue.

    Is this bug issued to the wrong team?

  5. Ccd7219721dddcbc31667f3b21a3f85a?d=mm

    unity_mhJkVl2oJFIbKQ

    Nov 15, 2019 17:40

    not fixed in 2019.3.0b11
    sad :(

  6. 716d25ab8b44047d4adcc564816784a3?d=mm

    michaelbartlow

    Nov 15, 2019 02:13

    Same on 2019.3.0b11.

  7. 63ca35ccc0a541c1dbac59ed4f103aca?d=mm

    Meatgrind

    Nov 12, 2019 08:42

    I'm very curious how this is a Unity Editor issue and not HDRP package - meta files missing and the source files being ignored because of that makes sense, but how would it be possible for the Editor version to affect deleting/not decompressing meta files from the downloaded packages.

    I've been anxiously waiting for HDRP 7.1.3 but it doesn't seem like they ever mention that issue in GitHub commits or changelogs for next version. https://github.com/Unity-Technologies/ScriptableRenderPipeline/blob/release/7.1.x/com.unity.render-pipelines.high-definition/CHANGELOG.md

    If it indeed is an Editor issue and not just missing files in the package, it would make sense no one seems to be acting on a simple-sounding fix (just add the missing files!) in GitHub. I would still be curious about what the issue is about!

  8. A36af09028b12bc670332d42454c4fe9?d=mm

    Erfan_SheikhHoseini

    Nov 08, 2019 10:27

    it happens on 2019.3.0b10 too

  9. 48b3e575302fd77d34dfb201e9ee0115?d=mm

    ingo_p

    Nov 07, 2019 09:59

    A quick fix is, to make the hdrp-package local. Just copy the folder "com.unity.render-pipelines.high-definition@7.1.2" inside the PackageCache folder to somewhere else. Then in Unity in the package manager delete the hdrp-package and then click on the + and "Add package from disc...". Add your local package. Unity is able now to create the missing meta-file.
    Surely not the best solution, but it works for me.

  10. D1607352de2382e04bf2506035407f15?d=mm

    FiveXGames

    Nov 07, 2019 09:45

    This was so annoying that I resolve to find a "permanent" solution, is a bit brute force, but it will work (windows, but mac should be the same).

    Disclaimer it could create some bug... do it and your own risk. (And you will have to "rollback" it when this is solved)

    1) Go to your old working 2019.3.0b8 version
    2) copy the file "SerializedScalableSetting.cs.meta" (The META) from ----> \Library\PackageCache\com.unity.render-pipelines.high-definition@7.1.2\Editor\RenderPipeline\Settings
    3) Paste it in your not working copy 2019.3.0b10 in the same location
    4) Access with file explorer, right clic the file, go to security revoke writing permissions to the file.
    5) Use unity it normally

    6) Don't forget that when they resolve this issue to set to default the permissions of the meta file.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.