Skip to content
← All articles
Article

Master's thesis — contact–appearance coupling for wear in texture space

Listen to the audio story

Giving surfaces a memory of contact · 2:25 · AI-written script, synthetic voices

Transcript

Ava: Think of a stone step worn smooth in the middle. Nobody painted that wear on. It came from thousands of feet sliding across the same spot. Now, how would a video game or simulation reproduce that?

Andrew: Usually an artist paints the scuffs by hand, I guess.

Ava: That's the gap Antoine's master's thesis at ÉTS tackles, under the direction of Sheldon Andrews, defended on August 14, 2026. A simulator's contact solver already computes impulses, sliding speed and friction. Then it moves the objects and forgets all that information.

Andrew: So the thesis keeps it.

Ava: Right. The idea is to give material maps, like color, roughness and normals, a persistent local memory of contact. Mechanical contact feeds the texture, exactly where contact happened.

Andrew: How does it work step by step?

Ava: Sparse contact points are grouped into small local patches and projected into texture atlases. On a GPU grid, the system reconstructs tangential velocity, traction and frictional dissipation. Those fields drive how much sliding distance, dominant direction and wear accumulate, and the maps update progressively, with no remeshing of the model.

Andrew: Three contributions, I think?

Ava: Yes. First, a way to accumulate wear locally based on dissipation. Second, an architecture that projects contacts onto atlases and keeps the memory on a fixed mesh. Third, GelSight measurements from a controlled wear bench, used to build the Wear Surface Texture Datasets and compare simulated patterns with measured microgeometry.

Andrew: And the software?

Ava: Two codebases. WearPaper holds the thesis sources, the article, the defense slides and the bibliography. TextureFriction is the interactive simulator, built with Qt six and OpenGL, with contact solving, GPU passes and wear atlases running in real time.

Andrew: And do the results hold up?

Ava: In the tested scenarios, the texels written track cumulative wear more closely than just how far a body traveled, and the contact shape changes the pattern. A cube or a torus on a plane stays within an interactive budget.

Andrew: Where can people see the measurements?

Ava: The public dataset is on GitHub as WearSurfacesDatasets. The full write-up has the pipeline diagram and links to the related GraphQuon talk.

Wear pipeline — contact, velocity, traction, texture integration, atlas and GelSight validation
Table of contents

Couplage contact-apparence pour l’usure de surfaces microstructurées en simulation interactive — my ÉTS master’s thesis (English abstract title: Visual Appearance Evolution from Wear on Microstructured Surfaces in Texture Space). Directed by Sheldon Andrews, defended 14 August 2026. The core idea: give material maps a persistent local memory of contact. Body travel alone cannot predict where wear shows up.

1. The gap

Real surfaces keep a trace of friction and slip. Interactive simulators usually throw that away at the end of each timestep. The contact solver already computes impulses, relative velocity, tangential traction, and dissipation — then updates rigid-body motion and stops. Material maps (albedo, roughness, normals) stay fixed unless an artist paints wear by hand.

The thesis closes that loop: mechanical contact resolution feeds texture-space appearance evolution at the places contact actually happened.

2. Pipeline (one glance)

Sparse contacts are grouped into local patches, projected into material atlases, and reconstructed as tangential velocity, effective traction, and frictional dissipation on a GPU patch grid. Those fields drive accumulation of sliding distance, dominant direction, and wear — then progressive map updates without global remeshing.

Source: wear-pipeline-flow.mmd (same chain as GraphQuon 2025). The interactive implementation in TextureFriction adds a stricter runtime order: pre-solve FBO passes → PGS or AVBD solve → post-solve velocity/traction → sliding/wear/direction deposit → rendering.

Real contact mask — from simulated contact to patch grid

Traction reconstruction on the patch (WLS) — local field before texture deposit

3. Three contributions

  1. Dissipation-based local accumulation — links sliding, reconstructed traction, and visual surface evolution in texture space.
  2. Contact-to-atlas projection architecture — patch clustering, GPU buffers, persistent material memory on a fixed mesh; sliding, direction, and wear written where overlap says contact occurred.
  3. GelSight acquisition and comparison — controlled wear bench captures build the Wear Surface Texture Datasets and calibrate simulated patterns against measured microgeometry.

4. Two codebases

RepoRole
WearPaper (not public)LaTeX thesis sources, ACM article, Beamer defense slides, and canonical bibliography.
TextureFriction (local, E:\master\TextureFriction)Qt6 + OpenGL 4.3+ simulator: PGS/AVBD contact, cluster FBO passes, GPU deposition into sliding/wear/direction atlases. Build: just build, run: just run-build. See docs/architecture/14-thesis-pipeline-and-rationale.md in the repo.

WearPaper is the paper trail; TextureFriction is where the loop runs at interactive rates.

5. Validation

Acquisitions on a reciprocal abrasion bench feed measured normal maps and staged wear progression. Public dataset: ETSim/WearSurfacesDatasets[1]. Surface metrology tooling connects to my CV work on TrueMapData[2] and surfalize integration.

6. Results (snapshot)

In tested scenarios, written texels track cumulative wear more closely than body travel alone; contact topology changes the deposit pattern. A cube or torus on a plane stays within an interactive budget; cost rises sharply when several contact groups are processed together. The method is a physically motivated appearance model, not a full tribology simulator — limits remain around effective-field reconstruction, calibration, and UV parameterization.

7. Research materials

The manuscript sources, article, and defense slides live in WearPaper, which is not public.

References

  1. ETSim. (). WearSurfacesDatasets. [Software repository] github.com.
  2. ETSim. (). TrueMapData. [Software repository] github.com.

References use this article’s publication date.