NodeCanvas causes problems with incremental compiler

NodeCanvas Forums Support NodeCanvas causes problems with incremental compiler

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #13317
    handsomegeoff
    Participant

    Hello,

    I’ve been trying to play around with the new ECS stuff and have noticed a problem importing NodeCanvas when the new incremental compiler is used. This is what I did.

    – Installed the latest version of Unity as of today.
    – Started a new blank project and imported NodeCanvas
    – Switched to .NET 4.x under the player settings
    – Opened the package manager and installed version 0.0.42-preview.1 of the incremental compiler

    I get the 2 errors you can see in the attached snips. I understand that the incremental compiler is still in preview, and hence I wouldn’t expect you to support it out of the box. I thought I would report it regardless and ask if you can think of any work-arounds?

    I should add that this doesn’t seem like a problem with the compiler. I’ve installed several other popular packages without these sorts of errors (A* path-finding project, Behavior Designer, Odin, etc.)

    As always, your support is greatly appreciated.

    Thanks,
    Geoff

    Attachments:
    You must be logged in to view attached files.
    #13333
    Gavalakis
    Keymaster

    Hello Geoff,

    Unfortunately I haven’t yet had the chance to check the ECS stuff, but this (rather weird) problem about UNetWeaver has been reported once before.

    At first I though it had something to do with the SyncBlackboard.cs file, which is the ONLY file that has any network code written within, but the other person that reported that same error, also reported that deleting the file had no change.

    With that said, I will need to download and test ECS myself and will do so within the weekend, but I truly suspect that this has to be a Unity bug, getting picky about some method/property naming I am using somewhere, since UNET works with explicit naming conventions and thus a conflict might be possible.

    Thank you for reporting and confirming the issue!

    Join us on Discord: https://discord.gg/97q2Rjh

    #13351
    dave
    Participant

    Hi Geoff,
    Your Error has nothing to do with nodecanvas. I read all threads about the new compiler.
    This Unet-Weaver Error is a Bug which has to do with one of unitys-dlls for the Unet-syncing.stuff, when utilizing the incremental compiler.
    If you are working on a multiplayer game depending on that, than you should switch back to the standard compiler.
    As the developers got more unresponsive in the last time, in the unity thread someone came up with a solution ( more of a hack ), which works.
    I did it for me, and it works just fine. He wrote a step by step guide for this .
    https://forum.unity.com/threads/unity-incremental-c-compiler.523993/page-2
    . Have a look at post #76 there.
    Also you may want to read a bit more through that thread, but if you just want a solution and start using the compiler , then all you need to do is follow that instructions.

    Hope this is helpful for you and anybody else interested.

    #13373
    Gavalakis
    Keymaster

    Thanks for letting us know @dave.
    I am glad it is not a NodeCanvas bug, which to be honest I could’t find any reason for it to be 🙂

    Join us on Discord: https://discord.gg/97q2Rjh

    #13410
    handsomegeoff
    Participant

    Hey Guys,

    Thanks for letting me know about the workaround, Dave. It seems to work!

    That said, a few things have changed since I originally posted this report and I wanted to share what I’ve learned; I’ve been able to confirm the problem isn’t with the incremental compiler; or at least it doesn’t seem to be. Here’s my reasoning (it’s going to be long winded, sorry)…

    I had been using the incremental compiler because when I downloaded the Entities package initially, the built-in compiler complained about some C# 7.2 features that Unity had made use of in the Entities library. The incremental compiler didn’t have such problems as it seemed compatible with these features.

    Now, having said that, Unity has since released Unity 2018.2. From what I can tell, they have added the C# 7.2 features as I no longer need to download the incremental compiler to build a solution with the Entities library. Great! Unfortunately, I still run into the same error. Please see below.

    – I created a new project with 2018.2.0f2
    – I added the NodeCanvas library
    – I changed the player to .NET 4.X Equivalent
    – Enter play mode – no problems
    – I downloaded the Entity package from the packages manager
    – *Boom* – stuff went south

    I’m wondering if the problem lies with the Burst compiler included with the ECS framework? I don’t know. I wanted to share regardless, as it may come up when ECS and the Burst compiler leave preview and enter GA.

    Thanks!
    Geoff

    Attachments:
    You must be logged in to view attached files.
    #13420
    sugoidev
    Participant

    The Incremental Compiler is a dependency for the ECS package, so it is added even if you don’t directly reference it in your manifest.

    You can check that it is indeed compiling your stuff by going into the preferences. There should be a “Compiler” section there. That’s from the Incremental Compiler. Also, you’ll notice a folder in your Library named “IncrementalCompiler”, where it generate its response files for compilation.

    The latest version of the Incremental Compiler (.16) added a workaround that might fix the error we’re all getting. It’s still only on the staging repository, so it won’t show up in the package manager unless you’re using the staging repo in your manifest. But, give it a few days and it’ll be in the normal repo.

    I didn’t test it yet, since I patch the Weaver (I’m the one that wrote the instructions on how to do it on that thread), but I plan to do so today.

    Edit: Just tested with the latest version of the Incremental Compiler and the issue remains.
    Patching the weaver still seems to be the only available solution for now.

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.