<genuinely...>
A while back, someone sent me a rather scantily clad character model that relied on the default Bioware pelvis texture to keep things clean. I was quite surprised to see her appear au natural. I habitually keep my override folder empty because I'm always trying new things and I can't handle some of the odd interactions I get with a fully-stocked override. So where was the naughty texture coming from?
While doing my own search for Vibrant's elusive Cloak textures and models, I noticed - on my brand-new start-from-scratch laptop, that the supermodels from the OC were showing up in explorer, er, they were showing more than they should.
Excuse me?
Side-tracked <of course>, I spent an hour tracking down every version of pfh0_pelvis_001.plt I had.
Can you guess what was overriding the OC texture? Texturepacks->Textures_Tpa.erf. I tested this by the simple expedient of removing that folder. The naughty-bits went away.
So far as I know, this was a bonus folder bundled with Diamond Edition, like the 2DAsource.
So, I have a couple of questions.
First, although I am no prude, I prefer to keep this machine clean. Did I simply miss the fracas where this scandal was exposed and tittered over? I.e. is this an open secret I just didn't know about?
Second, more interesting from a custom content angle, since when do erfs in a "texturepacks" folder override anything? Do any *other* folders override things? Are some of the bugs and strange behavior we experience related to a much looser resource chain than we (*I*) had assumed?
Edit: Hmmmm, come to think of it, is this where TSL's strange chromed bonnet mystery came from? Chromed in the toolset, fine in game?
<...puzzled>
Modifié par Rolo Kipp, 31 mars 2012 - 10:54 .