GrantSP

No, not a bug. About your log being filled with 'cannot resolve' references. The most likely candidate is somewhere on your system is some software that uses OpenSSL. You will need to go to https://slproweb.com/products/Win32OpenSSL.html and install the Win32 Open SSL v1.0.2a Light package. This is related to the third last question in the FAQ on the MO description page.

I'll look at the CPU cooler, its about $45 so I can afford that. @Greg You smoothy, always keep the wife on side. Anyway, she already had her gift, a cruise to South Pacific a few months ago, so I figure I'm good for a few more goodies for me. I've updated the build and will examine the peripherals next. I had the Logitech stuff, @Phazer has the cheaper CM bundle, I would like a nice mechanical keyboard. I'm hoping I can get all this done to allow me a few months Witcher III time before Fallout 4 hits the stores.

My wife is going to love you. I'll take that advice to heart and stick with the EVOs for the storage. 'Crazy Aussie' indeed! I'll take that as a compliment.

Next big change I've decided on is the SSDs. The Asus Z97-A offers a M.2 PCI-e connector that provides 10Gb/s so I'm going to go for a SSD to fit that. Plextor has a drive that fits that's $349 for a 256Gb, a bit expensive but may be a good choice.

derp! :facepalm:

I'm not sure this is actually an issue with using FNIS from inside MO. I have seen a few mentions of various animation packs that don't seem to be seen by FNIS, and I have personally experienced at least one example, but I believe this behaviour also is seen when FNIS is run outside MO.

hmm... I've just now updated DSR, including the hotfix, and now I'm getting a 'Java Virtual Machine Error' dialogue with the text: "A Java exception has occurred." Never had those before, any ideas? Happens regardless of the method of calling the *.jar, either directly or via the batch files.

The 'webcache' folder I am referring to is the one generated by MO and is found directly under the main MO folder. Have you cleared that folder?

So we now have a different problem. The original issue was the older MO couldn't order the latest USKP because of the large record size in the latest version. MO 1.3.8 handles those plugins correctly so USKP is now sorted in the correct order. The patcher throwing an error about the UDP is another story. You are running the patcher from within MO, yes? I can't make assumptions here, I have no idea of your level of MO knowledge. You have all the latest versions of all these mods, USKP, Dual-Sheath patcher and MO?

That's okay. You won't be able to read it with Notepad++, its a machine code report. Since the filesize is only 0kb it's probably empty anyway.

You will need to use the latest MO.

Check the input path in the top field, I see that sort of thing when the output path has those folders but the input path is only selecting some of them. I'm with you though, DDSopt is not the easiest to use. For that reason my solution may be completely off-mark.

This is to outline what the code inside MO that generates these PMOP messages does and why. Firstly your computer will not explode, burst into flame or otherwise if you disregard those messages, your game however MAY suffer from some bugs, unless you absolutely know what you are doing with those mods. The official stance for MO is to allow the MO warning dialogue to have the mods (left-hand pane) to be 'fixed'. STEP guides may provide another arrangement and therefore you can disregard any potential errors. PMOP = "Potential Mod order problem" The operative word here is 'potential'. There are no deep, fancy searches made inside the contents of your scripts to determine whether a mod should or shouldn't be where it is placed, that is for the user to determine. The steps involved are as outlined here: MO searches the list of mods for those that contain scripts (*.pex) and uses ONLY THOSE mods for the next step Using the order of the plugins (right-hand pane) as the desired order, it presents a series of moves to arrange the mods (left-hand pane) to match. A dialogue is presented that shows the mods that don't match the order as expected and the steps needed to arrange correctly. MO then checks the order again and if all is fine, the error message is removed. Note: The code needed to slimline these steps would be complex and extravagant. Often the provided list of steps needed to 'fix' the mods can be done by moving just one or two, not all of them. However, doing so will not break your game. After installing your mods, it is usual to arrange the plugins into the correct order, either manually or with a tool like LOOT. LOOT uses an extensive list of sorted plugins to assist this process, there is no such such list for mod order in MO's left-hand pane. It is after this step the order of your mods needs to be examined. Do it manually or allow MO to aid you, but you must also ensure the left-hand order is correct. Why does MO make these checks? As the dialogue says: Isn't that something we all want, a reliable working game? There is no nefarious intrusion on your modding going on, simply another tool to aid in ordering your mods. Doesn't LOOT already do this for us? No. LOOT deals only with the plugins (right-hand pane) and therefore has no possibility of handling the order of the mods. (left-hand pane) I didn't have to worry about this with NMM/FOMM/Wrye Bash. What's the big deal? That's right, you didn't. You also didn't have the ability to move your mods that contain these assets around to provide the best installation. All other managers rely on the actual install order and if you make a mistake, you have to start over. Because MO allows you to do this it also provides a tool to check for any errors. * Note the proviso mentioned in the first comment below. Okay, so if I do ignore MO's warnings, what will happen? Good question. Depends on what is provided by the 'winning' mod in the conflict. Remember all MO is doing is checking for the presence of scripts that are the same, it makes no line-by-line comparisons of the actual script code. If the scripts are identical, nothing will happen. If the scripts are different then the desired effect will either be missing or broken somehow. MO doesn't know there will be a problem, that's why it is called a "potential" problem. Yeah, yeah, but these messages annoy me. Hmm... easily offended are we? Not to worry, MO also allows you to disable ALL helpful messages if you desire, just examine the 'Settings'. So, next time you see this error dialogue, stop to think what is actually being offered to you. Here is a helpful reminder to re-examine the list of mods/plugins and check if there are issues. Have a look at the amount of code involved in the LOOT project to see what is needed to have software make all these checks for you, and that is only for checking *.esp/esm conflicts. Imagine what would be needed to create code that checks the internals of scripts or other assets to order them correctly! While MO isn't quite performing those sort of tasks, it is doing the next best thing - warning of potential problems!

Most, if not all, issues with Nexus related functions not working inside MO can be resolved with a clearing of the 'webcache' folder. Ensure that you have the correct login details entered into your MO settings and possibly do a restart. A user posted this same issue on the Bug Genie yesterday and then updated it with the fix coming after a restart of his system.

That's the file. No, a clean start won't refresh that dump, it is a solid piece of evidence that will not change. So you can post that dump to @tannin and advise that it isn't a repeatable crash or just put it down to 'one of those things'.

Actually those messages aren't pointing to any evidence of your FOSE crashing, you will need to post the full logs.

Can you do system wide search for *.dmp?

Worried, no. Amused, yes. They go to all the trouble of installing an intrusive taskbar app that glares at me to upgrade, but it all it tells me now is nothing new. I'm content with Win7 on this laptop but I'd like to see how things pan out so I can choose what to put on the new build without having to do too much messing around.

I do know they had some delays with Cortana for some markets, maybe my accent is playing havoc with their software.

I must be way down the line as far as updating priority is concerned, it's 2nd August already and nothing whatsoever has changed on my system, not even a download of the required files to that GWX folder.

Moving your Skyrim install resulted in an incorrect registry setting. MO makes a check in HKLM\Software\Bethesda Softworks\Skyrim\Installed Path and I am assuming whichever way you moved it didn't update that registry setting. The verification by Steam will have no bearing on any files other than those provided by Steam, so nothing MO had installed or modified was touched by that step.

There's probably a dump file created with that crash, you will need to send it to @Tannin via email to: sherb at gmx.netOn another matter, another user has posted here that he can't even get MO to start, could you provide any ideas about MO and Win10?

Well the only clue we can go on is the fact Win10 was installed in between it working and now. I don't have MO installed on a working Win10 system but many here do and don't see any issues. There have been statements about Win10 being very restrictive with permissions, maybe do a double/triple check that that exe has full permission on that folder. Are there any logs, no matter how small, created in the MO folder? I'm really at a loss, there should be no difference in Win10 and Win8 with how MO runs.

My mistake, I wrote 'mm' instead of 'cm'. :confused:

The maximum card length the case takes is 414mm and the R9 390 is only 287mm 28.7mm, so if I take their specs as gospel it should fit. Thanks to Nozzer for spotting the mistake.