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. The 2023.1 beta is now available for testing. To find out what's new, have a look at our 2023.1 feature highlights.
    Dismiss Notice

Question Any Tiny project throw Ambiguous reference in ConvertParticleSystem.cs

Discussion in 'Project Tiny' started by sthill95, Nov 3, 2021.

  1. sthill95

    sthill95

    Joined:
    Dec 17, 2019
    Posts:
    3
    Hello there,

    I tried to launch a project from scratch downloading com.unity.tiny.all by name in Package Manager.
    And in a second time, simply tried to open TinyRacing project from Samples repo.

    Both projects throw the error :
    upload_2021-11-3_12-34-51.png
    ('Range' is an ambiguous reference between 'Unity.Tiny.Particles.Range' and 'System.Range')

    This is a classical error that I understand but I tried to open the cs file and added "Unity.Tiny.Particles." at the right places killing the ambiguous situation but I cannot save the file.

    As it will happen to anybody, do we have a simple workaround or when will it be fixed ?

    Unity version 2021.2.0f1

    Best regards

    Stéphane
     
  2. GilCat

    GilCat

    Joined:
    Sep 21, 2013
    Posts:
    676
    Can you try with Unity 2020.1.x as suggested by the Get Started docs?
    I had problems with earlier versions of
    Unity.
     
  3. GilCat

    GilCat

    Joined:
    Sep 21, 2013
    Posts:
    676
    If you really feel that you must edit that file you must edit at C:\Users\<YOUR USER>\AppData\Local\Unity\cache\packages. Here are the cached packages that will overwrite the ones in your project Library, just make sure to after editing the source package also do some edit in your Library in order for them to be rewritten.
     
  4. bilalakil

    bilalakil

    Joined:
    Jan 28, 2018
    Posts:
    62
    Can confirm that I encountered this issue with Tiny 0.32.0 on Unity 2021.2.9f1. Downgrading to Unity 2020.3.26f1 seems to have solved the problem.