Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice
  3. Join us on November 16th, 2023, between 1 pm and 9 pm CET for Ask the Experts Online on Discord and on Unity Discussions.
    Dismiss Notice

Bug Error in 7.4.1 package : ScriptableCullingParameters does not contain a definition for maximumVisi

Discussion in 'Universal Render Pipeline' started by timbokoppers, Jun 11, 2020.

  1. timbokoppers

    timbokoppers

    Joined:
    Nov 14, 2016
    Posts:
    69
    Hi,

    When updating to URP 7.4.1. I've got this error, does anyone else experience this? Any clue how to fix?

    Library/PackageCache/com.unity.render-pipelines.universal@7.4.1/Runtime/ForwardRenderer.cs(466,31): error CS1061: 'ScriptableCullingParameters' does not contain a definition for 'maximumVisibleLights' and no accessible extension method 'maximumVisibleLights' accepting a first argument of type 'ScriptableCullingParameters' could be found (are you missing a using directive or an assembly reference?)
     
  2. luoweihong

    luoweihong

    Joined:
    May 27, 2019
    Posts:
    56
    I met that problem too, wait for some one give the answer
     
  3. LazyDog_Rich

    LazyDog_Rich

    Joined:
    Apr 27, 2014
    Posts:
    70
    Bumping this, I know is 4 years old, hopefully is there a solution now :/
     
  4. LazyDog_Rich

    LazyDog_Rich

    Joined:
    Apr 27, 2014
    Posts:
    70
    To add more content I have the same error, since it refer to this line:

    cullingParameters.maximumVisibleLights = UniversalRenderPipeline.maxVisibleAdditionalLights + 1;

    If I comment it out, the error is gone. But everytime I open the project, the error appears again and I have to comment that line again.

    I try to fin documentation about how to call maximumVisibleLights, but still not clue. And even if I found how to properly fix this, I am not sure if the script would not revert to its original state
     
  5. Tim-C

    Tim-C

    Unity Technologies

    Joined:
    Feb 6, 2010
    Posts:
    2,183
  6. LazyDog_Rich

    LazyDog_Rich

    Joined:
    Apr 27, 2014
    Posts:
    70
    I am using 2019.3.2f1, I download the package from package manager
     
  7. Tim-C

    Tim-C

    Unity Technologies

    Joined:
    Feb 6, 2010
    Posts:
    2,183
  8. LazyDog_Rich

    LazyDog_Rich

    Joined:
    Apr 27, 2014
    Posts:
    70
    I gonna try it this night and come back with news, thanks!
     
  9. LazyDog_Rich

    LazyDog_Rich

    Joined:
    Apr 27, 2014
    Posts:
    70
    @Tim-C Yes! The error is gone in 2019.4.1!
    Thanks for the help!
     
  10. maxxogg

    maxxogg

    Joined:
    Jan 16, 2020
    Posts:
    1
    Error still exists in 2019.3.3f1, any update?
     
  11. Refeas

    Refeas

    Joined:
    Nov 8, 2016
    Posts:
    192
    Update to 2019.4 LTS as stated above.
     
  12. Eloren

    Eloren

    Joined:
    Jul 17, 2019
    Posts:
    21
    2021.3...