Maybe because i haven't name it correctly, i renamed firmkey.bin to native.key.
EDIT: nvm
About this https://github.com/chaoskagami/corbenik/wiki/Building
Everything builds just fine on Windows, the only thing that won't work as-is are the bash scripts,
but those are nothing crucial.
IT WORKS NOW! It boots me to black screen...
Nice, if you build with "make full" it takes a little longer to build but you get the locales folder and all gameid files
(like in the release.zip )
Note:
Everything builds fine under Windows 10 now by just copying pyhton.exe to python2.exe (not renaming, cause some other projects need python.exe) in the \python27 folder.
Apparently my makefiles were better written than I thought. Oh, you could also use mklink for python2. People seem to forget that NTFS does hardlinks/symlinks.
...
thanks the noob i am wait this emunand support yeahhh.when you will add cetk support for decrypt fw ?Okay, making another release now.
Notable additions:
* EmuNAND support (only one right now, but this is due to lack of menu, not code)
* Screen-init for people with non-screeninit a9lh
* Loader now has rel commands for the other segments due to an oversight
* I fixed up some very wrong offset code that somehow worked before.
thanks the noob i am wait this emunand support yeahhh.when you will add cetk support for decrypt fw ?
Emunand work well but "Autoboot" doesn't workOkay, making another release now.
Notable additions:
* EmuNAND support (only one right now, but this is due to lack of menu, not code)
* Screen-init for people with non-screeninit a9lh
* Loader now has rel commands for the other segments due to an oversight
* I fixed up some very wrong offset code that somehow worked before.
release today?
Doesn't workAutoboot with EmuNAND, specifically? Yeah, I noticed that afterwards. The config file isn't getting saved just from ticking that, so next boot it doesn't use emunand. As a workaround, check the option called 'Reconfigured? (DO NOT UNCHECK' to force resaving the config and cache.
That was another oversight that I fixed in the subsequent commit. I can make another release since there's been another bunch of fixes, but it's getting to the point where I really need to slow down. If I keep releasing, there's going to keep being bugs.
Doesn't work
I'm making an Updater for this based on my easyRPG Updater.
Sent from my Nokia 3310 using Tapatalk
Seeing how alpha this is, besides the fact that it doesn't work for everyone I'd say you should wait until it's a bit more mature. The author himself has said that a lot of things might change, and as such it'd break the updater.I'm making an Updater for this based on my easyRPG Updater.
Sent from my Nokia 3310 using Tapatalk
Seeing how alpha this is, besides the fact that it doesn't work for everyone I'd say you should wait until it's a bit more mature. The author himself has said that a lot of things might change, and as such it'd break the updater.
It's your call anyways
Its LUA, I can easily implement something as a clean install. I can mark an update as incompatible with the latest and force deletion of current settings upon extraction of the new filesI would honestly prefer people just manually updated, anyways. There's a reason I haven't seen autoupdaters for cakes.
If the bytecode changes, that needs to get refetched too, and configuration information might need to be nuked between versions. It's not as simple as Luma.