283
They are they higher res icons. Something got borked again in 283. It['s not a biggie complain, but the download icons for the certain icons got screwed up again.
If anyone helping with dev would do this, this will cure the problem with icons res in further updates.
Oh ************ I forgot to update images folder... OUCH!... sorry... fixed, thanks.
So far so good with the ini.
well now that is nice.
(Maybe) bug report... I'm assuming that the bold text is the new "Deactivate" tag... (as an aside, and this is purely aesthetic, the bold is out of place... better it be a different color to remain consistent with the rest of the indicators) not just the things with "Deactivate" are getting bolded. Lots of stuff that shouldn't be is, including the Bashed Patch itself.
yes Bold was the 'Deactivate' tag (as per the readme)... I've changed it to slanted. The reason it isn't a colour is since there are already many colours fighting for superiority, so this way more info can be represented than if just using colour.
It can only be applied if the 'Deactivate' tag is on the mod... at least that's what the check says (the code for checking is: if 'Deactivate' in bosh.modInfos[fileName].getBashTags(): which although I've had some fun with crashing has never once been inaccurate) ... so no idea on that; try refreshing your whole list with Ctrl-A and mark mergeable.
So I should deactivate the mods with bold text?

import(and for some also merge) and deactivate.
Also, I'm still not sure the race import stuff is working right... the EVE_Khajiit fix is tagged for Body-F, because it changes the texture for the female body. It's also merged into the Bashed Patch, but the entire Khajiit record is still being merged into the patch, not just the texture path for the female body. I marked it NoMerge, and (even though the Race Record header says that the mods MUST be active or merged to be imported) it imported just that over top the RBP changes. The same was true for Diverse Voices.esp.
nope it definitely has to be merged.
that is totally bizarre... my tests have all been fine now. Also fine for both Corepc (he also reported a speed improvement - while I was there I did a couple optimizations) and Daemondarque... so I really don't know what to say on that (and I use RBP)
And, as an aside (but on a similar note), if I have an .esp that changes only the model and texture paths for the ears of, say, high elves, what should it be tagged with so that the entire record isn't overwritten? [EDIT] I'll bet it's graphics, isn't it?
nope... in fact it should be the racepatcher but the race patcher does nothing with the ear subrecord!... I'll fix that up (guess theres gonna be an R.Ears tag shortly).
Seems I had a bugged file in my download. Re-did it and it works fine now.
okay glad to hear its working now.
Also, this:
MERGE/SCAN ERROR: The Ayleid Steps.espTraceback (most recent call last): File "C:\Program Files (x86)\Bethesda Softworks\Oblivion\Mopy\basher.py", line 4567, in Execute patchFile.scanLoadMods(SubProgress(progress,0.2,0.8)) File "C:\Program Files (x86)\Bethesda Softworks\Oblivion\Mopy\bosh.py", line 13744, in scanLoadMods self.scanModFile(modFile,nullProgress) File "C:\Program Files (x86)\Bethesda Softworks\Oblivion\Mopy\bosh.py", line 13798, in scanModFile block.updateRecords(modFile.tops[blockType],mapper,mergeIds) File "C:\Program Files (x86)\Bethesda Softworks\Oblivion\Mopy\bosh.py", line 4175, in updateRecords fids = set([record.fid for record in self.records])MemoryError
that is according tot he python site (I had to look it up since I've never seen it):
exception MemoryError
Raised when an operation runs out of memory but the situation may still be rescued (by deleting some objects). The associated value is a string indicating what kind of (internal) operation ran out of memory. Note that because of the underlying memory management architecture (C’s malloc() function), the interpreter may not always be able to completely recover from this situation; it nevertheless raises an exception so that a stack traceback can be printed, in case a run-away program was the cause.
... so try restarting Bash and doing whatever you were doing from start; also how many times with how big a LO had you already built the patch without closing bash?
thanks;
Pacific Morrowind