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 (32)

  1. michaelbartlow

    Nov 15, 2019 02:13

    Same on 2019.3.0b11.

  2. 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!

  3. Erfan_SheikhHoseini

    Nov 08, 2019 10:27

    it happens on 2019.3.0b10 too

  4. 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.

  5. 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.

  6. badradionz

    Nov 07, 2019 08:54

    Please click "Vote on this issue" button to get this fixed!

  7. badradionz

    Nov 07, 2019 08:53

    Everything was fine in 2019.3.0b8 but I got this same error after upgrading to 2019.3.0b10

    I downgraded my project back to b8.

  8. alloystorm

    Nov 07, 2019 05:16

    Still a known issue in b10. Maybe they intend to fix it from the HDRP side?

  9. bsgbryan

    Nov 07, 2019 00:06

    I can confirm this is also an issue in 2019.3.0b10 on macOS.

    The only beta version that works for me is b8.

  10. mountblanc

    Nov 06, 2019 19:45

    I have the same but in other package:
    Asset Packages/com.unity.2d.spriteshape/Editor/Handles has no meta file, but it's in an immutable folder. The asset will be ignored.
    Asset Packages/com.unity.2d.path/Editor/Handles has no meta file, but it's in an immutable folder. The asset will be ignored.

    Both in 2019.3.0b9 AND b10

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.