these export scripts only work with 2.2 versions, grab the 2.2 RC3 from the release candidates forum...sgrinavi wrote:Version 1.021 beta 2.1Strange. Did you use the latest octane release?
Is that the one?
Radiance
these export scripts only work with 2.2 versions, grab the 2.2 RC3 from the release candidates forum...sgrinavi wrote:Version 1.021 beta 2.1Strange. Did you use the latest octane release?
Is that the one?
Thanks, that's better. One thing though; I'm guessing that it's not supposed to be upside-down when it comes into Octane?these export scripts only work with 2.2 versions, grab the 2.2 RC3 from the release candidates forum...
Radiance
Well, its not so much about the exporter as is about Octane, which right now doesn't support instances. They'll be here in version 1.23, which is coming soon, (at this rate it's probably out and we haven't noticed yetPhizter wrote:Is there any chance the exporter will one day support the 3ds Max substitute modifier or Xref proxy objects?
-o is the image path, should look like this:smalls wrote:Hello! Does anyone knows what this error message means?
I'm using octane on windows 7 and i tried octanetomax plugin
on max 2010 and 2011 64bit and it's the same message all over again.
Thanks!
kubo wrote:Well, its not so much about the exporter as is about Octane, which right now doesn't support instances. They'll be here in version 1.23, which is coming soon, (at this rate it's probably out and we haven't noticed yetPhizter wrote:Is there any chance the exporter will one day support the 3ds Max substitute modifier or Xref proxy objects?). Meanwhile instead of substitute modifier you can use this nice free script http://www.scriptspot.com/3ds-max/scrip ... ce-replace which works fine with instances and octane (I've used it before), And for xref you''ll need to bind them or merge them prior to export.