bbiller

If looking for fans, these tips will help. 1. Fan speed is not the most important thing, CFM is. Noise is good to deal with, but you can get decent CFM with low fan noise. CFM is how much air that fan can move, fan blade design plays a role as do the RPM's of that fan. 2. What helps spin that fan matters in that noise equation. There are many different kinds of bearings and ways to spin those blades. 3. Fan noise used to be measured by decibels, but sones took over, however some still post the db, as sones is a feel measurement, while db is scientific. There is a sone to db converter out there if you need it. Under 20db is considered quiet, over 30 is loud. You will want quieter, recommend 18 or less. 4. That fan connector matters. Fans now can use Pulse Width Modulation (PWM) to control fan speed and can report back to that motherboard or fan controller what they are doing, this let's you know when those fans are getting too gunked up or are going to die so you can swap them out or clean them and yes fans need to be cleaned. PWM fans have four pin connections and can be used in a three pin slot, you just lose the modulation to ramp things up when things get hot or more CPU/GPU intensive. 5. Size matters. Know how big a fan you can put where. These can be found from millimeter measurements. Typical dimensions are 80, 120, 140, there are larger than that and smaller, too. Bigger does mean lower RPM and less noise for same CFM as the smaller fan. 6. Prices will vary check on-line. Newegg and Tigerdirect are great resources for reviews and specs, and may have a good price to beat everyone else. For price comparison use google.com/shopping and enter the make and model fan you want. 7. Top recommended fan makers: Arctic Cooling, Cooler Master these will get you good bang for your buck. Noctua make good fans too but are expensive. If you need thermal compound for the CPU, Arctic Silver is a good idea, may be time to look at an after market cooler and maybe replace that thermal paste. Air cooling can be done well for around $30, you may find a deal. Heat pipes are a good idea as are a copper core on that CPU cooler. Aluminum will store more heat and take longer to heat up, but copper will move that heat away faster. 8. Fan Prices: 80 should be around $5, 120 should be between that and $10, though can go a little higher, no more than $15. 140 is a little above $15 or around that. Should not go above $20. If a larger fan is needed than those, prices will vary. Keep in mind I now have two noctua fans on my hyper evo 212 and one in the back, along with two 80mm Arctic Cooling fans on the front side to cool the hard drive cages and those cages use a built in 80mm fan and aluminum to cool my drives there. Power supply is a Corsair Tough Power Grand 1200W power supply (modular and gold certified, it was $20 more than the 1050 I could have picked up at that time. It was not cheap. But worth it and it was sitting idle for a few years and has been running strong no issues so far for the little over a year and a half I've been using it, should support any future upgrades I do for that setup. Hope that helps, I did a fair bit of research before buying things, those the Noctua I got from the local Micro Center (had no choice, needed the fans for my computer to work with my job, tech support from home).

Update: Just tried back stepping releases all the way to 0.65.10, still same Fallout 3 xml file issues in the trace log.

So while I did update F4SE a little while ago, I was going to go in and fix my mods making sure they were still all up to date when NMM notified me of the community bug fix version .70.8 and so I let the program put it in thinking all would be well, when lo and behold an exceprion comes up for Fallout 3, which While I may have that in my game library for Steam I have not installed on this computer yet. I have tried downloading directly from the Github site, but same error pops up in the trace logs. I am running Windows 10 now, but the last NMM run I did was back Windows 7, but I know others have 10 out there so that can't be it. I will post the log below with tags, maybe someone has an idea what is causing this? BTW, that is as far as the log goes, I probably can run Fallout 4 just from the F4SE launcher as the mod list has not changed, Last version I was using was 0.65.9 . Any ideas welcome at this point.

It's probably not scrap everything or place anywhere, but do make sure you have the right versions and have them in the right spot in the load order (there is an ultimate addition to scrap everything that has an additional patch, so do make sure you have it). Scrap Everything is last on the load order by the way. I have spring cleaning in too and so far no issues with mole rats or blood worms, still have to save the kid and there are plenty of mole rats where I'm going and no crashes there, just trying to avoid the things and not get infected to pick up the serum. Just remember don't go too overboard like John Candy in Caddyshack, stomp the rats or worms and deal with the spawn point/hole as needed.

Do remember sometimes the only way to get things to work is to add them in manually. You'll still want to make sure the mod is listed correctly in the plugins list, but your mod manager can help with that. Also note: If your mod has assets for the textures (a ba2 file), the manager may not have added it in, you can manually add it in though if needed, I've had to do that to get some things visible. The weapon would be on my hotkey list and my character would act like they were holding something and I could fire it, but nothing visible. Once the file was moved in, all was well.

If this is a laptop that memory and internal bios setting for thermal throttling may also be to blame.

I would be looking at other parts of your setup (memory, cpu, hard drive, power supply). I have a 3Gb MSI Lightning 2, AMD FX Black Edition 8150, 32GB of GSkill Ripjaws RAM (1866MHz), 2x2Tb hard drive in RAID 1 and the game works for me on a little above low settings. The video card is the bottleneck there. I would also check your driver's as those may be causing some of the issue. Airflow can also be an issue, so make sure you have a good case with enough fans to keep things cool and I do have a Hyper Evo 212 cooling my CPU with two fans (one either side) pulling and pushing air to the back of the case.

For this check on the following: 1. Head to nexus and log in. Can you log in? If not, fix that. Once in, if NMM is set correctly things should work. 2. Very important: NMM is github only, Nexus moved to Vortex some time ago (NMM is still able to be used, but their copy is way out of date). So check the version you're running, if outdated, update. 3. If you are updating, you should be able to keep things as is, but if all else fails, remove and reinstall, just do back up the load order and mods so you can put things back in order. Hopefully this helps you. By the way, Vortex has been a mixed bag as to working with Fallout 4 vs NMM, though they are still making improvements and releasing tutorials to help get around hurdles.

Spellcheck strikes again ear should be rar.

These tips will help: 1. Sometimes the best thing to do to get some mods to work is to put them in the game manually. F4SE is one of those, MCM (Mod Configuration Manager) is another. Keep in mind if a mod is not showing up manual may be the way to go. NMM (Nexus Mod Manager) can still help with mod order, as can the games built in manager. 2. Remember the 255 plugin/mod limit, esl doesn't count. If you're over the mod will not show up if out of range. Combining mods can help, but make sure it is a mod the author is done with else you'll have to remake that combined mod. 3. Nexus is using Vortex now so if you still want NMM, github is where the newest version is. 4. Keep an eye on F4SE, they update as the game is updated (that should finish at some point so that the mods they release will not need a version change). When F4SE or the game changes, check on your mods, make sure they stay compatible (this can help with some error dialogues you get). 5. Back up your base mod files, that way if the worst happens you can reinstall them in the order they should be in. 6. Back up that mod order and keep a running list of them, because not all mods are titled as to what they are out of the zip or ear file. 7. LOOT can help with conflicts, but in my experience it's a mixed bag of help. Bethesdas mod site has a good load order guide and there are things you can do to keep mod pieces together, but you need to know what your mods are affecting. 8. Wyre Bash can help with combining mods, but I would still have something to tell you what is in that patch. 9. Bethesda does release some of those mods they have free, or on sale, so keep an eye on those announcements, there are some good ones in there with some good additions to the game. Hopefully these tips help. BTW, if MCM is in properly you'll see that in the Escape key menu. If manually adding mods a good archive program like 7zip or IZArch will let you see the structure (Data folder in Fallout 4 folder is your starting point except for some of the files in F4SE, as that has been manual approach for many months. Best install method: 1. Delete F4SE base files in Fallout 4 folder. 2. Bring over new base files and make sure all old base are out. 3. Put those scripts where they need to be. That will get F4SE in place and the old shortcut for running F4SE will work and NMM will still use the entry for it.

While I don't know Fallout 4's requirements, here are some things you can check: 1. If you have some digital music around, load one of those files in your editor for audio. Take a look at the highs and lows there. If your audio file for Fallout has that base height or better, that should be a good starting point for your import. 2. Check audio options for when the system plays that audio file in the scripted process, is it following another sounds process and settings (ex replace shotgun fire with dog barking audio) and of course take a look in your editor at the sound you're replacing once it's extracted out where are its highs and lows along with format. 3. If an extractor or compactor/converter is involved, check those settings that might explain the difference. Do keep in mind your system may also be affecting the sound, differences in hardware can result in different sound. Great example: Eradicator by Accolade. The audio for the menu screen for that is in RAW format, so convert one way for a type of wav file and you get the normal version you hear in game, the other form of that wav file gets you a much speedier version. Both sound good, but only one is the true representation. My thoughts on things, hope it helps (may give someone the idea for the dog gun in Fallout New Vegas brought to Fallout 4).

That might be Sith Lords for that, been a while. But when you call in too many the game has a lot of math to do and the processor can't handle it.

Do you have a CPU temperature app on your computer? If yes, have it make logs, see if that temp is getting too high for your processor, or it could be too much for the CPU to do (see original xbox and Knights of the Republic and the dark kell dragon spawning areas for when players summoned too many at once). Once you have the log, you may want better CPU cooling, or a better CPU. I can say an AMD Athlon Back Edition 8150 that is an 8 core processor will work, as that what I have. Also check your graphics settings, might be too high for your video card (MSI Lightning 2 with 3Gb of video RAM on my end, so graphics are a bit above low with at best 2k textures in some cases, though do have Bethesdas hi texture pack in place). Hopefully that helps, do check complexity of mods while you're at it.

Not all mods are affected by F4SE, there are some which are. Make a list of your mods, check the authors page for the mod and what it requires. If it uses F4SE it may be ok as is once F4SE is installed to the game. Manual install from the zip file is an option, I've had to do it. Process is as follows: 1. Make sure you have IZArch or 7Zip, these will help you see the structure for the archive. 2. Get the F4SE files zip or installer, Installer is best but there are releases that are zip only. 3. Delete the f4se files in the main directory, move in the ones from the zip file, you can move in the custom controls file, too, just check on your setup, you may need to tweak it again. 4. You will see a Data folder with a scripts folder inside it, move all those scripts into the Fallout 4 Scripts folder in Data (this will require overwrite). Do check your mods for changes to vanilla scripts where they were lazy and didn't use a new name for their script. That should be an easy setup to have the character use the script in question. 5. Check on an F4SE using mods, most will probably work, but there may be a few more active ones that need something special. Update as needed. 6. Run some tests while gaming, use NMM or Vortex to run F4SE and see what needs fixed if anything. 7. Enjoy the wasteland.

I can tell you I'm using an AMD FX Black Edition 8150 (8 core) and Fallout 4 has no issues with that, though in your case I would squirrel away some money and add more memory (16Gb minimum, I'm running 32Gb myself (1866MHz DDR3 Ripjaws series, newegg can show you that). The only issue I have is my video card (MSI Lightning 2 6970, 3GB memory), but Fallout 4 works with that on a little above low settings at 1920x1080 resolution and I have the texture upgrade pack that Bethesda released installed.

Sounds like you're looking at a Visual Basic Runtime error, with that file name. That is an old file and there are copies of it all over the Internet. Once you have it, it should go in the same directory/folder as the application you're trying to run. That should fix it.

There is an enhancement process they give you access to, you do need to have done some work for them, though the process is cap and rad intensive (have rad away and rad x taken before some of the later parts of that). Skool Zone did a YouTube video on them with the enhancement process gone through and the benefit explained, check it out.

If you set that x as a storage location, then yes Fallout 4 can go there, but check the disk space they gave you. Mods take space and you are basically duplicating there, then you have the install for Fallout 4 and the save files, so you'd be better off with your own computer long term.

No Vortex is not the cause. As for the NMM versions, if you haven't heard, NMM is now being worked on exclusively at Github, so check for an update there. Right now Vortex is at a 50/50 state, with some of us using it, while others are sticking with NMM or MO (Mod Organizer). Vortex is what the Nexus uses and is still developing now and it has got a number of features on solid ground now. As to your files, grab an undelete program, check your recycle bin, and see if your AV or Anti-Malware program might have done something. There are a number of free undelete/file recovery programs, just don't write anything to the drive where your mod files were. If you have, recovery will be impossible for some of those. Any you can't get back, re-download from Nexus.

Some of what you're looking for you'll find in the Valt-Tec DLC, as there are weights, a bike, and a pomel horse available once the DLC is complete.

That should have been src, autocorrect strikes again.

I grabbed the zipper archive and dropped the files where they needed to be. Steps: 1. Go into data directory/folder or main Fallout directory/folder, delete all f4se files there, leave the directory/folder named F4SE alone for now. 2. Anything in a source or sec folder in the archive leave alone, those are to help models and programmers. 3. Take the 6 loose files in the main part of the archive and copy those to where you deleted the previous file versions. 4. In the Data\Scripts section of the archive leave the source folder alone, but do copy all other files there to the scripts folder in the data folder, this may overwrite the old files, that's fine. 5. Open NMM and run your F4SE launcher as normal, the game should start up, mine did with no alerts of incompatibilities (still need to sort my mods again to get some working, but no sign of anything super glaring, though MCM is not showing up at the moment, the tweaks to the order should fix it).

First question would be: did you check in your appdata section of your Windows User. #2 Did you run the main game launcher without anything else, as that will make the files that the game needs. An example for #1: C:\users\Your User Name Here\AppData\Local\Fallout4\ . This is where some of your ini files should be. Others are in: C:\Users\You Windows User Here\My Documents\My Games\Fallout4\ .

One thing not connected to your question, watch out for the pack attack mod, as I have seen reports of it causing issues for others.

The main thing with the combined patches, aside from cutting down the esp and esm files count, is that the combined patch will refer directly to the original ba2 and any loose files the mods need to use. So example, patch 1 has an esp and a ba2 file, patch 2 has an esm file and a batch of loose files. In the case of combining those, the resulting patch probably would end up as an esm, but would still refer to the original loose files and the ba2 file with what would be in those. Granted I would suggest checking what is inside the archives for your mods and just combine those that are independant/stand alone that only have the one or other of the file types with ba2 files that contain the rest of what the mod needs. Once you have the combined patch, you will want that listed in place of the original patches, but the ba2 files will need to be in the data directory through your mod manager. You may be able to put all the pieces in a new custom archive and that would save some issues, but you'd need to duplicate the internal structure for the archive. There should be an archive utility that will fit the need (suggest 7zip or IzArch, both are free, Google will help you find them).