Octane 3? what happened to June beta realease?

[Refracty]

And please take out the GEOMETRY LIMITATION before V3 - It is frustrating

[fatrobotsneedlove]

And please take out the GEOMETRY LIMITATION before V3 - It is frustrating

This and add an IOR texture if V3 really is not coming out til the end of the year

[Goldorak]

And please take out the GEOMETRY LIMITATION before V3 - It is frustrating

This and add an IOR texture if V3 really is not coming out til the end of the year

2.x is pretty much done with 2.25 (which adds ORC integration).

We are at the point where deeper changes to the 2.x engine (like removing the geo limit) would mean architectural rewrite of core code that would break things for many months or more. We have undertaken doing this work in parallel to 2.x releases since late 2014, and that is Octane 3.

OSL support is the best way to handle new texture input types like IOR. As OSL is not coming online until later in the 3.x beta, we will take a look at getting it enabled in the alpha as a texture pin, and possibly render pass option to complement the V3 reflection/refraction filter passes .

[darkline]

2.x is pretty much done with 2.25 (which adds ORC integration).

We are at the point where deeper changes to the 2.x engine (like removing the geo limit) would mean architectural rewrite of core code that would break things for many months or more.

That makes a lot of sense and I understand you dont want to slow development down. But please be aware that myself, and Im sure many other customers got stung with this fault. I work with large scenes, everything I used in octane 1x has never opened with v2. I have only used it for testing as it's no use to me with this limit.

Nothing can be done about that now, all I'm saying is think fairly about how much you charge for this upgrade. I paid for something which I couldn't use (we were never even informed this was an issue before purchasing), now I have to pay yet again to have the issue fixed. Not really a great way to hang onto users.

Clearly v3 won't be free as it has other new features, but accept some responsibility for this and be fair to your customers.

[Goldorak]

2.x is pretty much done with 2.25 (which adds ORC integration).

We are at the point where deeper changes to the 2.x engine (like removing the geo limit) would mean architectural rewrite of core code that would break things for many months or more.

That makes a lot of sense and I understand you dont want to slow development down. But please be aware that myself, and Im sure many other customers got stung with this fault. I work with large scenes, everything I used in octane 1x has never opened with v2. I have only used it for testing as it's no use to me with this limit.

Nothing can be done about that now, all I'm saying is think fairly about how much you charge for this upgrade. I paid for something which I couldn't use (we were never even informed this was an issue before purchasing), now I have to pay yet again to have the issue fixed. Not really a great way to hang onto users.

Clearly v3 won't be free as it has other new features, but accept some responsibility for this and be fair to your customers.

I totally understand. The V3 upgrade price will be reasonably priced.

[dcardwell]

Please add the Udim support and just ability to blend multiple displacement textures through mask. Also don't cut off negative values in floating point displacement. These are industry standards we need supported in film and tv. Other stuff is just gravy...

[geofnarlee]

tick tock. how's the release date looking?

[Goldorak]

tick tock. how's the release date looking?

See v3 update thread

[geofnarlee]

k thx!