Beyond Boulder and New Bison Steve Casino installation problems

[GrantSP]

'arguments' are extra instructions that added to the programme when you call it. Have a look in the section of my INI above at the lines called as such.

 

e.g.

8\binary=D:/Games/Utils/Merge/MergePlugins.exe
8\arguments=-profile FNV

 

translates to this if you entered it on the commandline:

MergePlugins.exe -profile FNV

[MrBrightside]

Thanks for the help, it turns out placing xEdit outside of my G drive and running it as admin helped to make it work. What I had to do additionally was pull the plugin file from Mod Organizers mod files and into the FNV data directory in order to clean it successfully. Only problem is I had to run it from outside MO to do it. While running it outside of MO it only sees the plugins in the FNV data folder, which is where I had moved the plugin. However, once I had successfully cleaned the plugin (NCR overhaul distributed), an FNVedit backup appeared in its folder within the MO mod directory. So its a bit confusing. Unfortunately this means that for me to successfully run xEdit it has to be outside of MO, for now. Any suggestions? Also I am running MO as admin still.

Edited December 30, 2017 by MrBrightside

[GrantSP]

If you run MO as admin then that may be giving xEdit access problems.

This is why I generally advise against running anything as admin, unless the author of the tool/mod specifically says to.

 

I saw nothing in your logs that would indicate an issue with MO's VFS not working correctly, which means I have no idea why your system can't get xEdit to run from MO. Sorry!

[MrBrightside]

This issue existed before I was running MO as admin. Also thanks for trying to help, though this does mean that trying to utilize xEdit is going to be rather tricky.

[GrantSP]

do you have any other games that MO manages?

[MrBrightside]

Not at the moment no.

[MrBrightside]

Would I have to reinstall MO in a different place to make this work? While this workaround means that I can move forward in the F&L guide it means that anything I need to edit in xEdit will need to be moved from MO's mod directory to FNV's data directory to be edited, then moved back again.

[GrantSP]

My advice is to find out why you are experiencing this odd behaviour and fix it before moving on.

Workarounds and hacks are, by their very nature, not very helpful and you will possibly want to do more advanced modding later on. Having to move plugins and the assets for those mods around is just not a good idea.

 

However it is your call. As for installing MO anywhere else, it is such a small install with little to worry about that what ever you do with MO is fine, just keep it out of the game folder.

[MrBrightside]

Is there anywhere you'd recommend to post this issue? I'm still not sure if this is a permission issue or if xEdit just isn't cooperating with MO (my money's on the former).

[GrantSP]

Start a new thread here at STEP in the MO section and post your INI and your logs from a typical issue experience.

Give as much info as possible to try and pinpoint the problem. Lastly eliminate as much extraneous stuff in your testing setup so that only the bare minimum is being used.

 

There is a Discord channel but that is focused on MO2 and you may not get as much traction there as here. Look at any Reddit threads or other forums you like.

 

There are 1000s of users on various OSes that are running MO and the solution to your issue will come... eventually.