Since there is the option of installing Windows games on Mac with the Porting Kit I have no reason to waste tons of gigabytes just to install Windows in a different partition and play the game. I won't be carrying two notebooks, using one of them just for gaming. Basically, I need a notebook and I need a Mac, so I have a MacBook. Since I'm also an university student and live too far of my university, I constantly move between my house, my gradma's house (which is nearest of my university) and my university.

I have a Mac for two reasons: it's my work tool (I'm an iOS and Mac programmer) and I like the system. This is not the point of the conversation, but I will still answer: You are more than able to risk the game not working, or you could just get an actual gaming PC with a halfway decent GPU and this wouldn't even be a concern. Given that DBXV2 is a direct port from current gen consoles, it's very doubtful it will support anything other than DX11. They are rarely ever supported by most game studios. Macs aren't for gaming and are overpriced paper weights. At least, DirectX 10 and further still aren't well supported by Wine. There are already some 64 bit prefixes, however the 32 bit ones are more stable. Originally posted by VitorMM:Well, when you went to play on Mac you need to use Wine/Wineskin/PortingKit, and most of the Wine-based wrappers are 32 bit prefixes, which means that they can only run 32 bit apps. not until these crashes are fixed, but since it has been over 2 years, I guess this won't happen by now.

I'm sad for saying that, but I don't recommend the native Mac version of TWAU. I really liked the game and I will finish it, even if I have to reinstall it on my Mac using Wine / Wineskin / PlayOnMac / PortingKit / CrossOver, but these crashes completely break my immersion. I thought I was a particular case since I never heard anything about Telltale games and crashes, but macOS's TWAU makes vanilla Skyrim look stable. The problem was noticed since September 18th 2014 and since then there was no response, nor fixes. Apparently that seems to be a VERY common issue:

Oblivion playonmac 2017