Jump to content

Leaderboard

  1. Shady Guy Jose

    • Points

      1

    • Posts

      147


  2. Atrius97

    Atrius97

    Super Moderator


    • Points

      1

    • Posts

      284


  3. Pako96

    Pako96

    New Member


    • Points

      1

    • Posts

      23


  4. BloodSugar420

    BloodSugar420

    New Member


    • Points

      1

    • Posts

      1


Popular Content

Showing content with the highest reputation on 04/17/23 in all areas

  1. Hi everybody. In my free time I decided to do some little research on the format in which trainer photo/icon are saved in S/V. After some trials and errors, I descovered that each pixel is represented by a sequence of 8 bytes, of which the first 2 represent colors in BGR 565 encoding and the third is some sort of Alpha channel transparency. I'm currently not aware of the purpose of the other bytes, since editing them didn't bring any noticeable change. Then, thanks to this recent commit , I was able to get the correct size and aspect ratio for the images, and I assembled a little python script that I'm attaching to this post. It is pretty simple to use, just open the save block editor in PkHex, save the image block you desire to see, check the corrisponding values for width - lenght - size (take for reference the previous link until PkHex doesn't get an official update), finally run the script. For example, if we want to save the current profile picture: export the block at 0x14C5A101 as 'picture.bin' check the width at 0xFEAA87DA, e.g. 1440 check the height at 0x5361CEB5, e.g. 832 check size at 0x1E505002, e.g. 599040 let's save the output as 'current.png' The code in the terminal, after changing directory to the one in which we find both picture.bin and imgdec.py, will be: python imgdec.py picture.bin 1440 832 599040 -o current.png In the future I'll try to understand better the other bytes of the encoding and maybe build a little editor/injector for custom images. Of course you are free to make any change you want, and if you want to share new ideas let me know in the replies! Alongside the script I also attach some example output images from my saves. imgdec.py
    1 point
  2. As far as I can tell, you got a save from somewhere (not your own) and you're trying to write it onto a cart. The format your cart reader uses might not match either the one you got or the one @theSLAYER provided when he fixed the file so it could open in PKHeX. Try playing the game for a bit, saving, confirming it's working (so we know it's not a dead battery, for example) then dumping the save file and sending us the dump. We can then compare it to that save and see if something's wrong
    1 point
  3. I figured this out because I wanted to have the same EggDate and MetDate. You just add a * to the field you’re gonna copy. .EggMetDate =*MetDate
    1 point
  4. Both of these assumptions are false. All Pokemon that originate from a Gen 8 game, LGPE, or GO have a HeightScalar and WeightScalar value, and these are retained regardless of transfers. (They're never "reset to zero" or altered in any way) SWSH displays the average height/weight for the species because those Height and Weight values are unused. They're generated, but SWSH doesn't do anything with them. When you transfer from LGPE to HOME, those Pokémon remain in the LGPE format and have their displayed height and weight properly scaled by those values. (LGPE converts them to HeightAbsolute and WeightAbsolute to display the variable sizes) When you transfer them into SWSH, they change to SWSH format, and stop using those values for Height/Weight calculation. This will be true for as long as they remain in the SWSH format. If you'd like to confirm this, use PKHeX to view a Pokémon in LGPE, transfer it into HOME, then SWSH, view that same Pokémon in SWSH, and confirm that the Height/Weight values under the Main tab are identical after the transfer. As a sidenote, BDSP and PLA also have HeightScalar and WeightScalar values. Like LGPE, PLA also uses them to calculate HeightAbsolute and WeightAbsolute to display the variable sizes ingame. There isn't any transfer compatibility between these games and HOME yet, but you can expect the same to be true for them as well. (aside from PLA's Alpha flag, which may be lost/become unused outside PLA)
    1 point
×
×
  • Create New...