NinjaBob2312

Has anyone been brave enough to download and try this mod?

Necromancing my own thread since I still hope one day to see this ported.

Been a couple of days since I posted this, I hope the title of the thread didn't scare people away. It is literally what the creator calls the weapon I'd like to see ported over.

I don't usually make requests, in fact this is the first time I've ever done so. There was a mod in new vegas: http://www.nexusmods.com/newvegas/mods/38762/? The author states he doesn't care if anyone uses his stuff. I'd love to see this ported into Fallout 4. Doing such is completely outside of my skill set, and with my work schedule I don't hardly have the time to game, much less learn how to do something like what I'm asking. In short, I'd just like to see someone get it working in Fallout 4. Thanks for your consideration guys.

Dude, you loaded links to a private album. Can't say much to help you when I can't see the images.

I was having a similar problem, I wound up opening Fallout.ini and changing the uGridsToLoad line from =5 to =11 and that fixed the texture and pop in problem. On the other hand, that means that everything loads up farther away than it normally would, so sometimes you'll have fights that you're supposed to watch playing out in the distance over a hill where you can't see see them, or just general system instability because apparently you aren't supposed to do that with this game.

Anything like this thread? http://www.thenexusforums.com/index.php?/topic/390357-texture-glitch-weird/

Problem is persisting, and the gridstoload setting change has created so much instability that my client crashes on average at least twice an hour and sometimes as much as every five to ten minutes. Game breaking mates.

FOMM has an auto-sort function on it that works fairly well. It's not perfect, but it's a good place to start. Generally you want your falloutNV.esm to be first, followed by your DLC.esm's. After that I'd have things that modify the way the game works, and then weapon additions and texture packs last. edit: From looking at your load order, I don't think there would be a problem except perhaps some of the older mods you've got in there not working with the new DLC. Honest Hearts has a bad rep for having conflicts.

Purple screen is odd, do you notice it with any other 3d applications?

I noticed this with GECK when I first used it, but waiting for a few minutes allowed the program to finish working and close. However, since 2GB is a fairly low amount of ram to be using these days it is possible that all or most of it is being used to load up the FalloutNV.esm file, whatever mod you are working on, plus all the windows 7 services which eat up around 500mb of memory just on their own merit. I would honestly suggest that you just try being patient with it, remember that it's development software and it has a lot of loose ends to tie up. If you're endprocessing it from the task manager after saving changes, you might even corrupt your NV install. I really have to suggest having some patience with it.

Can you kindly post what you did to fix it so those of us who are also encountering this can learn from it?

Using an Nvidia 275 GTX, latest drivers already installed. I've also got 8GB of DDR2, and a Core 2 Quad Q8200 processor. I can post a directX file for you if you want. Edit: I'm almost completely sure that the reason I'm having instability is because I had to crank up my uGridsToLoad setting in Fallout.ini to get the kind of graphics that I want.

All settings are set in the launcher, and then additional settings adjusted in the fallout.ini file before launch.

Although I am pretty sure that this is the wrong forum for something like this.

Sounds cool, as I generally play a sniper it would be fun to see this in practice.

Every possible option is cranked up to the max, including modifing the .ini files to raise the loaded distance even further. Also, I play on PC so I don't have a 'start' button, lol.

1. I'm not sure what this mod is, but if you want to get rid of it just unload it from your FOMM. Just uncheck the box on the FOMM screen and it should go away without any further effort. 2. If you can find the form ID's from the mod in the GECK, which you may have to download, you can take the number and swap out the first two for the prefix assigned to that mod in your FOMM. This link may provide you some more information on this subject. http://fallout.wikia.com/wiki/Form_ID.

Generally speaking, most mods go into your C:\......\Steam\steamapps\common\Fallout New Vegas\data folder. Make sure when you unpack the file, usually using software such as winRAR which can be downloaded from http://www.rarlabs.com/ you can look inside the download. Browse through the files until you reach the /data/ folder in the package. If you encounter something such as /textures/ or /meshes/ you've entered the 'data' folder section of the mod. Unpack these files to the /data/ folder and then use the integrated data file manager system in the fallout launcher, or (i recommend) downloading the Fallout Mod Manager at http://newvegasnexus.com/downloads/file.php?id=36901. Ensure that the file is being loaded (there will be a check mark next to it) and then start the game. Your mod should have loaded if you followed these steps correctly. Of course, all mods are different and some are packaged using different compression software such as .rar or .7z. However, winRAR can handle any of these types, and you should be alright. Feel free to PM me if you need more help. ...I realize this sounds complicated but it's really not that hard after some practice.

I've seen comparable screenshots on other websites like IGN and such, but nobody ever came up with a solution for this. As I said, this didn't start until the 1.3 patch came out so perhaps the answer is in those details. I'm not a programmer, I'm just a soldier with some hardware and moderate technical knowledge. I can help find the problem but I can't fix it myself if this makes any sense. So while I don't usually play this card, as a veteran of foreign wars can anyone help me fix this?

Unzoomed.

This is a scoped in shot of another area where I've noticed this bug. This is the 'brightly illuminated' Freeside sign that is near the Crimson Caravan and Gun Runner's areas. Following post has the non-zoomed image.

When I first installed this game about a week after release, I was one of the golden children lucky enough to have a nearly bug free experience. However, since the release of the 1.03 patch I've encountered this odd texture issue which doesn't seem to make any logical sense. Distant textures are being displayed on close objects, npcs such as the Legion members guarding the boat crossing used to be snipable from the "snipers nest" location but now they don't even render. I took this screenshot to illustrate one place I encountered this bug. So you all know in advance, I've already done a complete wipe, fresh install of new vegas including deleting my save games, mods, and ini files that are carried over from an uninstall. This is taken down a night vision scope on a varmit rifle from the cliffs just in front of the radio trailer about a click away from Primm. As you can see in the picture, the textures on the building in the foreground are extremely low res, the game hasn't even loaded the geometry for the structure right, it's just a cube with low res slime textures on it. Also, the giant (freaking) bison on top of the bison steve casino is missing, and you can see the top of the 'casino' sign over the door as the half circle visible over the top of the building in the foreground. If you approach Primm, you can get the textures to load and the bison sign to materialize, but doing so requires getting ridiculously close to the city. I've also noticed a comparable bug with the large light up sign in freeside which I will post if anyone wants to see it. Edit: I'm running this game on max settings. The only thing that seems to come close to rectifying the issue is to crank up the uGridsToLoad setting in Fallout.ini. I had to set it up to a 9 to make it acceptable, but as most people know who have ever screwed with this particular setting, doing anything to it is a recipe for constant crashes for no apparent reason.

Tried it, same issue. I've taken to punching the quicksave in combat when I notice the bad guys not shooting back and then quickloading. It's immersion breaking but not quite as bad as this quasi-godmode I've managed to somehow engineer here.