(01-13-2020, 03:31 AM)The7PercentSolution Wrote: Hello again and happy new year! I just wanted to share my success story with the 2018 Mac Mini. I caved and got one about a week ago and it's been fantastic. Just to note, I didn't get it ONLY to play GameCube games... although I'd be lying if I said that wasn't part of the goal. Anyways, as I mentioned in the first post my 2012 Mini will just barely play GameCube games but then the fan kicks in as the computer starts to get REALLY hot. That isn't the case for the 2018. I've been playing several games for extended periods of time and when I go put my hand on the computer it's barely warm! I can't express how ecstatic I've been about this.
Here's what I had before and what I ended up getting.
2012
2.6 GHz Intel Core i7 (Turbo Boost up to 3.6GHz) - I believe this is quad core
16 GB 1600 MHz DDR3
Intel HD Graphics 4000 1536 MB
1TB HDD storage
2018
3.2GHz 6‑core 8th‑generation Intel Core i7 (Turbo Boost up to 4.6GHz)
16GB 2666MHz DDR4
Intel UHD Graphics 630
2TB SSD storage
There are just a couple things though that maybe someone can help answer.
Initially I tried playing the GameCube games through OpenEmu because they just added Dolphin to that. However, I did notice the computer starting to get hot when playing on OpenEmu so I've opted to play directly from Dolphin which has worked great. Any particular reason why playing on OpenEmu causes more of a strain on the computer?
Also, I have version 5.0-11452 of Dolphin and the ONLY flaw with that is that when I want to close the program I have to use Force Quit. Not a big deal, but it'd be nice if it didn't do that. If anyone is familiar with that problem I'd appreciate any input!
Thanks!
For issues with OpenEmu I need to redirect you to the support of OpenEmu, but my guess is that OpenEmu doesn't unload itself and keeps using CPU power while playing a game in Dolphin, causing more strain on the CPU and thus resulting in more heat.
The issue with Force Quit I cannot help you with, maybe a dev can chime in or maybe it is a known issue that has already been solved in a newer dev-version, so you could try updating to the latest version.
Check my profile for up to date specs.