Sarcasm

I can provide details. This thread is solved now so I'm not sure it's the right place, but I'm not sure where to make a new thread for it so I'll just leave details here. I first ran into issues with these mods two years ago when I started using MO, and since neither mod has updated since then the problems have not disappeared. Weapons of the New Millenia uses some custom super installer that does not work in MO. It just opens the data folder and skips the installer. You can install it manually this way and hide the unwanted plugins with the Information tabs, but I cannot find any way to make the installer work. The archive seems to be packed in such a way that the installer cannot open in MO. Project Nevada & MCM are more complex. I cannot get them to run together without in-game popups for Project Nevada xml errors. Project Nevada comes with its own MCM that seems to conflict with the standalone MCM, which fails to overwrite it no matter what order the mods are placed in. Never found a solution to it despite trying countless different options. I've played over 500 hours of New Vegas with them installed this way, so I think it is basically harmless. Maybe.

Oh yes you are right! I must have missed it due to being grayed out. I thank you, I figured it was something simple I was overlooking. I have those mods in data since I cannot get them to install correctly with MO. Millenia's installer simply does not open in MO. Project Nevada & MCM give me .xml errors if either is installed via MO. I thank you again for the solution to this

Hi, I recently moved my Mod Organizer install for New Vegas from my old computer to my new. I've done this before with Skyrim and only had issues with profile load orders. However, this time around it seems Mod Organizer for NV is not finding any pre-existing directories in my mods folder. As you can see, the mods folder has almost 40GB worth of files, but the Mod Organizer window is empty of any MO-mods (a few FOMM mods that do not install correctly with MO are present.) Upon copying it over I reset all the file paths, and they look correct now. All the exe's are properly pathed and newly installed mods will show up in MO, but not the old ones. I am too faint of heart to rebuild the grand load order I had before. Is there any way to get MO to find my old, previously installed mods? Thanks.

Yes, it seems that this was only temporary. I knew something was up when I saw a streamer getting the same issue with failing to log in. It looks like it was a problem on the Nexus' end that was fixed, whew.

I've been downloading from MO for days, but today MO has decided it no longer looks fondly upon the Nexus. It refuses to let me log in or download from the site anymore. Here are two Logs of What Happens when I Try to Download. I've gone through the sticky about Google Chrome and done what it ordered, but there was no change in MO's attitude. I do not understand what could have transpired overnight to cause this to happen. Last night, downloading fine. Today, cannot download. Cannot even log in. I'm not sure why it says "user is not premium" since it is a premium account. How do I put a stop to this devilry?

Unfortunately turning off the proxy library did not stop the error from appearing. The ENB preset is using d3d9injFX.dll as the proxy library, but the problem is caused by dxgi.dll. I'd rather not turn off the SweetFX injection, since as TechAngel85 said it could be applying important aesthetics. I'm not sure what it is applying exactly or whether it is possible to find out. I've always used Project ENB, probably for 3 or 4 years now. It seems strange that upgrading to a better video card would stop me from using it as intended. I would much rather figure out how to stop this error because to me, changing presets is not an option.

Here is enblocal.ini. Some notes: STEP wiki says UsePatchSpeedhackWithoutGraphics=true , UseDefferedRendering=false for ENBoost, but ENB presets do not work with either of these options set so. Now I'm typing in green. The tool linked for VideoMemorySizeMb= returned 4064. That is 3714 following the STEP ENBoost instructions. I consulted numerous graphics guides to try and fix my error. Every such Guide I read said to use 6016 for 6GB of VRAM, so I changed it to try it. I saw no difference between the two. Setting it to extremely high, DX11-level values gives C++ runtime errors in game. Curious as to why ExpandSystemMemoryX64=false is recommended, but I trust in the wisdom of others to set it so. On an unrelated note, as of a few moments ago my Mod Organizer no longer logs in to the Nexus...

My Skyrim folder. The ENB added many files. From what I read, dxgi.dll is some sort of injector for rendering SweetFX. I don't know what most of that means so I will not pretend to be an expert. I'm not even sure what SweetFX is, because I don't see a difference with dxgi.dll renamed or not. The only "working" solution I have seen mentioned anywhere is to use old video drivers. Obviously, this is not ideal so I'd very much like to find an actual solution to stopping this error on the latest video drivers. Edit: I should add an explanation for ENB FXAA SweetFX manager. It simply stores ENB presets to be removed and added easily. I've completely re-installed the ENB so it doesn't seem to have anything to do with this.

It seems to be caused by video drivers. I completely uninstalled my current drivers with Display Driver Uninstaller, and launched Skyrim since it doesn't require drivers to see the main menu. It reached the main menu three times with no error. I reinstalled my latest NVIDIA drivers (361.43) and the error returned on launch every time. Uninstalled them again, and installed older drivers from June 2015 (353.30). No errors anymore. I see on several forums that NVIDIA released new drivers that broke dxgi.dll. Now two questions remain for me. First, if it is driver related, why did I have no issues at all for 2 or 3 days? It was only when I copied over an install from another disk drive that this error began. Second, is it worth it to run old drivers to avoid this problem? Is it better to use old drivers and have the ENB as intended, or is it better to have up-to-date drivers with dxgi.dll disabled? What does this dll even do, and how severely might it affect the look of the game? Edit; Okay that's four questions

Ah okay, thanks. Still though, now I'm even more confused as to why it worked once without error. Any more suggestions on how to stop that error without having to rename / delete dxgi.dll from the ENB? I've noticed no visual changes in-game from not having dxgi.dll working, and to be honest I'm not terribly familiar with what SweetFX is and whether or not the ENB's incarnation of it will work without that file. But I would like to be able to run the ENB in the intended fashion. I've used Project ENB for years and this is the first time I've ever seen this.

Thanks for your response. But of course, more strangeness. Verifying the cache downloaded 1 file and fixed the first problem. While looking for the SMIM forge meshes, I decided to be done and go to bed. Today, however, the first problem is back. Everytime I launch Skyrim, I get the dxgi.dll error. Everytime I verify the cache, 1 file fails to validate and is reacquired. Then the error still persists. Each time I verify the cache, 1 file is reacquired. I am confused. As for the lens flare, will hiding just the forge meshes stop this completely? There were other things causing it besides forges, like carriages and just random rocks in the middle of nowhere.

Hi, there I am having two problems with my Skyrim at this moment. Both appear to be ENB-related. The first problem just start a few moments ago. It is also featured in another thread here, but is not the topic of that thread. When I start Skyrim using Project ENB, I receive the following error message: This only just started, and I'm a little embarrassed to say how it started. I did something foolish and I'm not sure how to undo it. After two days of tinkering with lighting on my install and failing to get it to look how I wanted it, I became impatient. Soo...I copied over my Skyrim install from another computer, pasted it into my steamapps\common after renaming my current install, and launched it to see how the lighting was and which mods I used. When launching this foreign Skyrim install, I received this error for the first time. The game still worked, but some things looked odd in game. Namely, actors' skin (including the player's) looked very off, like cardboard. I renamed dxgi.dll in the Skyrim folder to dxgi.dll.bak and it launched without error, and everything seemed to look correct, but I worry that my ENB will no longer render SweetFX now. This file is created by Project ENB and is not native to the Skyrim folder. Even after undoing my mistake and returning my normal installation, I still get this error unless I rename dxgi.dll. I realize I made a mess of things, but does anyone have a guess as to how I can launch my game without having to rename this file? I have the most up-to-date NVIDIA drivers. I cannot fathom that it could be driver related since the game has run fine for three days now with Project ENB, and I have not seen this error until I decided to copy over this Skyrim folder. _________________________ My second issue is more minor but perhaps more annoying. Sometimes when wandering around, I get this crazy, random lens flare effect. It radiates out of certain objects and sometimes out of what seems like random areas. I managed to capture some screenshots of it at the local Forge, as forges seem to cause it all the time: One Two Three Four Five Six Seven Eight If I get very close, it messes with the lighting and makes day appear as night. Once the flare appears, it usually disappears shortly after and does not return until Skyrim restarts. The last five screenshots were all taken during the day of an un-shy flare that did not disappear when I got closer. It often radiates from forges and carriages, as well as from seemingly random locations. What is the world is this, and how do I make it go away? If there is more information I can provide apart from description that would be helpful, do tell. I would be infinitely grateful for any help, thanks.

That sounds about right, I'm aware that coc'ing skips startup scripts but it is a quick way to test for FPS, stuttering, and general graphical stability in specific areas. What concerns me is having to install a non-Step mod, Alternate Start, to test a Step install. Is this an endorsed method of stability testing? If so, then I suppose it's not a big deal, even if it does add time to each startup.

Oh wow, you are right, it is not infinite but rather extremely long. It took 6 or 7 minutes to finally load a coc character from the Main Menu to qasmoke. Not infinite, but it may as well be since coc'ing from the main menu is unusable on that kind of time table. By comparison it took 40 seconds to load a New Game, much longer than normal but not overly long. I saw that New Games worked before posting, it's coc'ing from the main menu that concerns me most. What is it about coc specifically that causes it to be so drastically longer? The problem is that this greatly slows down testing for bugs and crashes; I'll have to start a new game each time and load another save to coc to the area I want to test. Not to mention having to temporarily install Alternate Start just to get a character into a usable state without having to run through the intro. Is this what everyone who installs STEP does now to test their game? That seems cumbersome and uncharacteristic of STEP Core. Were it Extended it wouldn't bother me so much, but now installing even basic STEP involves tanking all my load times with new characters. This is uncomfortable to me, particularly due to the lack of any mention of this during STEP installation. Is there some way to stop this?

Not sure if it is proper to post directly in this thread itself, but after searching through all 17 pages and finding nothing, I simply have to comment on this. Am I the only person who receives an infinite loading screen every time I try to console coc somewhere from the Main Menu with this mod loaded ? I see on the mod's Nexus page, this issue is directly recognized and acknowledged. I'm extremely apprehensive about a mod being admitted to STEP Core which prevents me from quickly testing for stability by coc'ing from the main menu to an area I need to test. Even with Safety Load, SKSE.ini, 6gb of VRAM - infinite loading screen every single time. Is there any recognized fix for this? Any mention of this issue is absent from the STEP notes for the mod, which seems an oversight. I would be grateful for a proposed fix for this, or any word on whether it can be left out entirely without disqualifying the Core patch. Thanks.

Very strange to see this, and posted only a day ago. I'm having a very similar problem to the OP. When I have d3d9.dll in my Skyrim folder, I get some strange behaviors with my Skyrim. The first thing I noticed is that if I try to 'coc whiterun' from the main menu, I instantly CTD. Every coc I tried from the main menu crashed except qasmoke and volunruud01. As soon as I delete d3d9.dll, I can coc around. I wish I knew more about ENB so that I could help, but I suppose I'll just keep watch on this thread for now and try to mess around on my own. I have some other issues as well, like a random, massive FPS drop in Helgan just before the carts stop in the intro, so I may make a thread of my own if I find more problems.

Oh my, I'm not sure how I didn't see that while Searching. Thanks I say. The messages threw me off since STEP specifically mentions in an installation note to hide a file in order to avoid MO popping up with a conflict. Given that, the fact that it didn't mention these conflict messages made me think I did something wrong. I still have a lingering question about the Core Patch. I know partial installations are not support and not tested, but I'm still curious. RaceMenu is not a master of the Core Patch, so are there any guesses at whether dropping RaceMenu but keeping the Core Patch would cause problems ?

(1)I'm following STEP for my second time. This time I followed everything 100%, to the letter - even the stuff I don't want to use when I play - having learned from my mistake long ago when I installed STEP for the first time and picked and chose what I wanted. However now that I am finished with installing all plugins, I find myself getting a great deal of load order problems reported by Mod Organizer. This Screenshot shows my issue. In the screenshot I have two mods disabled - Follower Trap Safety and The Choice is Yours - because I do not plan on using them and I don't want extraneous scripts adding to script lag. However even with them activated, I still have the same six load order issues listed by MO. It tells me these 6 mods are all out of order, despite having them ordered in the left pane exactly as they are listed on the STEP wiki, and having sorted them via LOOT with all the proper metadata edits. So I'm lost as to why MO is reporting my left-pane load order is wrong. It's probably something simple, but I'm not familiar enough with STEP to understand why these errors are reported. (2)Finally, I have another question that pertains to STEP Patches. There are several mods in STEP Extended that I do not plan on using when I play, so I can rule out the Extended patch I assume. I had wanted to use the Core patch, but unfortunately I see RaceMenu is a Core mod. I prefer Enhanced Character Edit and won't use RaceMenu when I play, so does this completely disqualify me from using the Core Patch? The easiest way to put it is: are there any Core mods that are excepted in the Core patch and not required in order to use that patch? Thanks for any assistance. I have my computer specs here since the forum told me to post them, but they're likely irrelevant.

While I try to do that, I have a question. How does Mod Organizer store its load order? I see that my main profile has no loadorder.txt file in Mod Organizer\profiles anymore. I thought this was how it stored load order, but apparently not since it would not have any load order at all without a file. How do I back up my load order and create a .txt of it?

As I said, TTW installs just fine via Mod Organizer. The TTW developers themselves recommend using MO to run the mod. But two mods would not install via MO correctly for me: Weapons of the New Millenia and Project Nevada. Project Nevada had some problem detecting the Mod Configuration Menu through MO and kept giving me an in-game error about .xml files which would then break MCM entirely. Installing both through FOMM makes them work. Did I do something wrong or do these two mods not know how to talk to each other in MO? So if WotNM can only be installed manually, and manually installed mods cause MO to scramble its load order when switching profiles, do I just have to deal with this then ? Though I'm afraid the damage may be done either way. Now that MO has messed up my load order, I'm getting problems in game with invisible ghouls and cannot figure out the cause or what my load order was before. I played for 60 hours before MO scrambled my load order and never saw this invisible ghoul problem. A huge pain...

Oh well this might it be then. I have TTW installed through MO, but MO doesn't know how to handle some New Vegas mods so I had to install them directly to Data with old fashioned FOMM. Weapons of the New Millenia for instance simply does not work with MO at all, it uses some fancy custom installer that fails to load in MO. I had to install that to Data. So switching between profiles with mods installed outside MO will cause messy things with my load order, even if those mods are active on both profiles?

I'm not sure how to explain it. My Skyrim MO works fine when switching between profiles, and uses similar programs in much the same way (CK vs GECK, TESVEdit vs FNVEdit, etc) so I don't think it's a matter of being installed incorrectly. I have four profiles: my main profile plus two copies of it - one a backup, and one for tinkering around without affecting the main profile. I haven't used either in a while. Then I have fourth profile of very basic mods to test mods on a low load order. Whenever I switch to my basic load order profile and launch the game, the GECK, or FNVEdit, the load order on my main profile becomes disorganized. It's solved easily by just copying the loadorder.txt from my main profile between switching, and then copying it back in when I'm done. Still, it's another step that shouldn't be necessary. I organize my load order by hand, since it seems that no auto-sorter understands how to sort Tale of Two Wastelands or FOOK-PN Convergence, and they turn my load order into a mess. So it can't be that, either. I'm not expecting any changes I make on a profile to carry over to another profile, that obviously defeats the entire purpose of profiles. Yet for some reason using one profile messes up the load order of the other, but it was my understanding that MO is supposed to keep everything isolated. So why would launching an executable in one profile change the load order of another? It's not a huge problem since I can copy the loadorder.txt, but I'd still be thankful on any suggestions for why this happens.

Simple and infuriating problem. When I switch to a different profile and launch any executable with that profile, be it the GECK, FNVEdit, or the game itself, the load order on my main profile is scrambled. Esm's are jumbled around and moved to the bottom of the esm portion of the load order and some esp's are moved to the top of the esp portion of the load order. Obviously this is a huge problem that will cause instability within saves if the load order keeps changing. How do I stop this from happening?

I'd like to reiterate that I did follow the STEP setup for all these utilities to the letter, and SKSE and ENB especially since I know how important yet finicky they are. STEP has been my go-to for setting up both ENB and SKSE since I discovered STEP. Truthfully though, trying out random stuff posted on forums is what got my game running stable for the time being. Whether that changes I'll just have to play and see. From trying the game out for much of the day, I can say as a simple fact that if VideoMemorySizeMb= and AutodetectVideoMemorySize=true are set as STEP requires, then my game crashes after around 35 minutes without question, no matter what changes are made to other settings. Turning off autodetect and setting VideoMemorySizeMb=16384 resulted in the game running flawlessly for 3 and 4 hours straight in two different tests. Two other tests were interrupted by nosy Windows Update restarting my computer while I was away, but I know they both lasted for at least 2 hours each. Again, setting enblocal.ini as STEP says causes the game to crash on a regular basis after about 35 minutes; you could almost set a clock to it. I'm going to start a game and actually play. If I get no issues after a few days, then I'll come back and mark this as answered. Really though, thanks for all the help that people have provided thus far! I feel like the game is actually playable finally, and that's a huge relief. Hopefully it lasts, ha.

The Good News: The runtime errors seem to be gone. I haven't seen them in over a day now. The Bad News: Instead of runtime errors after 30 minutes, now the game just closes after 30 minutes. No error, no "not responding", no message of any kind. The game just disappears. I'm not sure what to think. I've been testing the game a lot today, just letting it run idle. I had it running for hours at a time until about 12 hours ago, but ever since for some reason it crashes after 30 minutes or so. I didn't even change any settings in that time. I'll leave the game running, and when I come back it's not running anymore. No error or crash report or anything, the game just isn't there anymore. I'm going to change the memory patch back to 768/256. I'm really confused, for a while I thought the problem was fixed. But now it seems to be back just in a different way, with the same behavior on auto-allocated memory and on 16382 fixed.