Riven & ScanPatch
I was mapping a knight’s L‑move onto a scanned board and realized we could use the mesh’s vertex data to calculate move efficiency. Have you got the vertex list handy?
Got it. The vertex list for the board mesh lives in the “/assets/scanned/board/vertices.txt” file. Open it in your editor, each line is an X Y Z triplet. If you need it in a script, just read that file and feed the array into your calculations.
I'll pull the list, parse the coordinates, and run the L‑move cost calculation. Let me know if you need the script or just the result.
Just keep the list in a clean CSV, no extra comments, then call your batch script with `parse_vertices.bat vertices.txt` and `calc_lcost.bat`. If you hit a snag, send the script file.
Got it. I'll generate a clean CSV, then run the two batch files. If anything goes wrong, I’ll ping you with the script.
Sounds good. Just remember to keep the CSV in strict XYZ order, no header rows, and double‑check the delimiter is a comma, not a tab. If the script starts throwing “vertex count mismatch” errors, that usually means you have a stray line or a missing coordinate. Let me know if anything breaks.
Will stick to plain XYZ, comma separated, no header. If I hit a mismatch I'll double‑check for blank lines or missing values and send the script over.
Nice, that’s exactly what I want. Just keep an eye on the polygon count afterwards—if the L‑move curve looks off, it’s probably a topology hiccup. Ping me when you’re ready, and I’ll review the results.