[Feature] Diagnostic tool to highlight self-intersections during transfer

Open
#46 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
python
Domain
computer-graphics

Research direction

The issue names no files, tests, or entry points. Start by locating the transfer or setup phase and its viewport overlay path, then determine how self-intersecting polygons or triangles can be identified. Done means a diagnostic control visibly highlights those intersections before solver initialization.

Written by the indexing model from the issue text.

Description

deployed enhancement worked
Motivation

Hello! First of all, thank you for the amazing addon.

I have a feature request that would greatly improve the workflow and debugging process. It would be incredibly helpful to add a button or toggle that visually highlights self-intersecting polygons/triangles during the transfer or setup phase.

Proposal

Currently, hidden intersections can cause the solver to become unstable or "explode" upon initialization. Having a diagnostic viewport overlay (e.g., highlighting intersecting faces in red) would allow users to quickly spot and fix topological issues before running the simulation.

Alternatives Considered

No response

Additional Context

Thanks for considering this!

Contribution Agreement
  • I confirm that any code, patches, scripts, attachments, or other copyrightable material I include in this issue may be used, reproduced, modified, and distributed by this project under the Apache License 2.0 or as otherwise described in CONTRIBUTING.md.
  • This is a feature request from the community (please provide a reference below).
Community Reference

No response

Dominant language
Python
Stars
4.5k
Forks
334
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from st-tech/ppf-contact-solver

All issues in st-tech/ppf-contact-solver

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.