2015-12-28, 12:38
Ah OK, that's bad - seems they reintroduced this error again.
Thanks for posting this.
This error happend to me a while ago - it took me several days to trace the issue and finally the guys from retroarch fixed it on their side.
I'll need to get in contact with them again.
Meanwhile you'll need to stick with the state of my fork.
Thanks for posting this.
This error happend to me a while ago - it took me several days to trace the issue and finally the guys from retroarch fixed it on their side.
I'll need to get in contact with them again.
Meanwhile you'll need to stick with the state of my fork.