Just wanted to pop in with a shameless self-commercial here too

As most MMM users are aware of, the enemies you meet are diversified by MMM. One of the effects of this is that their health may be buffed (fortify health?) to be quite a bit above their base health. This is all fine and good, but a side effect of this is that when you start fighting such an enemy, you will for some time not know if you inflict damage or not. The reason is that the Oblivion engine is hardcoded to display the damage bar only when the enemy's current health is below its base health.

E.g. An enemy has Base (normal) health of 200. MMM's diversify script buffs his health to 300. This means that when you fight him, the enemy health bar will not show up until you have battled away 101 of its healt, down to 199, and in the meantime you will not know whether the enemy is immune, whether he has some health recovery effect, or whether you are slowly wounding him down.

Cue my latest mod, http://www.gamesas.com/index.php?/topic/1118552-relz-hud-status-bars/. It lets you add more status bars to the hud, for most things you can think of, and easily control when the bars are visible too - by setting each bar up in "HUD Status Bars.ini"

One of the bars I have set up by default, is made with MMM in mind. It is a bar that is only visible when your current enemy's current health is higher than its base health, and this bar goes down towards empty when the enemy's current health reaches base health - in which the normal health bar takes over. So with this, you get to see how the fight goes against the buffed MMM enemies too.

Thank you very much for this!

Hello! First of all, thanks for this great mod. I wouldn't want to play this game without it, and I can't begin to imagine the work that went into this. So hats off.

Now, I have one question, or rather, I think i have found something wrong with the current version of MMM (of course, it might just be some fluke over here, so i need some help to verify this)

Thing is, it seems that when i run 300_test.esp (FCOM official testing module), it randomly crashes when i try to enter Cell 27 (in the 300_test, this is "cell26") - it seems highly random, sometimes it crash on first try, and sometimes on 10th try, but on average it seems to crash maybe 20% of the times I enter. I have been guessing that it is a random spawn that causes this (but what do I know - just seems logical) - and to test that it wasn't just the testmodule that bugs out sometimes, I coced to Vilverin, used god mod, ran through - I get random crashes in there, seemingly when there should be created new spawns (like if I enter a new area of Vilverin) - and a reload, then enter same place, all is fine, the next - maybe not. etc. Random there too.

I also looked in the CS at the "300_test.esp" I find that in Cell 27 (test300cell26) there spawns 9x of "LL1UndeadBones100" - a leveled list that seems to contain *alot* of different spawns with FCOM installed, which could maybe explain why the crash is so random (but still persistent). Also, I looked where this spawn point is used in game, and sure enough, Vilverin is one of thoose places. So I think it's indeed a spawned creature or such a thing that cause the crash (please correct me if this might not be the case).

So why do I bring this *here*? Well becouse after disabling all of my mods one by one (I thought some may conflict with FCOM etc), the problem remained, so i decided I would just reinstall the game but that i would first find out what part of FCOM that caused this, so i started to dismantle FCOM, removing mods one by one - I ended up, lastly, to use (only) the standalone version of MMM, and the crash still persisted. If MMM is removed, and I am reduced to vanilla spawns, the problem is solved. I re-add MMM properly, problem comes back, but rest of the MMM works *perfect*. I don't want to say that it is MMM that is causing this, but this is where my trail ends, unfortunetly (for me).

So how would I go about this? can someone else test to coc 300testcell26 and see if this is reproducable maybe? or, if I knew how to spawn MMM's creatures one by one, that exists in LL1UndeadBones100, then I could probably pinpoint this also, but I don't know how to do this...

or maybe this is a known problem?

Some extra info:
- It only seems to happen when i am level 13, but this may be some placebo effect, I don't know. For safety, I always "player.setlevel 13" before testing, and it is reproducible every time.

- All other cells seems fine, but I havent tested them as extensively, I only noticed this crash at Cell 27 at level 13 by chance, and since then i have focused on it (but when cocing around, only thing that has ever crashed is Cell 27).

- Cell 27 is working properly when I enter it without crash, and the spawns in there are mostly undead (and some single monster from other factions, sometimes, which they will beat to death)

- Overall, MMM works. The crash is also persistent with both many optional MMM plugins, or no optional MMM plugins at all (just using the normal esm/esp)

- When the crash happens, it always happen at the exact time the loading bar *should* start to move. Like you see the bar at standstill at the beginning for 0.5 - 1 second, then either it loads, or it crashes without the bar budging. I don't know what this means, but it is persistent.

Well, i tried to include as much information as I possible could. I hope someone has an idea about this any advice is appreciated! thanks again.

when testing presistent crashes, always try to turn off AI Processing, Combat AI and Script from the console to help narrow things down:
TAI
TCAI
TSCR

Also, if the crash is an instant CTD it could be a faulty mesh.

At least these two causes instant CTD for me, they are both part of the leveled creature lists for Cell 27:
0x001BC8 UndeadLegionKnight
0x003535 UndeadLegionBerserker3

That is alot of creatures that could be spawning at lvl 13 from that leveledlist since it draws from so many, but, luckly H20Dk has hopefully narrowed them down . Those from the AMMUndeadSpecial List and in particular the Undead Race at lvl 12 or higher.



This could be the problem with them, and the only thing that I can think of with the current bsa that everyone is using.

The UndeadLegionKnight and LegionBerserker are the Undead Race and they are missing their body textures from Warcry where they came from. In the current Public BSA

So try copying these textures from Warcry download either from the Zip or Extract from the Warcry EV.bsa

\OE\creatures\banshee.dds

and place in texture's directory.

See if that make a difference

===

I will add this into the next version and include the missing texture's for them and will add them to MMMOE Directory. And repoint MMM Undead Races to use that directory instead.

Else it could be faulty meshes or something they are trying to equip that is broken..

Thank you. I will try this at once and post my findings

It was only those 2 from the Leveled Creature List 0x0025BF (and 0x003480) that caused CTD, the other undead in that list worked.

But there are so many sublists in the master list (00034049 0003409C LL1UndeadBones100) that I might have missed some. (Any way to export the lists?)

EDIT: wrong ID

please do



Yeah there are so many that it could be because the LL1UndeadBones refer to either AMMUndead List or LLOUndeadBones which has sublist LLOUndeadNormal or Multiple which then have list themselves and so on down to LK and LCreature List..About four or five levels deep that list is in particular..hard to track down what it could be..

No way to export list that I know of, and what sublist is used by it other than by writing it down themselves..

Right. So heres what I have found. I try to be detailed and please bear with my technical ignorance becouse I am not very experienced with theese things in particular

- Taking the banshee.dds from WarCry ( \OE\creatures\banshee.dds ) and placing it in the Oblivion\Data\Textures folder makes no difference to this problem. Both with, or without it, the spawn (when it does not crash the game) shows up just fine.

- If I spawn 0x001BC8 UndeadLegionKnight I get a crash almost every time. Id say it crashes about ~80% of the times, however, when it works, the creature shows up and behaves just fine. I have not managed to spawn two of theese creatures in the same game.

- If I spawn 0x003535 UndeadLegionBerserker3 I get crashes less frequent yet it is apparent that something is wrong here. Crashes maybe ~30% of the times I try it. If I managed to spawn this creature multiple times, he varies in heads/face and equipment. Some also have no head at all. Weapons i've seen on them includes long green sword, and some flashy enchanted axe.

-When the crash occurs, the console just manages to display the usual "is not an interior cell" then Oblivion CTD. When the crash does not occur, then it displays additionally that a spell has (or has not) been added to this creature.

And further bad news: I saw a recent forum thread where some other guy had exactly this problem at Cell 27, but at lvl 30. So I tested to coc 300testcell26 at level 30 (instead of 13), lo and behold, it can crash as well. In identical fashion as the lvl 13 problem.

Now what? i'll test anything if you ask it. I just want to play this mod as stable as possible

I found a way to export the Leveled Creature lists with http://www.tesnexus.com/downloads/file.php?id=11484

I made a script that splits output into separate html files for each list, uploaded the lists & script http://www.4shared.com/file/pTNVHBxY/MMM.html

EDIT:
Updated the script to support Leveled Item lists
EDIT2:
Changed the output to html

Here is a list of all the creatures\NPCs in the Leveled Creature List 0003409C and it's sub-lists (made another script)
Maybe this can help find the problem

00xxxxxx = Oblivion.esm, 01xxxxxx = Mart's Monster Mod.esm


EDIT: Added min Level

What is the latest version of MMM that's compatible with OOO 1.33?

Thanks

Hey guys, just wanted to report an odd little inconsistency in regards to MMM's wild horses. It seems that geldings have a chance to spawn in herds of wild horses, which doesn't quite make sense to me. Horses obviously can't have that happen in the wild (at least not naturally) and I don't think geldings that escape into the wild would last long in a herd. There's probably someone here who could prove me wrong, though, but I thought I'd mention it anyhow.

While I'm on a horse kick, any chances for foals in the upcoming version?

The ideal situation would be to use the current version of MMM and update your OOO to 1.34. They work wonderfully together and we don't usually recommend older versions of MMM.


I can understand your point of view on the geldings however, since the horse addition is a tribute to Alienslof it is the way it is.

I ran check for errors in TES4Edit on MartsMonsterMod37b3 Public Release 3 plugins and it returned a few errors:
Hope this is helpful.

Errors were found in :[05] Mart's Monster Mod.esm
LVLF - Flags ->
Above errors were found in :LL1GoblinMissile100 [LVLC:00084B34]
Above errors were found in :GRUP Top "LVLC"

Errors were found in :[44] Mart's Monster Mod.esp
LVLF - Flags ->
Above errors were found in :LL1GoblinMissile100 [LVLC:00084B34]
Above errors were found in :GRUP Top "LVLC"

All of MMM components have been cleaned and should not be cleaned again. There are many intentional edits which will show up as errors in TES4Edit, they must be that way in order for all of the possible combination's of MMM to work correctly.

I think this is an actual error.

With an FCOM install only Mart's Monster Mod.esm has the flags for this LVLC set to "0101" ... or in plain text:
LVLF - Flags: Calculate for each item in count,

all the others (Oblivion, Fran, OOO & FCOM) have the flags for this LVLC set to "11" .. or
LVLF - Flags: Calculate from all levels <= player's level, Calculate for each item in count

It could very well be, but since it "seems to" revolves around FCOM it will have to wait for further investigation until real life releases Corepc again.

I Thought this Was his Real Life. :whistling:

Already fixed in the Next Release, Caught that one months ago by the way.






Not like it used to be. A couple of years ago, when that is all that I did, Mod 24 /7 almost. When Oblivion came out and years after.

I do have a REAL Life Job and REAL Life Girlfriend after all and Currently am having some computer problems has well in process of fixing and restoring things.

ROM Revised Oblivion is only compatible with OOO 1.33.

Thanks CorePC, your on the ball. Good luck getting computer problems resolved!

Please READ the ROM Docs you can use the older MMM 3.5.5b5 version with ROM and OOO 1.33, ROM will work OOO 1.34 and MMM 3.7b3 but it was not designed around these updates once again. If you need help with ROM then you need to ask in ROM thread. We do not provide support for ROM.

The creator of ROM doesn't play with MMM so the version I needed isn't mentioned in the manual. I only asked about MMM in this thread, but lilith was wondering why I wanted to use an older version of OOO in the firsst place. In any case, thanks for confirmation on 3.5.5b5.