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

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

  2. 3a08316249cc08780160f4c556115e8a?d=mm

    badradionz

    Nov 07, 2019 08:54

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

  3. 3a08316249cc08780160f4c556115e8a?d=mm

    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.

  4. 5a7bac4a2ba5a6489056d147b02690fd?d=mm

    alloystorm

    Nov 07, 2019 05:16

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

  5. 9b85a734132395f7229cf3850d1adf42?d=mm

    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.

  6. De120da1f513f8c8d28142d62a7e307c?d=mm

    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

  7. 27cb35316df01975c84bec8531227926?d=mm

    andybak

    Nov 06, 2019 12:53

    This has been marked as a "known issue" for 2019.3.0b9.

    So looks like it's back to b8 until b10 is released. Surprised this wasn't worth a quick patch. (actually surprised it wasn't caught by the automated tests!)

  8. Cabd5da7746d2afcf7be055d72907e67?d=mm

    unity_fg0s-1ln7SEspg

    Nov 05, 2019 21:19

    Guys, Unity, is this serious? Second time you release a beta and it simply does not work?!

    What's your point of releasing a new beta version at all?

    This problem apparently happens because the HDRP package folders are mandatory made read-only, and they don't have the meta files for those scripts. And you can't make it non-read-only because it looks like that Unity enforces read-only on it automatically.

    Now I am not sure if Unity is earning enough money by selling their dark theme to at least hire some basic QA specialists.

  9. Ea8897dae08ed0e6f99b1709117c819e?d=mm

    CosmosBear

    Nov 04, 2019 18:59

    I can't upgrade to 2019.3.0b9, it's been 5 days...

  10. 63eb28e1176e9f6c641763274bf6d48e?d=mm

    Ziflin

    Nov 04, 2019 18:25

    The sad this is that I ran into this issue while trying to update Unity to make sure 3 other HDRP bugs that I was about to report were still bugs in the latest version. Could someone at Unity please QA the next Unity Beta *with* HDRP and URP and make sure it actually builds/works...

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.