Version errors

[andpeterson]

To be figured out over time but I'm getting several errors when stuff gets compiled. Will upload errors as they are received

[andpeterson]

TL;DR Issues:
Assets/SteamVR/InteractionSystem/Core/Icons is missing
UnityEngine.GUIText is obsolete in SteamVR scripts
UnityEngine.GUILayer is obsolete in SteamVR scripts

Assertion failed: Removing Assets/SteamVR/InteractionSystem/Core/Icons because the asset does not exist

A meta data file (.meta) exists but its asset 'Assets/SteamVR/InteractionSystem/Core/Icons' can't be found. When moving or deleting files outside of Unity, please ensure that the corresponding .meta file is moved or deleted along with it.

Assets/SteamVR/Scripts/SteamVR_Stats.cs(12,9): warning CS0618: UnityEngine.GUIText' is obsolete: This component is part of the legacy UI system and will be removed in a future release.'

Assets/SteamVR/Scripts/SteamVR_Camera.cs(201,32): warning CS0618: UnityEngine.GUILayer' is obsolete: This component is part of the legacy UI system and will be removed in a future release.'

Assets/SteamVR/Scripts/SteamVR_Camera.cs(205,34): warning CS0618: UnityEngine.GUILayer' is obsolete: This component is part of the legacy UI system and will be removed in a future release.'

Assets/SteamVR/Scripts/SteamVR_Camera.cs(232,36): warning CS0618: UnityEngine.GUILayer' is obsolete: This component is part of the legacy UI system and will be removed in a future release.'

Assets/SteamVR/Scripts/SteamVR_Camera.cs(236,28): warning CS0618: UnityEngine.GUILayer' is obsolete: This component is part of the legacy UI system and will be removed in a future release.'

Assets/SteamVR/Scripts/SteamVR_Stats.cs(21,24): warning CS0618: UnityEngine.GUIText' is obsolete: This component is part of the legacy UI system and will be removed in a future release.'

[Albert]

I haven't figure this one out. Maybe each project should have a README.txt associated w/ it that lists compatible version number?

I think this also has to do with how these projects eventually get showcased. Perhaps we should just make executables as soon as they're done, and then let them rot out when the system needs to update around them. Then host the executables on a website...

[andybak]

Those look like warnings - not errors.

On Sun, 2 Sep 2018 at 23:32 Albert Hwang ***@***.***> wrote: I haven't figure this one out. Maybe each project should have a README.txt associated w/ it that lists compatible version number? I think this also has to do with how these projects eventually get showcased. Perhaps we should just make executables as soon as they're done, and then let them rot out when the system needs to update around them. Then host the executables on a website... — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADqg1-y_q2Vr5eufml_uV4yuLgZ15Pdks5uXFxygaJpZM4U-wPO> .

-- ixxy.co.uk • t 01273 906061 • m 07968 119324