Yup, same problem as with others; sometimes it doesn't give the error like that. But yeah, same problem. We're working on it.

Ooahh! I've gotten DR6 to work on a second computer. Somebody download this ( http://www.filesavr.com/SAPKRU30EKJN3SE ) and omod/bain it or copy-paste it into your main gamesas/Oblivion folder. Then omod/bain install DR6. Everything should work. I'll also mention I have not included drop lit torches. So for all intents and purposes deactivate it if you have it installed when you try this.

@TheNiceOne:

Thanks!

To be honest I haven't been able to achieve the effect yet. I haven't played extensively yet because of the bugs, and when I tried to achieve it I noticed that bashing with an Iron Longsword (vanilla) caused the same crash as throwing. Odd.

Can it be logical that spatter cause the crashes?

drsplatter only causes the crash on save (after getting splatter on your screen) as far as I know.

can someone add the timed block 250% damage ESP play it in game once to check its working, and then remove it and check in game again and see if the timed block still reduces your block rating while holding block? i need to know if its only a problem with my game or if it happens to anyone who uses the esp.

For those having the "Crash on Throw with certain weapons" bug you may want to check my post in the other thread. Apparently the problems is associated with NIFSE since I can throw weapons, that previously crashed my game, successfully with NIFScript. I'm off to do further testing on this. So far I have successfully thrown the Witsplitter and Glass Dagger multiple times successfully under NIFScript. I'll report back in a bit with more info.

As far as the "Crash on Save" bug. Yes it's related to having the DRSplatter.esp active and performing a critical kill that splatters your screen. I crash on save every single time after any Splatter hits the screen. So for now I have to deactivate it.

This is the first time ever to quote myself but I didn't see any question answered and (so far any issue fixed),
and beside noticed one more issue: when open and close the menu, there is a 4-5 seconds lag between closing the menu and gaining control 9f my character who remains immobile and inert regardless what keys I press or how many times.
Am on Darn UI 1.3.2 if this it relevant

This is inaccurate: removing NifSE will prevent crashes, but adding NifScript doesn't really do anything, and while the throw will work, the mesh will look wrong on the killed NPC (it'll appear, sheathed, in their hand, IIRC) because the NifSE functions required to fix that don't get called.

The momentum and unpredictability concepts are pure genius. Finally a solution to the "repeat the most powerful attack" syndrome that's plaguing so many games!
Thanks a lot for all your efforts SkyCaptain, can't wait to find some time to try DR6.

I′m personally confirming two bugs, just for clarity.


First is the crash with DrSplatter on save - I never catched that one as I never apparently saved when testing individual features, and when playtesting my low level char had maybe one or two criticals and I had other CTD problem with Cobl′s Power Exhaustion.

Second is the crazy high magic critical chance - you may not notice it with spells, as the damage threshold requires (by default) at least 30% damage before it even calculates the chance. With an enchanted weapon, the damage from spell PLUS the damage from weapon make it easier to cross the threshold even with very first strike, so the bug triggers.

The bug is idiotic - the chance formula is missing a divide by 100. So the chance is 100 times bigger than it should be. Thanks to the multiplier in the INI, you can easily fix this yourself temporarily - just change the default "magicCriticalMult" in the INI from 1 to 0.01, to comply with the 100 times larger-than-intended magic critical chance.



ps. I′m posting this in both threads, but after the release thread reaches its limit we are switching to one thread only - two threads was a temporary solution, as I didn′t have the time to involve Klaus in making the release thread as I was meant to, and he needed a place to manage the bug collecting, so he created this extra thread.

As a side note, I know I haven′t posted much - I′m testing stuff on the background, I′m reading the threads but as I have been busy I have been focusing on the testing and slowly checking out the reported bugs.

does this also apply to marksman right under it? "arrowcriticalmult"

how do i fix the first person camera issue? every now and then my first person camera sticks too far to the left. im not sure what causes it, but reloading seems to reset the camera. i can see my character's first person body on the right side of the screen. i've tried changing the fneardistance already.

Correct. I went back and clarified that somewhere, or so I thought. But this cross-posting between the two threads is confusing and I lose track sometimes. Currently I'm playing DR 6 without NIFSE or NIFScript and everything is fine, except for the few anomalies posted above.

That sounds like you have some normal 1st person animations installed, or some mod that uses idles made for normal 1st person view?

But unless you can track down the exact cause, it′s hard to say much more, than it sounds like an animation conflict.

Actually the mod is rather stable and well going for me BUT i have an issue...
Whenever i impale someone, the screen goes dark for 3 seconds, and then fades away to "normal" view...
And on a side note, new thread time

Do you have OGE? That′s the moment when you should have blood on your screen. That, or you don′t have the textures properly installed. Or, some some reason your setup hates the textures...are you using some other texture setting than large?

But, for now, disable DrSplatter,esp, or you most likely get a crash on save after you have the blood on screen effect. I don′t know what′s causing this, I have asked shadeMe for help as I don′t know anything about OGE shader code.

Ah, lol, some gremlins sabotaged my unpacker Will try to shed some blood now :]

I know this may seem like a bit unrelevant, but for me this is an important fix to the game.

I made this small script that prevents the NPCs from hitting you THROUGH each other. This is something that has been irritating me to no limit since I started playing Oblivion - you often get constantly staggered just because all the enemies can hit you at the same time, even though you are trying to strategically position yourself so that only one of them could attack you.


If people have interest in this, I would like to include it in DR, inside the Combat Moves esp - I could always have an INI switch for it. Since it requires some NPC looping, it would be more efficient to have it where DR does that anyways, rather than having a separate esp doing that too.


EDIT: I also made another script that stops any actor′s attack if he himself gets hit by a powerattack. This is another thing that has bothered me - you skillfully exploit the moment the NPC is attacking, cutting him deep when his defense is open, only to have no effect at all, the NPC continues to attack like nothing happened and you gain nothing for timing the attack like that.

The NCP is not forced to stagger or anything, the attack just stops / is inefficient. This holds for the player too, though.

When can the masses have it? :hubbahubba:

Oh yes man, please do include! No more goblin chain staggers in a corridor, hooray!

I can upload the temporary separate esps if you want to test them?

Come to think of it, they COULD be separate as well - the one requiring looping doesn′t need to run every frame, more like once every 0.5s, so the effect is processing wise very low - especially since while in combat there′s no looping, and there′s not much script anyways.

I just tested it, and it works very well - it′s accurate as well, so it′s hard to use the NPCs to block each other out. I′ll upload to a temporary host, so you can test it out if you want to.

I'd like a separate esp for these - I'd test with the Duke mods.

Merged mod plz

Also i found a peculiar bug, dunno if DR has anything to do with it...

NPCs that are meant to be "tame" or that should yield automatically won't do it sometimes. That happened with the Gray Prince (finished his quest and had to pummel him nevertheless...) and the Blade examiner from Choices and Consequences (he should yield after owning him, instead he wants to rip my intestines)...