Hi Guillaume,
You sure know who to send to to troubleshoot your custom node.
Mind sending it to them?

Chris


On 27 Sep, 2013, at 11:25 PM, Guillaume Laforge 
<guillaume.laforge...@gmail.com> wrote:

> Yes, SP2 fixed the ICE instance memory issue in SiToA I think.
> So it does not make sense to use 2014 SP1 as we are using Arnold.  
> 
> 
> On Fri, Sep 27, 2013 at 10:56 AM, Stephen Blair <stephenrbl...@gmail.com> 
> wrote:
> Maybe you should try compiling against SP1 and see if that crashes too.
> In SP2, wasn't there just that one SDK change for ICE array access, which 
> broke binary compatibility?
> 
> 
> On 27/09/2013 10:37 AM, Guillaume Laforge wrote:
>> Hi guys,
>> 
>> I compiled a custom ICE node for 2014 SP2 and it crash all the time (It 
>> works perfectly in 2013 QF7).
>> As this node is rather complicated and call external libraries, it is not 
>> easy to send it to support (and I don't have the time right now to isolate 
>> the problem in a simpler code).
>> Because of that we are staying in 2013 for the production.
>> 
>> I'm wondering if other users got similar issue with custom ICE node in SP2 ?
>> 
>> Thanks,
>> 
>> Guillaume Laforge
>> 
>> 
>> --------------------------
>> To unsubscribe: mail softimage-requ...@listproc.autodesk.com with subject 
>> "unsubscribe" and reply to the confirmation email.
> 
> 
> --------------------------
> To unsubscribe: mail softimage-requ...@listproc.autodesk.com with subject 
> "unsubscribe" and reply to the confirmation email.
> 
> --------------------------
> To unsubscribe: mail softimage-requ...@listproc.autodesk.com with subject 
> "unsubscribe" and reply to the confirmation email.
--------------------------
To unsubscribe: mail softimage-requ...@listproc.autodesk.com with subject 
"unsubscribe" and reply to the confirmation email.

Reply via email to