Holla! Posted February 7, 2017 Posted February 7, 2017 (edited) Hey, it's not much but when transferring g6->g7 in PKHeX on the latest version the Geolocation data gets set to the target game's under the Memories tab, however when transferred with Bank it doesn't set/completely removes the traces of Geolocation data. Here's a Typhlosion I tested with results from a Bank transfer and PKHeX transfer. Also included in its original g6 format if needed, notice it has Geolocation data in its Memories. in g6.pk6Fetching info... banked.pk7Fetching info... pkhex transfered.pk7Fetching info... Edited February 7, 2017 by Holla! grammar 1
Kaphotics Posted February 8, 2017 Posted February 8, 2017 Fixed in latest commit: https://github.com/kwsch/PKHeX/commit/989759942045448f28cd8077d6608af13f0ec565 Would you also be able to check an untraded specimen? related issue: https://github.com/kwsch/PKHeX/issues/783
Holla! Posted February 8, 2017 Author Posted February 8, 2017 (edited) Here's a random wild Ralts I just caught in Alpha Sapphire. untraded pkhex transfer.pk7Fetching info... untraded original.pk6Fetching info... untraded bank transfer.pk7Fetching info... Edited February 8, 2017 by Holla!
Aryan Posted February 8, 2017 Posted February 8, 2017 On 2/8/2017 at 12:10 AM, Kaphotics said: Fixed in latest commit: https://github.com/kwsch/PKHeX/commit/989759942045448f28cd8077d6608af13f0ec565 Would you also be able to check an untraded specimen? related issue: https://github.com/kwsch/PKHeX/issues/783 Expand when you say its fixed in latest commit, how does one fix it in their PKHeX? what am I supposed to do in my pkhex with that commit?
theSLAYER Posted February 8, 2017 Posted February 8, 2017 On 2/8/2017 at 12:43 PM, Aryan said: when you say its fixed in latest commit, how does one fix it in their PKHeX? what am I supposed to do in my pkhex with that commit? Expand it means wait for the next update. (or compile it yourself )
Aryan Posted February 8, 2017 Posted February 8, 2017 On 2/8/2017 at 12:45 PM, theSLAYER said: it means wait for the next update. (or compile it yourself ) Expand lol yea.. usually they add it in the next update..but how do u compile it yourself? Is there a tutorial here?
theSLAYER Posted February 8, 2017 Posted February 8, 2017 On 2/8/2017 at 12:46 PM, Aryan said: lol yea.. usually they add it in the next update..but how do u compile it yourself? Is there a tutorial here? Expand What I'll do is go to PKHeX's github, zip and download the repo, unzip it, then open the .sln in Visual Studio (I'm using Visual Studio 2015 for my own nonsense), then debug it once. After that, it'll have a PKHeX.exe in the debug folder.
ReignOfComputer Posted February 8, 2017 Posted February 8, 2017 To get a compiled version of the latest commit, go to http://pkhex.skyeditor.org/latest, click [Artifacts], then download the .zip. 1
Aryan Posted February 8, 2017 Posted February 8, 2017 hm... i'll try that and report back. love learning these new things. thanks
Aryan Posted February 8, 2017 Posted February 8, 2017 On 2/8/2017 at 12:51 PM, theSLAYER said: What I'll do is go to PKHeX's github, zip and download the repo, unzip it, then open the .sln in Visual Studio (I'm using Visual Studio 2015 for my own nonsense), then debug it once. After that, it'll have a PKHeX.exe in the debug folder. Expand On 2/8/2017 at 1:29 PM, ReignOfComputer said: To get a compiled version of the latest commit, go to http://pkhex.skyeditor.org/latest, click [Artifacts], then download the .zip. Expand i have a few questions regarding this now.. should i create a new topic or should i just type here?
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