Coming back to Oblivion after nearly 3 years absence I now have the doubtful pleasure of setting up a modded version from scratch, rather than incrementally as previously.

My problem is that trying to install Unofficial Oblivion Patch v3_2_0 OMOD Version-5296, (.ZIP) when double clicking the file OBMM is just coming back with "Unsupported file type". I am assuming that it is an Omod & not Omod-ready, Creating an omod from it is not working.

Creating an omod from UOP Supplemental v33-27710 is working properly.

I am running 64-bit Windows 7; but, I have installed Oblivion outside of the Programs folder, set OBMM & Oblivion to run as administrator & System.Net.dll is installed in both the 32 bit & 64 bit Program folders.

Has anybody got any idea of whats happening or what I can do?

I'd rather not use up another 125Mb of TesNexus bandwidth on the installer version if there is a way of getting the omod version to work.

You should be able to open OMM, click on the icon at the bottom that says Load, navigate to the omod, and have OMM recognize it, and install.

Sorry but all thats doing is opening the extracted folder & not seeing anything inside it that it recognises as an omod. It doesnt even display the .ZIP file

I'm little confuse what you mean about your problem, but I think you should http://www.gamesas.com/index.php?/topic/449239-oblivion-mods-faq/. :read:


Btw... welcome to the forum. :wink_smile:

First, I have solved my problem by downloading the installer version of the UOP (with my PES account, so saving TesNexus bandwidth), which has installed properly.

Going back to my OMOD problem, it is based on this:

I have 2 downloaded files
DarNified_Interface_Omod-3956
Unofficial Oblivion Patch v3_2_0 OMOD Version-5296

If I extract DarnUI I get a folder with Darnified UI 20060505 which says it is an Oblivion mod & if I copy it to obmm/mods folder OBMM recognises it as an .omod & puts it in the omod list & I can activate it - no problem

However if I extract UOP all I get is a folder with 7 files in it ( config, data, data.crc, plugins, plugins.crc, readme, script) - which seems to be a problem as it is not a .omod & if I use omod creator to create an omod from the folder, at the end of the procedure it does not seem to be installing the UOP as I dont get the UOP token when running Oblivion.

So basically, what am I doing wrong with the UOP ?

Btw... welcome to the forum. :wink_smile: I've actually been on the forums for 6? years but after 3 years absence the forum wouldn't recognise me & I had to start anew. :wink_smile:

Don't do this bit if the file already ends in .OMOD. :wink_smile:

Thanks, I didn't even know that you could extract a .OMOD :wink_smile:

but this is where I'm getting confused, both DarNified_Interface_Omod-3956 & Unofficial Oblivion Patch v3_2_0 OMOD Version-5296 are downloading as .ZIP.
I can extract DarnUI to get an .omod which when copied to obmm\mods folder is recognised by OBMM
but if I extract UOP all I get is a folder with 7 files in it (no .omod)
If I copy Unofficial Oblivion Patch v3_2_0 OMOD Version-5296 (.ZIP) to obmm\mods folder it is not recognised by OBMM

So, how do I install the UOP, Omod version :banghead:

Actually I'm feeling very apologetic for wasting other peoples time on this since I have got the installer version working, So please feel free to ignore this.

When you extract the zip files you get one omod for DarNified UI and 7files in total for the uop 3.0.2 it's that correct?
If so you didn't notice a folder called "omod conversion data" among these files?

He shouldn't as UOP is an actual OMOD, not files in the "OMOD Ready format."

I have it as well and it runs just fine (although I use another version through BAIN instead nowadays) but I did have this problem with OMODs a while back, when double clicking on them, which should install the OMOD in OBMM, instead opened it as a zip file with the 7 files metioned (actually the proper components of an OMOD file, usually hidden from the general user!)
I have no idea what was going on, and the few OMODS I still use don't seem to have that problem any more. :shrug:

That's odd and very strange to me, because I never had that kinda of problem before.