Don't they have a battery backup and a local buffer before uploading?
It probably had its last footage still stored locally, using the remnants of power in its internal battery.
Yes, have a look at ISPC - it's amazing. I especially like that it can generate code for multiple architectures and then select the best implementation at runtime for the CPU it's running on.
Would it be possible to build a web-hosted database of encountered shader configs against a game id, and have Dolphin fetch that list when a game launches and start doing async compilation?
When Dolphin encounters a new shader that wasn't in the db, it phones home to request it to be added it to the list.
I feel an automated sharing solution would build up coverage pretty quickly, and finding a stutter would eventually be considered an achievement - "no-one's been here before!"
I found the same with this library. I'm not sure if it's missing documentation, unintuitive design or both, but I always found it a bit of a struggle to use beyond simple cases.
> 2. Store metadata about the current a* search in the graph nodes themselves so you don't have to maintain in a separate associative array.
This might be suitable in some circumstances, but it mixes your hot & cold data, prevents concurrent searches from being performed. Personally I'd steer away from this without an extremely good reason.
Most software installers on Windows offer the user a "Install for this user"/"Install for all users" option, or will just install to the current user's appdata, which doesn't require admin rights.
For portable SIMD, have a look at ISPC. It allows you to write a function once, compile it for multiple instruction sets, and then automatically select the best one to use at runtime. You don't get the precision of hand-crafted SIMD, but it can grant some easy wins!
Every game I've worked on (360-era) with DLC has needed supporting code to be distributed in an update first. Everyone gets the update, then the DLC is either just an unlock for what's already there (but hidden), or contains some supporting data.
Also consider AI, that has a greater training base of JavaScript than Lua. So making Lua look more like JS, should improve output and reduce mistakes.