public record class AtlasSettingsHow the atlas comes off the patch layout, when one is asked for.
Remarks
docs/plan/41 § D13, amended by docs/plan/42 § D2 in one half and not the other. A quantized quad patch is a rectangle, so the layout is already a chart decomposition with zero in-chart distortion and re-cutting it with a general charter would be worse in every respect — that half stays here. The packing does not: the merging described below hands its islands to UvUnwrap.Pack, so there is one packer and one margin rule in the engine rather than two.
⚠ Resolution exists because Margin is counted in texels, which is doc 42 § D8's rule and is not this document's to relax. A margin expressed as a fraction of UV space looks right at the resolution it was tuned at and bleeds at half of it, in a build nobody connects to the packing.
Fields and properties (4)
public int ResolutionThe atlas's edge length in texels.
public int MarginHow many texels of empty space separate two charts.
public float SeamBudgetHow much seam the result may keep, as a fraction of the output's total edge length.
public bool PreferFeatureSeamsWhether the seams that remain are pushed onto feature lines.
Used by (3)
- LayoutAtlasVixen.Geometry.Remeshing
- LayoutAtlasTestsVixen.Geometry.Remeshing.Tests
- RemeshSettingsVixen.Geometry.Remeshing