Sim Racing on Apple Silicon Mac – The complete guide

If you’re reading this on a Mac and wondering whether you can actually sim race seriously – the answer is yes. Not “yes, with caveats that make it barely worth it”. Just yes.
This guide covers everything you need to run a proper sim rig on Apple Silicon in 2026: which games work, how to get them running, what to do about force feedback, and what to expect performance-wise. Written by someone who actually races on a Mac, so the goal here is to give you accurate information, not to sell you something.
The state of sim racing on Mac in 2026
Two things changed in the last few years that made Mac sim racing viable:
Apple Silicon. M-series Macs are genuinely fast enough. The M1 was a signal; the M4 and M5 chips are outright quick. Unified memory architecture, efficient CPU cores, and the Metal GPU stack put current Macs in the same performance tier as mid-range Windows gaming machines. The hardware objection is gone.
CrossOver. This is the compatibility layer that lets you run Windows games on macOS without a virtual machine. Once CrossOver matured on Apple Silicon and performance caught up, the software objection mostly went away too.
The last remaining gap was force feedback. Logitech doesn’t ship a macOS FFB driver for their wheels. For a long time, even if you got your game running perfectly, the wheel just sat there limp. That problem is now solved – more on that later.
The point is: this is no longer a “it sort of works” situation. With the right setup, you’re running a real sim rig.
CrossOver – the software that makes it work
CrossOver is made by CodeWeavers and is based on Wine, the open-source compatibility layer that translates Windows API calls into macOS equivalents. The key distinction: this is not emulation. The game code runs natively on your CPU – CrossOver just translates the system calls. On Apple Silicon, the performance hit is minimal for most titles.
Cost: Around $74/year or $15/month. There’s a 14-day free trial. If you’re serious about sim racing on Mac, it’s worth it.
Alternatives worth knowing:
- Whisky: free, open-source, Wine-based. Less polished, no commercial support, but works for casual use. Fewer configuration options, which matters for sim racing.
- Parallels: runs a full Windows virtual machine. More compatible with arbitrary Windows software, but more overhead and less suited for gaming. Not recommended for sim racing.
For sim racing, CrossOver is the right tool.
Which sim racing games actually work?
Here’s an honest breakdown as of 2026. “Works great” means it runs reliably at good performance with no showstopper issues.
Works great
Assetto Corsa – The standout recommendation for Mac sim racers. Runs excellently on CrossOver 25.x using D3DMetal + MSync settings. Mod support is full (with one caveat — see the mods section below). Physics, tyre model, the full package. Force feedback works completely with Torqer.
Assetto Corsa Competizione – Runs well with the same CrossOver configuration. GT3 and GT4 racing at full visual and physics fidelity. FFB works with Torqer.
Assetto Corsa Rally – Also runs well. Native force feedback via Torqer.
KartKraft – Runs well. Native force feedback via Torqer.
rFactor 2 – Runs, but requires a different graphics mode: use DXVK instead of D3DMetal. Worth the configuration effort — rFactor 2’s physics model is exceptional.
RaceRoom – Runs well.
Richard Burns Rally (RSF version) – Works, though loading times are slow. Important: launch from the main executable, not the RSF launcher, for best compatibility.
Live for Speed – Runs well.
Doesn’t work
Le Mans Ultimate – Not running yet under CrossOver. Check back later.
iRacing – Anti-cheat software blocks Wine entirely. No workaround.
EA Sports WRC / Dirt Rally 2.0 – These titles run, but the data they expose doesn’t include the physics information needed to implement proper force feedback. Not recommended if FFB matters to you.
Quick reference
| Game | CrossOver | Force Feedback |
|---|---|---|
| Assetto Corsa | ✅ Great | ✅ Full (Torqer) |
| ACC | ✅ Great | ✅ Full (Torqer) |
| AC Rally | ✅ Great | ✅ Native (Torqer) |
| KartKraft | ✅ Great | ✅ Native (Torqer) |
| rFactor 2 | ✅ (DXVK) | Coming soon |
| RaceRoom | ✅ Great | Coming soon |
| Richard Burns Rally | ✅ Slow load | Coming soon |
| Live for Speed | ✅ Great | Coming soon |
| Le Mans Ultimate | ❌ Not yet | — |
| iRacing | ❌ Anti-cheat | — |
Setting up CrossOver for sim racing
A few configuration decisions make a meaningful difference:
Use Windows 10 64-bit bottles. This is the right target for all current sim titles. Windows 7 compatibility mode causes unnecessary compatibility issues.
D3DMetal + MSync for most titles. D3DMetal is CrossOver’s Metal-based DirectX translation layer – it’s fast and stable for DX11/DX12 games, which covers AC, ACC, and most of the list. MSync is a synchronization primitive that dramatically reduces CPU overhead compared to the default. Always enable it.
rFactor 2 exception: use DXVK. rFactor 2 works better with DXVK (a Vulkan-based DX translation layer) than D3DMetal. The default sync settings work fine here.
Separate bottles per game. Keep your games in individual CrossOver bottles rather than one big shared bottle. It’s slightly more disk space, but it makes troubleshooting much easier and prevents one game’s configuration from breaking another.
Install Steam inside the bottle. Buy your games through Steam as normal. Install Steam inside your CrossOver bottle, then install games through that Steam instance.
Tested version: CrossOver 25.1.1 is the confirmed-working version for the games listed above. Note: Content Manager (the popular AC mod manager) reportedly doesn’t work on CrossOver 26.0 – if you use Content Manager, stay on 25.1.1.
Force feedback — the former missing piece
For years, this was the dealbreaker. You could get your game running, the graphics would look great, and then you’d grab the wheel and feel nothing. The wheel was just steering input – no resistance, no road feel, no kerb impacts.
The reason: Logitech doesn’t provide a macOS force feedback driver for the G29 or similar wheels. And CrossOver’s Wine layer, which handles the translation between Windows game code and macOS, historically couldn’t route FFB signals through to the actual hardware. The game would try to send force feedback commands, they’d disappear somewhere in the translation layer, and the wheel would never receive them.
Torqer solves this. It’s a macOS app that bridges the gap between the game’s force feedback output and your wheel. When you’re driving in Assetto Corsa, the wheel responds – understeer, oversteer, kerb feel, tyre lock. The actual FFB you’d get on Windows, running on Mac.
A free 5-day trial gives you the full feature set, so you can verify it works with your setup before committing. After that it’s a one-time purchase. Download and try it for free here.
Racing wheels that work on Mac
macOS sees most USB and Bluetooth HID devices natively, which means many wheels register as input devices without any driver. Force feedback is a different question – it requires active software to send commands back to the wheel.
Logitech G29 – Fully confirmed. Works as an input device out of the box on macOS. Full force feedback via Torqer. This is the wheel to get if you’re starting from scratch.
Logitech G923 – Input works on macOS. FFB support via Torqer is in testing.
Logitech G920 – Similar situation to the G923. Input confirmed, FFB support being evaluated.
Thrustmaster / Fanatec – Input may work, depending on the specific wheel. FFB is not currently supported by Torqer. These manufacturers also don’t ship macOS FFB drivers.
Important: do not install Logitech G Hub on macOS. It conflicts with how the wheel presents itself to the system and creates more problems than it solves. The G29 works without it — just plug in and go.
Performance on Apple Silicon
Here’s what to realistically expect:
M-series chips handle sim racing well. Assetto Corsa and ACC run at 60fps easily on M2 and M3 at high settings. Push the resolution and visual quality – the frame rate will hold. An M3 Pro running ACC at 1440p high settings is a comfortable experience.
Unified memory is an advantage. Apple Silicon uses shared memory for CPU and GPU, which means an M3 with 16GB has more effective graphics memory available than a discrete GPU with 8GB VRAM. Texture-heavy mods and high-res tracks benefit from this.
MSync matters. Without it, CrossOver puts significant CPU load on synchronization primitives. With MSync enabled, CPU usage drops noticeably and frame times get more consistent. Always enable it.
Close background apps before a session. Safari tabs, Slack, whatever — close them. The GPU and memory pressure from browser content is real. It’s not that Macs are underpowered; it’s that macOS background processes compete for the same unified memory pool.
D3DMetal settings to experiment with: Anti-aliasing is where you’ll find the most performance headroom. AC and ACC both handle MSAA drops well visually. If you’re seeing frame time spikes, reduce AA before dropping other settings.
Mods – Assetto Corsa specifically
Assetto Corsa’s mod library is enormous, and most of it works on Mac. The caveat is one specific mod type that causes crashes under CrossOver.
Some mod cars use CSP Extended Physics (you’ll see VERSION=extended-2 in the car’s data). This feature calls Windows APIs that don’t translate properly through CrossOver, and the game crashes when you try to load those cars.
The fix is straightforward and takes about 30 seconds per car: edit one value in the car’s data file, changing extended-2 to 2. Full instructions at: torqer.app — why most modded cars crash and how to fix it
Stock Kunos cars are unaffected. Most road, GT, and touring car mods work without any modification.
Content Manager: The popular mod manager for Assetto Corsa runs inside your AC CrossOver bottle. Use version 25.1.1 of CrossOver – there are known compatibility issues with 26.0. Once it’s running, Content Manager works normally for car and track management.
The Mac sim racing community
It’s small, but it exists and it’s growing. As Apple Silicon has removed the hardware objection, more people are building Mac sim rigs seriously.
Torqer Discord – The most active place for Mac-specific sim racing discussion. Join for setup help, game compatibility news, and community. (Link available at torqer.app)
Reddit: r/simracing and r/macgaming both have Mac-specific threads. r/simracing is worth searching before posting — many common questions have been answered.
The honest take: most of the “Mac can’t do sim racing” reputation is outdated. The hardware and software situation changed significantly in the last two years. If you find a thread from 2022 saying it doesn’t work — it’s probably wrong now.
Getting started
The practical path to a working Mac sim rig:
- CrossOver – $74/year, 14-day trial. Install it first.
- Assetto Corsa (or ACC) – buy on Steam, install inside a CrossOver bottle using Windows 10 64-bit, D3DMetal + MSync.
- Logitech wheel – plug in, no drivers needed. macOS sees it immediately.
- Torqer – download, start the 5-day trial, confirm FFB works with your setup. If it does, the full purchase is torqer.app/#download.
That’s a complete sim racing setup on Mac. No Windows machine. No Boot Camp. No compromises that actually matter when you’re on track.
If you have questions or hit something that doesn’t match this guide, the Torqer Discord is the right place to ask.






