jasenyoface

Hey FalseSwipe! I agree with you, it’s the best solution for PKHeX to run on MacOS. In fact, I recently put together this guide to help members go that route:

PKHeX on Mac A User Friendly Guide for WINE Intro This guide will hopefully clarify a few things regarding WINE and PKHeX running on MacOS as well as help anyone start from scratch with WINE [in order to run PKHeX]. WINE is a fickle thing; it's not guaranteed to work (at all) but the success rate these days is impressive! So, don't get discouraged if things do not work the first time around. Nothing we do in this guide is permanent, although I encourage you to make a Time Machine backup of your system or at least backup your important data. With that being said, I have been using WINE for quite some time. Regarding PKHeX, It's going on almost a year and I have yet to experience any depressive issues using WINE to run it. I have done several clean installs of macOS Sierra and macOS High Sierra in order to give you the most accurate information possible. If I have missed something or you know any tips or tricks, I would appreciate the feedback! Also, you'll find only the bare minimum information in this guide of what you will need to get PKHeX up and running. I say this because without any theming, the app will look like an old school Windows program. NOTE: Aesthetics may not be the most important thing to consider (especially if you're in a hurry or maybe don't care) however there are some dependencies (winetricks) that are absolutely necessary for some programs to run. Fortunately PKHeX isn't too picky. Choices Download the PKHeX app in the PKHeX for Mac thread Use Winebottler to make a PKHeX.app for yourself Use Wineskin Winery to make a PKHeX.app for yourself (no support here) Use WINE to run the PKHeX executable via Terminal Use a Virtual Machine (VM) or something along those lines (no support here) Winebottler Pretty straight forward process. Tick all of the items with arrows next to them, like in the screenshot below. Also necessary winetricks for PKHeX: dotnet461; corefonts; cjkfonts; tahoma. May need to change security preferences to run the app: NOTE: Winebottler is the fastest, easiest "DIY" option for a beginner. (Some argue that Wineskin Winery is the fastest and most easy way to whip up an app. I'll say it just depends on your skill level, though I agree.) Another thing, apps may be less stable than if they were launched using other methods basically because of the lack of options Winebottler has to fine tune things (e.g.; adding a string in the Registry Editor to enable Retina compatibility.) Install WINE on your Mac [Run PKHeX Using Terminal] Installing WINE on your system using Homebrew is the most noob-friendly way [to install WINE on Mac] that I have found, so let us just use that. To start, I'll tell you that you will be installing 4-5 minuscule things on your Mac; Xcode CLT, Homebrew Package Manager, XQuartz, WINE, and some Winetricks depending on the executable your are attempting to run. In this instance, our target is PKHeX. So onto the first thing, Homebrew. Before you can use "brew commands" in Terminal, you must have Xcode Command Line Tools installed. If you already have Xcode installed on your Mac, you should be peachy. If not, no problem! Open Terminal to get started! Xcode CLT: xcode-select --install If you're asked to agree to Xcode's ToS, next type: sudo xcodebuild -license Homebrew Package Manager: /usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)" When that finishes up, you'll want to make sure everything is in order: brew doctor For future reference, you can update Homebrew using: brew upgrade XQuartz: brew cask install xquartz WINE: brew install wine brew upgrade wine # For future reference That will create a 64-bit WINEPREFIX which will be located at: ~/.wine NOTE: If you would rather use the developer version of WINE, use these instead: brew install wine --devel brew upgrade wine --devel # For future reference Winetricks: brew install cabextract brew install winetricks brew upgrade winetricks # For future reference NOTE: You DO NOT need to install every winetrick available, just the ones your programs depend on to function. For PKHeX, you will need to install these; dotnet461, corefonts, cjkfonts, and tahoma (why not). Install the "tricks": winetricks "trick" # (e.g.; winetricks dontnet461) Complete list of Winetricks For some, the winetricks process will be easier with a GUI. I suggest installing Zenity if you want one: brew install zenity # After installation finishes, you will have a neat GUI for winetricks. Use: winetricks --gui Attention Okay, this is important, so listen up. It's a known issue that .NET Framework 4.5 and up, (dotnet45 and up) does not install properly on a 64-bit WINEPREFIX, which was installed by default earlier (brew install wine). That is okay because a 64-bit WINEPREFIX may come in handy in the future. To get around this issue, you will create a 32-bit WINEPREFIX. Creating the 32-bit prefix: WINEPREFIX=~/.wine32 WINEARCH=win32 wine wineboot You will now have a 32-bit prefix located at: ~/.wine32 Next, install the aforementioned winetricks in your new prefix. It is important that you use these next commands any time you want to run or install ANYTHING inside of that 32-bit WINEPREFIX. Remember, we need at least .NET Framework 4.6 to run PKHeX and we must install .NET Framework 4.6 in the 32-bit prefix, therefore we will be running PKHeX from inside of the 32-bit prefix. (I know, don't ask, lol) WINEPREFIX=~/.wine32 WINEARCH=win32 wine "Program.exe" WINEPREFIX=~/.wine32 WINEARCH=win32 winetricks "trick" Senario: You have done all of the above and you're ready to run "PKHeX.exe". Download PKHeX and remember its location. It's usually in the Downloads folder. Open Terminal and change directories to the PKHeX (version) folder. For example: cd ~/Downloads/PKHeX\ \(171205\) Then, run the executable: WINEPREFIX=~/.wine32 WINEARCH=win32 wine PKHeX.exe

Sometimes (and I don’t really know why) this method works when the app won’t launch: Right click PKHeX.app and choose “show package contents”. Next, enter the “Contents” folder and then the “MacOS” folder. Run “WineskinLauncher”.

The last time I checked, there is an option in PKHeX that enables a reminder to “set” your Pokémon. I believe the action is triggered when you try to edit another Pokémon without “setting” your recently edited one. The feature was a big plus for me because I frequently forgot to set my changes.

OP updated!

You really should let more time pass before posting again. Just be patient, someone may come along to help you.

Here you go, try this:

Do your setting look like this now:

Infamous Innovator/ROM researcher @SciresM tweeted earlier this evening revealing new information he discovered about the up-coming update to Pokémon Bank and Poké Transporter. In his next few tweets (by now SciresM had shared the news on Project Pokémon IRC too), he confirmed support for newly released: Pokémon Ultra Sun and Ultra Moon and Pokémon Gold and Silver, which were released back in September for the Nintendo 3DS Virtual Console. As a welcomed bonus, it appears that Poké Transporter was updated to add support for [unreleased] Pokémon Crystal on the Nintendo 3DS Virtual Console. One more thing was brought up by SciresM in Project Pokémon's main IRC channel (#projectpokemon); the event-only Pokémon, Zeraora, was referenced in the text dumps for this update! No word yet on an official date for that event Zeraora. At the time of writing this, the official Pokémon Bank website has only updated their Pokémon Bank + Poké Transporter "map" (shown above) and current details for the services are still in need of an update. It reads as follows: On the other hand, Nintendo's 3DS support page (Japanese) shows official announcements for Pokémon Bank and Poké Transporter v1.4, sans mention of Pokémon Crystal. In-Game Images (Spoiler) Sources: SciresM's Twitter; Nintendo.co.jp; Pokemonbank.com; Pokemon.com View full article

What RobertJSpradlin is correct. There's also the option to disable Gatekeeper, if you wish. sudo spctl --master-disable To reverse: sudo spctl --master-enable

First, inject a backup of your save file (pre-FTPD) into your UM game, just to make sure it works. Then, using (a save manager), export your data to your SD card. Plug in your card to your PC to do edits. Save your work and re-insert your SD card into your 2/3DS. Import your save using (a save manager). I got the same error before I stopped using FTPD to transfer my USUM saves. Luckily I made backups.

No problem! Don’t be a stranger Project Pokémon’s Patreon is located here for anyone that is interested in supporting the community: https://www.patreon.com/projectpokemon/

Read back through this thread, I’m sure you’ll find a solution. It seems like a common nuisance. ********** As far as installing .NET Framework 4.6, you don’t actually install it on macOS. Open wine. And then.... then... then... finally, launch the PKHeX.exe

PC Pikachu Mr. Mime Dusk Lycanroc Litten Primarina Gligar

I believe ReignOfComputer's response to your topic, Mac Help is correct where he mentions .NET Framework. --Install the 4.6 .NET Framework Winetrick. As far as the PKHeX app, maybe kai1998's solution will help:

Which way you would like to run PKHeX? Launching the PKHeX app or using WINE to run the ".exe" The app in your screenshot^ is "macOS Sierra 10.12.X" friendly. If, Sierra is your OS then it should launch. If you want to run the ".exe" with WINE, it appears that you need to install some Winetricks. More specifically, the ".NET Framework 4.6" one.

@JoeGuar The deed is done, enjoy!

I'm testing my wrappers now. The OP should be updated soon.

Congratulations @Jovie !!!

Going back to April: Maybe try that setup again?

Download the latest unofficial build from: https://teamcity.projectpokemon.org/login.html Login as Guest. Or here is a direct link: https://teamcity.projectpokemon.org/viewLog.html?buildId=16344&buildTypeId=PKHeX_BuildWindows&tab=artifacts

Is there any new information related to this? Such as met level (I assume It 20)

Two

Which game? Did your save work previously?