Octane Crashed Modo 11.2 on obj import Tweet

[face_off]

I know OTOY are currently working hard on the next release at the moment, but I am unsure of the exact release date.

Paul

[Greggers]

Ive just downloaded the latest build. 3.8 and modo 11.2v1 v2 v3 crashes still while I try import an obj into modo. Take off the octane plugin and modo works fine on import. So I still have the same issue.

I only came here to check because I saw the news of octane 4 and couldn't believe that my issue has not been resolved since before Christmas. I saw a new build for OS X and downloaded it as soon as I got home. Who do I speak to because its just beyond me now as to how long I've needed to wait for a fix and nothing has happened. I would like to be using the latest build of modo with the latest build of octane.

[face_off]

Ive just downloaded the latest build. 3.8 and modo 11.2v1 v2 v3 crashes still while I try import an obj into modo.

I specifically tested this prior to posting that build yesterday, and the crash was fixed. Can you pls confirm exactly which version of the plugin you installed pls?

Paul

[Greggers]

yep its OctaneRender for Modo 3.8.0.128

Im using modo 11.2v3 OS X and I have the octane standalone version 3.07.0.

[face_off]

yep its OctaneRender for Modo 3.8.0.128

Thanks. I have been able to replicate the crash on the latest Octane API release (3.08 RC2). I have had to re-escalate this to OTOY as it's an Octane API issue, which they will need to address. My apologies for the delay.

Paul

[Greggers]

Oh ok. Well hopefully I’m not waiting till fours release. Thanks for the test Paul and the feedback.

[Greggers]

Any update Paul, I've moved to modo 12 now?

[face_off]

Regretfully even Octane 3.08 RC3 is crashing Modo when importing an OBJ file. I have reported it to Otoy.

Paul

[Greggers]

I’m lost for words really.
So each time you are reporting it to otoy they just ignore you? I’ve had this issue since December. It’s April 2018. I don’t understand why no one else is reporting the problem. I must be the only person using a mac with updated Modo because it’s unbelievable that I’m having to either use an older version of octane missing out on new features and bug fixes if I want to stay up to date with my main modelling program or I miss out on bug fixes and new features in my main modelling program to enjoy octane and the £600 I paid for it.

Can you point me in the direction of someone I can speak to who has the power to resolve this?? It’s just not right and I’m annoyed as well as disappointed. It’s not good enough.

[abstrax]

I’m lost for words really.
So each time you are reporting it to otoy they just ignore you? I’ve had this issue since December. It’s April 2018. I don’t understand why no one else is reporting the problem. I must be the only person using a mac with updated Modo because it’s unbelievable that I’m having to either use an older version of octane missing out on new features and bug fixes if I want to stay up to date with my main modelling program or I miss out on bug fixes and new features in my main modelling program to enjoy octane and the £600 I paid for it.

Can you point me in the direction of someone I can speak to who has the power to resolve this?? It’s just not right and I’m annoyed as well as disappointed. It’s not good enough.

No we are not ignoring Paul. The problem is that we have no idea what's going on and what we can do about it on our end.

All we know is: FBX of Modo crashes, when the Octane plugin is installed. The Octane for Modo plugin is using an Octane DLL which is statically linked against its own version of the FBX library, i.e. it should be independent of the FBX library in Modo, but for some reason that doesn't seem to be the case. We also don't know why Modo is using the FBX library at all when it loads an OBJ.

In other words: From what we can see, the problem is in FBX and/or Modo but not in Octane. And since both FBX and Modo are closed source we have 0 insight what is going on here.

Last week I have asked on the Autodesk FBX forum, what we can do about it, but my post got deleted. I will try again today, but that's the current status.