Weighted Creases Please?

[Wegg]

In Wings3D currently we have the ability to select an edge and define if it is a hard or a soft edge. When you subdivide your mesh it then uses that information to define what that area looks like after it has been subdivided. Generally the end result looks like a hard crisp edge or a "crease".

Do you think it would be possible in future versions of Wings3D to change this from being a binary "on" "off" to a percentage? I would love to have the ability to select an edge and set to to 50% hard. Or 90% hard. . . I think my models would be a lot leaner due to me not having to throw in as many bevels.

Possible?

http://www.blender.org/development/relea...-subsurfs/ How Blender does it.

[Wegg]

I guess I'm alone in my desire for Weighted Creases. :-)

[Geta-Ve]

I guess I'm alone in my desire for Weighted Creases. :-)

Funny enough I have need of this very feature recently. My question is though, how well do weighted edges transfer between programs?

[Wegg]

That I don't know. I don't think there is anything in the obj file format that lets you define the weight of an edge. From what I am reading, the only format that does it well is the lightwave object format. Blender doesn't have an option for importing these edge weight or "Creases".

Such a shame. My models tend to be much more dense then they really need to be. :-(

[ggaliens]

Hmm ... what can be done with a Surface Evolver plugin. Maybe ... ANYTHING CAN HAPPEN.

LOL.

[Geta-Ve]

lol.

To be honest, if these weighted edges (other than hard / soft) can't be exported out, then there is really no need to even attempt the feature, in my opinion at least.

[Wegg]

They can be exported out if they are supported by the lightwave exporter/importer. Then the Lightwave, messiahtudio and Modo users could benefit. But I don't know who uses wings currently. . .

[Geta-Ve]

The thing is, at least in my opinion, it would be wrong to give users modelling features that "probably" won't transfer over to most other packages. The reason is because you will just end up confusing them and causing needless frustration when they open their model in, let's say, Maya, and can't figure out why their model doesn't subdivide like they want.

It's asking for alot of headache.

Don't get me wrong, I would love this feature, but if my efforts can't be moved over to any other package than it is simply a waste of my time even considering it.

The reason why it works in Blender (from the standpoint of it simply existing) is because Blender is an all in one package, it's self contained within its own pipeline. Blender can have features that don't transfer simply because they don't need to.

Same with Maya, Lightwave, Max, etc etc etc.

Just food for thought.