The Witcher 3
From AppleGamingWiki, the wiki about gaming on M1 Apple silicon Macs
 |
|
| Developers | |
|---|---|
| CD Projekt Red | |
| Publishers | |
| CD Projekt | |
| Engines | |
| REDengine | |
| Release dates | |
| May 19, 2015 | |
| Reception | |
| Metacritic | 93 |
| OpenCritic | 92 |
| IGDB | 92 |
| Taxonomy | |
| Series | The Witcher (series) |
| Resources | |
| PCGamingWiki | |
| Codeweavers | |
| WineHQ | |
  |
|
General information
- Official Forums
- The Witcher 3 Nexus Mods
- GOG.com Community Discussions
- GOG.com Support Page
- Steam Community Discussions
macOS Compatibility
| Compatibility layer | Rating | Notes |
|---|---|---|
| CrossOver | 1 or 2 type of enemies are invisible but they are very easy to kill.[1] | |
| Wine | A few enemies are invisible and a few have bugged textures. Most notably the Hounds of the Wild Hunt are invisible in the first quest you meet them, the rotfiends are invisible in Velen and the sirens are invisible in Skellige. Skellige also has a lot of places in the coastline where the game becomes very glitchy.[2] | |
| Virtualization | ||
| Parallels |
Availability
- See PCGamingWiki for Windows and/or Linux availability.
Gameplay videos
References
- ↑ Render issue with The Witcher 3 Wild Hunt · Issue #582 · doitsujin/dxvk · GitHub - last accessed on 2022-07-16
- "err: D3D11Device::CreateGeometryShaderWithStreamOutput: Not implemented. Sirens are one of the enemies in Witcher 3 that rely on Stream Output which DXVK currently can't implement."
- ↑ Verified by User:Exerra on 2022-12-28
- Device: Mac Mini M1 2020 8GB RAM
- OS: macOS 12.2
- Method: PortingKit
- Game version: 1.32
- Store: GOG
- Resolution: 1920x1080
- Settings: Medium
- Controller: Xbox Series S
- Comment: NVIDIA Hairworks must be turned off, game crashes if the graphics quality is higher than the Medium preset and every postprocessing item can be turned on and still have the game be smooth (except motion blur). When using PortingKit the game does not exit when the button has been pressed in-game, it only closes the window. To exit fully, either go to PortingKit and kill all processes using the PortingKit GUI, or go to Activity Monitor and kill all the wine processes. If the game does not launch (wine process starts, then quits automatically) restart your computer and try again.