Jamiras

> could announce in the appropriate forums so everyone has time to comply? What would the appropriate forum be? It seems like the target audience would get the notification about...

Did we come to a verdict on this? @ScottFromDerby seems to want to keep them where they are to keep the "barrier for entry" low. @meleu suggested a new git...

The problem this is trying to address is git is a distributed system, and keeps history for everything. So that 40MB FBA core that's in the repository now is downloaded...

With #103, cores can now be downloaded/updated from the nightly buildbot **just like RetroArch**. The dlls have been removed from the current `develop` branch, but still have to exist for...

Logging is desirable. I'm going to treat this as a bug. The file should be written in the same directory as the RALibretro.exe, not the current directory. I'm genuinely curious...

This core crashes when loading a game in RALibRetro

The core seems to working now, but there's some odd static in the sound - RALibretro doesn't appear to like the fact that it's sending us 384KHz audio. Easily noticeable...

> Every operation tested, including switching cores or exiting the application, causes access violations after the first failed load attempt. Failing to load the game results in a call to...

also recommend modifying/extending the error reporting added in #35 so users are informed when a game fails to load.

I believe the crash has been addressed by this change: https://github.com/RetroAchievements/RALibretro/pull/146/files#diff-fde495e29ccb3e6e525307003905d382R1157-R1160 The internal state is updated to "no core loaded" when a game fails to load. It's probably still desirable...