Odaxis Posted October 25, 2015 Posted October 25, 2015 Bug with the latest commit. The game stops responding correctly when ever I inject a Wondercard. Injection works fine on previous version posted on the 20th. What seems to happen is after injection when accessing the Pokemon Center pc all I get is a black screen and if I leave the Pokemon center the game crashes.
Kaphotics Posted October 25, 2015 Posted October 25, 2015 Fun Tomorrow (well, half a day from now) I'll do a whole bunch of tests; refactoring definitely turned up a bunch of loose ends that need resolving. (note to self: compare stable vs current by doing same changes to same file and comparing export)
Odaxis Posted October 25, 2015 Author Posted October 25, 2015 Fun Tomorrow (well, half a day from now) I'll do a whole bunch of tests; refactoring definitely turned up a bunch of loose ends that need resolving. (note to self: compare stable vs current by doing same changes to same file and comparing export) As always, your work is much appreciated.
Kaphotics Posted October 26, 2015 Posted October 26, 2015 As always, your work is much appreciated. I'm unable to recreate the issue you had; this issue is reminiscent of the whole Battle Box deal... http://projectpokemon.org/forums/showthread.php?46863-PKHex-Hax-causing-black-screen-in-save Would you check your save in a hex editor @ 0x483F to be sure it's < 0x1F?
Odaxis Posted October 26, 2015 Author Posted October 26, 2015 I'm unable to recreate the issue you had; this issue is reminiscent of the whole Battle Box deal... http://projectpokemon.org/forums/showthread.php?46863-PKHex-Hax-causing-black-screen-in-save Would you check your save in a hex editor @ 0x483F to be sure it's < 0x1F? Tried opening it in HxD but could not find the ref 0x483F If you could take alook, here is the file. https://mega.nz/#!GJ9FSCDA!XkSPHGKdIPqvXLiGXgZW17MX__6GN4btgmJIqM6Lbl4
Kaphotics Posted October 26, 2015 Posted October 26, 2015 Tried opening it in HxD but could not find the ref 0x483F Oh, ramsavs. I'll investigate further tomorrow edit: looks like it was set to 0x1F... dunno why. change 0x354C to anything else, I'll have to see why it was exporting like that (maybe the commit I pushed today fixed it?).
Odaxis Posted October 26, 2015 Author Posted October 26, 2015 (maybe the commit I pushed today fixed it?). Tried the ramsav file on the PKHeX from October 20th, works fine, The version from yesterday and today both black screen.
Kaphotics Posted October 27, 2015 Posted October 27, 2015 tfw you omit an optional parameter that is actually needed Fixed in latest commit. Thanks for reporting
Odaxis Posted October 27, 2015 Author Posted October 27, 2015 tfw you omit an optional parameter that is actually neededFixed in latest commit. Thanks for reporting Confirmed resolved. thanks again. Will report if i find any new bugs.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now