AGreatWeight

Brandoman, you need Fallout4.ini, not Fallout4Custom.ini Just load up Fallout4 without NMM being active i.e. straight-up vanilla, and it will be created once the game has initialized. Once you get to the main menu, simply quit the game & the .ini file will have been created.

https://www.nexusmods.com/fallout4/mods/29701

Correcting someone who distorts the truth makes me a fanboy? Riiiiiiight, gotcha. Congrats for using that within the first sixteen words of your response, you don't waste any time do ya? Keep on keeping on with the hate Zanity, it's what makes you S.P.E.C.I.A.L. TM @Reneer :laugh:

That looks like some kind of rendering issue, possibly driver-related (I note that in the last picture, over on the right hand side, the textures haven't loaded correctly for that shack & it's still displaying a mip map instead, this commonly occurs when your system is struggling to stream the texture data into memory) As HadToRegister noted, wth is going on with that entry for the Max filepath? That could well be indicative that whilst extracting the textures from the ba2's, they've somehow got corrupted. What are your system specs? I've not come across any cases of this happening before, and now that your saying that you can't even get into the game... Have you checked your gpu/cpu temperatures? Is F4SE fully updated to match the latest version of FO4? Perhaps it would be wisest to reinstall from scratch (I know that's the last thing you want to do, but if you're unable to pinpoint exactly what is causing this, as long as it's not hardware-related, it might be your only recourse)

Every time you chime in... What you've said above, is factually incorrect and a blatant & intentional misrepresentation to provide some sort of credence to your continuous arguments about bad Bethesda. Todd Howard actually said "I wouldn’t say never, but now that our company is so big, it’s always better to keep stuff internal ... it becomes less likely, but I could never say never. I thought the Obsidian guys did a fabulous job." Link to the interview here for those interested If you're gonna continue to rant and rave and hate on Bethesda, at the very least pull your finger out, get your facts straight, and provide evidence to back up your claims.

I'm just dropping my two cents to say that the OP is incorrect when the made the bold claim that Xbox modders made an attempt at a 1st person camera first. Not true by a long shot. The first attempt for Fallout4 was initially released on Nexus back in November 2015. It was last updated around March 2016 before the author realized that they'd pretty much painted themselves in a corner, due to the way that they'd chosen to impliment it (the mod altered camera values to mimic the look) so development ceased. Not a bad effort all things considered, but buggy & fundamentally flawed https://www.nexusmods.com/fallout4/mods/1944

That's such a subjective question, and comes down to what your individual tastes & preferences are & what kind of atmosphere you want in your game. Perhaps a good start would be for you to look through this image set of mine, it shows off over 15 presets - https://www.nexusmods.com/fallout4/images/71087. I've included direct links to each preset shown on the page. Of course, there are other ENB's that weren't included in that image set, such as PRC (PhotoRealisticCommonwealth), XCinema, Film Workshop, Pilgrim:Dread the Commonwealth - which all come highly recommended.

To disable that from happening, add these line at the end of your Fallout4.ini [Camera] bDisableAutoVanityMode=1

Whilst in-game, pause to open up the menu, go to settings and switch off auto saving, saving on sleep and saving on fast travel. You'll have to remember to manually save your game from there onwards, but that will reduce the number of saves being made. Alternatively, if you want to keep save-files you can simply go into Documents/MyGames/Fallout4/Saves and simply cut/paste them to another drive as back-ups (this also fixes the game attempting to read all the save files when it first boots up to the main menu, so can reduce lag/stutter that sometimes occur when you have a lot of save files stored) That you mention laggy loading screens whilst going into/out of interior locations is somewhat troubling, as the number of save files you have doesn't make a difference here. Make sure the drive that Fallout4 is installed on isn't defragmented, and that it's also got plenty of free space available. Secondly, make sure that you have as few apps running in the background as possible whilst you play (for example, anti-virus/anti-malware software that can hog system resources, or things like Steam overlay etc) Basically, if you don't need it running whilst you're playing Fallout4, close it.

Several months back, I had a similar issue where out of the blue, in-game my view was distorted (similar to how you described above) even when I wasn't in any areas with Rads/Rad Storms. Somestimes it'd happen whilst it was raining (just regular rain, nothing else) The way I fixed it was to switch off the Rad fx, and I also reset the NAC settings. I'm not sure what initially caused it to funk out like that, and it hasn't happened since.

Possible it's the radiation fx from NAC, which can be removed via the NAC main menu

It's likely there's some remnants of the ENB files still residing in your Fallout4 install, looking through your load order you don't appear to have a dof mod (like Dynavision from Gopher, for example) Easiest way to ensure that everything ENB-related is removed is to use this exceedingly handy little tool - https://www.nexusmods.com/fallout4/mods/5347 It's a simple .bat file that you place in your Steam/Steamapps/Common/Fallout4 folder (also works for Reshade/SweetFX folders) Double click it and it'll remove everything. If that doesn't fix it, then it must something else?

Quite likely it should be ok to do that once you've chosen the settings you want to use with them, although can't say for certain as I keep holotapes with mod settings in my inventory at all times during a playthrough. There are two ways you can go about trying to narrow down which mod/s may be the culprit for the issues you're experiencing in-game. One way is to (download and) use FO4Edit, load all your installed mods into it and look for any compatibility issues that it will identify if the mods you're using are conflicting with one another; not sure if you have any familiarity with FO4Edit, if your new to it I highly recommend you do your research & gain some familiarity before using it. Until then, as an alternative you could try the method below. Another way is to click on the plugins tab in NMM (you'll see that all installed mods will show up with a tick next to them & they'll be arranged as per your load order) From the list, click on the tick for half of your mods, say the last 50% (this will disable/deactivate them & the tick will disappear from the small square box) Then load the game and see if the same issues persist, if it does then you've possibly narrowed it down to one of the mods among the 50% that are still activated; now disable half of those ones and repeat the process. Doing this makes it easier to narrow down & hone in on if a particular mod you have installed is the cause of the problem. As your the number of mods you have installed is relatively low, this shouldn't take you too long to do. If you're successful in finding one mod that is causing the issue, completely uninstall it from NMM, then reactivate all your other mods, and test your game once more. An alternative to this that you could try is deactivate/disable every single mod you have installed, load Fallout4 and start a new game to see if the performance issues you mentioned occur. ***Make sure that you don't allow the game to overwrite the save you've loaded whilst you're testing, the easiest way to do that is instead of going to the menu and selecting quit, open the console (via the 'tilde' key) and type qqq then hit enter - this quits the game but doesn't autosave or overwrite the save you're using.*** If you end up going through all your installed mods and still can't identify which one is causing the issue, the only other options available to you would be to go to the mod page for each mod, check the description pages, comments pages, and bug report pages to see if any other users have mentioned similar issues, and if there are fixes available. It would also be worth your while to do so for the 'fixes' you mention that you installed. You didn't say what they were called, so I can't comment as to their usefulness etc. The only mod of that kind that I personally use is the UnofficialFallout4Patch; I highly recommend that you install and use that mod. As a last resort, if nothing else works, uninstall every single mod, start a brand new unmodded game, play through to the point where you first exit Vault111, save your game there (and then make a back-up copy of that unmodded save as it will come in handy in the future when testing mods) and don't overwrite that particular savefile. From there, you can quit the game and go about the process of reinstalling all your mods, one at a time, and testing them in-game, before installing the next mod. Having a 'clean'/unmodded save file is the best practise to use, and installing numerous mods at once isn't recommended as it's too easy to lose track and make it harder for yourself to identify when a mod is conflicting or causing problems with the game etc. Good luck. -edit- Almost forgot, make sure that you have as few external background processes running whilst you play the game. For example, anti-malware/anti-virus software, Steam overlay, EVGA, Afterburner, Avast antivirus, EMET, D3D Overrider, Razer and Logitek utilities can negatively effect game performance whilst you play; basically anything that loads up after your OS has booted (excluding for example, Steam itself). From your system specs, you should be able to play the game fine at low settings. Make sure that your display/gpu drivers are up to date etc.

Download the latest version of NMM over on Github (fixes a number of issues that the now-unsupported version here on Nexus has) https://github.com/Nexus-Mods/Nexus-Mod-Manager/releases

It can affect any main menu replacer with custom audio, and I've not been able to pinpoint an exact cause. The issue is known to occur if either you're using a mod that 'bypasses' the Bethesda/S.P.E.C.I.A.L. intro vids, or if you choose skip them yourself. Unfortunately, it's also known to happen seemingly at random when you first boot-up the game (I've had this happen numerous times myself, but haven't been able to pinpoint the exact cause) although once you've loaded a save, quitting back to the main menu results in the custom music working.

This could be due to having missing/incorrect drivers for your hardware, alternatively (and more probable if your system is several years old) it could be an indication that a particular part of your system is on it's last legs, whether that be ram, gpu, cpu, motherboard or psu. First things first, check to make sure that all your cables are securely attached to the mb etc. It might be worth your while to do some diagnostic testing on your system components to see if you can pinpoint the issue... although I note you do seem to state that you've always had ctd's with Fallout4 (does your system meet the minimum requirements? If not, then that could be the cause) Sorry I can't be of more help.

Thanks for all your hard work & contributions Ousnius, it's really appreciated.

In my experience, the safest practice is to start a new, completely unmodded, vanilla game, and make your way through the Pre-War Sanctuay/Vault111 section. Once you've passed the point where you exit the Vault (just after coming out from the elevator whilst your eyes adjust to the light) save your game right there. Make a back-up of that save file, store it in a different directory (or even better on another drive) and keep it safe. The copy in your default save location should be used for testing newly installed mods out thoroughly (and only for that purpose) so don't overwrite this one. Instead, create new saves when you begin to 'play' the game once you're satisfied the mod in question works correctly. 'Clean saves' is a term that generally refers to save files allegedly scrubbed clean of residual data (script fragments etc) left over from mods that are no longer installed, by so-called save-game cleaners. In my own experience testing with Fallout4, I've not seen any benefit to using this kind of program, and am left wondering if users proclaiming the virtue of said cleaner/s are merely experiencing a kind of placebo effect. It's generally a good idea to install mods based on the 'type' of mod it is, doing this makes it easier to keep track of issues, as it's contained to that certain 'type' of mod (whether it's armors, weapons, new quests etc) though I'd strongly recommend that it's exceedingly wise to install one at a time (and then to as test thoroughly as possible) if you value being able to quickly identify the cause of mod conflicts or game crashes/errors - far too many users unfortunately don't do this, which compounds the problems they inevitably experience as they've made it almost impossible to identify for themselves. Generally speaking, replacement files such as texture and audio mods are the safest mods you can install, whereas script-heavy mods can be the most problematic. If you're using NMM, you can make use of the tab functionality to keep track of 'when' you installed a certain set of mods & the order thereof, via the 'installed' tab; clicking on it will rearrange the list of all your mods in order (if it displays the earliest mods you installed, simply click on the 'installed' tab again to rearrange it to show the most recently installed mods) With VotW, the advice you mentioned was in response to numerous users informing us that the holotape mods weren't working correctly and were displaying the wrong content. Unfortunately, as with a lot of bug reports we've recieved I've not been able to replicate any of them myself in my game (using an unmodded save file for test purposes) Most of the issues reported are down to either user error*, or problems that occured because the user was (unknowingly) using a version of NMM that is severely bugged that results in either textures, meshes or other parts of the mod not being installed correctly in the Fallout4 data structure - the solution to that particular problem is to use the newest version of NMM, which is now being (unofficially) developed over on Github, due to the Nexus officially ceasing development of NMM, in favour of development of Vortex - newest version of NMM found here: https://github.com/Nexus-Mods/Nexus-Mod-Manager/releases Because of a combination of the huge amount of mods that exist that alter/add to the Settlement system, and VotW being reliant on the vanilla workshop records (which numerous other settlement mods alter (effectively stopping VotW from correctly functioning) as well as the logistical improbability that we can test every mod combination available, we're unable to test the majority of mods out to hunt down incompatibilities and provide patches when possible*. Every time I've tested a test build for a new version of VotW, it's always on an unmodded save-file, and with the exception of one time that Dertspovor06 forgot to include certain files in the update when he uploaded it to Nexus, every version has worked... I've never personally experienced most of the issue being reported/commented on, but because there are so many variations of mod-list/load order*, we decided to take the precaution of advising users to minimize the potential for this to happen.We're also compounded by those users who don't read the main description/sticky posts, especially in cases where the user is updating from a pre 2.0 version; older versions of VotW had some issues due to some unoptimized coding in the original script files, which was known to sometimes cause game crashes when VotW was installed. Again, not an issue I have personal experience of dealing with myself, but plenty of users complained about it for a while (2.0 came with completely rewritten optimized scripts) We also always advise that users ensure that VotW is last in their load order, to minimize the potential of other mods interferring with the VotW functionality. * The single biggest problem with mods is caused by users blindly installing & uninstalling countless mods all over the place during a playthough, with no real understanding/knowledge of the impact it can have on their save files; things like scripts get baked into a save file itself and stay there even after the mod that the script is from is uninstalled. That's a major cause of what is known as 'save bloat', where users report save-files with huge (mb) sizes, which can lead to increased load times, or in extreme cases game freezes/crashes. Patience, caution and a little bit of familiarity/research/reading-up so you understand exactly what you're installing and how it will affect your game are the key to a (mostly) trouble free modded game. It get's easier with time. Sorry for the lengthy response!

More info on the game here in NoClip's 'the making of Fallout 76' short documentary - https://www.youtube.com/watch?v=gi8PTAJ2Hjs

Well, whilst I'm not initially keen on it being pvp/multiplayer etc... I'm reserving judgement until the game is released & I've tried it out for myself. It might actually be fun, or maybe it wont be. Maybe it will have more depth than we imagine, or maybe it won't. No one knows right now. Fading Signal's expression is priceless.

You are correct, he did use the word 'solo' - that's an important distinction from being able to play single-player. I think a lot of people are feeling the same way now... :confused:

I thought I heard Todd state that 'you can still play it single player' or was that a hallucination?

Wait a second, were you watching the same thing as I was? Todd specifically stated in the presentation that you could still play Fallout76 by yourself, meaning co-op wasn't the only option.

Wouldn't be allowed as the Silent Hill OST's are copyrighted content, neither Nexus or Bethesda.net allow the redistribution of copyrighted material in mods, unless permission from the owner of the copyright is granted - and I highly doubt that Akira Yamoaka & Konami would grant permission for use.

Probably because enhanced lights & fx and Darkner Nights are incompatible with NAC* * check the list of incompatible mods on the NAC main page (scroll down, and click the spoiler tag)