st-tech / st-tech/ppf-contact-solver
[Bug] Simulation stalls on first frame for high-poly drape scene
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 4.5k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
Summary
Running a cloth drape simulation over a high-poly car model can stall on the first frame. The scene appears to start, but progress does not advance even after waiting for a long time.
Steps to Reproduce
- Open the scene linked from the community discussion.
- Set up/run the cloth drape simulation over the car model.
- Click Run.
- Wait for simulation progress.
Test scene from the discussion link.
Expected Behavior
The simulation should either advance beyond the first frame or report a clear validation/runtime error explaining why the scene cannot be simulated.
Actual Behavior
The simulation appears to get stuck on the first frame and does not advance, even after about an hour.
The mesh was reportedly cleaned before running, including checks for zero-area faces/edges and loose parts.
Environment
- Add-on version: 1.0.9
- Solver version: 2026-05-28-17-20
- Blender version: Unknown
- OS/GPU/driver: Unknown
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 bug report from the community (please provide a reference below).
Community Reference
https://github.com/st-tech/ppf-contact-solver/discussions/68
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the test scene from community discussion #68 and reproduce the cloth drape simulation using add-on 1.0.9 and solver 2026-05-28-17-20. Compare behavior on the first frame while checking the available simulation progress or runtime diagnostics. Done means the simulation advances beyond the first frame or reports a clear validation/runtime error explaining the failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100