Mr. Tassev, have you ever considered making CrochetPARADE a video game?
I'm an indie game designer planning out a cozy life simulation game called Textisle, in which the core mechanic is a real-time, player-controlled crochet simulation. The player executes stitches one at a time using button inputs, and the fabric grows stitch by stitch as they work through a pattern. Players harvest and process fiber, spin it into yarn, then crochet and block wearable, usable, and giftable objects. The goal of the game is to introduce new people to the pleasure of crochet and to allow experienced crocheters to design quickly and without the expense of materials (like CrochetPARADE)! I have attached a simple UI wireframe demonstrating the idea. (Please forgive that the stitches in the upper bar don't make sense with continuing in the round; I wanted non-crocheters to be able visualize that it's pattern-based rather than just have a bunch of plus signs for the SCs.) When I posted it in crochet communities with the game idea, the overwhelming response was, "Where can I playtest this?" which was very exciting.
I found CrochetPARADE while researching and wanted to ask whether the graph.cpp layout algorithm could be adapted for real-time interactive use. My current prototype built in Godot 4 uses pre-made stitch mesh scenes placed on anchor points. It's a purely topological approach where stitch formation is recorded as data and geometry is constructed from known state rather than simulated physically. This works for the prototype, but I'm thinking ahead to what the fabric geometry system needs to look like at scale.
The documentation describes a weighted graph where nodes are stitch-level material points and edge weights encode stitch-scale distances, with geometry reconstructed via shortest-path distances and annealed gradient descent. Does the algorithm require the complete connectivity graph upfront, or can a new node and its edges be appended to an existing solved embedding and relaxed locally? I'm an experienced crocheter but a beginner developer (my day job is in the legal field), so I'm sorry if my question is obvious or dumb. Any guidance would be appreciated.
Thank you for building and open-sourcing this. It is so cool and I think I think wrapping it in a free-to-play game could bring it to people who would never find it otherwise!
I'm an indie game designer planning out a cozy life simulation game called Textisle, in which the core mechanic is a real-time, player-controlled crochet simulation. The player executes stitches one at a time using button inputs, and the fabric grows stitch by stitch as they work through a pattern. Players harvest and process fiber, spin it into yarn, then crochet and block wearable, usable, and giftable objects. The goal of the game is to introduce new people to the pleasure of crochet and to allow experienced crocheters to design quickly and without the expense of materials (like CrochetPARADE)! I have attached a simple UI wireframe demonstrating the idea. (Please forgive that the stitches in the upper bar don't make sense with continuing in the round; I wanted non-crocheters to be able visualize that it's pattern-based rather than just have a bunch of plus signs for the SCs.) When I posted it in crochet communities with the game idea, the overwhelming response was, "Where can I playtest this?" which was very exciting.
I found CrochetPARADE while researching and wanted to ask whether the graph.cpp layout algorithm could be adapted for real-time interactive use. My current prototype built in Godot 4 uses pre-made stitch mesh scenes placed on anchor points. It's a purely topological approach where stitch formation is recorded as data and geometry is constructed from known state rather than simulated physically. This works for the prototype, but I'm thinking ahead to what the fabric geometry system needs to look like at scale.
The documentation describes a weighted graph where nodes are stitch-level material points and edge weights encode stitch-scale distances, with geometry reconstructed via shortest-path distances and annealed gradient descent. Does the algorithm require the complete connectivity graph upfront, or can a new node and its edges be appended to an existing solved embedding and relaxed locally? I'm an experienced crocheter but a beginner developer (my day job is in the legal field), so I'm sorry if my question is obvious or dumb. Any guidance would be appreciated.
Thank you for building and open-sourcing this. It is so cool and I think I think wrapping it in a free-to-play game could bring it to people who would never find it otherwise!