So is support for the ICE toolset dead? I received no response to my support emails of several weeks ago.
When I first installed ICE, I had to fix code in one of the C# files to get a clean compile, enabling some defines that should have been enabled by virtue of the installation process. I reported it. Got no responses. Since then, every new Unity update has broken ICE. After the last update (2017.1.1f1) , ICE generated 705 (seven zero five) compiler errors. From the sounds on other ICE-related threads, it appears there may be an incompatibility with another package (Terrain Composer? Gaia?). Today’s update failed me entirely. I thought I would try yet again to remove the asset and reimport it. I got an error message that the updater script itself crapped out trying to import ICE.
I am now going through the process of dismembering my test projects, third party asset by asset, to determine the incompatibilities. Wouldn’t it be nice if the provider of the tool collected our user inputs and told us what was going on? If I missed some obvious “do THIS to fix THAT” discussions that any of you know about, please point me to them.
No one wants to see the asset reviews used as a weapon, but it may be time to ask the asset store admins to add a new “Support Deprecated” state for assets that no longer have visible support, so new customers do not get burned.
A minor update. I was able to confirm there is an asset incompatibility at work here, between ICE and Terrain Composer. Removing Terrain Composer fixes the problem for my affected projects, but it also nukes many existing terrains that have already been detailed. And there are still actual code issues with ICE off-the-shelf. But I was able to work around them.
If this is an inappropriate post for the given forum, my apologies. Admins, nuke at will if so. The alternative seemed to be to tag this message onto the existing product thread, which made no sense, as the many issues raised there are not being addressed.
While ICE actually works well on my 2017.1.1.p2 rig, the developer kinda marches to the beat of his own drum. (Dodgy support is very frequent with Unity assets.)
It hasn’t been updated for 3 months now, but I trust it will be.
And yes, calling out absentee developers in the asset reviews does make sense: it is something they are forced to react to.
Thanks for your reply. I have since found a couple of recent public comments from the developer in response to other support requests. He also speaks to the code issue I found and provided a solution (though not explained well). We seem to be on the verge of the Next Big Release from him, but that is an old story. Let’s hope it is a true one in this case.
The 1.4 update was announced for last month. I am extremly dissappointed, for me the worst buy ever in the asset store.
It is extremly hard to learn and use, Buggy and it says in the description it is very easy to use. I am still waiting for the update without much hope.
Thanks for the hint. I am a hobby developer and a angry with ICE now, it is bad to pay two times for the same thing I Need. But thanks for the hint, I will think about it.
Settle petals, tantrum’s don’t accomplish much, just make you guys look childish, impatient and helpless. Like it was mentioned above, an update is coming, patience…had my rant too
For my issue, the big problem was several hundred error messages when ICE and Terrain Composer are both installed. I resolved that problem by removing Terrain Composer. The smaller problem was that with Terrain Composer removed, ICE would still not compile cleanly unless an ICE-specific global define was manually set in the environment (no instructions for this included with the install or documented where I could find it) or the ifdef for this define was commented out in one of the source files. I figured out the work-around myself, then found a comment in a thread that explained the problem.
I am not sure why the Unity update exacerbated the problem, but the Unity update is working fine in every other area that I can see. The problem seems to be with the Terrain Composer and ICE assets only. There are some new warning messages for other assets that have apparently been using deprecated functions for a while, but nothing just plain broke that I can see.
If I encounter this problem again, I will try to capture the log file (if any) to get an explanation as to why the rebuilding compile aborted. This time around, I could not find a log with any useful data.
I understand that complex software sometimes has subtle issues that need resolution. My concern is that an asset supposedly on the top tier of Unity 3rd party tools should “go silent” on support. But I have it basically working again now.
