Wine is not faster than dual-booting, but has the advantage of being integrated into your OS, so you don’t need to reboot every time you want to use software made for a different operating system. Therefore, it’s much faster than emulation and doesn’t require a Windows license to use. It does not actually run Windows like an emulator or virtual machine does rather, it translates Windows instructions so that Unix systems can use them. Wine is a compatibility layer that allows certain Unix-based operating systems, including Mac OS X, run Windows software. Until then, if you want to use this guide, avoid the new OS while you can, and attempt to downgrade if you are able. In the the very, very (very) distant future, we may see the excellent OpenMW open-source engine project expand to fully support Oblivion, enabling even better cross-platform support for Oblivion and eliminating several modding headaches as well. There's reason for hope: CodeWeavers just released a new version of Crossover that supports 32-bit applications without 32-bit support for OS X, and since CrossOver and Wine are closely tied projects, we may see such support in Wine as well. I have not tested this guide with this most recent OS, but since Oblivion is a 32-bit application, there's reason to believe it won't work with this new version of OS X, even though the guide calls for a 64-bit engine. Note that one unfortunate thing that's changed is that since its most recent update (OS 10.15, or "Catalina"), Mac OS will no longer support 32-bit applications. For these reasons an update has long been due this guide represents my efforts to provide such an update. I've changed too, both in what I've learned about modding and in my approach to modding Oblivion.
Wine and Wineskin (via the Unofficial Wineskin Project) have continued to develop and improve. I can only hope that some people found it useful, but since that time, a lot has changed. Just over two years ago, I posted a guide on how to run Oblivion natively in OS X, using Wine and Wineskin. In the meantime, see what happens if you use a 32-bit wrapper instead.
A major revision to this guide may be in order. This seems not only to be wrong, but deleterious. EDIT 5-20-2020: This guide advises using a 64-bit wrapper, under the belief it was necessary to take advantage of Large Address Awareness.
0 kommentar(er)
