Running WDS games on macOS (or Linux)

Wargame Design Studio games are Windows games. They are developed and tested for Windows, and Windows remains the supported platform. That said, many players use Macs or Linux systems and naturally want to know whether they can still play their WDS titles.

The answer is: yes, in many cases, but the method is important.

There are several ways to run a Windows game on a Mac or Linux system. Some methods run an actual copy of Windows. Others try to translate Windows software so that it can run directly under macOS or Linux. The distinction is important because the first approach is much more reliable for WDS games. 

The best general rule

If you want the least trouble, run the games in Windows.

That can mean using Boot Camp on an older Intel Mac, using a virtual machine such as Parallels Desktop, or using a normal Windows PC. Boot Camp is (or better was) Apple's tool for installing Windows directly on an Intel-based Mac, so the computer starts up as a Windows machine when you want to play. Parallels Desktop takes a different approach: it runs Windows inside macOS, in a virtual machine, so you can use Windows programs without rebooting. In both cases, the important point is that the WDS game is still running in Windows, which is the environment it was designed for.

Wine-based solutions work differently. Programs such as CrossOver, WineBottler, Proton, and similar wrappers do not install a full copy of Windows. Instead, they try to translate what the Windows game asks for into something macOS or Linux can provide. CrossOver is the more polished commercial version of this approach; WineBottler packages a Windows program so it can be launched more like a Mac app; Proton is Valve's Wine-based compatibility layer used mainly on Linux and Steam Deck.

These solutions can work in some cases, but they should be treated as experimental. They may launch the games, but they may not display them correctly, especially in newer patched versions of the WDS games. The most common problems are graphical: garbled map tiles, distorted terrain, strange overlay effects, or display issues with on-map combat results. 

First question: Do you have an Intel Mac or an Apple Silicon Mac?

This is the first thing to check.

If your Mac uses an Intel processor, you may be able to use Boot Camp. Boot Camp lets you install Windows directly on the Mac and choose whether to start the computer in macOS or Windows. When started in Windows, the Mac behaves much like a Windows PC, and WDS games can be installed and updated normally.

If your Mac uses Apple Silicon, such as an M1 or newer processor, Boot Camp is not available. In that case, the usual practical route is a virtual machine, most commonly Parallels Desktop. Parallels runs Windows inside macOS, so you do not need to reboot the Mac, but the WDS game is still installed and runs inside Windows.

In both cases, you need a valid Windows license. If you use Parallels, you also need a Parallels Desktop subscription or license. These are separate from any WDS purchase. The Parallels subscription costs are available on their website: https://www.parallels.com/. A free 14-day trial is available.

You can check which type of Mac you have by opening the Apple menu and choosing About This Mac. The processor or chip listed there will tell you whether your Mac is Intel-based or Apple Silicon.

Option 1: Intel Mac with Boot Camp

For an Intel Mac, Boot Camp is usually the cleanest solution.

With Boot Camp, you install Windows on a separate partition of your Mac. When you want to play WDS games, you restart the Mac into Windows. From that point on, the game runs in a real Windows environment, not through a translation layer.

In practical terms, the process is:

1. Use Boot Camp Assistant in macOS to create a Windows partition.
2. Install Windows.
3. Boot into Windows.
4. Install your WDS games as you would on a normal Windows PC.
5. Apply updates normally.

Some more detailed information can be found here: https://www.pcworld.com/article/474061/how-to-install-boot-camp-and-run-windows-on-your-mac.html

The advantage is compatibility. The game sees Windows, uses Windows graphics handling, and behaves much like it would on a regular PC.

The trade-off is convenience. You need a Windows license, you need to reserve disk space for Windows, and you must restart the Mac whenever you want to switch between macOS and Windows.

For Intel Mac users, this is normally the preferred solution.

Option 2: Parallels Desktop (or other virtualizing software)

Parallels Desktop (https://www.parallels.com/products/desktop/) runs Windows inside macOS. Instead of restarting the computer, you open Windows in a virtual machine and then install and run your WDS games inside that Windows environment.

This is currently the most straightforward option for many modern Mac users, especially those with Apple Silicon Macs.

One important point for Apple Silicon Macs: install the ARM version of Windows, not the Intel/x64 version. Apple Silicon Macs use ARM-based processors, so the virtual machine should use Windows 11 Arm64. Windows 11 Arm64 can still run many standard Windows applications, including many traditional x86/x64 programs, through Microsoft's own compatibility layer inside Windows.

Microsoft provides the Windows 11 Arm64 ISO here:

https://www.microsoft.com/en-us/software-download/windows11arm64

In practical terms, you would:

1. Install Parallels Desktop.
2. Create a new Windows virtual machine.
3. On an Apple Silicon Mac, use Windows 11 Arm64.
4. Start Windows inside Parallels.
5. Install your WDS game in Windows.
6. Run the game from within the virtual Windows desktop.

Because the game is running inside Windows, Parallels gives WDS games the operating environment they expect. In effect, Windows acts as a full virtual computer inside your Mac. That also means it should be treated like a normal Windows installation: Windows updates, security patches, security settings, disk space, and other routine maintenance still apply.

One practical setup that can work well is to install the WDS games on a fast external drive that is accessible from both macOS and the Windows virtual machine. This lets Windows run the games normally, while macOS can still access the game folders directly. That can be useful for PBEM play, for example, when you want to retrieve or send .bte files without first digging through the Windows virtual machine's internal file system. If you use this approach, make sure the external drive is reliably mounted before starting the game, and avoid disconnecting it while Windows or a WDS title is running.

Parallels also offers "Coherence Mode", which lets Windows programs appear alongside your normal Mac applications rather than inside a separate Windows desktop. A WDS game can therefore look like a Mac app, even though it is still running inside the Windows virtual machine.

In normal use, this has proven to be the most trouble-free option on Apple Silicon Macs. I personally play, test, and design with this setup and have not encountered any WDS-specific issues.

The disadvantage is cost. Parallels is commercial software, and you also need a valid Windows license. You also need enough disk space and memory to run Windows comfortably alongside macOS. As a practical matter, the virtual machine should not be configured with the absolute minimum resources if you intend to use it regularly for gaming.

For Apple Silicon Mac users who want the most reliable answer, Parallels is the recommendation.

VMware Fusion is another virtual machine option. Like Parallels, it runs Windows as a virtual computer inside macOS, so WDS games are still installed and run inside Windows rather than through a compatibility layer. This makes it a more suitable alternative than Wine-based solutions.

VMware Fusion (https://www.vmware.com/products/desktop-hypervisor/workstation-and-fusion) may be attractive because it is currently available free of charge, including for commercial use. It supports Windows 11 on Apple Silicon Macs, and recent versions include a “Get Windows” option. As with Parallels, Apple Silicon users should install Windows 11 Arm64, not the Intel/x64 version.

The trade-off is ease of use and support. Parallels is generally the more polished and commonly recommended Mac option for non-technical users. VMware Fusion can be a good alternative, but users should be prepared for a little more self-support and configuration.

Option 3: CrossOver

CrossOver (https://www.codeweavers.com/crossover) is a commercial Wine-based product. It allows some Windows applications to run on macOS or Linux without installing a full copy of Windows.

That is the main attraction of CrossOver: unlike Boot Camp or Parallels, it does not require a Windows license. You do, however, need to buy CrossOver itself. CrossOver+ includes 12 months of support and updates; after that period, the version you are entitled to continues to work, but further upgrades and bug fixes require a renewed support period. In practical terms, users who want to stay current should treat it as an ongoing cost rather than a simple one-time purchase.

There is also a longer-term concern about Apple Silicon. CrossOver on Apple Silicon Macs currently relies on Apple's Rosetta 2 technology to run Intel/x86 Windows applications on Apple's ARM-based processors. Apple has begun warning users that support for Rosetta 2 will end in a future version of macOS.

That does not necessarily mean that CrossOver will stop working immediately, and CodeWeavers may provide new solutions in future versions. However, it does mean that CrossOver compatibility on Apple Silicon Macs could change significantly in future macOS releases. For WDS players, this is another reason to treat CrossOver as experimental rather than as a dependable long-term replacement for running Windows in Boot Camp or a virtual machine.

In most cases, WDS games do launch and run under CrossOver. However, there is an important limitation: CrossOver is not Windows. It is a compatibility layer based on Wine. Instead of running a full Windows operating system, it tries to translate or reimplement the Windows functions the game expects so that they can work on macOS or Linux.

That distinction is important. A game may start, load menus, and even open scenarios, but still encounter display or interface problems if the compatibility layer does not handle the game's graphics the same way Windows itself does.

Older WDS games used BMP-based graphics, and those have generally been less problematic under Wine-based solutions. Newer WDS updates are moving the games to PNG graphics. As more titles are updated in this direction, CrossOver and other Wine-based setups may show graphical problems that did not appear with older builds.

The most visible issue is corrupted map graphics: garbled hex tiles, distorted terrain, repeated geometric patterns, or broken overlays. On-map combat result displays may also be affected.

In practical terms, CrossOver may be worth trying if you already own it or are comfortable experimenting. But it should not be regarded as equivalent to running the game in Windows.

A typical CrossOver setup would be:

1. Install CrossOver.
2. Create a Windows bottle.
3. Install the WDS game into that bottle.
4. Launch the game from CrossOver.
5. Test the map display carefully before committing to that setup.

Unfortunately, after installing a game, the launchers shows all executable files in a rather chaotic way. If you have many games, it might make sense to use a separate bottle for every game series. Also our WDS Menu Program can be installed in a bottle and does mitigate the chaos.

When you initiate a game or one of accompanying editors for the first time from within Crossover, the launcher might request access rights to local folders, network, and occasionally access to the microphone(!). This request originates from the Crossover layer, not the game itself. Typically, you can deny these requests without any adverse consequences. 

The important step is testing the map. A game may launch successfully but still not be practically playable if the terrain display is corrupted.

If you see garbled hexes, strange repeated patterns, or broken terrain, the problem is probably not a bad WDS installation. The same game may display correctly under Windows. The problem is more likely to be how the CrossOver/Wine compatibility layer handles the newer PNG-based graphics.

In the screenshot above, the see Advance of the Reich (left) and War of the Austrian Succession (right). Advance of the Reich uses PNGs in it newest update. As you can see (clicking the screenhot enlarges it), the hexborders and part of the info panel is garbled.

Option 4: WineBottler and other Wine wrappers

Tools such as WineBottler (https://winebottler.kronenberg.org) and similar utilities take a Wine setup and package it into something that looks more like a normal Mac application.

This can be convenient, because the user can launch the game like an app. However, these tools still use Wine underneath. That means they are likely to have the same graphics limitations as CrossOver.

There is also an update problem. WDS games receive regular patches and updates. If you have packaged a game into a Wine wrapper, you may need to update the contents of that wrapper or rebuild it after a game update. For one game, this may be manageable. For several WDS titles, it can become tedious.

The usual workflow is:

1. Create a wrapper for the game.
2. Install the WDS game inside the wrapper.
3. Launch and test the game.
4. Revisit the wrapper when the game is patched or updated.

This route is best suited to users who already understand Wine and are comfortable troubleshooting.

For most users, it is not the recommended first choice.

Option 5: Linux with Wine or Proton

Linux users are in a similar position to macOS users who rely on Wine. Some WDS games may run under Wine or Proton, but results can vary depending on the Linux distribution, graphics drivers, Wine or Proton version, and the specific WDS title.

The basic idea is the same:

1. Install Wine, Proton, Lutris, Bottles, or another compatibility tool.
2. Create a Windows environment or prefix.
3. Install the WDS game.
4. Launch and test it.
5. Pay particular attention to map graphics and on-map results.

Experienced Linux users may be able to get good results, but this is not an officially supported configuration. If graphical corruption appears, it is probably the same Wine-layer issue described above.

What about Steam Deck?

The Steam Deck is Linux-based and uses Proton to run many Windows games. Some WDS games may launch on it, especially through Steam, but there are two separate questions: can the game run, and is it practical to play?

WDS games are traditional desktop wargames. They expect a mouse, right-clicks, menus, toolbars, detailed map interaction, and readable text. Even if the game starts, the screen size and control scheme may not be ideal.

Steam Deck should therefore be treated as experimental. It may be interesting for technically inclined users, but it is not a supported platform.

Why Wine-based solutions can have graphics problems

The most common issue reported with CrossOver, Wine, and similar tools is not that the game refuses to start. The game may start normally, show menus, load a scenario, and appear to work. The problem often appears once the map is displayed.

Older WDS builds used BMP-based graphics and have generally been less troublesome under Wine-based systems. Newer WDS builds are moving to PNG-based graphics. Under Windows, this is handled correctly, but under Wine-based systems, the rendering can fail or partly fail. As more WDS titles are updated in this direction, users should expect these issues to become more common rather than less.

Typical symptoms include:

• garbled hex tiles;
• distorted terrain;
• Repeated geometric patterns;
• incorrect map overlays;
• broken or missing on-map combat result displays;
• odd transparency or layering effects.

Some users have reported that recoding or resaving the affected PNG files helped in their specific setup. This may be worth knowing for technically experienced users, but it is not a guaranteed fix and should not be treated as an official workaround. Results can vary depending on the game, the graphics files involved, the Wine or CrossOver version, and the user's system.

If this happens, changing in-game settings may not solve it. The problem is usually below the game level, in the compatibility layer.

That is why a full Windows environment, either through Boot Camp or a virtual machine, is more reliable.

Which option should I choose?

If you have an Intel Mac and are comfortable installing Windows, use Boot Camp.

If you have an Apple Silicon Mac, use Parallels Desktop with Windows if you want the most reliable, practical solution.

If you already own CrossOver and want to experiment, try it, but test the map display before assuming the game is fully playable.

If you use WineBottler, Proton, or similar tools, expect some trial and error. These can be useful community solutions, but they are not equivalent to Windows.

Troubleshooting advice

If a WDS game behaves strangely on macOS or Linux, the first question is whether the same problem occurs under Windows.

If the game displays correctly in Windows but not under CrossOver, Wine, Proton, or a wrapper, the issue is most likely related to the compatibility layer rather than the WDS game itself.

If the game also displays incorrectly under Windows, then it may be a game installation, update, graphics, or configuration issue.

For WDS support generally, the most useful diagnostic item is a saved game file that allows us to reproduce the issue, along with a clear description of what happens and what should happen instead. If we cannot reproduce the problem from a saved game file or from clear, repeatable steps, it is often not possible to fix it. 

WDS support position

WDS games are Windows games. The official system requirements are Windows 10 or Windows 11. Any setup outside those requirements should be considered unofficial.

That means any non-Windows environments are not officially supported platforms. Some players can run WDS games using these methods, but compatibility cannot be guaranteed.

We will try to help where we reasonably can, especially if a problem may also affect the supported Windows version of a game. However, WDS cannot provide official support for platform-specific issues that occur only under one of the aforementioned setups. In those cases, the problem may lie in the compatibility layer, virtual environment, host operating system, drivers, or hardware configuration rather than in the game itself.

For help with these unofficial configurations, please use the relevant community discussion thread on the WDS forum. Other users with similar setups may be able to share advice, settings, or workarounds. Note: An account is required to both view and post in these forums.

https://forum.wargameds.com/viewtopic.php?t=248

The best troubleshooting test is to run the same title under a supported Windows 10 or Windows 11 environment. If the game works correctly there, but not under macOS, Linux, Wine, CrossOver, Proton, UTM, or another workaround, then the issue is outside the officially supported WDS environment.

For the most reliable experience, use Windows 10 or Windows 11 directly, or run Windows in a stable virtual machine.

Highly experimental: WDS games on UTM on iPad

There is one more possibility, but it should be treated as a curiosity rather than a recommendation: running Windows on an iPad through UTM.

UTM is a virtual machine and emulator app that can run other operating systems on Apple devices, including iPadOS. In principle, this means that an iPad can run Windows, and Windows can then run a WDS game. This is technically interesting, but it is far outside the normal and supported use case for WDS games.

I have tested this on a slightly older 6th-generation iPad Pro with an M2 processor. In that test, it was possible to install Windows 11, install Panzer Campaigns: Smolensk '41, and run the game using an attached keyboard and mouse. So the basic idea can work.

However, it was very, VERY slow. The game could be launched, but performance was not good enough for practical play. In other words, this was a successful technical experiment, not a usable gaming setup.

There are several reasons for this. On iPad, UTM is much more constrained than on macOS. The App Store version, UTM SE, is an emulator and does not have the same performance characteristics as running Windows in a proper virtual machine on a Mac. UTM's own documentation notes that UTM SE does not support JIT and will run much slower. That matters because Windows itself is already heavy, and a WDS game then has to run inside that Windows environment. For details on UTM, see here: https://docs.getutm.app/installation/ios/

There are also practical interface issues. WDS games are desktop wargames. They expect a Windows-style desktop, a mouse, right-clicks, menus, toolbars, file access, and a reasonably large screen. An iPad with a keyboard and mouse can provide some of this, but it is still an awkward environment for regular play, PBEM file handling, updates, and troubleshooting.

A typical experimental setup would look something like this:

1. Install UTM or UTM SE on the iPad.
2. Create a Windows 11 Arm64 virtual/emulated machine.
3. Install Windows 11. 
4. Attach a keyboard and mouse.
5. Install a WDS game inside Windows.
6. Launch the game and test whether the map, menus, and file access work.

This should not be confused with the Parallels-on-Mac recommendation. On a Mac, Windows can run as a much more capable virtual machine. On an iPad, the environment is more restricted, slower, and less predictable.

For that reason, UTM on iPad should be considered highly experimental. It may be interesting for technically curious users, but it is not recommended for normal play, and it is not an officially supported WDS configuration.