Build errors with latest Unity - Printable Version +- Obi Official Forum (https://obi.virtualmethodstudio.com/forum) +-- Forum: Obi Users Category (https://obi.virtualmethodstudio.com/forum/forum-1.html) +--- Forum: Obi Rope (https://obi.virtualmethodstudio.com/forum/forum-4.html) +--- Thread: Build errors with latest Unity (/thread-817.html) |
Build errors with latest Unity - Bluerex - 14-01-2019 Hi, With the current asset store version of Obi Rope, I get build errors. I created a new, empty project, imported Obi Rope, then opened the solution and did a build, and I get the following errors: Code: Error CS0308 The non-generic type 'Queue' cannot be used with type arguments Test F:\Unit Projects\Test\Assets\Obi\Scripts\Actors\ObiBone.cs 104 Any tips on how to fix this? RE: Build errors with latest Unity - josemendez - 14-01-2019 (14-01-2019, 06:39 PM)Bluerex Wrote: Hi, Hi, Cannot reproduce this on Unity 5.6, 2017.4 or 2018.2. Stopwatch is defined in System.Diagnostics; and CoroutineJob.cs includes it. Queue<T> is defined in System.Collections; and ObiBone.cs includes it. What is your target platform and project settings? (specially Scripting runtime and API compatibility level) RE: Build errors with latest Unity - Bluerex - 14-01-2019 (14-01-2019, 07:29 PM)josemendez Wrote: Hi, My unity version is 2018.3.02f (the latest). My scripting runtime is .NET 4.x My API compatability level was .NET 2.0, but I also tried .NET 4.X and it still didn't work. RE: Build errors with latest Unity - ibbybn - 14-01-2019 (14-01-2019, 10:03 PM)Bluerex Wrote: My unity version is 2018.3.02f (the latest). I'm using 2018.3.1f1 with no problems here. Must be something else. Btw 2018.3.02f is not the latest, it's a half year old beta. RE: Build errors with latest Unity - Bluerex - 14-01-2019 (14-01-2019, 10:36 PM)ibbybn Wrote: I'm using 2018.3.1f1 with no problems here. Maybe that's the issue then - I'll get the latest from the site. Thanks! (14-01-2019, 10:43 PM)Bluerex Wrote: Maybe that's the issue then - I'll get the latest from the site. Thanks! Just to update this thread - Updating unity didn't help, but updating Visual Studio 17 to 15.9.5 worked. |