Smooth613

You don't change .7z files to .esp files. They are two completely different file extensions. A .7z file is a compressed archive, much like a .rar or .zip file. Compressed archives require extracting software to extract them. You can use 7zip, WinRAR, etc... I suggest 7zip since it's 100% free and does the job, and does it well. WinRAR is also a very good choice if you want to pay for the full license. Download 7zip from SourceForge.net In order to install mods via Oblivion Mod Manager - OBMM, I suggest you check out LHammonds' OBMM How-To. And finally about your missing mesh problem. The yellow exclamation marks you are seeing is due to missing resources, particularly meshes. This is the result of improperly installed mods or incomplete mod installation. This is likely due to not completely understanding different file types, .esp & .7z, and not properly using OBMM to install the mods. Below is some information about missing resources and more. Missing Resources | Scroll down to the Pink or Missing Textures Section. You likely need Archive Invalidation. TESIV:POSItive -- Excellent resource site loaded with information for the beginner to advanced user. Good luck! *EDIT* I also just remembered that when you are downloading files a message is displayed stating the following...

BOSS would not tell you to remove that ESM in a proper FCOM setup. You either misunderstood the suggestion or have something else going on that shouldn't be. That something else could be a number of things, and since you didn't Post Your Load Order you leave us with nothing but guessing. Here is a snip of a BOSS log with FCOM installed. As you can see Francesco's Optional New Items Add-On.esm [Version 4.5bSI] is present, and FCOM is detected, and BOSS clearly doesn't tell you to remove it. In fact there are no suggestions for the previously mentioned file.

No problems from that file on my end. I've been using it for ages and the Megaupload file is clean from my reports. GreatLucifer: I understand you want to be cautious but by what you've said you haven't actually checked the file, you're only going on a warning of other users. Other users can falsely report problems and tarnish a file just as easily as they can hype it up. You need to actually scan the file yourself before just assuming by word of mouth that it's infected. To add further to this... I've seen many many of times where people come here to TESNexus and report downloads as being infected when clearly they are not. They may have had a virus previously or it could just be a false positive. And since the folks reporting that file would be the same folks that would come here (Megaupload) it's very likely a handful of people falsely reported the file as malicious and now McAfee is just warning you of these reports, not of actual infection.

By the looks of the screenshots you're loading nearly every shader available in OBGE, which is not necessary and most likely not desirable. You need to read the descriptions for each shader and decide which ones you want to use and disable the rest. There's really nothing more that can be said about this. The effect you're getting is from SSAO, ColorEffects, and most likely CellShading, along with other shaders. However each of these shaders can be tweaked to your liking or completely disabled. SSAO is an excellent lighting effect and when used properly adds great "shadowing" to the scenery. But if you just plop 10-15 shaders into your game and don't tweak or disable any of them you end up with the mess you see on screen now. You need to read the documentation included with OBGE to grasp an understanding of what each shader does and how to tweak them manually or with the support plugin. The ReadMe is chock full of information and is worded rather simply, and straightforward, for what the mod does.

MartG66 is indeed correct and found the issue. You're not loading the RAWZfix.fx shader. Certain cards require you to run this fix in order for OBGE to work. This is documented in the ReadMe. You need to load the RAWZfix.fx file, reload the game, check for the error, and post your newly generated OBGE.log here. You simply need to drop the RAWZfix.fx file into the Shaders folder and alter the OBGE.ini file to activate the fix. bUseRAWZfix=1 ;0/1 = off/on respectively bUseRAWZfix - Activates a fix for graphics cards that use the RAWZ depth buffer format. My log, with OBGE working perfectly, also reports the same as MartG66's... RESZ format supported. I'm fairly confident that is your problem.

The screenshot looks to be corrupt shaders, yet you mention other saves don't have the issue. Either way I'd start by replacing the Original Oblivion Shaders and disable OBGE if you use it. Report back with the results and be sure to include your Load Order and post any/all of your OBSE plugins you use.

Incorrect. The files would need an ESP to force the game to recognize their existence. Otherwise the game will use only the files in the loose folders and the original Oblivion BSAs. *Quick bit of info on how BSA loading works: In order to get the game to recognize files in BSAs you need to have the BSA named in a way that matches an active ESP file. For the below example we will have a minimal Load Order of only Oblivion.esm, MyMod.esp, and OtherMod.esp. That's it. Example: I have a mod called MyMod.esp that uses a BSA that I've also named MyMod.bsa. With this the files in the archive are recognized and used in game. However if I rename the BSA to TEST.bsa the files will not be loaded in game. I could also remove the MyMod.esp and rename the BSA to OtherMod.bsa and the files would load, since there is a mod in my active LO with that name. Additional note: The names of BSAs don't have to exactly match the ESP. You can have additional descriptive information after the name that matches the ESP. Example: Using the same LO and mods as above; I could have MyMod.esp active in my LO and rename the BSA to MyMod - Weapons Textures and Meshes.bsa and it would load correctly. This is because the first part of the BSA name exactly matches an active ESP. However you cannot flip that around. i.e. Weapons Textures and Meshes - MyMod.bsa would not properly load. And there you have it, a quick look at how BSAs are loaded.

No, that's not how you properly build the patch, Moonsun. If you only select the merge patch option you will miss many many benefits and compatibility "fixes" from the other options. That's what Bash Tags are for. They aren't just there for no reason, they are tagged for specific causes to alleviate issues and ensure the mod(s) function properly. Adam9122: You are still not quite getting it... In the box on the right you can select each individual option you want to use. You don't have to select everything on the right, it's optional. The reason the names of items have changed is because you have selected that specific tweak. Again you need to actually read the descriptions for each option you are selecting, and obviously you are still not doing that. You're just randomly and blindly clicking around hoping for the best, and that's not going to get you very far as you've noticed. I suggest you actually take the time, maybe 10-15 minutes tops, to read and understand what each option in the Bashed Patch does. When you mouse over them a description is listed. In the ReadMe that's included in the archive you downloaded there is even more in-depth information about all of the Bashed Patch options. I suggest you take the time to read it also. Until you decide to pay attention and read some information you will continue to experience these "issues". I think this was already linked but here it is again. You would greatly benefit from reading it. Wrye Bash Pictorial Guide for Newbies - by alt3rn1ty Good luck.

If both of you keep fueling each other in saying just how bad and dated, and that it's impossible to install FCOM, then yes you've convinced yourself of this and you will not succeed. However if you look at the Official FCOM Thread, that I've linked multiple times in both of your topics, then you will have a much better chance of success. This is where the updated information resides, and it does indeed instruct you to rename certain files/BSAs. Many people have a full, completely functional, FCOM setup because they put the time in and didn't give up. Like I've said before, it's not an easy installation and yes some of the information is dated and confusing. Precisely why this is not a "beginner" friendly mod. That's why you always use the most recent Official FCOM Thread for information and advice, since that's where the authors and team are active. I've provided tons of information in the other thread, thwap's thread, and if you take the time to read it and understand it you chance of success greatly increases. Good luck to you both.

@FrozenGalen: You need to reinstall. Copying to a new location does not change registry entries that are tied to Oblivion. Follow Bben's guide I linked earlier. Sure there is. I linked the most recent and complete thread above. It was updated just a few days ago. The FCOM Team are always active in that thread at BethSoft and willing to assist folks, as long as they are willing to help themselves. I'm not saying it's the best, or even 100% complete, but the information is there. Yes, some of the information is confusing, and spread out a bit, but remember, you are installing the four major overhauls at once. These mods in themselves can be complex to install with the multiple options available, much less trying to combine them all to work in unison. This is precisely why this mod is not recommended for newcomers. This is precisely why you should have prior knowledge of all the utilities and other basic mod functions and such before trying to tackle this beast known as FCOM.

Select each option, and each file on the right, individually, rebuilding the patch and testing the game after each. Once you select an option in the Bashed Patch and the game no longer loads then you know that's the cause. Post exactly what option is causing the crash for further information. *Side note: It does not matter one bit that you have the STEAM version. If you properly install everything, OBSE included, it will function correctly and mods will properly detect that you have OBSE installed. You can launch Oblivion from your STEAM library and OBSE automatically hooks in, when properly installed. So if a mod said it couldn't detect OBSE then indeed you don't have OBSE properly installed. Check the appropriate documentation for installation instructions.

Or you could check out LHammonds' Oblivion Mod Manager How-To.

Missing Resources | Scroll down to the Pink or Missing Textures Section. You likely need Archive Invalidation. TESIV:POSItive -- Excellent resource site loaded with information for the beginner to advanced user. Other possibilities are improper mod installation and Operating System related problems for Windows Vista and Windows 7 Users. The following does not apply to Windows XP users. Window 7 Related problems, etc... | Are you using Windows 7 or Vista? Did you install Oblivion to the default directory of Program Files? If you answered yes to to both then you are likely experiencing, or will experience problems due to UAC, Windows security. Windows doesn't like it when an application, program, or even the user, attempts to alter files in a protected directory. UAC sees this a potential security threat and treats it as a malicious attack and blocks the action from happening. To prevent this you need to install Oblivion outside the jurisdiction of UAC, to an unprotected directory. A popular and suitable location is <drive letter>:\Games\Oblivion. For information on proper installation I suggest you follow Bben's Reinstall Procedure. If that's not the case then you have either improperly installed the mods, therefor needing to completely uninstall and reinstall the mods properly according to the ReadMe, or you need to activate, or update, Archive Invalidation. You might also want to read the section about Pink or Missing Textures Section. Virtual Store – Win 7 & Vista | Windows is basically ghosting your files since you installed to Program Files. UAC doesn't like it when files are altered in anyway and sees this as a security threat. This is why you should always install Oblivion outside of Program Files to a directory such as <drive letter>:\Games\Oblivion. Windows is storing the files in the VirtualStore, located at <drive letter>:\Users\<username>\AppData\VirtualStore.

There's your problem. You should actually read the descriptions for what each option does and select them accordingly. BOSS also tags your mods appropriately and lists notes in the BOSSlog.html if you actually take the time to read over it. There are some options that require other mods (masters) in order to work. If you select these/this option and you don't have the required mod(s) then you will get a missing master crash, as you are. Solution? Pay attention and Rebuild your Bashed Patch, proper.

As already mentioned, if the "old" texture is still showing in-game then you obviously didn't delete it. It's impossible for it to show up in-game without the texture file being in either A) Data/Textures folder or B) the Oblivion - Textures.bsa or any other mod-added BSA that includes this texture. Or you never had the "old" texture file showing in-game anyway and you've always been using the default textures and just didn't realize it. The reason for this would be the lack of Archive Invalidation, or improper installation. That's the only possibilities for the situation you describe to occur.

Delete pidfile.tmp from your Oblivion/Mopy directory. Every time you open Wrye Bash this file is created to let WB know it's already running to ensure multiple instances of the program cannot be running at the same time. This file is supposed to auto-delete itself when Wrye Bash closes. However when Wrye Bash, or your PC, crashes or isn't closed properly this file can be left behind and will prevent Wrye Bash from starting, since WB thinks it's already running.

That's what we call improper installation of mods. The method of delivery doesn't matter, it's whether or not you place the files in the proper locations.

Searching for hours with no results? Hmm. Google's top three results have plenty of FCOM information. However Dev_Akm's site (result 1 & 2) is dated, but result #3 takes you to the FCOM Convergence page here at TESNexus. From there you have access to multiple files and are linked to the Official Bethsoft Forum Thread. (However the link on the page, not the one I just linked, is to an older thread. The newer thread is on the same forum section though.) So there you go. Start there and read the information in the Official FCOM Thread thoroughly. You'll also want to check out TESIV:POSItive, a great resource site. However you need to realize that FCOM is one of the most complex mod installations out there. It requires you to have general to moderate, even slightly advanced, knowledge of other Oblivion mods and Mod Utilities such as Wrye Bash. I strongly urge you to hold off on FCOM until you familiarize yourself with the basics of Oblivion modding. Start small and walk yourself up to more complex installations and features. Try some basic tweak mods, armor additions/replacers, a weather mod, etc... before you attempt to completely overhaul the entire game. Otherwise you're just asking for trouble and you'll be right back here in a few days complaining about how this or that broke your game or PC. Then you'll post another of the endless "FCOM Help" threads that never seem to disappear, although that's not entirely the fault of the users since the documentation is not consolidated and exactly clear in many aspects. Either way it's completely possible to have a working FCOM setup, many folks do it. However these user's typically have experience and understanding with how Oblivion modding works, and know how to analyze and fix issues if and when they arise. Oh, and please don't install Oblivion (and in this case STEAM) to the default directory of Program Files if you use Vista or Windows 7. You'll save yourself many headaches, trust me. Read the information contained in the spoiler. UAC Related Problems & Information I know this is going to seem like an overload of information but eventually you'll need to know most, if not all, of this stuff to seriously mod your game and have it working properly with minimal conflicts and crashes. Just take it slow and soak up as much information as you can. Don't try to move too quickly, take baby steps and you'll be much more successful in your modding adventures. It's much better to read the information first, and as you're installing mods, then to install mods and have issues then try to dig through mounds of information you're totally unfamiliar with. And remember K.I.S.S. - Keep It Simple, Stupid. Don't neglect the basics. Below are some useful links to helpful resources and utilities,... [/line] Official BethSoft Oblivion Forums -- Exactly what it says. Better Oblivion Sorting Software - BOSS -- Sorts your Load Order for you to help minimize conflicts related to LO positioning of mods. Wrye Bash Download Page -- There is an updated form of the ReadMe included in the Mopy folder in the archive. There is also a slightly dated Online ReadMe. Wrye Bash Pictorial Guide for Newbies -- Great "starter kit" to get your hands dirty with Wrye Bash. Wrye Bash (Quick) Installation Guide/Procedure BAIN Mod Installation Projects -- Comprehensive instructions from beginner to advanced for using BAIN, Wrye Bash's Installer function. BAIN is by far the best method of installation, hands down. OBMM - Oblivion Mod Manager -- A useful utility but not nearly as versitle and necessary as Wrye Bash. Once accustomed to Wrye Bash and BAIN you'll likely ditch OBMM all together. I know I have. I keep OBMM for one single purpose, BSA Extraction and Creation, nothing more. LHammonds OBMM How-To -- Some great information to assist you with OBMM. TES4Edit -- It's actually a handful of utilities compiled into one executable. TES4View, TES4Edit, TES4LODGen, FO3Edit, maybe more. You simply change the name of the executable and bam, different application. Useful for analyzing mods, finding and resolving conflicts, and much more. TES4LODGen -- A One-Click DistantLOD Generator. TES4Edit Training Manual -- It's worded for Fallout 3 but everything applies to Oblivion the same, since they run on the same engine. RefScope -- Excellent utility mod to identify missing resources and produce other useful information that's usually "hidden" to the naked eye. Great when you run across those "Missing Mesh" icons in game and wonder where they are coming from. FormID Finder -- Same type of utility mod as the above mentioned RefScope. Different style interface and not quite as in-depth in certain aspects, but still an excellent utility. Conscribe -- A console logging utility mod to complement the above mentioned utility mods, RefScope and FormID Finder. Information is saved to logs for further review. Contains customization options for general or mod specific logging. TES4Gecko -- Another great utility for cleaning and merging mods, plus more. TESIV:POSItive -- Excellent, excellent, site loaded with information to assist anyone, from beginner to advanced. [/line]Welcome to Oblivion Modding and Good Luck!

You haven't properly and/or fully installed the mod. At the time the download page is currently down so if you didn't download all the necessary files then you're out of luck until the author unlocks the page again. However if you did download all of the necessary files and still have the issue you need to properly install the mod according to the ReadMe provided. Below is some information to assist you with missing textures and much, much more. Missing Textures | Scroll down to the Pink or Missing Textures Section. You likely need Archive Invalidation. TESIV:POSItive -- Excellent resource site loaded with information for the beginner to advanced user.

It's not OBSE causing this. This is such a common issue, and very easily resolved, when people don't read documentation for mods they download and then wonder why they have issues, then falsely accuse other mods for the cause. In this case Oblivion Graphics Extender v2 is where you need to look for your answers. The game is not "freezing". It's initializing the shaders in your shaders folder. Certain shaders take longer to load than others, some upwards of 30-60 seconds depending on various conditions. I use OBGEv2 and it initializes in under 2 seconds with many shaders loaded. However I read the documentation in it's entirety for mods I download. I encourage you to do the same. Head on over to the Official OBGEv2 Thread for complete information. Good luck!

You need to set texture size to large under display options.

You never mentioned what Operating System you're running. Please enlighten us and read the information I've posted below. There are only three reasons for the issue you are experiencing to occur. OS Related interference. i.e. UAC blocking/relocating files on Vista and Windows 7. Improper mod installation. i.e. Missing resources and/or files installed to improper directories. Archive Invalidation is not active and/or updated correctly. See below. That's it. There is no other reason you should experience this issue. Window 7 Related problems, etc... Are you using Windows 7 or Vista? Did you install Oblivion to the default directory of Program Files? If you answered yes to to both then you are likely experiencing, or will experience problems due to UAC, Windows security. Windows doesn't like it when an application, program, or even the user, attempts to alter files in a protected directory. UAC sees this a potential security threat and treats it as a malicious attack and blocks the action from happening. To prevent this you need to install Oblivion outside the jurisdiction of UAC, to an unprotected directory. A popular and suitable location is <drive letter>:\Games\Oblivion. For information on proper installation I suggest you follow Bben's Reinstall Procedure. Virtual Store – Win 7 & Vista | Windows is basically ghosting your files since you installed to Program Files. UAC doesn't like it when files are altered in anyway and sees this as a security threat. This is why you should always install Oblivion outside of Program Files to a directory such as <drive letter>:\Games\Oblivion. Windows is storing the files in the VirtualStore, located at C:\Users\<username>\AppData\VirtualStore. If that's not the case then you have either improperly installed the mods, therefor needing to completely uninstall and reinstall the mods properly according to the ReadMe, or you need to activate, or update, Archive Invalidation. You might also want to read the section about Pink or Missing Textures Section.

The cause for your issue is Deadly Reflex 6 BETA. The body mod was mistakenly included in the upload. You can remove the meshes and such with no ill effects. You need to read the Official Release and Bug Report Thread (mentioned in the ReadMe...) and you'd have known this is a very common report. It's a BETA, you need to treat it as such. There will be more bugs and glitches as you use this mod due to its' BETA status. Some as serious as recurring CTD's and others not so much. If you're not willing to deal with and report such issues you need to remove the mod immediately and revert to an earlier version. Deadly Reflex v5 is near perfect, and about 99% stable, as good as it gets basically. BETA's should only be used by folks willing to deal with bugs and glitches and folks that are experienced enough with Oblivion to report, deal with, and potentially find fixes for such issues.

First, you need to properly Post Your Load Order so that we can actually read it and make use of the information. Next, and related to your problem, disable Autosave completely. It's known to cause crashes of this type and eventually end up with corrupt saves. It's best to always create a new save in a new slot to avoid issues and to have multiple "restore points". You can never have too many backups with Oblivion. To disable Autosave completely edit the following lines in the Oblivion.ini file. The INI is located in Documents\My Games\Oblivion. Just open the INI file in any text editor, such as Notepad, and do a Ctrl + F search to easily find the following lines. Change the value from 1 to 0 as shown below. bSaveOnTravel=0 bSaveOnWait=0 bSaveOnRest=0

Since deactivating your Bashed Patch allows the game to load you know the problem is related to your Bashed Patch. You have obviously imported something that you should not have, or you imported something that requires a master (another mod) that you don't have installed. Resulting in immediate crash. You need to go through the options within the Bashed Patch and select them more carefully to ensure you're properly selecting the correct options. There's plenty of documentation out there that covers this type of information, I suggest you do your research. I'll point you in the right direction however. Start with the Wrye Bash Pictorial Guide for Newbies then head on over to TESIV:POSItive.