Occam's Razor states that the simplest explanation is often the correct one, and when it came to finding the broken configs in Satella's SV bank, that was also the case.

In the devkit, there's no obvious error reading, no notification dot showing which samples are broken, and nothing in the error log that actually gives you any idea of what the error is and where. But, I remembered something I'd overlooked - the llsm-cache folder that's built with every build. If a sample couldn't build for whatever reason, it wouldn't have a cache file, and the latest cache file would be where to look for the broken config.

So I checked, and it worked! I found the broken configs one by one using this method, and now I can finally get back to work, knowing that she'll actually build when I test her latest configs. If in doubt, keep it simple, stupid!

This post was last edited 1 day, 2 hours ago.