Closed ghost closed 6 years ago
This core does not use our filestream interface, it only uses regular fopen() so that is why it does not support non-ascii characters on Windows. Someone would have to port that over, not sure if @twinaphex would be willing to do it or someone else.
But it worked before (and I supose that the core always used fopen).
I have a backup of my 1.6.7 where, if I don't update the core, it works (but if I update, it breaks).
So I supose that something changed (in retroarch? in the libretro api? i don't know) that makes that my backup works (and when I update the core it breaks)
But well, is not critic. I downloaded "fb-alpha" core and it works. I only downloaded this because I was looking for a NeoGeo, but I found that the "general" (fb-alpha) works too.
Hi
In actual builds FB Alpha 2012 Neo Geo can't load content from path with special chars.
I have: D:/Emulación/Neo Geo/neogeo.zip D:/Emulación/Neo Geo/wjammers.zip
When I select "wjammers.zip" it goes to black and return to RetroAch, with core loaded (core names in in te bottom corner) and with a message of "Failed to load content".
If I move this to a non-special chars path it works: D:/Neo Geo/neogeo.zip D:/Neo Geo/wjammers.zip
Actually I reported 2 bugs related to simmilar problems for RetroArch (https://github.com/libretro/RetroArch/issues/6026 and https://github.com/libretro/RetroArch/issues/5959) but this seems to be a problem on the core with last changes, because I have a backup of a 1.6.7 with FB Alpha 2012 Neo Geo v0.2.97.29 that works fine, but if I update the core (core updater -> FB Alpha 2012 Neo Geo) it chrashes (the revision number doesn't change, it says 0.2.97.29 too).
I tried to move the core that works to 1.7, but it chrashes too.
I'm using the current last nightly build of RetroArch on Windows 10: Build date: Jan 3 2018 Git version: 0e337bb11