Jump to content


Photo

Beyond Boulder and New Bison Steve Casino installation problems


  • Please log in to reply
39 replies to this topic

#16 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 25 December 2017 - 06:01 PM

So, if I'm now understanding you, the error message is from xEdit and regardless of your choice, the plugin is still updated.

Sounds like a case of internal file management between xEdit and MO referring to differing filenames but the end result is still correct.

 

nb. You shouldn't need to re-download any mods if the merge process borks. Just reinstall them from MO's download tab.

 

To be sure I just redid my merge of Advanced Recon mods and then applied the "Generate BASH tags" script and no errors were shown.

 

Must be some odd setup in your machine that is causing this odd behaviour.

All my game tools such as MO and xEdit are in a folder that is not UAC and it is alos away from the Steam install. No programme runs as administrator on my machine which is the latest patched Windows 10. (Though I have heavily edited my install of it to remove Microsoft's data mining tools. See this.)



#17 MrBrightside

MrBrightside

    Citizen

  • Members
  • Pip
  • 52 posts

Posted 27 December 2017 - 01:50 AM

I've held off on the Advanced Recon bit while still going through the list, though the same problem is presenting itself again in a different way. While following the steps for installing NCR Trooper Overhaul Distributed, I am instructed to clean the mod in FNVedit of 6 ITM records. I go through and clean the mod, then when I'm exiting FNVedit I'm hit with that same error message again, only this time around the NCR Trooper Overhaul Distributed mod.

 

I suspect that this is some kind of permission/authority issue since someone else appeared to have a similar problem for skyrim. I've tried to deactivate read-only for my whole FNV folder, but for some reason it doesn't seem to work as the next time I check its properties, it is read-only again. I have tried to give myself full control over the folder through properties but that doesn't seem to be working either. For some reason FNVedit isn't being allowed to re-name things inside my FNV folder. Unless I was supposed to have Mod Organizer outside of FNV, in which case that could raise a bit of a problem.

 

Edit: Just realized what you said Grant, and I may have accidentally put MO inside my FNV folder. Does this mean that I'm screwed?


Edited by MrBrightside, 27 December 2017 - 01:57 AM.

  • 0

#18 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 27 December 2017 - 02:05 AM

No, you're not screwed. You can easily move the entire MO folder out into it's own location. It does sound increasingly like permission issues.



#19 MrBrightside

MrBrightside

    Citizen

  • Members
  • Pip
  • 52 posts

Posted 27 December 2017 - 02:17 AM

So I can move the whole folder? Will try that. Won't there be issues of MO looking for files that aren't there anymore? Anyhow, the permission issue does seem to be what is vexing me. Is there a way to run FNVedit as admin through MO? Otherwise I'm going to try and figure out ways to get more control over the folder. I'm sorry for constantly pestering the forum, but you guys and this guide have been a godsend to me since modding for me has always been a painful trial/error process that more often than not ends with me breaking the game.


Edited by MrBrightside, 27 December 2017 - 02:17 AM.

  • 0

#20 MrBrightside

MrBrightside

    Citizen

  • Members
  • Pip
  • 52 posts

Posted 27 December 2017 - 02:45 AM

One last note for right now, I had to kick Wasteland Flora off the list for now, its giving my game massive stuttering issues.


  • 0

#21 MrBrightside

MrBrightside

    Citizen

  • Members
  • Pip
  • 52 posts

Posted 27 December 2017 - 11:30 PM

Something I've noticed, that whole thing with FNVedit has it trying to rename files in places they do not exist. I think its trying to find them in the NV data folder, when they're in the mod organizer mod folder. Is there a way to change where FNVedit is looking?


  • 0

#22 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 28 December 2017 - 12:27 AM

You must call xEdit from MO to allow it to edit your modded game.

 

There is no other way to get it to "see" where your game resides. MO is tricking all the tools it runs to use paths to folders that exist only in memory when MO's VFS is active.

Any issue with files not being accessed is most likely a permissions issue. ie. Your tools or MO or the game itself is in a UAC folder under Windows strict control.



#23 MrBrightside

MrBrightside

    Citizen

  • Members
  • Pip
  • 52 posts

Posted 28 December 2017 - 01:14 AM

Alright I got onto the Nexus Discord and am talking about it with another guy. This might be an issue with windows 10. Re-installed xEdit, run both that and MO as admin, but still can't get FNVedit to clean things without that error popping up. I've already went into the properties of the FNV directory folder to give all users full control, but I can't seem to untick the read-only property. I can, but then if I right click the folder again it is ticked again. Is there anything else I can do to get full control of the folder?


Edited by MrBrightside, 28 December 2017 - 01:18 AM.

  • 0

#24 MrBrightside

MrBrightside

    Citizen

  • Members
  • Pip
  • 52 posts

Posted 28 December 2017 - 01:32 AM

Just tried to do the steps to take full control of the FNV folder, it only sort of worked. It said it couldn't let me modify certain files (mostly ini and a few exe files). Still I thought that I had control over the rest of the folder. But FNVedit still isn't working for cleaning.


  • 0

#25 MrBrightside

MrBrightside

    Citizen

  • Members
  • Pip
  • 52 posts

Posted 28 December 2017 - 01:50 AM

Or running Bash tags


  • 0

#26 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 28 December 2017 - 02:09 AM

Can you post your MO INI and also let me know where all your programmes are located?

 

I generally advise against running MO or tools called from it as admin, but with your issues that may be the least of your troubles.



#27 MrBrightside

MrBrightside

    Citizen

  • Members
  • Pip
  • 52 posts

Posted 28 December 2017 - 01:54 PM

 

That's my MO INI


  • 0

#28 MrBrightside

MrBrightside

    Citizen

  • Members
  • Pip
  • 52 posts

Posted 28 December 2017 - 02:02 PM

G:\SteamLibrary\steamapps\common\Fallout New Vegas\Mod Organizer

Is where my MO exe is

G:\SteamLibrary\steamapps\common\Fallout New Vegas

Is where my FNV exe is as well as my FNVedit exe

G:\SteamLibrary\steamapps\common\Fallout New Vegas\FNVLODGen 3.1.2a

Is where I have LODGen

G:\SteamLibrary\steamapps\common\Fallout New Vegas\LOOT

Is where I have LOOT

G:\SteamLibrary\steamapps\common\Fallout New Vegas\Mopy

Is where I have WryeFlash

G:\SteamLibrary\steamapps\common\Fallout New Vegas Mods\Merge Plugins-69905-2-3-1

Is where I have Merge Plugins


  • 0

#29 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 28 December 2017 - 05:15 PM

Try creating a folder called: Tools either off the G: drive or another drive and move MO, LOOT, xEdit, LODGen and MergePlugins to folders under that. Try and avoid using folder names with the version in them.

 

e.g.

 

G:\Tools\MO

\xEdit

\LOOT

\Merge

\LODGen

 

This is a snippet of my MO INI with those tools:

5\title=xEdit
5\custom=true
5\toolbar=true
5\ownicon=true
5\binary=D:/Games/Utils/xEdit/xEdit.exe
5\arguments=-fnv
5\workingDirectory=
5\closeOnStart=false
5\steamAppID=
6\title=LOOT
6\custom=true
6\toolbar=true
6\ownicon=true
6\binary=D:/Games/Utils/LOOT/LOOT.exe
6\arguments="--game=FalloutNV"
6\workingDirectory=
6\closeOnStart=false
6\steamAppID=
7\title=FO4Edit
7\custom=true
7\toolbar=false
7\ownicon=true
7\binary=D:/Games/Utils/xEdit/xedit.exe
7\arguments=-fnv
7\workingDirectory=
7\closeOnStart=false
7\steamAppID=
8\title=Merge Plugins Standalone
8\custom=true
8\toolbar=true
8\ownicon=true
8\binary=D:/Games/Utils/Merge/MergePlugins.exe
8\arguments=-profile FNV
8\workingDirectory=
8\closeOnStart=false
8\steamAppID=
9\title=Mator Smash
9\custom=true
9\toolbar=true
9\ownicon=true
9\binary=D:/Games/Utils/Smash/MatorSmash.exe
9\arguments=-profile FalloutNVProfile
9\workingDirectory=
9\closeOnStart=false
9\steamAppID=
10\title=FNVLODGen
10\custom=true
10\toolbar=false
10\ownicon=false
10\binary=D:/Games/Utils/xEdit/xEdit.exe
10\arguments=-FNV -LODGen -o:\"D:\\Games\\FNVLODOutput\\\"
10\workingDirectory=
10\closeOnStart=false
10\steamAppID=
11\title=WryeFLASH
11\custom=true
11\toolbar=true
11\ownicon=false
11\binary=D:/Steam/steamapps/common/Fallout New Vegas/Mopy/Wrye Flash.exe
11\arguments=
11\workingDirectory=
11\closeOnStart=false
11\steamAppID=

Notice i have one install of xEdit and by using arguments in MO's settings I can call as FNVEdit or LODGen or indeed for other games.

Also arguments call LOOT and MergePlugins with FNV as the selected game saving one step upon loading.

 

Additionally I have been running Windows 10 for some time now and I have missed ALL the so-called problems that it is supposed to have called, with the one exception of the RAM allocation in DX9 which is now fixed.

 

You'll need to refresh my memory as to what your plugin cleaning problem is and also the bash tag issue.



#30 MrBrightside

MrBrightside

    Citizen

  • Members
  • Pip
  • 52 posts

Posted 28 December 2017 - 10:33 PM

I'll try and see what I can do about moving the programs.

 

The issue right now is that FNVedit cannot clean nor apply bash tags right now without going into that "re-name" issue that I posted earlier. To bring this back up to speed when I try and apply bash tags to the advanced recon mods as I close xEdit It tells me that it could not rename G:\SteamLibrary\steammaps\common\Fallout New Vegas\Data\Advanced Recce Merged.esp.save.2017_12_25_13_39_12 to G:\SteamLibrary\steammaps\common\Fallout New Vegas\Data\Advanced Recce Merged.esp

 

I get a similar message if I try and clean a mod through xEdit. I have assumed that this is a permission problem so far and have tried to fix it by running xEdit and MO as Admin and by trying to get full control of my FNV folder, but neither have worked so far. I am not sure why xEdit is doing this.

 

Edit: Also regarding MO's ini, I do not know what you mean by "arguments", I'm assuming its something to do with how the ini is written


Edited by MrBrightside, 28 December 2017 - 10:35 PM.

  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users