Hair & fur won't work natively in some plugins...

[face]

When there is no way to get needed data for hair and fur from the host app, how should Octane manage this?
It can´t be the problem of the plugin devs to create a fur system inside the apps only because Octane has it in the feature list.

Some car radios have as feature a docking station for an ipod. When you doesn´t have one, it´s your loss.

face

[Seekerfinder]

When there is no way to get needed data for hair and fur from the host app, how should Octane manage this?
It can´t be the problem of the plugin devs to create a fur system inside the apps only because Octane has it in the feature list.

Some car radios have as feature a docking station for an ipod. When you doesn´t have one, it´s your loss.

face

This is what the announcement said from Otoy: "Hair and fur – An optimized hair render primitive is now available...". But it is not available for everyone. The plugins use the same core and I am not aware of any feature available in Standalone to date that is not also transferable to the plugins (save alembic which is a one-way street by definition). So, to me, that's a somewhat misleading claim. I am not the only that was disappointed about this...

Like I said before, all sorts of things we claimed to be 'impossible' before, some of which is now available in 2.

Seeker

[face]

Alembic wouldn´t help when you haven´t spline/strand data to fill the alembic file...

face

[Seekerfinder]

oi...