EssArrBee

I think when we made that, LOOT was much newer and none of us really knew much about it. Now that I look at it, it does make sense to have the same priority.

I don't add those mods because I like to keep the DLC as isolated experiences. I know some of the weapons are common, but there are more than enough vanilla weapons in the mojave. Then throw in all the mods and it's getting crowded. I wouldn't want to see any OWB stuff in the Mojave, no one ever made it out except Elijah and he left his gear behind when he escaped. Sierra Madre is really isolated and most of the stuff their was made for the hotel or by the Ghosts. Each tribe would have different weapons from the next, so the White Legs' stuff shouldn't be in the hands of the Legion even though weapons from Zion making it to the Mojave is the most plausible. I really need to play Lonesome Road again, but some of the weapons are really unique so I wouldn't want to undo that. I meant to on my last playthrough, but moved on to test new stuff. GRA is already done by The Right to Bear Arms. It actually distributes stuff way to much IMO and some of the weapons are placed in spots that are to easy to get to. If you play as much as I do then you remember where the weapons are placed and it makes the weapons less special then just buying the weapons for a ton of caps. As for fast travel stuff, I always forget to test that stuff. I use regular fast travel when testing to save time, so it's something that just slips my mind. One day I'll look into it, but people have reported using Mobile Truck Base with F&L and it didn't cause problems.

it only matters if you have a plugin that has them as masters so they aren't out of order. But, you shouldn't have a mod that does that anyways since the pre-order packs use injected records.

You want to leave all those plugins in your load order that Wrye bash unchecked. Just make sure that you ticked everything in the merge plugin part of the bashed patched menu so they get merged. You can get rid of Hall or Equipment to save some VRAM. I've been thinking of dropping that mod anyways. It's just upscaled vanilla and in some places it isn't even better. That might help with the black stuff, since that is indicative of running out of VRAM.

You should ~180 plugins and the bashed patch should put you under 135. Make sure you allow the bashed patch to disable anything it can merge, they will be green and purple in Wrye Bash.

At the top of all the 'Condition' records is a line that says 'Conditions' right click that line in the custom patch column and select add. Do one for each record that you want to add to the patch. There should be empty 'Condition' records added and you can drag the missing ones on top of the those. It won't be straight across for those type of records.

Take a screen and I can tell you how how to add it with FNVEdit. It probably isn't that hard.

I'd like to make something clear about grass rendering in FO3, since Grant asked and it's not the first time this has come up. FO3 and FNV have some differences and one of them is engine bugs. The grass rendering bug is only in FNV. The INI tweak is still valid in FO3 because the default setting may be to low. Grass rendering in FO3 is tied to the INI setting, but cannot go further than the ugrids setting, or 5x5 cells if you use the default ugrids. 17000 appears to be about right for ugrids of 5 to render grass the furthest it can go, but you do not need NVAC for it to work in FO3. Someone at either Bethesda or Obsidian probably was messing with the engine and created a little hack that limited grass rendering to 3x3 cells and never put it back to normal.

The problem doesn't exist in FO3 like it does in FNV. The grass renders fine and you can use the INI setting to make it further or shorter away from the player. It is limited by the ugrids settings in FO3. For FNV, NVAC ties it to the ugrids settings instead of the 3x3 cells that exists in the game. The funny thing is that the calculations are still being by the engine, so you aren't getting better performance by having the grass render less distance with FNV. I did confirm the Lucky revolver had a texture issue. I may need to play around with the files. I don't know why, but the world model had the correct handle texture with the 357 texture for everything else. The equipped texture had the correct textures, but they were wrapped around the model in a spiral. It was really weird.

Extract the archive, delete fomod folder, 06, 08, and 10. Then you have to copy the contents of the remaining numbered folders into the 00 folder. For 01 only get the ADAM Complete plugins (there are two). Make sure you copy over 07 last. Then go into the 00 folder and pack everything in it to an archive, .7z, .zip, .rar... Then install that with NMM and it will skip the installer and install just the complete ADAM package with the PN patch. I don't have or use NMM and wouldn't know how the fix the installer anyways, so I don't know any other way to install it with NMM.

I know that modgames.net site. I've gotten a few files from there and scanned them with Malwarbytes or Bitdefender without any problems. I haven't used the other one though, but they look way better than some sites I've found. There was an East Asian site I was looking at a while ago and it was way worse, had to jump through hoops on some shady sites for files. I really want to just download all the ones on that site and put them on my Copy so anyone can PM for it.

Done.

Why are you messing with a stable installation of 130 mods if you are in the middle of a playthrough?

You gotta be more specific.

Just make a list of what you think should be it's own page. Not sure that I want to test a lot more weapons when I need to move on to other stuff. If you want to test then out I'm sure the it wouldn't mess up anything in your current playthrough, just copy that profile and add the weapons. I'll look into it later if I get a chance.

I'll take a look at it. I like little mods like that. The old installed didn't add new files it replaced the NexuxClientCLI.exe included in MO. Just install the new MO by overwriting the existing one and it will be fine.

Good idea, I'll pass it along to Z. We have Wrye Bash, MO, and a bunch of other niche support forums for one program, so no reason we can't have one for xEdit. Should probably make it something like TES4/FO3/FNV/TES5Edit Support.

I could have sworn I made a thread like this (well, not as thorough), but I can't find it. Anyways, I remember testing a while back, but real life got way to crazy for me. I'll get back to testing again. I don't even remember what version I was testing, so is there a change log for the experimental versions? Also, I used to run WB through the debug.bat with the Python version. Is that still needed?

The change seemed to indicate that it was more of a update to the functions it listed then adding anything new. 16.5 just corrected a bug that was part of 16.4. Nothing really major about it, but I did notice that my bashed patch generated much faster. That is always welcome when you test as much as I do.

We can also put all the available links on the Wrye Bash wiki pages and you can just link to that so people can see all the places that it is available to download. I was getting the beta versions from your OneDrive or w/e it's called, but it always feels weird bookmarking or link sharing someone else's person storage.

Actually, I do know what TeX is. I just didn't put the LaTeX part together with it. I usually just use Eclipse plugins. I think it's called TeXlipse or BiblaTeX and it's used with something like Pdf4Eclipse. I probably wouldn't do it with this sites pdf version due to the amount of tiny changes I make. The app I use is simple and works well, but I guess I just neglected it since it's easy to forget about.

I used a little command line program called htmltopdf or something along those lines. I did a big reinstall of my drives and OSs a while back and have not updated the pdf in a long time. I should probably get around to that. I've never heard of LaTeX, so I'll check that out.

I mean open the plugin in FNVEdit and then right click the plugin and click Check for Errors. If there are no errors then it would probably merge. You would need to do it with all the plugins. Also, I wouldn't merge the Someguyseries.esm, just leave it be and merge the other stuff if you do that.

I've looked over Puce Moose's mod quite a bit and just never pulled the trigger on it. Parts of that mod are covered by other stuff or I just didn't want to install more stuff. If the plugin limit was even 150, then I'd probably have a bunch more stuff. I do like some of the tweaks, but I forget what they were. I'll add something from that mod one day. I know lots of the fixes in that mod are in YUP, but I just didn't want to have the armor and weapon adjustments and then everything added by armor/weapon mods is out of balance with the vanilla stuff. I may look at it one day.

Those are in STEP Extended. They go a bit far from vanilla, so we didn't include them in STEP Core.