The test results for this version are very old, and as such they may not represent the current state of Wine. Please consider submitting a new test report.
Selected Test Results (selected in 'Test Results' table below)
Installing using the obmm_setup.exe
running the utility from the Wine-created desktop shortcut
adding archives, extracted archive folders or individual files to OMODs
setting screenshots for OMODs
creating (compressing) OMODs*
viewing the website associated with an OMOD* (if IE6 has been installed via Wine-Doors, winetricks or Wine itself)
deleting an OMOD*
converting an OMOD to an archive*
extracting an OMOD to a folder*
exporting OMOD conversion data*
activating ESM/ESP files in the Launcher window
changing view settings in the Launcher window using the drop-down menu
changing load order in the Launcher via "move up/down" buttons, context menu*, drag and drop, or ALT+ arrow key
reading/editing OMOD readme or script from within the OMOD Creation window or context menu* of the OMOD in the OMOD database
Resetting BSA timestamps using the Archive Invalidation utility
enabling BSA Redirection using the Archive Invalidation utility
both the old and new conflict detectors
Data File Browser
Save Manager (opens fine, but I didn't have any saves to manage)
Hidden OMOD switcher utility
viewing the load order as text
exporting load order and active omod list
creating an omod report
viewing the Help file from the button so designated
Viewing the "About" information when clicking the 'About" button
Visiting the website when clicking the "Visit the website" button in the 'About' dialog (if IE6 is installed)
launching Oblivion via the button so designated
launching Oblivion with OBSE via the Launch button.
* - see "what does not work (completely)" section for further notes.
What does not
- Editing the path of a file inside an omod in the Data Files view, because it requires a (triple) mouse click, and mouse clicks don't seem to be recognized in the OMOD Creation Window or the main window (they are recognized in the text editing windows insofar as those windows ever accept certain mouse clicks-- not all of them do). However, you can manually extract the archive to a temporary folder, customize it to your desires, and then create an omod from the folder.
- Left-clicking does not bring up the context menu, again because mouse clicks are not recognized in the main window. However, if you have a keyboard which has the Windows keys, the "context menu" key on the right (next to R-CTRL) does bring up the context menu for the selected item normally, and once visible, the context menu works normally.
The functions only available from the context menu are:
In the OMOD Creation window:
open (useful if the associated program that opens the selected file type is installed and you want to have a look at it before including it in the OMOD)
remove from omod (very useful function)
validate (I think this is obsolete, and don't use it)
Import mod details (a very useful function if you want an author name and description attached to your self-created OMODs, assuming that the author has put this information in the ESP header)
scan for data files (never used this myself)
View required data files (also never used).
In the Database window:
View readme/view script* (these functions are available from the OMOD Creation window that opens if you choose to Edit the OMOD, but from the context menu you can open these files without opening the OMOD Creation window)
View data conflicts (vastly useful)
Group* (again, can be set from the Creation window by Editing the OMOD, but from the context menu allows you to attach the omod to a group without opening the Creation window)
So these functions are not available to users with keyboards that do not have a "context menu" key, due to the fact that the left mouse click does not work in the main window (or in the OMOD Creation window).
- Compressing large OMODs (>200 MB) can hang the program. However, ending the OBMM process in the System Monitor, reopening the app (there will be an error message saying that the 'central directory' of the OMOD in question could not be found; ignore it and the program will then open normally), and then compressing the same OMOD before doing anything else appears to work (eventually; I've had to rinse and repeat up to 3 times before getting the OMOD to complete creation).
- NifViewer does not work. It eventually comes up with a (Windows) crash dialog, but does not crash the program as a whole. I believe this utility had issues under Windows as well, so this may not be a Wine problem as such.
- When using the dialog to specify the location to a) save an OMOD extracted to a folder or b) export omod conversion data, the dialog does not allow you to create a new folder. Clicking the "New Folder" button does absolutely nothing.
This is not a major issue when extracting an OMOD to a folder, because the extraction creates a folder named the same as the OMOD, then puts the files inside. If you extract the conversion data for multiple OMODs, however, there is a small problem, as the only folder created is titled "omod conversion data" with no further individuation. Naturally, you can pre-create folders with "mod_name" titles and then extract the various OMOD conversion data folders to those individual folders, but if you did not do some form of pre-preparation such as that you would run the risk of ovewriting each "omod conversion data" folder with the following one.
What was not tested
Group creation, editing or viewing
changing settings (moving the temp directory or the omod directory)
viewing the website of an OMOD using Firefox (for Windows) rather than IE6
emailing the author of an OMOD (assuming you entered an appropriate email address in the OMOD data, but I have no Wine-useable email program installed)
Acquisition Activate (telling the OBMM that manually-installed files already in the game's Data folder should be associated with a newly-created OMOD)
Simulated installation of an OMOD
Cleaning an OMOD
Any of the functions under the 'Batch Actions' button (activate filtered, deactivate filtered, etc.)
Any of the "Import" functions under the 'Import/Export' button
Writing/compiling a new OMOD installation script in any of the available scripting languages
Attempting DLL overrides to see if that would resolve any of the issues above (I have no idea what DLLs are involved, so....)
This program requires .NET 2.0. If you can get that to install, this application will run extremely well for both beginner and advanced use, with a few relatively minor caveats (as long as your keyboard has Windows keys).
IE6 and/or a Windows email application are necessary if you desire to use the 'Visit (omod) website" or "email (omod) author" functions, but if you don't, then you don't need them to support this app.
The main difficulty is getting .NET 2.0 to install (well enough that it is recognized by this application), but it is well worth it to persist and get the OBMM running, even if you don't use a lot of OMODs-- but especially if you do.
The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.
by Mariano on Monday January 9th 2012, 15:11
Anyone tried it on newer wine? I installed it on 1.3.34 and it worked as displayed here, but afterward I had to revert to 1.2.3 and it doesn't start, no matter what (shows some error about msvcr, but I have all of them installed and they work on other games, and can't be .NET, since I installed both 2.0 and 3.0)... If anyone posts something, we can update it. :)