Search the Community

So I got PKHeX to work on mac… Not the simplest, nor the plausible cheapest (14 day free trial, $59 for a license), but compared to the literal day and a half I spent trying to get the free options to work? I considered what my time was worth and $59 is worth a day and a half of my time. Anywho here’s a rough tutorial, PKHeX running through Crossover on the Mac. I make no guarantees, but this is how I've gotten it to work for me. Let me know if it works for you too! Resources MacOS - I'm running 12.4 Monterey on a 2019 Intel MBP Crossover app (free 14 day trial) - https://www.codeweavers.com/crossover PKHeX - https://github.com/kwsch/PKHeX Crossover Archive - DL from Google Drive Preamble Crossover will create a container called a “Bottle” (it uses a project called Wine, get it, Bottle of Wine…Get it? #dadjokesaside Anywho). Your goal is to create a Bottle that has all the Windows bits necessary to run PKHex. There is no actual installing of PKHex, just running the .exe in a habitable space. There are two ways…. The easy way- Import Crossover Archive 1. Download the crossover archive (see above in resources) 2. Install Crossover (pretty self-explanatory, if you’re having issues check youtube “Install Crossover macos”) 3. Launch Crossover 4. Import Bottle Archive and Name it (Either of the following will get ya there) * Bottle > Import Bottle Archive… (from the system menu) * or the little + sign in the lower left and select “Import Bottle Archive” * Note: This archive includes only .NET and Core fonts 5. Run PKHex 1. Select your Bottle 2. Double-click “Run Command” (upper right, gear icons) 3. Use the “Browse” to find your PKHeX.exe file 4. Either 1. Run (one time use) * or 2. Save as Launcher (should appear in programs) * After this all you have to do is double-click the PKHeX App that will appear in the launcher. The manual way- The steps to self-build: 1. Install Crossover (pretty self-explanatory, if you’re having issues check youtube “Install Crossover macos”) 2. Launch Crossover 3. Create Bottle 1. Create a new bottle (Any of the following will get ya there) * command + N * Bottle > New Bottle (from the system menu) * or the little + sign in the lower left 2. Name your Bottle 1. Whatever you like, “PKHex Bottle” makes sense to me 3. New Bottle Type 1. Windows 7 (others might work, but for me… this is the only one that does so far) 4. Click Create 4. Create PKHex Environment 1. After a hot second, select your new bottle in the left panel and Click the big blue “Install a Windows Application” button to the lower right. 2. Type "micro" in the field, and select Microsoft .NET 4.6.1 and click “Continue” 3. In the list of compatible Bottles you should see the one you created, e.g. “PKHex Bottle”, select it and click “Continue” 4. Finally click install 5. Then comes the long, long as heck part where Cross over will download and install a couple versions of .NET 1. Accept all the EULAs 2. Do NOT click Send reports 3. Always “Restart now” (note: this does NOT restart your computer, it just allows Crossover to continue) 4. And always “continue” when asked 5. Optional Fonts: 1. Go through the same steps as above, but instead of searching for/installing .NET, search for “Core Fonts” and install that package. 2. Note: It takes far less time than the .NET stuff and helps PKHex look better. 6. Optional (but recommended BEFORE you run PKHex, see upgrade Q in FAQ) 1. Make an Archive of your Bottle 2. Right-click your bottle and select “Export <your bottle name> to Archive” 7. Run PKHex 1. Select your Bottle 2. Double-click “Run Command” (upper right, gear icons) 3. Use the “Browse” to find your PKHeX.exe file 4. Either 1. Run (one time use) * or 2. Save as Launcher (should appear in programs) * After this all you have to do is double-click the PKHeX App that will appear in the launcher. FAQ: 1. Why are there all these x86-64 preloader things running? * Crossover has to run whenever you run this app because (to the best of my knowledge) it’s basically providing the magic services that allow Windows apps to run. 2. Why Should I make an Archive before I run PKHeX? * So, in theory you can run all your PKHex.exe from a single Bottle… But the underlying tech that enables .exe to run on Windows is finicky and you could run into some issues especially when all the executables have the same filename. If you do want to run multiple PKHeX in a single Bottle, try renaming the executable before running it. I recommend adding the release date MMDDYYYY, so PKHeX.exe would become PKHeX06102022.exe. That way you’ll never get ‘em mixed up. Eventually though your bottle is gonna end up getting pretty big… But the choice is yours! 3. How do I uninstall or upgrade to a new version of PKHeX? * Simply put? It’s easier to create a new bottle or import an archive and run the new executable from it. There’s no easy way to uninstall a program once it’s associated with a Bottle. The “Move to Trash doesn’t really seem to work well.

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

PKHeX for Mac Made with Wineskin Welcome to PKHeX for Mac Discussion thread! Please post here if you need help or are experiencing issues related to this Wineskin wrapper, and use the PKHeX Support forum for issues related to the program. This is a Mac App that was made using Wineskin; it is not a port of PKHeX onto the Mac operating system. With Wineskin, we can recreate an environment where executable files will launch on Mac. As far as what is known, all features in the original program work in this wrapper. There are a few differences though. PKHeX for Mac is styled with MacOS. Also, the app's icon is different from the original PKHeX program to better fit in with the theme of the app. Download Credit to Kaphotics Source: https://projectpokemon.org/home/files/file/1-pkhex/ Issues with Wine and PKHeX? This app not working for you? Check out the PKHeX on Mac guide:

HELP ME PLEASE!!!

Dear creator of PKhex. I request that pkhex's change to .net 4.6 be reverted for a build that actually works on mono found in wine, as I use linux, and would not like to waste space on my hdd with .net 4.6. If you could make your code more universal, that would be very desired. Sincerely, St. GIGA

Hi guys, so I've been trying to install the latest version (17.01.28) on my Mac using wine bottler, but to no avail. I managed it successfully with the last version of PKHeX, but this time the wrapper simply refuses to complete the launch when I double-click the .app file. Is there anybody here who could help me go through the steps please? Thanks in advance.