Almost everything. The game is very much playable; no problems are known with installation or gameplay. All sound plays correctly. Extensive modding also worked well; it would be impractical to list every single mod tested, but very complex mods which made vast changes to the game functioned flawlessly, including Necessities of Morrowind v2.13 and Tamriel Rebuilt Maps 1 and 2. Many different types of mods worked well.
What does not
pbuffer and backbuffer; these rendering modes produce a number of bugs, including some issues with displaying the paperdoll inventory. using the fbo mode, however, appears to work flawlessly.
Attempting to alter the default input controls causes the game to crash.
The game freezes occasionally on entering combat phases for about 5-10 seconds, sometimes less, and sometimes not at all. This error is slightly irksome, but does not make the game unplayable.
Some errors with water rendering exist; these are purely cosmetic.
Occasional unexplained crashes did occur. These were very sporadic, and not frequent enough so that I was able to determine some common cause.
The Elder Scrolls Construction Set for Morrowind did not work correctly. Existing plugins could be edited and saved, but attempting to save a new plugin file caused the Construction Set to crash. No other errors with the Construction Set were observed, but it was not tested extensively.
What was not tested
Short of playing every single quest and area of the game, almost no major aspect of the game was left untested. The main questline was only minimally tested, but questlines for House Redoran, the Imperial Legion, and the Tribunal Temple were all extensively or partially completed. There was no visible indication of any broken quests.
The game was tested on Ubuntu 8.10 x86_64, GeForce 8800, AMD Phenom 9750 processor, 4 GB RAM. The addition of multiple mods created only one discernible performance issue; framerates were sluggish (but manageable) in Vivec with the use of Vivec Redesigned v1.1. Otherwise, performance is generally excellent, even with the use of a number of very large and complicated mods.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Show||Ubuntu 19.10 "Eoan" (+ variants like Kubuntu)||Oct 29 2019||4.18||Yes||Yes||No||Platinum||consolelogger|
|Show||Linux Mint 14 "Nadia"||Nov 22 2013||1.7.6||Yes||Yes||Platinum||Booman|
|Show||Ubuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)||Oct 19 2013||1.7.4||Yes||Yes||Bronze||mx2|
|Show||Arch Linux x86_64||Feb 03 2013||1.5.22||Yes||Yes||Gold||P. Neidhardt|
|Show||Ubuntu 13.04 "Raring" amd64 (+ variants like Kubuntu)||Dec 24 2012||1.5.16||Yes||Yes||Platinum||Dale|
2014-11-14 Admin note: the following was extracted from a user comment made on November 9th 2013, and may not be relevant to current Wine.
About windows getting minimized, the workaround is pretty simple : the MenuStates of the .ini file is reset everytime you launch the game, which causes it to define minimized windows. What you need to do is chmod it to read-only (chmod 444 does the trick) after having changed the MenuStates parameters to suitable window sizes.
I got it to work with around 50 mods, the thing is the .ini file needs to update the modlist, so you first need to run Morrowind with a writable .ini file (chmod 644 works like a charm), then you can kill the process immediately afterwards (wineserver -k after Ctrl+Alt+F1 for instance), chmod the .ini to 444 after checking the MenuStates section is still well and about, and launch the game !