Oblivion TES Construction Set – Self-made landscape patch not working

modsthe-elder-scrolls-construction-setthe-elder-scrolls-iv-oblivion

Introduction: I made a very small landscape patch mod to make two different mods compatible.

The Mods:

The compatibility problem:

The landscape changes made by OotD made it so that the large Ayleid tower was unreachable, as it was floating high in the air, which is very bad for immersion, and quest-breaking.

Now using The Elder Scrolls Construction Set, I moved the tower (and other floating things around it) to the ground and it was looking fine in the mod creator.

Now the problem:

After saving my work as a new mod, I added it to the Data folder, I activated it and made sure to place it after all other mods. As I used Wrye Bash, I placed it before the bashed patch at first, rebuild the bashed patch, and started the game.
The game started fine and everything was normal, but when I came to the place that I had altered in the mod creator nothing had changed, and the tower was still floating in the air.
After this I quit the game, made a new safe file, and checked again, but nothing had changed.
Then I moved the mod after the bashed patch, rebuilt the patch, tested again, and it did not work.

Final:

That is it, I have been looking online for good tutorials and people with the same problem, but I can't find anything helpful. If anyone has some good tutorials please post it in a comment, and of course if you have a solution please help me out.

Best Answer

After more research, I have found a partial solution and an alternative workaround. It is not a perfect solution, but it does its job.

Partial solution: First for the partial solution I used this guide, but this was only a partial solution as it only seemed to fix some problems with the landscape, but was not able move the watchtower of the "Fall of the Ayleids" mod.

Alternative workaround: For the alternative workaround I edited the mods individually, this worked, but it is just a workaround. The problem with this workaround is that if I were ever to reinstall the mod, or a new version of the mod were to come out, I would not be able to just apply the previously made patch, but would have to do it again.

For information on editing mods you can take a look at the BethesdaGameStudios Creation Kit tutorial playlist, because, even if this is for Skyrim, it seems the basic functions of the Creation Kit have not changed so much from the previous version.

Related Solutions

TES IV: Oblivion + Nehrim – save game corruption

For the save game bloating (which could be the reason for the crashes), you might want to try this mod:
Clean up by kuertee

Description
Prevents saved-game file-size bloating by cleaning the game of actor and item references that are no longer required. (e.g. inactive references created from dropped items that were picked-up by the player.)

Cleans long-dead actors that may have been corrupted somehow.

Details
The cleaning process used is the game's inherent behaviour of removing items that no longer has any "links" to the game world.

Normally, dead actors and "dynamically created" items that were not picked up by the player will be removed from the world, when the cell they are in resets. (Dynamic items are those created at game-time as opposed to those created in the Construction Set. Examples of these items are: those created by PlaceAtMe, those dropped by the Player, those dropped by dying NPCs: e.g. shields, etc.)

However, there are cases when these actors and dynamically created items will (for some reason or another) stay in the game world forever. And actors not cleaned up by the game properly will never respawn, causing a "broken" game experience. Saved-game bloat is the result of these. And saved-game bloating may be the cause of some game crashes.

To prevent crashes, I'd recommend Streamline's Streampurge feature (memory purging on an intelligent, scheduled basis - can be configured to do a memory purge before a save, which can help with stability; more info here) and Fast Exit 2 by Scanti. You can choose to enable only Streampurge and Streamsave and not the other Streamline features in sl.ini (Streamline's configuration file).

If you are running a 64-bit OS and have 4 GB or more RAM, you might want to try the 4GB EXE Patcher on Oblivion.exe . More info on the Steam forums thread on this link here.

You could also try OSR (Oblivion Stutter Remover):

This plugin makes Oblivion not "stutter" as much, and generally feel smoother or perform better. It prevents or mitigates a number of issues related to stuttering and framerates, and can reduce the frequency of stutter related crashes.

Make sure you set MaximumFPS = 0 in 'sr_Oblivion_Stutter_Remover.ini' to avoid it putting an artificial cap in your framerate. Aside from that, try using it with the default options. If it still crashes, you might want to try to replace the default Oblivion heap (memory manager) with one of OSR's. In 'sr_Oblivion_Stutter_Remover.ini', set bReplaceHeap = 1 and change iHeapAlgorithm to 1, 2 or 5 - read 'sr_Oblivion_Stutter_Remover.txt' for more info and other OSR tweaks that you could try.

Note that Streamline, Clean-up, Fast Exit 2 and OSR requires OBSE (Oblivion Script Extender)

After installing any new mods, make sure to run BOSS (Better Oblivion Sorting Software). BOSS properly sorts the load order of the mods, avoiding crashes and mod conflicts. It also provides a large number of usage notes for many mods, including requirements, incompatibilities, updates and bug warnings.

More info on configuration and mods that can help stabilize and prevent crashes in Oblivion here: http://tescosi.com/wiki/Oblivion/Stabilization_and_Optimization

Minecraft – How to activate the Cheat Mod in Zombes ModPack

You seem to have uncommented some lines that should have remained as comments. "Uncomment to enable mod" actually refers to the line below it ("modCheatEnabled = yes").

Every time there's a blank line, the first line afterwards is a brief description of what the option does and so should remain as a comment.

So, for example, the first couple of lines originally look like this:

# Uncomment to enable mod:
#modCheatEnabled       = yes

You changed it so it looks like this:

Uncomment to enable mod:
modCheatEnabled       = yes

But it should actually look like this:

# Uncomment to enable mod:
modCheatEnabled       = yes

The "modCheatEnabled" line should be the ONLY line you remove a '#' from in the Cheat Mod section of the config. I noticed that several other options (presumably all the options you changed) have been uncommented in the same way. "Toggles Cheat mode on / off", "Show / hide ores", "See through everything nearby..." and all the other lines that look like descriptions should still be commented with a '#' sign in front of them. It's the lines below those comments ("keyCheatShowOres = C", "keyCheatSee = T", etc.) that actually do anything.

Best Answer

Related Solutions

TES IV: Oblivion + Nehrim – save game corruption

Minecraft – How to activate the Cheat Mod in Zombes ModPack

Related Topic