I vibe-coded my project to failure. I know I’ve hit a dead end because Claude thinks everything is working even though there are obvious issues. It’s time to take 10 steps back so I can take another 50 steps forward. Before I do so, I want to make note of the successes I can extrapolate into the context I use in my next attempt.
- I created a unified conda environment that works with both Sports2D and VDAL. However, VDAL might be slower now (seems to be).
- I downgraded OpenCV in that environment in order to fix an issue Sports2D was having (according to Claude).
- I created an implementation strategy that would allow both libraries to utilize the camera at the same time. Claude automatically documented this strategy in markdown (as it tends to do now).
- I installed a Unity MCP and linked it to Cursor. Its able to play my Unity scene but doesn’t seem to be able to read the logs (which is the important part). There’s another Unity MCP but it seems to be less active. The course of action I need to take is to debug the process of running the webcam through Unity and passing frame data to the libraries by simplifying the amount of libraries I’m doing it for. Since I already have Sports2D working with my basic integration, I need to first get this working only with Sports2D, and then once that works, work on integrating VDAL. One thing at a time.
Tags: unity gamedev cv debugging opencv 2d python vdal sports2d mcp