The issue is how the files are handled in the game, you need to make SDCafiine act like Cafiine instead of just changing file paths. Easier said then done, at least it's not using the network.
Kinda... but... yeah.So how DO we make SDCafiine act like Cafiine? Does it require a complete code rewrite?
?You didn't get it...
I was telling to use hbl if you want tcpgecko. No need to combine it with Mocha.?
I did understood if you wanted to know if it work with the hbl
I second this ^^^Worth noting - I've got a rather unique code injection platform in the works. If you're planning on rewriting SDCafiine, you might want to take a peek at it.
As for your SD access, I'd reccomend using /dev/iosuhax to mount the SD rather than FSHax. You're running Mocha anyway, so it shouldn't be an issue. FSHax seems like an unnecessary risk on a conceptual level alone.
Because this is way faster...I second this ^^^
Why do you want a CFW with full FS access just for SDCafiine instead upgrading SDCafiine?
Yes, it worked with Super Mario Maker.oh
it seems to not be working. Have you tested it Abood?
You mean like libiosuhax? Like I said, patching mocha is way faster and easier than to allow every homebrew to access the SD Card individually...As for your SD access, I'd reccomend using /dev/iosuhax to mount the SD rather than FSHax. You're running Mocha anyway, so it shouldn't be an issue. FSHax seems like an unnecessary risk on a conceptual level alone.
chmod 777 /You mean like libiosuhax? Like I said, patching mocha is way faster and easier than to allow every homebrew to access the SD Card individually...
I don't see why would FSHax be dangerous, unless you did something stupid (something you shouldn't have done). As you used a CFW at your own risk and did something you shouldn't have done, which lead into unexpected(?) results.
In the case of SDCafiine, the changes aren't permanent, so I don't see why would FSHax be dangerous.
Lastly, I will try to get in touch with @Maschell about SDCafiine soon.
I thought the object of fshax was to let a title (like a game) access a device that it wouldn't normally have access to. Wasn't the problem that games didn't work with sdcafiine because they couldn't access files that sdcafiine was trying to redirect them to, not that sdcafiine couldn't access the files? I'll admit that I haven't even glanced at sdcafiine's code, but that seems like how it would want to work.As for your SD access, I'd reccomend using /dev/iosuhax to mount the SD rather than FSHax.
It's the same thing if you look at it from a different angle.I thought the object of fshax was to let a title (like a game) access a device that it wouldn't normally have access to. Wasn't the problem that games didn't work with sdcafiine because they couldn't access files that sdcafiine was trying to redirect them to, not that sdcafiine couldn't access the files? I'll admit that I haven't even glanced at sdcafiine's code, but that seems like how it would want to work.