Jump to content

GrantSP

VIP-Supporter
  • Posts

    4,289
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by GrantSP

  1. If Steam is saying you need to acquire a new file on each verification then I would look at your install for an issue. There really shouldn't be any reason why files are being changed/removed. The only time a file should be different is after you have cleaned them with xEdit. I note this part of you OP: It may be that this is the cause of your issues, if your Windows registry is looking for an earlier install of Skyrim. You are going to have to go back to a basic setup and check your system from there. What happens when you remove all additions to your Skyrim install, ENB, SKSE, etc. and start the game from its launcher? If you can successfully start the game from the vanilla launcher start adding in these extras one at a time and try to start the game each time. If you cannot start the game from its launcher with just the vanilla game, then your install is broken and will need to be purged and re-installed.
  2. Anyone know of a mod that allows for a peaceful resolution if Elder McNamara has already been ousted from office before meeting Col. Moore of the NCR? I found it a little strange no peaceful resolution could be had if he is missing from office.
  3. You and I clearly have a difference of opinion as to what constitutes a significant change. The ethos of MO is to maintain a pristine Data folder so that nothing the modder/user does will affect the vanilla game, this flys in the face of that. Take a user that is migrating to MO and is still examining the details of the program. Suppose they have cleaned their plugins and, for whatever reason, starts a vanilla game from the desktop. The result: instant crash with the thought in their mind now - "MO stuffed my game". Every other edit made to plugins in the 'mods' folder result in the original being updated and the backup being created. To have the original plugins in the Data folder moved is counter-intuitive and needs to be addressed. Anyway, this whole discussion may be moot if @Tannin's comments in Bug Genie are anything to go by. It would appear that an entirely new, rewritten hook library is to be released sometime in the near future. Let's see if that procedure makes a change to this.
  4. You haven't really given us much to go on here. I'm assuming the game is Skyrim, but it might be anything. Is this a recent change, if so what is different with your setup? Have you checked the drivers? Is this a heavily modded game or does it also not work with just a 'vanilla' game? Does it make a difference if the game is managed with MO or not?Anything extra you provide will help.
  5. As much as I don't want to question this, I will. While it may be the case, this represents a significant change in program behaviour and I don't recall seeing any mention of this in changelogs. We need to have definitive answer for this since my hardware has remained unchanged and the behaviour is different with the later versions. If this behaviour is hardware dependent, then fine we add a note to the guide. If it isn't then we also need to know what conditions trigger this difference. Just downgraded to 1.2.18 and cleaned Update.esm and this time the file in 'Data' is being updated and only the backups are in 'Overwrite'. Reverted my install to 1.3.8 and then cleaned Dawnguard.esm and MO moved the cleaned ESM out of 'Data' into the 'Overwrite' along with the backups. For whatever reason MO 1.3.8 is moving the file but not copying it back. 1.2.18 is just editing it in place and placing the backups into 'Overwrite'.
  6. Yeah, after a few days of work on their end, 'My Content' is back also. Just too quick to assume they were dropping it. Actually I kind of wish that did drop it, now my routine has been drawn back into checking redundant threads just because they were commented on recently. I so wish there was a way to prune some of the deadwood from that list.
  7. You can also wait a while for the maintainers of the proccers to fix the issue. The Requiem tool has apparently been updated so the actual fix isn't too detailed, just needs someone to do it.
  8. Which version of MO are you on, the 1.3.x series of MO have resolved all the BSA issues from the past. Additionally you should check that each BSA is actually checkmarked, just in case one or two are missed. MO's 'Manage Archives' doesn't always check them all.
  9. The established method of installing SKSE using MO is described here along with the method of ensuring you have a valid 'skse.ini' file for the game to use.
  10. I've been following, from afar, the discussion and it looks like the Requim tool has a fix already so the other SkyProccers will no doubt shortly fall into line.
  11. See what happens you start asking around for stuff! It just starts coming out of the woodwork. Fantastic. Interesting comment he makes about @PuceMoose's "fix".
  12. It looks you may have updated your current install over a previous one and there is some 'cruft' leftover. Open your MO folder and delete everything except your 'mods', 'downloads' & 'profiles' folders and your ModOrganizer.ini, nxmhandlers.ini and if you have one, categories.dat. Open the latest MO full archive and copy everything from that archive into this now cleaned folder.
  13. Check all BSAs in the 'Archives' tab.
  14. The screenshot shows the 'Run' option as "Fallout3" and not "FOSE", is there a reason for that? Was that just what it was when you took the shot or are launching via that run command? Also I am curious, did you make the change to use the 'Script-extender' workaround or was that set when you installed MO? If it is set that way on install we may need to change that.
  15. What MS is catering for isn't just an easy way to maintain their OS across platforms, but an easy way to maintain their "support" for users that are either oblivious to or unconcerned about, the differences. Sadly the average user of any computing device today has next to no knowledge of what is an UI or widget or a processor or a graphics card or ... You get the idea. For such a large conglomerate that caters to many differing formats I can fully understand the need to bring everything onto the same page, it just makes sense. (to me)
  16. I would like to see your ModOrganizer.ini to check what settings you have to call xEdit, if you don't mind. The only thing different in your video to what I see, apart from the obvious of course, is you are on Win8/8.1. It might be the case of the OS and permissions with MO placing the edited file in a secondary location if the first refuses. (that's just my wild guessing!)
  17. Check the actual argument that you have in the shortcut. According to that log you have it as: command line : "D:\Games\Steam\steamapps\common\Skyrim\TES5Edit_3_1_1\TES5Edit.exe" -o:'D:\TES5LODGenOutputTake note of the ' immediately before the output folder. It should be: command line : "D:\Games\Steam\steamapps\common\Skyrim\TES5Edit_3_1_1\TES5Edit.exe" -o:D:\TES5LODGenOutput
  18. Note the highlighted words in the first line of the MO wiki section for the 'Overwrite'.
  19. Can you try and start the game using the 'Script-extender' workaround? Open "Settings -- Workarounds" and select 'Script-extender' from the "Load Mechanism" selection menu.
  20. Can you post which version of MO you are running because there were a lot of changes to the fomod installer in the 1.3.8 version? If we could clarify that this is an issue or not with the specific version.
  21. That would explain why I haven't seen it, I use the "Dead" version.
  22. Thanks for that. I changed the original post.
  23. No, that isn't what I am seeing. The latest versions of MO are moving the cleaned ESM to overwrite, not copying it.
  24. I just checked the cleaning instructions in the guide and they describe exactly the 'new' behaviour and how to have the correct files in their place. I hadn't read the instructions for many months and I was going off my memory of what they said so that would allow for some strangeness in observed results. You are correct about the TES5Edit cleaning steps in the separate wiki page, they are outdated and need revising. Keep in mind, in the STEP instructions you need to firstly make a backup of the original ESM and it is that file that needs to be placed back into 'Data', not the cleaned one in 'overwrite'. That's my bad, I usually don't bother with having the original AND a cleaned file. My apologies if I caused confusion. EDIT: Those instructions are now updated.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.