Jump to content

Recommended Posts

Posted

Just want to inform you guys, that I asked the author about using his mod only for his textures, and this is his response.

 

Question:

Hi dDefinder1

 

First I want to start off by saying I have mad respect for this beautiful mod.

However, i am currently in the process to eliminate mods that are script heavy such as yours but would love to continue using your blood textures.

Now my question is: Is this possible?

Would I be able to use this mod without the scripts? and if the answer is yes, how would i go about it?

 

Thanks, and I eagerly await for your reply =-)

 

Author Response:

 

You going to have to delete about 90% of the mod to use the textures that vanilla uses. Delete everything, this includes the bsa and the plugin file.

 

Leave the textures inside the gore folder and the following files.

decalsbloodsplatter01.dds (this file is already included in the vanilla folder)

decalsbloodsplatter01_n.dds

decalsbloodsplatterblend01.dds

decalsbloodsplatterblendaltalpha.dds

screenbloodalpha01opt.dds

screenbloodcolor01opt.dds

 

 

Hope this helps the STEP community for their future endeavors

Posted

Tip for the future.

The Information selection when you right click in MO allow you to see what is overwritten. Assuming ofc. that you extracted the vanilla bsa´s.

But those textures are the only things true enough.

 

However its not like the textures are super good compared to the vanilla ones... but worth trying out.

  • 4 months later...
Posted

Is the information in the wiki about the crashes and stuff still true?

 

According to the author, it doesn't seem so clear.

Q: I’ve read somewhere that this mod is “known†to cause CTDs.

When the mod author and a large majority of the EBT users are not experiencing this issue the “known†thing loses its merit. I have gone through a recent 20+ hour playthough with the following mods (https://pastebin.com/mARR2kpV) and have not experience CTD during combat. A deeper test needs to be done to find out if a mod is causing issues rather than just “I disabled this mod for 5 minutes and it stopped CTD.†Other harm can be caused by this besides mods, such as, editing the ini, especially the papyrus or the ugrids settings. Testing under a new game using the COC command is the best way to find out if there is something going on with a certain mod or if its caused a the current save. A lot more is covered in the FAQ below.

- quoted from Nexus.

No idea when was this written though.

Posted

I've actually been running BFS, DSI, and EBT all at once without issue or script lag since the mem patch. I suspect it was a mem allocation issue when all the scripts fired.

 

Sent from my XT907 using Tapatalk

Posted

It would be nice to test it as it is without that patch and update the wiki accordingly I guess.

That should be done before 2.2.8 is released. Whether or not it will be is not up to me atm since I'm out of commission until my rig is built.
Posted

I nominate z, he has been testing most of the mem patch stuff. :p

 

Use Convenient Horses, in the MCM menu there is a script latency tester, you want values between 50 and 100 maybe 150 max during high levels of combat or actors on screen.

Posted

I've actually been running BFS, DSI, and EBT all at once without issue or script lag since the mem patch. I suspect it was a mem allocation issue when all the scripts fired.

 

Sent from my XT907 using Tapatalk

me too. I am running this now in my mega-requiem build just for my own personal entertainment. No crashes on that huge, script/graphics-heavy build as yet (running at uGrids=11 for over 25 hours game time now).

 

So far, so good for EBT (default settings).

Posted

I've actually been running BFS, DSI, and EBT all at once without issue or script lag since the mem patch. I suspect it was a mem allocation issue when all the scripts fired.

 

Sent from my XT907 using Tapatalk

I have run these mods as well + Deadly Combat (more scripting) and several other mods, after the sheson memory patch I have not had a CTD event, with gameplay up to 7 hours straight. I not saying this qualifies as rigorous analysis, but in my experience quite stable together.

 

That's on my i7 4770k (3.5GHz) with 16GB Ram and a GTX670 (2GB) with Realvision ENB .246 Full, ugrids at 7, patched SKSE loader (768/256 memory blocks)/cell stabilizer/safety load in play.

  • 1 month later...
Posted

There is an ini file included in the mod, and regarding adding those settings to Skyrim's inis, Nexus says "You don't need to follow these steps if you used a mod installer. The ini changes are already included."

I am not sure I understand. I see the file in the mod's folder, but I am not sure that MO actually has any such functionality as adding ini entries from extra files to the main ones.

Posted

There is an ini file included in the mod, and regarding adding those settings to Skyrim's inis, Nexus says "You don't need to follow these steps if you used a mod installer. The ini changes are already included."

I am not sure I understand. I see the file in the mod's folder, but I am not sure that MO actually has any such functionality as adding ini entries from extra files to the main ones.

MO probably does pick it up, but v1.1.2 changed the way INI work and I'm not sure that it will not change again. I wouldn't worry about it or just add it in from the INI Editor.

Posted

Can you point me to the discussion about the ini changes? (I don't think reading the changelog is enough to understand it all in this case)

And yes, I thought to add it all manually anyway. However... at least one of the settings has a comment next to it saying it's controlled by the MCM, so I really am not sure what approach to take.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.