Purchase and download Oblivion from GOG.New wrappers are in /Applications/Wineskin folder. Click View wrapper in Finder when Wineskin creates the wrapper and move it to your desired location.Click Create New Blank Wrapper and name it Oblivion.As of this writing, more recent versions suffer various bugs. Download an engine by clicking the + button and selecting an engine.
Click Update if available to make sure your Wrapper Version is up to date.Move the Unofficial Wineskin Winery application to a different location to work around a security issue.This prevents a bug that won't let the program run properly.).
Double-click to unpack (If you have a third-party archive tool like Keka, bypass it by right-clicking the file and selecting Open With > The Unarchiver.It makes managing these little environments much simpler, more reliable, and conflict-free. Think of each wrapper like a little ecosystem that’s independent of anything else on your computer, including other wrappers. This may seem odd, but the fact that each wrapper is so self-contained is what makes them useful. Same with everything else the game needs to run, including the Wine engine itself. With Wineskin, every program that needs that library will have its own copy of that library. On Windows, if you need, say, a particular DirectX library to run a certain game, you just download it once and it will work for every other game that needs it. To use Wineskin, you create a wrapper, which is a self-contained group of files that contain everything you need to run a particular program, including a Wine engine, the program itself, and any other support files required to make the game run.Ī thing to realize about Wineskin wrappers is that since they are self-contained, each wrapper has its own copy of what’s needed to run a game. This makes installing and modifying programs using Wine much easier. Luckily there’s Wineskin, a GUI front-end for Wine and many of its tools. Wine usually runs in the command line and is likely beyond the computer skills of many users (this writer included).
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.