since the authors of wrye-bash don't want to support Skyrim le a 32 bit game the arrogant bastards won't get my support as the only current version is 64 bit that cant run in 32 bit environment i am asking they pull their head out of there asses and fix this matter also mo 2 has the same problem it just breaks my 32 bit game
Avast is blocking some .dll's in my Temp folder when I launch this. In turn, the program doesn't start and an error report is generated. Anyone care to clarify?
Hmmm .. I compared your config with mine. My NMM settings, skyrim tab for Install info points to "D:\Games\Nexus Mod Manager\Skyrim\Install Info" .. which you may need similar. Also I would try "full path" without %skyrimmods% var in nmmtowrye.xml .. again note installlog location ..
I simply do not want NMM installed on my computer and download manually. Please can we have a standalone application to convert fomod xml to wizard. I am sure I saw a fomod fix for Wrye Bash somewhere but cannot find it anymore. Anyone?
Very good idea! It is a shame that this view is abandoned. The amount of mods is becoming incredible, and the need to merge or patch with bash becomes more and more obvious. NMM has been updated quite some times now, and so is the Nexus-site. Things are broken now. How about do some updating to make this really good initiative working again? I think it becomes necessary now more than a year ago.
Trying to install and get this running, but when the packaged Nexus Mod Manager client asks me to log into Nexus, it comes back with an error: Cannot connect to Nexus server. The remote server returned and error. (404) Not Found.
it simply deletes the skyrim.esm before NMMtoWRYE converts the content of TempData folder to an archive and recreates it afterwards
just replace %skyrimmods%, %Skyrim Install Location% and %WryeBash Install Location% with the proper path, put it in a batch file and replace NMMs custom launch command with the path to the batch file
Give Feedback
64 comments
Fortunately Wrye Bash 307 currently has experimental FOMOD support in the nightly builds as of Q4 2019.
Nexusmods.com doesn't want to play with the version included in this download.
What I'm doing wrong?
View image
Someone help me?
<nmmtowrye>
<installLog>
<dataDir>
<archiveDir>
</nmmtowrye>
Very good idea!
It is a shame that this view is abandoned.
The amount of mods is becoming incredible, and the need to merge or patch with bash becomes more and more obvious.
NMM has been updated quite some times now, and so is the Nexus-site.
Things are broken now.
How about do some updating to make this really good initiative working again?
I think it becomes necessary now more than a year ago.
@echo off
@DEL /S /Q /F "%Skyrim Mods%\TempData\data\Skyrim.esm"
chdir /D "%WryeBash Install Location%\Mopy"
nmmtowrye.exe
mkdir "%Skyrim Mods%\TempData\data"
copy "%Skyrim Install Location%\Data\Skyrim.esm" "%Skyrim Mods%\TempData\data\Skyrim.esm"
it simply deletes the skyrim.esm before NMMtoWRYE converts the content of TempData folder to an archive and recreates it afterwards
just replace %skyrimmods%, %Skyrim Install Location% and %WryeBash Install Location% with the proper path, put it in a batch file and replace NMMs custom launch command with the path to the batch file