Jump to content

enneract

Citizen
  • Posts

    5
  • Joined

  • Last visited

enneract's Achievements

Watcher

Watcher (1/12)

0

Reputation

1

Community Answers

  1. I can't properly explain it, to be honest. There is something else at play in 'protecting' %programfiles% outside of UAC, and any program that does anything other than the 'normal' range of behavior tends to behave quite strangely.
  2. Figured it out. I have C:Program Files (x86)Steamsteamappscommon junctioned to C:Games, so I forget that C:Games is actually located in %programfiles%, heh. Moved MO out of C:GamesSkyrim, and it works fine.
  3. Ah, I started cmd through MO, VFS looks fine. Another interesting note is that FNIS had to be installed into the base data directory, instead of through MO, in order to notice anything in the VFS.I didn't directly upgrade an in-place, working MO setup. I actually had skyrim uninstalled for quite some time, and only recently reinstalled it.Just did a fresh MO install, with only SkyRe + ReProccer. Both checked in the left pane, ran reproccer jar... and it can't see anything in the VFS, but cmd can!https://pastebin.com/kSYHH7SC
  4. Nope, that isn't the problem. I've ever tried dumping the patchers in the overwrite folder, no joy.
  5. I've been unable to get any SkyProc patcher to work with the current (1.1.2) version of MO. Reproccer can't see Skyre_Main.esp, DSR can't see its esp, SUM can't see any other patchers, etc. I've tried running MO as admin, disabling windows defender (no other AV products installed), using java 6 and 8 instead of java 7, even shennanigans like pointing the patcher's 'start in' directory directly to the real skyrim data folder (That got some result, SUM could see other patchers, but the patchers themselves failed to find any ESP files). It is worth noting that I've successfully used SkyProc patchers in conjunction with MO in the past, though not since the version number was < 1.I'm at a loss. Any ideas?
×
×
  • Create New...

Important Information

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