Followed the Complete v055 version instruction. But when I rebuild the bashed file with Wrye Bash, it said there's an error on morrwind_ob.esm. The game loaded without any problem and was able to play. Any idea how to fix that error? Thanks.
Thanks for your reply.
Try turning off distant land.
Try turning off distant land.
thermador wrote:Try turning
thermadorNope, didn't make any difference. Turning off distant land/tree/water did not change anything. Now I'm lost what to do. I'm still at Seyda Neen and I can't even complete Fargoth's hidden gold quest due to crashes. Btw, do I still need Lost Spire-Morroblvion patch if I have Lost Spire in my game (v055)?Try turning off distant land.
I had the same issue, more or
I had the same issue, more or less and turning distant stuff off didn't help. Somehow it seems that Morrowind part of the game is pretty "heavy" on resource useage part.
Anyway, I did some tweaks to the oblivion.ini file and installed Stremline and it helped a lot (although I have a small issue with all water turning pink for some reason, but I believe it's due to me messing around with oblivion.ini). Now I maybe CTD'ed once or twice (and that's due to "Crossbows of Cyrodiil" mod) after CTD'ing after about 5 minutes of gameplay. Got to add though my Oblivion is not so heavily modded (about 30 mods active tops) so my problems might be different than yours.
Still got to figure out how to fix that pink water before I get used to it lol
If you have >2Gb RAM and Win7
If you have >2Gb RAM and Win7 x64, apply 4Gb patch
4Gb patch was applied a way
Put uGridsToLoad=9 back to 5
Put uGridsToLoad=9 back to 5 and make sure that you have texture size set to "Large" in oblivion.
It might not work,but worth a try.
doggy
doggyuGridDistantTreeRange=50
uGridDistantCount=40
uGridsToLoad=9
I'd suggest dropping all of these to the half of their value, at least to see if it's more stable. My values are 15/25/5, rest of the settings are more or less the same as yours.
Played around with ini and
The error that the bashed
The error that Wrye bash is talking about has something to do with one of the lute players idle animations, it has existed since version 51 (maybe even farther back, but I've only been using Wrye bash since then.) and prevents the bashed patch from being built properly, however it is easy to fix with TES4Edit. I will tell you now, this may not be the cause of your crashes, but I can confirm that correcting the error using TES4Edit will cause the error on rebuilding your bashed patch to stop appearing. If you do not know how to work TES4Edit, I can use private messages to send you a link to a fixed version of the .ESM.
Can someone post the actual
Can someone post the actual error text? I play Morroblivion since v048 and didn't see any errors in Wrye Bash
doggy, yes, your crashes were probably because of ini edits. Increasing uGridsToLoad is known to cause all sorts of issues.
The only actual error text
The only actual error text is:
Error in Morrowind_Ob.ESM
I found out how to fix it by browsing for similar issues on the forum, I've long since lost the post that helped me solve the problem, but it had something to do with similar issues around a version close to thirty. In the end I ended up filtering the .ESM for errors in TES4Edit and correcting one number in the ID of a lute players idle animation (It was missing a single one), which fixed the error appearing during the bashed patch process.
Yup, like Valtallan said the
The lute music stopping is a
The lute music stopping is a sad limitation of oblivion. I'm not sure of the exact reasons, but interacting with containers and such stops music from playing.
Its not just instrumental
Its not just instrumental music, its ambient sounds like torchfires etc. i found this annoyance on a project im doing for morroblivion. Unfixable short of reverse engineering unfortunately.

It might just be the same
It might just be the same warning that BOSS reports; Morrowind_ob.esm has to load immediately after Oblivion.esm due to the configuration of the mod. I wouldn't worry about it unless you're having problems. Maybe the Wrye Bash documentation can help explain the error?