doophus
Joined 4 years ago
Joined 4 years ago
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.
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!"
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.
I often wonder if I'll run out of ideas, but inspiration appears from nowhere and suddenly I've got 2-3 types more to try out. That said, there are quite a few ideas that have gone in the bin - it's surprising what the human mind can do effortlessly, or not at all - it can be very hard to find the right balance of difficulty or intuition. At the moment I'm adding 1-2 new types a week; I'm sure that'll slow down eventually.