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

Bug with assembly references?

Discussion in 'Project Tiny' started by meanfox, May 26, 2020.

  1. meanfox

    meanfox

    Joined:
    Apr 9, 2020
    Posts:
    25
    I'm trying to modify the Tiny3D sample by adding an authoring assembly.

    All I do is this:

    1. Add an "Authoring" folder under scripts
    2. In that folder, add an assembly reference called Tiny3D.authoring with a reference to the Tiny3D assembly.
    3. In that folder, add a MonoBehaviour that references Rotate.
    4. Confirm that Tiny3D and Rotate show up in the Tiny3D.authoring references in visual studio.

    result: The type or namespace name 'Rotate' could not be found (are you missing a using directive or an assembly reference?)

    Can anyone advise what's wrong with this process?

    Thanks
     
  2. Ted_Wikman

    Ted_Wikman

    Unity Technologies

    Joined:
    Oct 7, 2019
    Posts:
    883
    Hello @meanfox,
    I take it that the Rotate structure you are referring to is
    Tiny3D.Rotate
    found in the Tiny3D demo.
    When you are referencing
    Rotate
    , are you also referencing it by the full name
    Tiny3D.Rotate
    or have added a using statement at the top of the file (
    using Tiny3D;
    )?

    If you have done this, but still have the issue, could you share a screenshot of your assembly definition, and the full code. Then I can have another look at it.
     
  3. meanfox

    meanfox

    Joined:
    Apr 9, 2020
    Posts:
    25
    Thanks @Ted_Wikman

    I think these 2 screenshots tell the whole story:

    1.jpg 2.jpg
     
  4. Ted_Wikman

    Ted_Wikman

    Unity Technologies

    Joined:
    Oct 7, 2019
    Posts:
    883
    Thank you for the screenshots. What you have should be valid. I recreated the exact setup you are using, and I do not see the error you are seeing.

    Do you see the error both in Unity's console and in Visual Studios, or only in Visual Studios?
     
  5. meanfox

    meanfox

    Joined:
    Apr 9, 2020
    Posts:
    25
    Only in VS.
    Do you not see the bug in VS?
    I made a test using vanilla Unity (no dots/tiny) and did not experience this problem.
     
  6. Ted_Wikman

    Ted_Wikman

    Unity Technologies

    Joined:
    Oct 7, 2019
    Posts:
    883
    You can try the following two solutions, to see if it helps with your situation.
    1. Remove the .sln and any other VS related files and folders in your project directory, and re-generate the solution files
    or
    2. Generate a DOTS C# Solution, by navigating to Assets > Generate DOTS C# Solution, and then press the Generate Solution button in the popup window, and Open Solution once it is ready.

    We will investigate this further internally, to see if we can figure out the root case of this issue.
    Sorry for the inconvenience.
     
  7. meanfox

    meanfox

    Joined:
    Apr 9, 2020
    Posts:
    25
    I guess I'll put Tiny aside and check back in about a year.
    This assembly issue is not a showstopper but was a timewaster.
    But more critical are the following deficiencies:
    1. Need some very simple UI (even just button) and text so can make something interactive
    2. Editor is very crashy. Cannot be productive. Takes a long time to reopen the project.
     
  8. Ted_Wikman

    Ted_Wikman

    Unity Technologies

    Joined:
    Oct 7, 2019
    Posts:
    883
    Thank you @meanfox for the feedback and that you took the time to test Project Tiny out. A UI solution is in the works, and will be included in a later version of Project Tiny.

    As for the editor crashes, was there any particular actions that seem to trigger the editor instabilities? Any leads on this are highly appreciated.
     
  9. meanfox

    meanfox

    Joined:
    Apr 9, 2020
    Posts:
    25
    Hi @Ted_Wikman - the crashes were too random to determine a repro.