Curvature graph weirdness

Is it normal that the curvature graph command in a surface will show the whole untrimmed surface? It looks to me like a bug, I would expect that only the part of the surface that is not trimmed to be shown.

torusslice.3dm (192.1 KB)

It’s always done that.

For beginner 3D surface modellers, it’s actually a useful thing; a reminder to rebuild trimmed surfaces before proceeding.

Why should a trimmed surface be rebuilt? Rebuilt as in using Rebuild? Or something else?

Does not mean it is the right thing to do. I feel it is weird to me

just that you manage to get a weird view of an analysing tool - it does not mean something is wrong or there is a bug.


at least do:
before cutting of the slice of the torso (or explode / untrim)
_srfSeam to have a single surface / face - not a big trimmed one twice.
after trimming the minimum step i would recommend is
_shrinktrimmedSrf
then curvatureGraph is readable in the correct scale - see above.

if there is a explicit use case from a real modelling task share it please.

(but i agree that sometimes curvatureGraph is to enthusiastic and showing to much - one use case is _blendCrv from Edge to Edge with CurvatureGraph on … )

happy modelling - kind regards - tom

A natural surface boundary is better for building neighbouring surfaces with a good CP structure and G1/G2 matching, so when possible (non-colinear U or V edge-to-edge trim boundary) it’s good to rebuild. I have tried RefitTrim, but it is not yet as developed as Alias’ equivalent tool. It would be great if RefitTrim would receive some love from the developers.

It’s not. The trimmed part of the surface is still there–trimming an object ADDS information it does not take anything away–and still influencing the part you can see, which is really important and frankly it’s probably a mistake that there isn’t a simple switch for all the other analysis tools to graphically untrim your surfaces.

Okay, but if the math is ‘still there,’ then why does the Curvature Analysis texture magically know how to stop at the trim line while the Graph acts like it’s hallucinating the rest of the surface? Make it make sense. Why is one tool smart and the other one stuck in 1995?

I just explained that it’s a mistake that CurvatureGraph and Zebra and Emap don’t have an easy way to show the whole surface. Fine surface tuning without seeing the whole surface doesn’t work.

Do you think I’m mistaken about the nature of trimmed surfaces?