Jump to content

emmingerl

Members
  • Posts

    22
  • Joined

  • Last visited

Nexus Mods Profile

About emmingerl

emmingerl's Achievements

Apprentice

Apprentice (3/14)

0

Reputation

  1. Ah, will move it and see if that works. I'm using CBBE so had the regular when do you want it to load question in regards to Armor Keywords. other than that just the esm files notices, maybe it will clear up when I redirect the download folder. Mod folder ok though? Thanks for response, and yes, I remembered the Vortex support forum after I posted this one. :confused: been one of those days.
  2. So the Vortex update on March 20th has thrown my whole everything in disarray and I'm not sure what gives. It asked to do a purge before finalizing updates and, as I kept my targets out of Vortex directories as recommended, I said sure. (I also keep a back up of all zip files separate as well so, I actually haven't lost anything just needing to untangle the wires here really). Game starts fine but, will CTD when loading a save. I validated game files via Steam and, for what that's worth, all checks out. Checked Vortex, deployed mods, cleared error messages (mostly file conflicts between armor mods) and fired up the game again. CTD when loading a save. Save files are where they are supposed to be. Had Vortex sort plugins as I noticed a few were not numbered and received messages saying that save headers were not recognized. Then began getting error messages saying that the .esm files that Vortex just processed were invalid and could not complete the sorting process. So, I had Vortex re-load files again and replace the existing ones and that seemed to clear things up. Finally got it back to no error messages. Before I go on, I want to show the screen shots of where the targets are at (cause I think I may have them wrong). Mod Stager is set to: http://i64.tinypic.com/sc9fg5.jpg Download file is set to: http://i67.tinypic.com/5mihqx.jpg OK, so, with all that out of the way, I fire up the game and.... CTD when loading a save. However, it will let me start a new game BUT.... As soon as Nate says "War never changes", I have the steam clear and I'm looking at the mirror. I back the camera out and this is what I see: http://i65.tinypic.com/eq57jc.png So, at this point I'm just about ready to peal my skin off. Any advice will be most welcome. Thanks in advance to anyone who drops by! :turned:
  3. I've been at this for over a month now and I've gotten it to the point where everything works until you put it on and then BAM... CTD. So, in my infinite wisdom I accidentally deleted my freaking file. :wallbash: So, if anyone is interested in assisting me with their awesomeness ( :dance: )...I have 58 military berets I'd like to get into one mod that can be crafted at the chemlab. I have already uploaded all the berets as individual replacements to the game's "Military Cap" on the Nexus so, all the graphic files are available and photos with descriptions for each are posted as well. I would reeeeeeeeeeaaaaaalllly appreciate if someone could make an esp that will work! Please PM me! I would like to see this become a reality! Thanks guys!
  4. Wow that's weird, haven't seen that one. Do you have the high def DLC with this? I know it caused problems with faces. Usually black facing the characters but, I know there is a fix out. Might try this and see if it helps: https://www.nexusmods.com/fallout4/mods/21907 Hopefully it helps.
  5. I had same issue. My initial load of Vortex was a nightmare because I forgot to set my Mod Staging target. Then it was a nightmare again because I targeted the actual file and it made the standard folder inside the folder. Anyway double check your file targets are correct and this may resolve the issue.
  6. To everyone else reading this, if I miss something please add it! Thanks! Ok, it's -1 because you either have the "auto sort" on the plugins page disabled and you haven't clicked the "sort now" button, or have not hit the "deploy mods" button on the top of the mods tab. Check also that your targets are set to where your game is and not just a Vortex default folder. Click the "settings" tab on the left hand side of Vortex and then click the tab that says "Mods" at the top. The Mod Staging target should be: C:\Users\{computer name}\Downloads\Vortex Stager *Note: Vortex Stager is a folder name I gave for my mod staging. You will have to make a folder and name it for this target set. Make sure it is empty when setting up target. The second portion on that pade should read "Hardlink Deployment" Next, click the "Download" tab at top. Download folder target should read: C:\Program Files (x86)\Steam\steamapps\common\Fallout 4\Mods Also check that the "Handle" button at top of page is green for Nexus Mod managing. Next tab "Games" should be default set to search both C: and D: drives. so nothing to do there. Under the Vortex tab it should read "Multi-user mod" : shared and "Update": stable. Now go down to the "Mods" tab on the left hand side menu. You can verify targets by clicking the "Open" folder tab at the top of the page menu. A drop down should appear asking you to select the "Game Mod" folder, the "Mod Staging" folder or the "Game" folder. Clicking each one should open a File Explorer window to that file location and should take you to the targets you put in. Next: Check your mods and see if they are enabled. If so, look under the "Dependencies" column and see if you have any red lighting bolts. If you do, that means there is a file conflict preventing activation. Click the red lightning bolt to see what the problem is. If you have a conflicting file, it will ask you whether or not you want the conflicting file to load before or after the mod you opened. Example: Armor and Weapons Keywords will conflict with Armorsmith Extended. If you click on Armor and Weapons Keyword's lighting bolt, on the pop up page it will show Armorsmith Extended. You will select it to "load after" and save it. It will close the window and prompt you to deploy the mod again so corrections will take effect. Do this for any of your conflicting files and then hit the "Deploy mods" button at top when done. This will deploy the mods again and alert you to anything you may have missed. If it deploys without any notifications, you should be fine. Now click the "Plugins" tab at the left hand side. Make sure auto sort is enabled on the top bar menu. You can also hit the "Sort Now" button to make sure everything is in order. Now scroll down the list of plugins. Everything should be green buttons and white lettering. If you see anything orange, you have a file problem. You can disable the plugin and hit enable again to see if that clears it up. Usually it will, some FOMODs will do this as it needs to go through the install questions before installing. OK, now go to the "Dashboard" button on the left hand side menu. Make sure "Profile Management" is on. The box below that should show the Fo4 picture and have tabs to the right of it. Those are the launch tabs for the game, F4SE, and other tools like Bodyslide etc. IF the tab is targeted, it will show a "Play" button triangle. To the left og that triangle will be 3 dots. Click that and hit "Edit". A pop up window will show you the Name "Fallout 4" the target file (i.e. the Fallout4.exe) and the location where to start. Make sure the target is to the .exe file for fallout. the rest will auto fill when you select the file. If you use F4SE, do the same thing but, select the f4se_loader.exe file. Make sure F4SE is up to date. Now try running the game. Hopefully that should resolve any issues you may have. Hope this was helpful! Cheers!
  7. @ applegatc: Thanks! Did that, just wasn't sure if I was in right folder. Found this post from way back and it has fixed my issue. I disabled ALL mods in Vortex, ran the game and no crash, ran F4SE and no crash. It did however pop up that my looksmenu was out of date but, otherwise ran everything ok. Just to be clear... What I did was disabled ALL mods but, I let all the plugins enabled and it did the trick plus mods were running in game as well. Hope that helps. Also, I went through and enabled each mod to find the culprit. Found it was simply a mod that did not go through its normal FOMOD install menu. Also found 1 mod was not playing well with others period. I suspect that it just needs to be deleted and reinstalled but, since it's not a mod I really use, I just got rid of it. Make sure you have the latest F4SE installed and screen through your mods to make sure there are no orange colored notes or flags on them in Vortex and you should be good to go. I'll leave a copy of the full post I found that helped me.:
  8. @applegatc Trying that but, not having same success. Color me dumb but, which folder are you deleting out? I've eliminated all of the v0.6.14 files I can find and have reinstalled v0.6.15 but, still having crash.
  9. I think this was something in the last update for Fo4 as there are a few of us having the same issue of crashing during the opening. Even if you do not select anything on the main menu it will crash at about the same time that it takes you to load up a save. I know myself and a few others have done a clean install on everything and also updated F4SE to the current update but, still crashes. My ini files appear to be in good order and was working before two days ago. So, not sure what was in that last Steam update but, it seems to have effected several people. Crash happens whether I use the regular exe or F4SE to open the game. I have reached out to Bethesda Support to see if there is anything in the recent update that may have been missed. I'll let you know when I hear back.
  10. Same here, since last update nothing but crashes. Even did a clean reinstall and same.
  11. Ok, so it seems we've pretty much narrowed everything down as much as possible. Thanks Augusta and HadtoRegister! I do appreciate your help! I'm gonna have to clink around with Win10 and find out what it is that's causing it to prevent the mods from coming through.
  12. Ah, I see, because waiting 3 days for a response from anyone outside of HadtoRegister is apparently expecting too much on a forum area designated for support and assistance. No worries.
  13. Thanks for the responses! :smile: Sorry HadToRegister, was not trying to be pushy with you, I do appreciate your advice and it did remind me of the custom ini file which I forgot about. However, problem does persist. I have unistalled NMM and Vortex twice now so, I'm fairly certain it's not them. This is a brand new machine. I had a Dell before but, it was pretty old and not keeping up with what I needed in design work. So, I replaced it with this HP Pavilion thingie. It's a 570-p047c with a GTX760 card in it. Not whizzbang like all the gamers out there but, not what I primarily use it for. My old machine ran NMM with all my mods just fine. So, Having ran through absolutely every avenue I can think of above, I think its the machine or the way HP has Win10 set up on it. Right now I'm playing well enough through my game. Would like to use some of the mods I'm used to using like the Beretta 9mm and it's replace all 10mm pistols. Lot better than running around with the brick of a hand gun. Other than that, I love the new set up, no bogging down in downtown Boston anymore! plus the 32" monitor helps. Still would be nice to get CBBE working so I can get my presets working again and my armor mods back. It was interesting loading my saved game and running around without any skin. Just hair, eyeballs and teeth. Whatever you guys think it might be, I'm all ears! :smile: PS: Oh, yes Augusta, "Literal" garbage...perhaps that will help generate more responses! :happy:
×
×
  • Create New...