Smooth613

Good to know then. Still I've never had such issues, or any issue for that matter, with ScreenEffects. And I've used it for as long as I can remember with many different mod setups. I guess it just has to be chalked up to one of those odd Oblivion, "Works for some, but not others." issues.

When only 2D objects, such as the UI and menus, are being rendered and not the 3D objects, the world and terrain, that points to insufficient hardware. Please post a DXDIAG. If that's not the case, another possible issue is the Nvidia fog/gray/black screen bug. But before we continue we need to see your DXDIAG to ensure sufficient hardware is being used. You should also include other information such as; Has Oblivion ever worked on this PC? If so, when did it last work? And if it did work in the past, what has changed, exactly and everything, since then? Post a DXDIAG | Please use ["spoiler"]["/spoiler"] tags to enclose the information. XP: Go to Start->run, type “dxdiag” and hit enter. Click the Save All Information button near the bottom right. This will save a Dxdiag.txt in C:\ by default. Then open the dxdiag.txt and copy/paste the information into your post. VISTA/Windows 7: Go to Start->Search, type “dxdiag” and hit enter, click the Save All Information button near the bottom right. This will save a Dxdiag.txt in C:\ by default. Then open the dxdiag.txt and copy/paste the information into your post. EDIT: I just seen Hickory's post but I'm not so sure it's ScreenEffects alone since I've used that mod for a very long time with no such issues. By all means try removing it and see if the problem resolves. If not, then follow through with the information I have posted. Also I think if it was related to ScreenEffects then the bug would happen all the time, including the tutorial dungeon. However it's very common for people to be able to progress through the tutorial dungeon with insufficient video hardware and encounter issues immediately upon entering the wilderness.

BOSS does not sort Better Cities to the middle of the Load Order. Better Cities has it's own group in the masterlist and it's one of the very last groups in the masterlist, aside from some tweaks, filters, and patches. So if Better Cities is anywhere but near the end of your LO BOSS is being blocked from properly executing, or you have a very dated masterlist. The latter is not likely since for at least the past 8-10 months that I can recall, probably longer, BC has been at the end of the LO. As for the former, it's possible you have Lock Times on in Wrye Bash, or something else such as UAC (Windows Security) is blocking BOSS from functioning properly.

This boils down to an installation error, or mod conflict. The scripts in All Natural are not faulty and work just fine for many thousands of users. If you're experiencing errors then it's something on your end, not the fault of the mod. I would suggest you double check your installation and disable any other mods while testing. The symptoms you describe would lead one to believe you have not properly imported the cells in your Bashed Patch. That's the most probable cause.

Oh I'm not upset, I was only sharing some information. :wink:

The installation order in BAIN works the exact same as a Load Order, the last package "wins", or overwrites previous packages. So if you want Mod A to overwrite Mod B you would install Mod A below Mod B. Example below. 1)Mod A 2)Mod B 3)Mod C With the above order if any files are shared, or conflict, the ones in Mod C "win". 1)Mod B 2)Mod A 3)Mod C Again Mod C wins overall but this time A wins over B but loses to C. 1)Mod B 2)Mod C 3)Mod A This example, Mod A wins overall and C over B. That's the basic concept of BAIN and an Installation Order. Installation Order works exactly the same as Load Order, the last one wins. If you've already installed mods and need to shuffle them around you can do that too. Then just use the Anneal function to correct any underrides/overrides. You really should read the Wrye Bash Pictorial Guide for Newbies, as the basics of this is covered, and then some.

I'm just telling you the only possibilities for this to happen. From there you can do what you wish. However it is always advised to install Oblivion outside of Program Files due to the many complications UAC presents. If you don't want to take my word for it just search around this forum, and others, and you'll see hundreds, probably thousands, of reports regarding this issue. If it's not a security issue then you're not properly installing the mod and its' resources, simple as that. But you can never be 100% sure since you have Oblivion in a protected directory.

Improper or incomplete installation is the only possibility unless you have outside interference from UAC, Windows security. That's the only possibilities here. Read on for more information. 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. Another great resource is Tomlong's site, TESIV:POSItive. She has included information on nearly every aspect of Oblivion you might need help or just be curious about. It has information to suite anyone from beginner to advanced. I urge everyone to bookmark this site and soak up as much information as you possibly can.

You're missing resources, particularly meshes. That's what the <!> means. You need to properly install the mod and ensure you have all of the necessary resource files according to the ReadMe. Since you say you only replaced the ESP file and nothing more, that likely explains it. You need to install all of the files for version 1.34 and any prerequisites required.

It has nothing to do with a lack of faith, or confidence, or anything of the sort. It's more to do with, no reason to reinvent the wheel type thing. That's all. Who knows, maybe the MERP team did exactly what you're describing.

You would have a much better chance at receiving proper help by posting in the Official Pluggy Thread.

The only thing I have to offer to this thread is you should avoid such mod compilations such as TCOM or any other similar packs. They often include mods that they do not have permission to redistribute and also contain outdated versions of said mods. I've heard TCOM mentioned before and I'm 99% certain it contains at least a handful of mods that the uploader was not given permission to redistribute. You should always download and install mods on your own, not in compilation packs, and do so slowly to avoid and remedy as many conflicts as possible.

Try setting your texture setting to large under video options. Similar anomalies have happened under certain circumstances with LOD textures when set to anything but large.

I take it you're trying to do something like THIS? Might want to talk to the MERP folks and see if they'd be willing to share some insight on how this was accomplished.

Oh, that launcher, I was under the impression you were using the supplied OBSE loader. I've never used any additional launcher for OBSE since it's not needed. I would start by ruling those out as a possibility for failure. You don't need them. If OBGE is still not creating logs or the INI it's not properly initializing. As mentioned previously the reasons for this happening, or not happening, are: Improperly installed OBGE. Improperly installed or improper version of OBSE. Not launching Oblivion properly via OBSE Loader. UAC interfering due to your installation location. Since you're running Windows XP, UAC is not an issue, you can rule that out.

The Official Patches and such are still available from the Official Site, however they're a little more "hidden" than they used to be. I'm not sure why you'd be receiving the message you are unless you haven't updated your game to the latest patch. What version do you have, and where did you purchase it? Retail? Steam? Direct2Drive? Where? I would link you directly to the patches but my ISP is being retarded right now and I'm tethering through my Android to my home PC to access the internet. It works, just at 40kb/s which is a little lackluster for data heavy sites.

Oblivion's default Combat AI setting is 10 characters, PC or NPC. So if you exceed a total of 10 combatants then you will experience issues. However there is a tweak in Wrye Bash that allows you to increase or decrease the Combat AI characters. That could help alleviate some of your issues. As mentioned by Hickory you should take the time to learn Wrye Bash as it's much more useful than OBMM. OBMM is basically useless and should be tossed out the window. Currently it has one function that is useful, BSA extraction. Even that feature can be achieved via other applications such as BSA Commander though.

Are you using a save file that has had Streamline used with it before? If so, unless you've clean saved without Streamline, it will not initialize again upon start-up, since it's already initialized. Try pressing Ctrl-Home and see if the Streamline menu comes up in-game. If so Streamline is already running. You can then sync it with your current INI by going into the Special Actions section of the Streamline Menu and select the Sync with INI option, or similarly named option. Other than that I'd have to go with improper installation or some other issue such as UAC interference. Where did you reinstall Oblivion to? What directory? That's all I can think of since I've never had a problem with Streamline and have used it on many characters across multiple installations. Streamline is LO independent, meaning it doesn't matter if it's first, last, or anywhere in between, it works the same. So posting a LO won't get us too far, but it never hurts to PYLO when having issues.

This is the third time in the past handful of days this exact issue has been posted. Not to mention it's covered in the ReadMe for OBGE. A little searching or flipping a page or two wouldn't kill ya, would it? HERE is another thread regarding this issue.

If you alter the setting in the OBGE.ini that you're referring to you're essentially disabling 95% of OBGE functions. The ReadMe mentions this, and also mentions how you should properly fix the issue. It's also possible that the issue is caused by you altering the Oblivion.ini setting recommend in the Deadly Reflex 6 ReadMe for fNearDistance=. Also, if you don't have an OBGE.ini then something is wrong anyway. Upon OBGE's first initialization it creates the INI file automatically. If it's not doing this then you have not properly installed OBGE or OBSE is not functioning correctly. Or you are having Read/Write errors that could be the cause of UAC, depending on your installation directory for Oblivion. If you installed Oblivion to the default directory of Program Files and use Windows Vista or Windows 7 then it's very likely your issues are due to UAC. You need to reinstall to a directory that's not under the jurisdiction of UAC, such as <drive letter>:\Games\Oblivion.

Posting Your Load Order would be a good start to help identify the problem, don't ya think? My first guess, without seeing a LO, would be WarCry. Or you could always use FormID Finder or RefScope on the door to find out which mod it's coming from. Either way you should PYLO.

The only accurate answer to this question is; "Try it and find out". No one can really answer performance questions such as this due to the many different hardware, software, and driver configurations available for each different user.

Depending on your graphics card and what type of depth buffer (z-buffer) it uses you may need to use the RAWZ.fx fix, and enable it via the OBGE.ini. This is mentioned in the OBGE ReadMe, along with what xchargerfanx just mentioned. Also since you're not getting an OBGE.ini and the OBGE.log is empty that indicates OBGE is not properly installed or OBSE is not functioning correctly, or is not up to the proper version. You should be running OBSE 19b. Also, why are you using the OBSE 1.7 launcher with OBSE 1.9? That makes no sense. You also need to make sure you're using OBSE 19b, as it includes some rather serious bug fixes over 19. Always use the updated files in the archive you download. There have been so many changes made from v17 to v19 it's likely that the launcher has been changed also. The launcher version changes every time the .dll files get updated so one must assume the launcher is updated as well to match the current version. It's possible the launcher is exactly the same and they only change the version number, but why even take that chance?

As already mentioned, reinstalling the game will do nothing to fix issues such as the A-Bomb (Animation Bug) or any other issue "trapped" within the save file. You already have Wrye Bash installed so you have no use for the mod previously mentioned. Just use the Repair A-Bomb function of Wrye Bash and that will take care of the issue, if it is indeed the A-Bomb you are experiencing. And it definitely sounds like symptoms of the A-Bomb. Open Wrye Bash Click Saves Tab Right click your Save File Select Repair A-Bomb Confirm Now try again and report back with the results.

This is precisely why I use, and recommend, the mod Soulgem Magic by TheNiceOne. Just like all of TNO's mods this is another excellent, near essential, mod produced by him. Below is an exert from the ReadMe covering the issues you depict in this thread. [/line]=== Waste control But there is more. One problematic facet of vanilla soulgems is that if you're not careful, your empty grand soulgem may suddenly be filled by a petty soul. With Soulgem Magic, this is no longer any problem, and how it solves it is dependent on your ini settings, specifically the "soulgemMode" setting. Set soulgemMode to a value between 0 and 4, and the value, controls how well a soul must match the soulgem to not fall right through it. Normally, if the only empty soulgem you have is a grand one when you slaughter a rat, the grand soulgem gets wasted with a petty soul. With the soulgem waste control feature, you can set up the amount of waste allowed (0-4). With 0 waste, a soulgem will only hold souls equal to its capacity. With waste 1, a soulgem will only hold souls equal to, or one less than its capacity, etc., and with waste 4 (or higher), there are no restrictions. Ex: Set soulgemMode to 1, and your grand soulgem may accept grand or greater souls, but any soul of a lesser type will fall thtough the soulgem. You will get the normal "You have captured a soulgem" message, but the soulgem will immediately empty itself again.