GrantSP

For anyone that has been using either the Legacy Script fomod installer (NexusClientCLI) or one of the later MO builds (versions 1.2.15 onward), you might want to check in your temp folders such as: C:\Users\&Username%\AppData\Local\Temp\NexusClientCLI\There isn't any clean up code attached so all the mods you have been installing are found duplicated there. For those that do a lot of testing and/or installing it might be gigabytes worth of HDD space, as it was for me. I'm not sure if that is worth bringing to Tannin's attention, as a lot of users are conscious of where they want their mods to go so as to maximize hard drive space and speed, being able to specify which drive to use as a temp location during installation might be a good idea. Since I'm only on a one HDD laptop, being able to choose a location for these things is a moot point for me.

The current bug report also has users noting this but as you can see from posts here, it is reproducible in 100% of occasions. Perhaps you could post your setup on the Bug Genie and perhaps the reason for your error may be found.

Thanks, it is most likely my laptop not allowing me to use that key then, the same way I can't access the console with the ~ key on some of my games. (though Skyrim allows me to use it with no issue.)

It is noted as part of an existing, open issue regarding FWE not installing correctly. Probably is a good idea to make it a separate issue as now it seems it isn't exclusively a FWE issue. New issue here #972

Tannin has updated the bug report and stated they are different errors, I have added some more info about the install I have as the code he changed was specifically about Skyrim, I asked if that might cause the other games some trouble. If you want to keep progress with this issue I suggest checking the Bug Genie and we can let this thread go.

I believe the consensus is to use Sheson's Memory Block Log alongside the CTD and Memory Patch instead of Safety Load. You could always read the thread here about Safety Load and see where you experience falls compared to everyone else? Some swear by it, others say it isn't needed, others say it causes other problems. YMMV.

That tool is editing the Fallout.ini and FalloutPrefs.ini so it is those ini files. Make sure they are the files in the profile you have selected, not the ones generated in your My Documents folder. While it may be true you no longer get that error with an earlier version, that isn't to say the newer versions are faulty, just the error-checking may be more stringent. hmm... there may be more to this than the original bug report shows. I just tried it on all my MO installations and they all produce exactly the same error as yours, except for my Skyrim installation which loads but doesn't show the tabbed dialog to select either Skyrim.ini or SkyrimPrefs.ini. I'll reopen that bug report and add your new details to it. EDIT: It might be possible that my non-tabbed UI may actually be because of a version 1.2.15 change: Strange though that my Skyrim ini files are full of commented settings yet my other game ini files don't. EDIT: Idiot that I am, the Configurator never had a tabbed interface.

Hello, welcome to the STEP forums. Firstly we would prefer if you used Mod Organizer as your manager instead of NMM, it is better and easier to diagnose problematic mods. Putting that aside though you and I have the same situation. Even though I manually set my nVidia control panel to force the Skyrim Launcher to use the dedicated video card, it always only shows the Intel one. However, unless I am getting some really good results from the Intel card, the actual card that is used is the dedicated nVidia, in your case AMD card. I put this down to some poor code from Bethesda that can't detect the card unless it is actually used in displaying the screen in normal use. I have seen other tools also being unable to detect unless the specific 3D rendering is needed and then it kicks in and is seen. As for the ENB, it is also the same thing. I have seen a few comments on the ENB forum noting this phenomenon and likewise my actual results seem to indicate that it is actually the nVidia that is used. No matter what I have tried, from manually editing the ini files to show my nVidia card to running all the control panel tools available to set nVidia as the default for the Skyrim Launcher, it still never shows. I would like to have someone say something different and provide THE way to use it. That would mean I would be getting insanely better performance out of my laptop compared to what I have now. What I have at the moment is pretty good, anything better would be a bonus. As it is, I put it down to just a glitch and the real cards are being used.

Thanks, so I'm not mad after all?!

Ditto!

This looks similar to an issue posted on the Bug Genie that proved to be a problem with the ini files having descriptions attached to the values. Could you check both that issue and your ini files and post back here, as the issue was closed, with what the ini settings were?

I also tried the FWE part 1 and got it to install correctly but I had to bypass a check for Archive Invalidation. My MO profiles have that checked in FO3 but the script is checking for ArchiveInvalidationInvalidated!.bsa but that isn't the way MO does the AI. Is this just me? Have I overlooked something obvious? I'm not actually playing FO3 lately, just testing certain mods and MO's manner with it. Was I supposed to install that Archive Invalidation mod like I did years back?

This is a known bug that only affects a few users, myself included. Could you please provide a detailed list of all the paths for all the affected software, ie. Skyrim, Steam, MO, Wrye Bash and even the Internet browser you have as default. Additionally provide the versions for all these software. Could you look at this thread and see if your experience matches that of those posted.

It's actually quite easy, and you were almost there when you chose to right-click 'incorrect version' flag. Instead of asking MO to apply a different version scheme, in this case there isn't one since 3.5.6.0 and 4.0.0.0 share the same scheme, choose the next option, "Ignore Update". This will flag the currently installed version as the one you want and display it in green but it will also check for a newer one and if one exists, ie. 4.0.0.1 or greater, then the "Update" option will show. Basically, MO is showing you what it thinks is the case but it also concedes that humans are better at deciding and allows you to override its decision.

Oops! Didn't even bother checking the name. No offense meant.

You may be a little late to the party. I think you will find this thread is the same issue. Perhaps a little searching first.

That's very interesting Kelmych, there is already an issue about installing FWE posted on the Bug Genie, Can't Install Fallout Wanderers Edition 6.0 I had noted that the new fomod installer didn't solve it with 1.2.16 but this new info might help track it down. If you like I can attach your comments, maybe you could also keep track of it too?

Is Busworld that mod that has issues with the way you exit the carriages? It's been a while since I had it and can't recall. I just remember entering through the door having a look around the carriage and exiting and finding myself on the otherside of the carriage.

Good, glad it is sorted out. FWIW, @Tannin has a replacement hook.dll on the Bug Genie that fixes this issue so I imagine 1.2.17 isn't too far away.

hmm... well that throws that idea out of the window. I too have my Fallout 3 in C:\Games\. So Nozzer66 you and I have MO set to Fomod Installer == preferred is false

There must be something about the location of the temp folder that is created then when that legacy script runs. We all must have different set ups and the locations for me must be working more often than for you guys. Since according to the legacy mod page it only added that function it couldn't really be anything else could it?

I did choose that name for a reason. Many times it has been shown I have been 'mistaken'. I'll go with your reason though, I was just tired. Good to see you have a sense of humour about all of this. I would hate to get off to a bad start.

I always use the archive version, I'm a bit wary of any installers, I like to know exactly what gets placed and where. BTW, I PM @Reunion, the Legacy Script author, and asked if he would be able to look into writing/assisting with a new plugin.

Judging by the screenshot I would say that version of LOOT isn't version 0.7, but 0.6. That means it would be something strange with the individual setup, as I have both versions and have never seen this blank page issue.

Hello @fore Apologies if the content of this thread seem a bit like an attack. As my later posts here, and also those in Nexus show, I have a great deal of respect for your assistance. It was a mistake of mine in not installing 5.2 over 5.1 correctly and in saying what I did in the post you have quoted. For that I can only offer an unreserved apology. While not trying to justify my actions, the stickied post or the FAQ you have doesn't say that this warning is only in 5.1 and 5.2 resolves it. Going on the information you provided me in the Nexus thread I would conclude it, the warning, is actually an error and not the users fault, whereas the FAQ and sticky post imply a fault with installation due to uncommon Skyrim installs, usually from pirated copies. Since the registry setting I provided you results in no warning with 5.2, I must conclude 5.1 was in error. At any rate, due to your diligence and patience, this can now be considered a non-issue and can justly be put to rest. Thanks again.