[relz] Wrye Bash : IV - Oblivion

» Tue Apr 05, 2011 10:52 pm

Pacific seems to be net-less at the moment and I've only just started working on Bash (and have really only looked at the Tool Launchers).

Ctrl-movement: That seems to be an error; doesn't work on a single package or a group of packages.

Color schemes: While I generally agree with you, I'm not sure what you're expecting. To summon Wrye for a bit - you're not giving an alternative, and you're attacking the single most sensible part of the color scheme - gray = not functioning, just like every other program.

You can set it in the .ini file; it will also accept absolute paths.

Thank you for the replies. Hmmm...Maybe the selected package could be highlighted in blue or yellow, perhaps? Is Wrye still around? I did not know about that INI thing. I would like to keep my duplicates on a separate HDD too.

» Tue Apr 05, 2011 10:24 pm

Pacific seems to be net-less at the moment and I've only just started working on Bash (and have really only looked at the Tool Launchers).

Ctrl-movement: That seems to be an error; doesn't work on a single package or a group of packages.

Color schemes: While I generally agree with you, I'm not sure what you're expecting. To summon Wrye for a bit - you're not giving an alternative, and you're attacking the single most sensible part of the color scheme - gray = not functioning, just like every other program.

You can set it in the .ini file; it will also accept absolute paths.

You can specify the Oblivion Mods folder in the INI file. If the hard drive is always attached, that should work just fine.

For a removable drive, I think you might have issues because I believe WB also stores some mod data in that folder, so if it tried that when you didn't have the removable drive installed it might cause problems.

Excellent. Thank you. I am doing to be doing some serious upgrades to my machine here shortly, just waiting for the parts to arrive, and am planning on doing some reinstalls. This info will make life much easier. (and it is an internal drive, permanently mounted.)

» Wed Apr 06, 2011 4:48 am

I couldn't get the INI link to work, and it took almost an entire day for me to sort the mods properly. I really, really hope Bash retakes its old package info list thingy.

Edit: Should I have changed something other than the default ini. I made a back up of it.

» Wed Apr 06, 2011 2:58 am

Edit: Should I have changed something other than the default ini. I made a back up of it.

Yeah - you've got to save it as "bash.ini".

» Wed Apr 06, 2011 2:45 am

Yeah - you've got to save it as "bash.ini".

Thought so. What is that warning about putting the Mods folder outside of the Oblivion install folder? Oh, not put it under the Oblivion install directory. I'll try to move it again then.

from the INI:

;--sOblivionMods is the Alternate root directory for installers, etc. You can;  use absolute path (c:\Games\Oblivion Mods) or relative path, where path;  is relative to Oblivion install directory. It is strongly recommended that ;  you do NOT put it anywhere under the Oblivion install directory itself, ;  since (due to a bug), Oblivion.exe will at times search through every directory;  under the install directory. This "directory thrashing" can then cause performance;  problems during gameplay. sOblivionMods is defined specifically to circumvent ;  this bug by storing files elsewhere.

Geez, I totally misread the warning.

» Wed Apr 06, 2011 5:48 am

I've been looking over the latest changes to the BOSS master list, noting all the new tags, and I have a question regarding the overhauls specifically: Do those tags apply only to the newest version of the overhaul mods (FCOM, OOO, MMM, etc.), or should I stick with the ones I have? I'm using FCOM 0.9.8, because I don't want to use OOO Full - I much prefer Lite, and since 1.34 isn't a full release yet...

There's really no good reason not to upgrade. Things have been much improved all around. 1.34b is a stable release with less issues than 1.33.

As for full OOO vs Lite, if you have specific questions, you can take them up in the FCOM thread, but, again, there's no reason to forego all the benefits of an upgraded FCOM setup.

As for the tags question, you can certainly use some of the new tags (like scripts) with the outdated FCOM components. Don't know if you'll have to add them manually though.

gothemasticator

» Wed Apr 06, 2011 5:18 am

Ctrl-movement: That seems to be an error; doesn't work on a single package or a group of packages.

That's funny. Ctrl-arrows work fine for me whether I've selected a single archive or a group. Try arranging the archives in order of "Order" (click on the order tab) then try using Ctrl+arrow again.

» Wed Apr 06, 2011 2:48 am

I am using the "Order" sort.

» Wed Apr 06, 2011 8:14 am

There's really no good reason not to upgrade. Things have been much improved all around. 1.34b is a stable release with less issues than 1.33.

I'm sure it is... I'm eagerly looking forward to the Lite version.

As for full OOO vs Lite, if you have specific questions, you can take them up in the FCOM thread, but, again, there's no reason to forego all the benefits of an upgraded FCOM setup.

Yeah, I could ask, but I figure it's pretty much the same as previous versions.

As for the tags question, you can certainly use some of the new tags (like scripts) with the outdated FCOM components. Don't know if you'll have to add them manually though.

Probably, but that's fine - I manually adjust my load order anyway. Thanks for the info.

» Wed Apr 06, 2011 6:27 am

That's funny. Ctrl-arrows work fine for me whether I've selected a single archive or a group. Try arranging the archives in order of "Order" (click on the order tab) then try using Ctrl+arrow again.

Works for me (not intuitive, but it makes sense)

» Wed Apr 06, 2011 7:22 am

Ctrl+down worked once. The next time, the focus jumped up to the top, and Wrye Bash choked up for a bit.

Edit: no success

I must be missing some thing. I get errors when I change the file in the downloads folder and BAIN refreshes. It errors when I uncheck esps in the right window sometimes.

Traceback (most recent call last):  File "L:\Program Files\Bethesda Softworks\Oblivion\Mopy\basher.py", line 6196, in Execute    self.data.refresh(what='NSC')  File "L:\Program Files\Bethesda Softworks\Oblivion\Mopy\bosh.py", line 10676, in refresh    if 'S' in what or changed: changed |= self.refreshStatus()  File "L:\Program Files\Bethesda Softworks\Oblivion\Mopy\bosh.py", line 10967, in refreshStatus    changed |= installer.refreshStatus(self)  File "L:\Program Files\Bethesda Softworks\Oblivion\Mopy\bosh.py", line 9890, in refreshStatus    for file,sizeCrc in dirty_sizeCrc.iteritems():RuntimeError: dictionary changed size during iteration

Update:

Just had to reinstall 276 (again) to get the installers tab to load without issue.

» Tue Apr 05, 2011 7:53 pm

Camero-

I'll try to clarify a point or two. If you really did install everything via BAIN then it will not show red unless ...
1. You manually removed those files from the data folder.
2. You used another installer like OBMM to remove or replace a file.
3. You changed the options in the BAIN package of what is to be installed but did not anneal those changes.

Snip

So with UFCOM loading after my FCOM package - the FCOM Package is orange.

In the final anolysis if you are sure that everything is where it ought to be then it will not harm anything to click anneal all.

Again Thank you for your time in answering me...Very helpful . With 187 mods loaded ,and I can play for hours on end I know that is because BASH is doing its Job!!!

» Tue Apr 05, 2011 10:31 pm

...I get errors when I change the file in the downloads folder and BAIN refreshes. It errors when I uncheck esps in the right window sometimes.

RuntimeError: dictionary changed size during iteration

I had that problem as well. This is how I fixed it:

Exit Wrye Bash then open Bosh.py in the Mopy folder with notepad.
Click on Edit -> Search and Replace.
Have Notepad replace every instance of "iteritems" with "items".
Save and exit then restart Wrye Bash.

I think PacificMorrowind originally suggested this fix somewhere. He also mentioned that "items" is faster than "iteritems"

» Wed Apr 06, 2011 12:13 am

Sorry if this question has been answered a million times...

When I build my bashed patch and after wards un-check all mods with green text so that they show a "+" symbol, do I need to recheck these same mods each time I re-build my bashed patch? Or can I just leave them as is with the "+" symbol?

» Wed Apr 06, 2011 10:57 am

Sorry if this question has been answered a million times...

When I build my bashed patch and after wards un-check all mods with green text so that they show a "+" symbol, do I need to recheck these same mods each time I re-build my bashed patch? Or can I just leave them as is with the "+" symbol?

You can leave them as '+' symbols.
Wrye Bash doesn't care if a mod is checked or unchecked if it's merged.

» Tue Apr 05, 2011 10:48 pm

You can leave them as '+' symbols.
Wrye Bash doesn't care if a mod is checked or unchecked if it's merged.

Thanks DD :goodjob:

» Wed Apr 06, 2011 7:04 am

I have recently build a new Oblivion install, and everything works fine as it is now (over 350 mods, merged/cleaned a lot of them). However I am having an issue with "Let There Be Darkness".

I used the regular version, and imported the C.Light option into my bashed patch. After running the game I noticed that my cells were untouched. I then used a different LTBD (that includes support for lots of known quest mods) and I merged them all into 1 ESP. After importing those, I ended up with same issue.

My load order is perfect, since everything else works fine. I tried moving it, but no luck so far.

After I used the option "Mark Mergeable" in Wrye bash I ended up with:

Not Mergeable* Let There Be Darkness All.esp:Unsupported types: CELL.Empty mod.

At first I thought I screwed up the merging, but the default version has this as well. Does anyone know a work around for this, so I that I can import the cells and have my dungeons dark again?

Lunat1c

» Wed Apr 06, 2011 3:59 am

@lunatic: Cell records re not mergeable, so of course you cannot merge that mod. You need to make a patch. One of the things that can happen is that another merged mods C.Light tag is overriding Let the be Darkness. Use TES4Edit to make a patch that loads after the bashed patch or something.

Edit: ...forgot about my issue. DLCShiveringIsles, a renamed copy of the USIP, is uninstalled every time I load the installers tab. This only ever happens to one file. When I was installing BOSS through BAIN, the BOSS BAT file was uninstalled every time. *Correction: BAIN thinks its missing, but the file is still there.

» Tue Apr 05, 2011 11:27 pm

Ah, thanks for clearing that up.

Well made a patch, and it is working now as intended.

Thanks!

» Tue Apr 05, 2011 7:02 pm

Ah, thanks for clearing that up.

Well made a patch, and it is working now as intended.

Thanks!

Sure thing. I generally have a patch for Cells & World at the very end of my load order that contains all of those type of overrides.

» Wed Apr 06, 2011 12:37 am

Hey, im having a problem i've never had before. i just re-installed wrye-bash, and all the required files (according to the readme), when i try to run the launcher, nothing happens... theres no bugdump, looked for that, and when i do the whole command prompt thing, nothing (other than what i typed) appears on it... but Wrye bash starts... as soon as i type in "\python25\python.exe bash.py -d" and click enter, Wrye bash launches... wont launch unless i do that.. it works fine after i do that, but its just slightly annoying... and as soon as i close the command prompt, wrye bash closes too.

» Wed Apr 06, 2011 1:04 am

Error in svn revision ##184-187

Traceback (most recent call last):
File "D:\Games\Oblivion Gold\Mopy\basher.py", line 4514, in Execute
raise
File "D:\Games\Oblivion Gold\Mopy\basher.py", line 4476, in Execute
patchFile.buildPatch(log,SubProgress(progress,0.8,0.9))
File "D:\Games\Oblivion Gold\Mopy\bosh.py", line 13871, in buildPatch
patcher.buildPatch(log,SubProgress(subProgress,index))
File "D:\Games\Oblivion Gold\Mopy\bosh.py", line 19059, in buildPatch
if set(race.eyes) != set(raceData['eyes']):
KeyError: 'eyes'

» Wed Apr 06, 2011 6:18 am

I Have just re-installed Oblivion & Tools on 64 bit Win 7 and have the following problem;

Python 2.5.2 - no problem
wvPython2.8-win32-ansi-2.8.7.1-py25.exe - no problem

pywin32-212.win32-py2.5.exe - X The program can't start because MSVCR71.dll is missing from your computer.
psyco-1.6.win32-py25.exe- X The program can't start because MSVCR71.dll is missing from your computer.
PIL-1.1.6win32-py2.5.exe- X The program can't start because MSVCR71.dll is missing from your computer.
comtypes-0.5.2win32.exe - X The program can't start because MSVCR71.dll is missing from your computer.

Compatibility mode as usual suxors. Does anyone have any experience of this?

With some re-pointing of wrye bash launcher.pyw runs fine but i think i need those add-ons

I have a seperate F: drive for my games C: is just for the O.S.

Any help appreciated!

» Wed Apr 06, 2011 1:13 am

I Have just re-installed Oblivion & Tools on 64 bit Win 7 and have the following problem;

Python 2.5.2 - no problem
wvPython2.8-win32-ansi-2.8.7.1-py25.exe - no problem

pywin32-212.win32-py2.5.exe - X The program can't start because MSVCR71.dll is missing from your computer.
psyco-1.6.win32-py25.exe- X The program can't start because MSVCR71.dll is missing from your computer.
PIL-1.1.6win32-py2.5.exe- X The program can't start because MSVCR71.dll is missing from your computer.
comtypes-0.5.2win32.exe - X The program can't start because MSVCR71.dll is missing from your computer.

Compatibility mode as usual suxors. Does anyone have any experience of this?

With some re-pointing of wrye bash launcher.pyw runs fine but i think i need those add-ons

I have a seperate F: drive for my games C: is just for the O.S.

Any help appreciated!

http://www.dll-files.com/dllindex/dll-files.shtml?msvcr71

Download and stick dll in your system32 folder.

» Tue Apr 05, 2011 7:42 pm

http://www.dll-files.com/dllindex/dll-files.shtml?msvcr71

Download and stick dll in your system32 folder.

Woot! ta.

I gotta stop tryin to do stuff at 3am