TechAngel85

The highlighted part would not apply to MO since it uses a virtual system and the only assets the game would even see are the final ones picked and presented by MO. The game would not even be aware the assets were even there to begin with. Using the game or NMM to manage the assets might be a different story.

Just released I moved this to the wrong thread. Keep discussing and I'll fix it later.

I've moved the relative post to this thread for continued discussion.

I find this curious since STEP uses the HRDLC alongside other mods and anyone with a GeForce 700 series or higher can achieve a rock solid 60FPS in most circumstances. That alone, at face value, seems to oppose what you're saying here. This is getting off topic so I'll split it out if we want to continue this discussion.

A new addon for lava craters hit Nexus and from the shots, it looks really good. Could someone please grab a shot of vanilla and/or STEP and this new addon so we can compare? I've striped my computer down in preparation of my new SSD so I am unable to do it myself.

The thought of making a game with this software is, admittingly, captivating; however, having the skills to do so is another story.

Let me attempt to understand. What do you mean when you say "upscale"? Because to me, "upscale" means the same texture that has simply had it's resolution increased with some blurring and/or sharpening effects applied. These are not "upscaled" according to my definition. Take the first compare. The shape of the tile is different, the color is different, the actual texture used for the wood is different. Not "upscale". Take the last compare...that is 100% different. Yes, there are a few textures in this mod that have very little change, but the majority of it is a complete change, but remaining in a similar style to vanilla.

I always use the HRDLC for my compares since it's just vanilla, but higher res. I consider the HRDLC a basic to have installed regardless of setup. Just like the Unofficial Patch. But comparing them strictly to the base game, they probably are twice the size.

I've checked most of the textures from the mod and they've all been the same size as the HRDLC. I've not looked at the vanilla textures from the base game.

LOOT would only sort the DB addon after the main plugin if the DB addon has the main plugin as a master. Since it doesn't, the order doesn't matter and LOOT sorting is fine.

Updated my post above.

You really are a clueless one aren't you... This is your "go to" for the majority of texture replacers you comment on. Please compare before you say anything that isn't true and may offend the author so I don't have to take time out of my day to correct your view and show everyone that visits this thread that you are indeed, incorrect. The compares above just keep on going, but I thought three would be enough. Although, they are indeed not "twice the vanilla size" if you consider the HRDLC "vanilla content"...which most do. They are the same size as the HRDLC textures.

I'm going to say no on that one and that you'll have to remove it yourself. We're already providing multiple version of the patches and if we keep going as we are, we're going to end up with way too many patch versions that will be far too difficult to manage. The STEP Patches are all handcrafted, so with each version of the patches we're adding man-hours to our workload that is just too much. I think the best solution is for us to create a generic Guide to removing mods from the Patches that users can follow to customize their own versions. Hopefully this will all be replaced by Mator Smash soon anyway.

In the STEP Patches, we are simply carrying forward some records that get overwritten by other mods. These are typically just the text that appear in the books. So removing this mods from the STEP Patches isn't going to break anything.

That's for that info!

Removing this from the STEP Patches shouldn't be too hard. Fairly easy to do with xEdit.

The VideoMemorySizeMb setting tells ENBoost how much system RAM it may use. Contrary to the name, it's not setting anything to do with VRAM.

I'm pretty certain it's referring to RAM not VRAM. Someone corrected me to say it's VRAM recently, but you seem to prove my point of it being RAM. This makes sense because ENBoost uses RAM, not VRAM for its "boosting".

I believe in both and will tell my stories when I'm back in front of my computer.

Best solution is to create a user "portal" page that has all the Guides listed in a nicer format with descriptions included until future projects begin to take fruit.

This might be a good idea and I agree that the way those guides are presented suck. There could, at the very least, be a short description for each guide listed. I'll let s4n and Z chime in.

Marked for Testing.

No, that's how downsampling works but you can disable it since it's not doing anything for you. The red lettering is caused by having something set wrong in the enblocal file. Since you're not using a preset, all those settings should be turned off. Refer to the ENBoost wiki mod page for proper settings.

You already have a thread open. Use that one.

Thanks for the report. It can be safely deleted or ignored as the files are included in the correct path, as well. We'll fix this with the next update.