Jump to content

GrantSP

VIP-Supporter
  • Posts

    4,284
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by GrantSP

  1. MO2 is what is called a "portable executable", ie. it isn't installed by an installer and everything needed to run it is in the one location you installed it. This means you can simply move the entire MO2 folder to a place somewhere else, I suggest simply putting it off the root of a drive you have: e.g. C:\MO2 There is a folder in %AppData% that houses the settings for your modded games, but as long as you set the settings correctly it will "just work". Those settings are accessed via the settings inside the MO2 UI. Whilst MO2 is a different tool to MO the main help file, and the wiki housed here on STEP, is still applicable for most things. Check the online help and the FAQ for common things and feel free to ask for anything else.
  2. I'm seeing a t lot of discussion about FNIS and MO2 in the MO2 Discord and no one there is having issues, I suggest it is because they do not have MO2 installed into the Steam folder structure. Move it elsewhere and check how you go from there. MO2 can be installed anywhere else, as long as it isn't in a UAC folder, ie. one under control of Windows.
  3. It's alright @Tzefira, I wasn't having a shot at you, just a friendly reminder to all. STEP appreciates everyone that comes and lends a hand with modding.
  4. MO2 should NOT be installed into the Steam or the Game folder. This is a documented issue that has been discussed with the devs and the best option is to install MO2 somewhere away from those folders. Also there are no justifiable reasons to run MO2, or for that matter any game tool, as administrator. If you are having issues with permissions the fault lies in your Windows system,or the way your Windows account is set up, and that should be fixed. Whenever a tool is run as admin the properties on it are now going to be at odds with any other tool that tries and accesses that file that doesn't have admin rights.
  5. Well I've decided to bite the bullet and create one as it seems so many users like their support given in realtime. Discord MO1 Server I can't guarantee that all posts will be given satisfactory answers, ie. those that fix whatever is broken, but it will serve as another avenue for MO users to get support. Feel free to share it and join up if you wish. Many of us have now been using MO for many years and it is still a viable manager even with MO2 development coming along at a cracking pace. If we all share what we know, nothing can stand in our way. Mwuhahaha!!
  6. That server is where the devs are discussing the latest bugs and releasing test builds. Testers are encouraged to use them and provide feedback. I believe the Nexus downloads are a little behind the time and there may be a fix for this issue. I do recall some chatter about this lately. Sadly my desktop system is broken and I am unable to do any testing on MO/MO2 until it is fixed so I'm not paying as much attention to fixes as I used to.
  7. I'm going to close this thread as you have a duplicate issue open in the MO forum where it should be.
  8. I'm currently off my desktop and on my backup laptop which is a Linux machine, so I can't offer up-to-date insight on this. Have you tried in the Discord server? Here's a link if you haven't been there yet. https://discord.gg/MM5SA5
  9. If there was a recent update to either Steam or SSE you may need to run the launcher from the desktop to re-establish the correct registry settings.
  10. This isn't really a MO issue though, this is applicable to any managed game. Moved to General Support.
  11. Hey @Nozzer66 that's a real bummer. How long are you going to be laid up?
  12. Well I'm glad that your issue is resolved but to be honest I was not expecting clearing your logs to do anything other than remove them from view. I only wanted it to be easier for you to see which log to post. In the future for large posts you may need to use a service like PasteBin or simply zip them into an archive. PasteBin is preferred. Happy gaming.
  13. Nothing so fantastic as to warrant the change, no. However there is a lot of work happening so stay tuned.
  14. Can you delete all the logs you currently have and then try to use the CK from MO and post that log here please. This one looks to be run of FNIS.
  15. Editing of posts is disabled after 15 minutes as is outlined in the Citizenship Guidelines linked at the bottom-right of every page. As for switching to MO2 for Oblivion. MO2 is in active development and Oblivion support is receiving some attention but aside from that I see no reason to switch to it. If MO is working well in this instance, why bother?
  16. I'm only concerned with MO logs.
  17. Okay, still need logs though to see what is happening. I've also moved this to the MO sub-forum.
  18. Go to the MO2 Discord server and in the #builds channel grab the latest build and install that and then re-check this.
  19. As for the re-installing of MO, that is a simple task. Simple back-up the "mods, profiles & downloads" folders and then remove the existing MO install. Replace it with a new install and copy back the saved folders into place. As for the no-merge tags, I'm not sure. You could post a question in the WB forum.
  20. I'm assuming there was a Steam update or something like that. MO just doesn't decide to not work, there must be an external reason for this behaviour. Assuming as such you will need to run the Skyrim launcher from the desktop to reestablish the correct registry settings so MO knows where to look. If it doesn't automatically fix the issue please post your logs here for our examination.
  21. Did you at any time try to make a new "instance" or configure MO2 for another game? If you did it may be that the SSE instance is now trying to look in the incorrect place for the tools and game files. But looking at your logs again it doesn't look like that. Can you install a brand new copy of MO2 and set that up to see if it works. This makes no sense that there are no USVFS logs or the general failure of MO2.
  22. What about trying a different naming scheme for your system. Instead of @Programs try something else. Not saying that is the issue, it shouldn't be, but stranger things have been none to work.
  23. Has MO2, at any stage, been able to run correctly, ie. this a recent change? Or is this a brand new install and MO2 just refuses to work for you?
  24. Yeah, we're aware of what the issue is and how to fix it. It will mean disassociating the code from Nexus's NCC codebase as whenever they update their code, ours inherits the bugs.
  25. If there are any USVFS logs could you post the latest one please?
×
×
  • Create New...

Important Information

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