AGreatWeight

You need to use OutfitStudio (find it on Nexus) to import an .obj file. From there, you can convert it to a .nif file for use in .nifskope.

Hmm, aside from some things that are mentioned by the author (Midhras) in the mod's description page - having HDR enabled, Water Displacement + Anti-aliasing + anisotropic filtering all turned off, via the game launcher. Check that your Fallout3 .ini files don't have hardware anti-aliasing enabled. that you have the d3d9_smaa.dll, SMAA.h, SMAA.fx, and injector.ini in your Fallout directory, alongside the d3d9.dll Don't use any gpu-based multisampled anti-aliasing (either via Nvidia or AMD software/drivers. Before starting the game, delete the 'rendererinfo.txt' file that should be in the Fallout directory, then backup your .ini files somewhere, and remove the ones in your Fallout3 documents folder. Launch the game via the game launcher, it'll generate a fresh 'rendererinfo.txt file, as well as new .ini files (this way you can rule out if your original .ini files may be causing the issue or not - if not, simply replace them with your backed-up ones. Make sure you don't have any software active that adds an overlay (such as FRAPS, MSI Afterburner to name a few) as these can cause issues with enb... for example, an external program that adds an fps counter to FO3. - aside from all those, nothing really comes to mind, except one final stab in the dark. Though it might not work (or even do anything) you could perhaps attempt to download, then install the DirectX 9 runtime. https://www.microsoft.com/en-gb/download/details.aspx?id=34429 If when installing it asks you if you want to repair, select yes; otherwise install as normal. Perhaps having the DirectX 9.0 API's installed via this method will solve it... at this point, there's no harm in trying & nothing to lose. Wishing you the best.

The C++ redist should only ever be installed into the default location (of your O.S. files, not the game directory) to the best of my knowledge, whilst the d3d9.dll from the enb wrapper only be placed in your Fallout3 directory. If you already have a redist installed & try to reinstall, it should (by default) ask if you want to overwrite or repair the existing version of that particular redist. With the v118 of the d3d9.dll, make sure you're only using the original version of Midhrastic. Looking at the error code you mentioned in the initial post, usually this happens when there are either missing system files or system components, which is what made me suspect it could be related to a missing redist dependancy, though with that not solving the issue, I'm a bit stumped. As an aside, I'm guessing that you'd already gone through the process of installing Games For Windows LIVE, then (via a mod manager) installed the Games for Windows LIVE Disable/d mod... and the FO3_3GB_ENABLER mod. (this part may be completely unrelated to your specific problem, but seeing as I've pretty much exhaused every other possible cause for having that error appear, I might as well throw these ones in here too) You might have to consider uninstalling everything and starting from scratch (unless your modded/unmodded Fallout3 was working fine prior to installing the enb preset/enb .dll) Again, apologies for being unable to help you narrow it down to the root cause & fix it.

Doesn't a redist exe come with the Fallout installation by default? If so, I've seen it and installed it. No luck. Yes, but bear in mind Fallout3 came out in late 2008. Installing the game on a modern machine + O.S. may require that additional step I mentioned to fix the problem you're experiencing with the d3d9.dll from ENB. Here's some links that may contain useful info... hopefully this'll help you out further. https://steamcommunity.com/app/22380/discussions/0/3377008022030319366/ https://forums.nexusmods.com/index.php?/topic/3089504-fix-for-skyrim-crashing-instantly-with-enb-on-windows-10/ https://steamcommunity.com/app/22370/discussions/0/135511379838364898/ https://forums.nexusmods.com/index.php?/topic/6215506-d2d9dll-crashing-game-nothing-ive-tried-has-worked-at-my-wits-end/ https://www.reddit.com/r/FalloutMods/comments/7if2cs/fnv_cannot_get_d3d9dll_to_work_for_enb_or_reshade/

I believe this issue is caused (or can be caused) by not having certain dependancies installed - in this case, Visual C ++ redistributables (sometimes your OS doesn't download/install them all by default, so you have to do it manually) I can't recall offhand exactly which version you'd need, but you can check to see which ones you already have by going into the control panel of Windows, and select Uninstall a program. From there, scroll down until you find entries that list Microsoft as the publisher. Here's a screengrab of all the ones I have (I'm on Windows 7 btw, and run Midhrastic ENB on Fallout3 with no issues) From the entries that will appear when you check on your machine, you can determine which ones you're missing, and just do a google search to download them from the Microsoft site.

You'll need F4SE, as well as the FreeFlyCam to do angled shots like this. The last version of FFC was released on the 10th December, and works with F4SE 0_06_15 (this version of F4SE is for Fallout 4 v1.10.120) https://f4se.silverlock.org/ http://enbseries.enbdev.com/forum/viewtopic.php?p=75209

If the map texture is from a mod, it's likely packaged up into a .ba2 file inside the data folder.

I second what HadToRegister said, it's usually caused by those textures not installing correctly; reinstalling the weather mod should fix it.

You could use the mod Videos of the Wasteland, it adds a framework for working TV's (both pre-war and post-war variants of the Radiation Kings, as well as new custom models) that can be placed in your settlement/s. Besides the S.P.E.C.I.A.L. vids that come included with the mod, there's a varied selection of additional mods that add new content to play on the TV's; check the VotW description page for links to them all. https://www.nexusmods.com/fallout4/mods/24435

Moribund World is a weather/climate overhaul, whereas Dustbowl Overhaul alters the worldspace by removing most trees/vegetation from view. Both mods do completely different things and technically can be used together. The only caveat would come if alongside Dustbowl, you also want to install the seperate Western Weathers mod made to go with Dustbowl - doing this will likely cancel most of what Moribund World does, so you'd have to pick one or the other. Dustbowl itself doesn't cause game crashes (can confirm this) so whoever sold you that tale was incorrect. More than likely a mod conflict or an issue within your load order. The only issue that Dustbowl had was related to some instances where birds were perching on invisible trees. (@Undeadbob666 - Moribund World is only available on Beth.net for unknown reasons, almost like inverted snobery on the mod authors part. If I remember correctly, they made it for some competition that Beth ran with Nvidia to promote the (then) newly launched GTX1080 series)

Yeah, we'll need to know your system specs before we can give you appropriate advice.

The only (minor) performance impact you'll notice when you have a lot of save files is right at the beginning when the main menu is loading, in the form of audio/video stutters, pops or mini freezes. Fallout4 scans all the save files to bring up certain info from them (mini thumbnail, name of character, game-time etc) Obviously the more you have in your save folder, the longer it'll take for the game to read all that data. Not sure how SSD's fare, I'm just going on HDD performance - if that's what you're using, backing-up all your saves, and only keeping the most recent 10 or so should be fine. A bigger problem with save files is 'savebloat', due to the save file containing references to mods that were used at one time or another in that saves history, but have since been uninstalled.

Go into your Fallout4 DATA directory (usually C/STEAM/STEAMAPPS/COMMON/FALLOUT4/DATA unless you've installed it somewhere else) Inside the DATA folder, navigate to TEXTURES/INTERFACE/PIP-BOY and delete WORLDMAP_D.DDS

From Vault 111 (pre-war) the nuclear blast seems to appear in close proximity to the crater in Canterbury, although post-war, there clearly isn't enough damage around that area to indicate a bomb hit anywhere near there (or any part of Boston city for that matter) https://vignette.wikia.nocookie.net/fallout/images/3/30/Ruined_Boston_BirdsEye.png/revision/latest?cb=20151229201144 In the concept art above for Fallout4, it's clearly visible that Canterbury was utterly decimated. The game never directly addresses the dissonance between what's depicted pre-war and what you encounter post-war... unless you subscribe to the whole 'Nora/Nate is actually a synth and their memories are just implanted' hypothesis.

Start a new game, play through the the pre-war section and the Vault111 part, once you've emerged head down to Sanctuary Hills, wait for 2/3 in-game days and save your game there. Use that save purely for testing mods (but don't overwrite it, and make a back-up copy)

This is happening only at a specific time at night, correct? It's an issue with the ENB preset you're using. You'll also notice it appearing heavily on trees as well as the underside of all in-game objects/structures.

Thanks to Neiro, I killed a feral ghoul with a critical, only for it's charred skeleton form to reanimate thanks to a glowing one's radiation attack, then proceed to slowly shuffle after me.

A badly made or poorly tested mod can. Aside from that, mods themselves don't crash the game. Installing mods that conflict with each other without the user attempting to resolve the conflict, badly organized load orders, and removing mods on an existing save/playthrough can cause CTD's.

Make sure that your texture has an alpha channel, and that you're not encoding the .DDS with DXT1 (as that codec has no alpha) Use DXT5 instead.

Yeah, a lot of clothing mods are made in this fashion, so lack the area of 'fabric' that would normally appear between breasts. @OP, short of making a custom mesh for the clothing (which would also involve creating new UV's for the textures, among other things) there isn't much you can do sadly. The bigger the breasts, the more noticable it is.

From what little I know, the decriminalization and intentional demonization of cannabis (in the public eye) began thanks to the efforts of big business. A new device, called a decorticator, threatened to completely revolutionize the production of paper via hemp, making it cheaper and more profitable than traditional means of paper production via wood fibres, meaning (if not for interference) that tradional paper production would have most likely eventually become obsolete. Obviously, this was a huge economic threat to those heavily invested in said traditional methods, so they used their contacts in the government to collude to outlaw the use of hemp in all forms, as well as misinform the public by deeming it dangerous, as a way of maintaining their own wealth/vested interests. (link) Various fictions were purposefully created in an effort to convince the people and the government that hemp was dangerous and should be outlawed. It's name change to Marijuana was another concoction of the propaganda, designed to inflame the passions and prejudices of the white man by demonizing Mexican and Black men via claiming they were using the drug to corrupt white women into interracial relationships etc. They preyed on peoples fear and ignorance to further push their propaganda and political motivations, all so that certain wealthy men could continue their monopolies in numerous industries undisturbed. It was certainly effective, considering we're still in the process of completely dismantling the myriad lies, disinformation & sheer dishonesty that's been purposely built up around the plant since then. Not to mention the devastating impact all these untruths have had on so many lives since their inception, such as all the people wrongfully incarcerated, as well as the retardation of scientific study into the numerous uses/benefits (including medicinally) that the plant offers. So much damage done purely for $$$'s. C.R.E.A.M.

@Reneer Perhaps the OP's game install is haunted? ;)

The only mod I'm aware of that does this is Reneer's Close That Door mod.

Until KingEric releases an update* the only way to use the freeflycam plug-in would be to downgrade to the previous version of the Fallout4.exe & F4SE.

Noticed that in your Fallout4.ini, under [General] you didn't have sStartingConsoleCommand=bat Godrays which is required for the godrays mod to work (alongside the .text file in the mod that you manually place in your Fallout4 directory) Aside from this, I didn't notice anything in your .ini files that stuck out as a likely culprit. From your load order, the only thing that caught my eye was ENBLightsHDRPatch.esp, though I'm not familiar with/ don't use ENB Lights Overhaul so can't state if the lighting changes it impliments are affecting godrays.