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
Comments (27)
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
- MouseDownEvent is triggered when changing from Scene view to Game view
- "GlobalObjectIdentifierToObjectSlow" returns Null when retrieving "GlobalObjectId" from GameObject inside a Prefab
- Shader is invisible in the Build when using BiRP on Meta Quest 2
- Data Bindings are lost when UIElements are reparented without a delay
- Crash on StringToIntCheckedUInt8 when opening a specific Scene
sionzee_
Nov 03, 2019 22:25
I have got another errors from JetBrains
Asset Packages/com.unity.render-pipelines.high-definition/Editor/RenderPipeline/ScalableSettingLevelParameterEditor.cs has no meta file, but it's in an immutable folder. The asset will be ignored.
System.Reflection.MethodBase:Invoke(Object, Object[])
JetBrains.Rider.Unity.Editor.UnityUtils:SyncSolution()
Asset Packages/com.unity.render-pipelines.high-definition/Editor/RenderPipeline/Settings/SerializedScalableSetting.cs has no meta file, but it's in an immutable folder. The asset will be ignored.
System.Reflection.MethodBase:Invoke(Object, Object[])
JetBrains.Rider.Unity.Editor.UnityUtils:SyncSolution()
sionzee_
Nov 03, 2019 22:16
Reproduced on 2020.1.0a11
AlexFCL
Nov 03, 2019 17:06
The solution GOA provided works, but the problem comes back after Unity3D is restarted. Basically the packages are reset, so any scripts that were edited will be reset and the issue resurfaces. Anyway to make this fix permanent?
crashTX
Nov 02, 2019 19:16
That worked GOA, thanks! Also error now in Asset Packages/com.unity.render-pipelines.high-definition/Editor/RenderPipeline/ScalableSettingLevelParameterEditor.cs also missing meta file
Goa
Nov 02, 2019 10:04
Note:
This happens cause "*YourProject*\Library\PackageCache\com.unity.render-pipelines.high-definition@7.1.2\Editor\RenderPipeline\Settings\SerializedScalableSetting" doesnt gets processed with Unity somehow (no Meta file).
You can fix it by copying "SerializedScalableSetting" scripts into another script. (I just copied it into to SerializedScalableSettingValue)
PetraCephas
Nov 02, 2019 07:50
Reproduced on 2019.3.0b9 Windows 10
dan_wipf
Nov 02, 2019 07:27
Reproduced aswell on 2019.3.0b6