I have played games on Wine since Baldur's Gate was new, and you're severely overestimating the weight of these translation steps. Here is a relevant Debunking Wine Myths page on the Wine wiki. Wine actually stands for Wine Is Not an Emulator. Rixasha: I was trying to be funny with that line. But in terms of ease of setup and features, the EE in WINE is much easier to setup and play (especially since it doesn't need any special dependencies, settings or registry hacks) for me, with almost no discernable loss in performance versus the CE in DOSBox. Sure, running SS through the EE running in Wineskin or CrossOver is not as elegant or efficient as running the CE in DOSBox with whatever patches I need to get most of the functionality in the EE (or just running the whole thing in Windows). That's especially if they're not using intensive 3D graphics/hardware accelerated graphics. But overall hardware has gotten so powerful, in addition to continuing improvements in the host OSs and APIs themselves, (and WINE has made a lot of significant strides in boosting performance, compatibility, and efficiency) that the performance hit is almost negligible for old games like System Shock. ![]() ![]() There is obviously a performance hit when running games in WINE on Linux or OS X, especially if you're using an additional layer of abstraction like a 3Dfx GLIDE wrapper or in this case, the EE's version of Shlink. In short, it's a 2-step conversion rather than a single step that it would be for DOSBox, and the emulation/conversion of Windows is a more complex process overall. Firebrand9: For OSX, you're asking it to convert every Win GDI function, to Cocoa (even if it's using OpenGL) via Crossover in addition to the conversion already taking place from the DOS to Windows translation for the EE.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |