Any support for Unity 2017?

  • July 21, 2017 at 16:31 #21473

    Apex Path is not working with Unity 2017. Are there any plans for an update?

    July 22, 2017 at 15:08 #21483

    I asked the same question six days ago. Not even an answer so far. Abandonware?

    July 25, 2017 at 14:19 #21501

    Works fine in 2017.1 not that I have used it extensively. But no errors or anything.

    What the exact problem?

    Its summer time, and summer vacation time, be cool

    • This reply was modified 11 months, 4 weeks ago by Linus.
    July 26, 2017 at 20:28 #21506

    Hi, Thanks for your reply.

    For example I get the following (pure apex path):

    Assembly: ‘C:/Development/Unity/Apex Path/Assets/Apex/Apex Binaries/Editor/ApexSharedEditor.dll’ uses obsolete Unity API (UnityUpgradable)
    Assets/Apex/Apex Path/Scripts/Units/UnitComponent.cs(235,49): error CS0619: UnityEngine.Physics.minPenetrationForPenalty' is obsolete:use Physics.defaultContactOffset or Collider.contactOffset instead.’

    The examples are also not working
    Internal error: Recursion detected while updating scripts (assembly name: Assembly-CSharp.dll)

    Best regards

    July 27, 2017 at 02:55 #21508

    Sorry for late reply.

    Forgot I got that error as well. But simply do as the error suggest :)

    Change line 235 in UnitComponent.cs to

    totalOffset -= ( 2 * Physics.defaultContactOffset );// Physics.minPenetrationForPenalty);

    Gets the code compiled. Bet they will have a proper fix soon

    • This reply was modified 11 months, 3 weeks ago by Linus.
    July 27, 2017 at 07:03 #21511

    Thanks for your hint :-)

    I’m not sure if this is the way for a 100$ asset, that every user has to patch his own local copies. Unity 2017 beta is out for a long time, so I expected that a professional company like Apex is fixing this issue very fast.

    July 31, 2017 at 15:59 #21550

    Same issue here. Instead of changing line 235 we added || UNITY_2017 to line 232.

    Besides the code compilation issue we also ran into an issue with one of the inspectors using a texture API that is moved in Unity 2017.
    We’re currently trying to build our own dlls from source, but since there are no solutions or build instructions included this is somewhat painful trying to figure out what to include and not include.

    Apex, please release an update for 2017.1 or at least comment on if Unity 2017 will be supported so people know what to expect.

    July 31, 2017 at 16:26 #21559

    We will provide an update for Unity 2017 as soon as possible.

    August 2, 2017 at 13:32 #21615

    Thanks for the update!
    We upgraded to 2.5 today and can confirm that everything works. The one issue we had was Unity changing the GUID in ApexShared.dll.meta breaking the connection to the master component on our prefabs.
    We fixed it by reverting the GUID back to the old one.

You must be logged in to reply to this topic.

Topic Tags