Jump to content


Photo

Wrye's Bash won't run from inside MO2


  • Please log in to reply
75 replies to this topic

#16 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 08 July 2017 - 03:18 AM

I got nothing else apart from the fact Steam is in Program Files (x86).

 

Do you have old Skyrim? If so does the same thing happen when you try to run WB on that setup?



#17 shadow1

shadow1

    Prisoner

  • Members
  • 26 posts

Posted 08 July 2017 - 05:04 AM

I only have SE installed ATM. Internet is craaaaapily slow here.

 

I'll download it to test, but it might be a while.

I'll see if I can flip SE out of program files, and see if that helps.

 

Cheers.


  • 0

#18 shadow1

shadow1

    Prisoner

  • Members
  • 26 posts

Posted 08 July 2017 - 08:51 PM

Well, that's interesting.

 

Slung skyrimSE over to another drive, run wrye bash and ...

 

I'll fix it up and keep you posted.

 

Wrye bash could not find a game to manage. Please use -o command line argument to specify the game path.


Edited by shadow1, 08 July 2017 - 08:52 PM.

  • 0

#19 shadow1

shadow1

    Prisoner

  • Members
  • 26 posts

Posted 08 July 2017 - 09:18 PM

Okay, so now...

 

abbab.png

 

They all result in bombing back to MO

 

Edit: This seems to happen even when I delete the tmpfile in skyrim\data and the clear out the temp folder in AppData\Local

Even funnier, when it reoccurs, there is no file in skyrim\data

This whole thing is fckn wierd.


Edited by shadow1, 08 July 2017 - 09:32 PM.

  • 0

#20 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 08 July 2017 - 10:54 PM

Remember to run Skyrim at least once outside of MO to establish the correct registry settings otherwise tools like WB or xEdit won't know of it.

 

The image above will also be a result of WB trying to use the SSE paths instead of old Skyrim.



#21 shadow1

shadow1

    Prisoner

  • Members
  • 26 posts

Posted 08 July 2017 - 11:42 PM

Okay, so now pops up asking which game.

Select Skyrim (not SE)

Does same thing as image above.

Directory is now "WryeBash_tsjnec" and "skyrim" (not the SE folder)

All three options lead to backing out to MO


Edited by shadow1, 08 July 2017 - 11:42 PM.

  • 0

#22 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 09 July 2017 - 12:33 AM

Sorry, I've got nothing.

Scrap your entire MO2 install and start again maybe?



#23 shadow1

shadow1

    Prisoner

  • Members
  • 26 posts

Posted 09 July 2017 - 12:42 AM

That's cool mate.

 

Thanks for your time, it's appreciated.

 

Nuke time.


  • 0

#24 shadow1

shadow1

    Prisoner

  • Members
  • 26 posts

Posted 09 July 2017 - 07:29 PM

Okay, so nuked and still no good, looks like a wrye bash issue perhaps.

 

Run wrye bash by itself results in the image posted above. Difference being, when I select one of the options it actually runs.

Maybe MO just doesn't know how to deal with it when it does that. Still fekkin wierd, though.

 

Time to hit up the wrye forums and see wassup.

 

Is anyone else experiencing this issue?

OP is your issue solved? Or still problem like me?


  • 0

#25 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 09 July 2017 - 08:23 PM

You'll get no support from Wrye forums as anything to do with MO/MO2 will automatically be blamed on MO/MO2.



#26 Tabris

Tabris

    Prisoner

  • Members
  • 13 posts

Posted 13 July 2017 - 04:40 PM

Somebody else posted about this on /r/Skyrim mods , he also has the insider build for Windows 10, I seriously suspect that is the cause of the problem.
  • 0

#27 cptmcsplody

cptmcsplody

    Guard

  • Contributors
  • PipPip
  • 179 posts

Posted 15 July 2017 - 07:33 AM

Have insider with a week, issue only started since then. Can run all other versions of wrye bash through mo2, only SSE version is causing issues, it does not recognize plugins installed by MO2 or it fails to launch properly and leaves behind a temp file in the SSE data directory. Getting windows error [32] failed to get process file in use. Perhaps some python process is hanging or failing and leaving a file open?


  • 0

#28 cptmcsplody

cptmcsplody

    Guard

  • Contributors
  • PipPip
  • 179 posts

Posted 15 July 2017 - 11:50 AM

logs so far
 
from MO2 - 
failed to spawn "wrye bash.exe": failed to start process( the parameter is incorrect [87])
after usvfs_proxy.exe cmd window
 
Also getting
 
usebackq tokens was unexpected at this time error when running wrye bash debug from MO2
 
 
Running wrye bash python launcher will not recognize mo2 plugins

 

This has to be an issue with  usvfs_proxy.exe surely?


Edited by cptmcsplody, 15 July 2017 - 12:04 PM.

  • 0

#29 GrantSP

GrantSP

    The antipodean

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 4,333 posts

Posted 15 July 2017 - 06:09 PM

I opted out of my Insider account with MS a few months back so I'll need to wait for a complete update from them to verify. However it is very likely that they have upped the ante on how they treat 'malicious' code.

MO/MO2 uses exactly the same methods to 'hook' executables as that of viruses or malware, ie. changing the code in memory to do something else.



#30 cptmcsplody

cptmcsplody

    Guard

  • Contributors
  • PipPip
  • 179 posts

Posted 15 July 2017 - 06:10 PM

Rolled back my install to last insider slow release and its working now, just getting files in overwrite which i have to delete every time I run Wrye bash.

 

E:\ModOrganizer\overwrite\Tools\Wrye Bash 307\Mopy\Wrye Bash.exe\comtypes\gen

 

Not sure what its supposed to contain as it is empty. But leaving the empty files in overwrite prevents wryebash running through MO.


  • 0


1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users