Made for Shade vs Compatible with Shade

[lynnfredricks]

Hello all,

Along with a certain release we all know is coming, is also coming Hanako for Shade (in English). Meshbox has ported a number of existing models to Shade, much as it also supports Poser and Vue. But "ported" models also tend not to have much in the way of native Shade geometry and are typically straight up polygon meshes.

Id like your feedback on a "Made for Shade" specification, vs "Compatible with Shade". That is, a narrow set of required or recommended things for a model that works best with Shade.

My feeling is that at the top of the list are:

-At least some, if not all native Shade geometry (curved surfaces, line objects)
-Specifying the minimum version of Shade for compatibility purposes (makes a difference when new features become part of the product).

What do you all think?

[Stefan]

Hi Lynn,

well, i can only speak for original Shade titles. I hope that model sets from e frontier, when distributed via Mirye are in it´s original state and not reworked so that they can be used with other programs (in case one does not have Shade). I think translating them from Japanese into English is fine.
But please leave original e frontier Shade titles in it´s original state (curved surfaces etc.)

P.S. i wonder why Hanako took so long, was she reworked so that she can be used with other programs?

Regards
Stefan

[lynnfredricks]

Originally Posted by Stefan

Hi Lynn,

well, i can only speak for original Shade titles. I hope that model sets from e frontier, when distributed via Mirye are in it´s original state and not reworked so that they can be used with other programs (in case one does not have Shade). I think translating them from Japanese into English is fine.
But please leave original e frontier Shade titles in it´s original state (curved surfaces etc.)

P.S. i wonder why Hanako took so long, was she reworked so that she can be used with other programs?

Regards
Stefan

Hi Stefan,

Hanako is in English, and the manual is a little more polished than the original - but nothing in Hanako was changed from the original. Hanako has been waiting for the release of Shade 10, because of the switch joint used in Hanako to switch her expressions.

[Stefan]

Hi Lynn,

thanks a lot for the information!

Regards
Stefan

[Bowring]

Hi Lyn,

I would think that for a start....
'Made for Shade' should mean essentially made or (very) heavily tweaked IN Shade with much of Shade's native geometry etc and as you said a Shade version number for compatibility.

'Compatible with Shade' could be a polygon mesh or something in a Shade file that was created in in another program, then ported to Shade and that may or may not contain any Shade specific features.

Something like this could give people an idea of what to expect in the model.

Another piece of feedback for you.

[lynnfredricks]

Originally Posted by Bowring

Hi Lyn,

I would think that for a start....
'Made for Shade' should mean essentially made or (very) heavily tweaked IN Shade with much of Shade's native geometry etc and as you said a Shade version number for compatibility.

'Compatible with Shade' could be a polygon mesh or something in a Shade file that was created in in another program, then ported to Shade and that may or may not contain any Shade specific features.

Something like this could give people an idea of what to expect in the model.

Another piece of feedback for you.

That's what I was thinking, too.

Hanako is "all natural" for example. In fact, if you thinking about creating your own Shade content, Hanako is a good one to get just to see how E Frontier approaches it.

For example - poses are actually stored as motion files. What's nice about this is that it allows you to keyframe between poses easily for animation purposes.

We have loads and loads of content from Meshbox, and most of it is "Compatible" with Shade, in that its been ported to Shade. Some of the characters, too have expressions stored in Switches (like Nosferatu for Shade and Toon Franklin for Shade).

Anyway - keep the feedback coming on what you think about "Made for Shade". It would be nice if we could come up with a set of recommended specifications and also point to assets you all create that are well optimized for Shade.

[lnbolch]

Perhaps "Made in Shade" rather than "Made for Shade" when the object or scene is 100% Shade. Shipped as .shd. If it is - or has been - say .obj, then "Compatible with Shade".