hxazgalor

On a related note, I don't suppose there's a faster method for troubleshooting mods besides having to test them one by one? I've just about arrived in the vicinity of Novac when the crashes started. My game would just suddenly hang without warning, though environmental sounds and music will still play. I get the feeling that the Willow mod might be the source of the problem, but that's just me speculating. It's because after some interaction with her, whether by conversation or using her utilities in the Pip-Boy, the game tends to crash shortly after. Strangely, before I completed her main quest that allowed me to hire her, I had no trouble with my game; had zero to little crashing. I'll share my load order later today, as I'm not on my laptop.

I've resolved the issue by unchecking all active mods, then manually reactivating them one by one. I did NVCE first before Delilah, so now I no longer have the eyes issue. I'll be sure to look out if it comes back, and with the links you've provided, I should be able to rectify the problem next time I face it. Thank you once more! :D

Thank you, I think I understand now. Essentially I'll need to overwrite the original NVWillow.esp file with the one provided by Dracomies? I'll give it a whirl later and see how that turns out. In the meantime, could you perhaps help me with another issue I'm facing? I just posted it as a new topic re: eye glitches for the companion Delilah. My humble thanks once again!

I had this problem some time ago, and somehow rectified it after reinstalling every mod I was using. It seems to have cropped up again, but is there a way to overcome this problem without needing to reinstall everything? I get the feeling this has something to do with my installing of NV Character Expansion in place of NV Redesigned 3, and this issue happens even when I start a new game. Should I then reinstall NVCR FIRST then Delilah, or the other way around?

What do you mean by "they need to be renamed to match the ESP from the original Willow mods"? Which file would I need to rename in this case?

Here's how the installation process is worded: 1. Install the original Willow file. Its master file and meshes, etc. are needed 2. Drag over the textures to your Data folder. 3. Enable the .esp file. 4. This mod requires New Vegas Redesigned 3 resources. So as you can see, I'm not entirely sure how to proceed with the installation. Plus, I'm using MO for all my mods, so I'm not sure how to properly replicate this via MO.

There's no way to "merge" them, I suppose?

Thank you! I wish there was a faster way to check if it's working as intended. Edit: the patch I'm referring to is included by the author of NV Redesigned 3. It's just that I'm not sure on how I ought to follow his instructions, or how I should install it directly.

I would like to know how to properly install the compatibility patch for NVWillow, as the included instructions were tailored for a manual install and not via MO or any mod manager, or at least it seemed that way to me. I'm not sure if I should merge it with NVWillow, or with NVR3, or if I should install it on its own; and which of the two .esp files should I use? Could someone please help me out with these questions? I would greatly appreciate any assistance.

Thank you for the response. I'll look into it and see if I can't come up with something. But how would I know what shared/conflicting features need to be overridden in order to make the compatibility patch work?

A lot of mod compatibility patches in Nexus Mods seem to no longer be maintained for newer (or later release) versions of existing mods. My concern is that if I use these newer versions, the compatibility patches I currently use would no longer be viable to use. It really sucks, if I must be honest. Plus, any existing ones out there are usually created to enable compatibility with some mods but not some others (i.e. the FOOK-PN Convergence covering only a select number of major FNV mods), or they cater specifically for certain mods and require that all these mods be installed - no more, no less (i.e. the WCP, or Weapon Compatibility Project). Would it be possible if there be members who could look into this and perhaps create new compatibility updates? This would be a great boon to the community, especially where there is a need for these compatibility options for users who use specific mods or don't use all the major, popular mods available at Nexus Mods. Thanks for hearing me out.

2 months and nothing? I'm kinda disappointed :(

Does anyone know if RedHawke is still around or contactable somehow? I've encountered bugs with his Jawa shop mod, where the Baragwin assault blades cannot be upgraded even when they're description says they are, and certain custom crystals cannot be used to modify my Jedis' lightsabers. Has anyone had this issue as well? I don't have BoS installed, btw. I've installed the mod as per RedHawke's instructions (necessary files in modules and override folders). Thank you in advance!

As the title suggests, for some reason I was faced with this problem of the Pip Boy automatically equipping or unequipping a weapon when the cursor hovers over it. As long as the cursor remains there, this will continue to happen on and on and on until I finally moved it away. I did a clean uninstall after facing this problem, so unfortunately I can't show the mod load order I used. If anyone wishes, I can list down the mods I used when the problem arose. Has anyone else had this problem? Is there a fix for this? Many thanks in advance :)

EDITED Strange problem, this one is. Finished Lonesome Road DLC, got myself the cool Riot Armor sets, but decided to give to my companions. Strangely, whenever I crouch and start getting sneaky, my screen suddenly turns sepia. Kinda like the 'sneak sight' effect the helmet has while sneaking, but this has a more pinkish hue. If I repeat switching between sneaking and standing, the brightness ramps up each time to a point where I can barely see anything. Menus and the Pip Boy were OK, though. The only solution so far is to leave the helmet in my inventory at all times, which I'd rather not do. Has anyone else encountered this problem? Can someone help me with this issue? Thanks