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
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
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
badradionz
Nov 07, 2019 08:54
Please click "Vote on this issue" button to get this fixed!
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.
alloystorm
Nov 07, 2019 05:16
Still a known issue in b10. Maybe they intend to fix it from the HDRP side?
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.
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
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!)
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.
CosmosBear
Nov 04, 2019 18:59
I can't upgrade to 2019.3.0b9, it's been 5 days...
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...
maxxa05
Nov 04, 2019 14:17
Why is this set to wont fix? It breaks the HDRP package, that's a major bug.