Thanks for the reply.  I've been using the nraas story progression since Indie died.  Awesome was always just there and I got so used to the commands, I've forgotten that they aren't part of the game.

The mistake was mine.  I used nraas supercomputer to set "disableclothingfilter", which is where the persistence is.  Then when I switched awesomemod out from underneath it, the setting no longer had a core mod to handle it.  I had set it so long ago that I forgot all about the setting.  And the nraas supercomputer changed it's menus around, so I didn't even see it where it used to be.

But a big "duh" on my part.

Weirdness with having used awesomemod, then switching to another core mod (in this case, extended core - testing it's perv stuff, which, while amusing does get old quick.  Still, there are a few nice tweaks in it that are good to have)

Anyway, the problem shows up using nraas supercomputer to force a sim to dresser or CAS and going to clothing.  The clothing GUI is all foobar, nothing shows up *and* the category buttons (eg: top, bottom) disappear when they're active.  They stay gone until the next time you enter CAS (or dresser).  A normal dresser still works, all the other parts of CAS work.

According to twallan, this shows up when disableclothingfilter has been activated but the core isn't there to handle it.  Is it possible for awesomemod to leave that setting lingering to bite me later, when using a different core mod?

Sigh... Very frustrating the one core at a time and no way for core mods to work together.  There are about 6 things in expandable core I like (and it's plugin architecture), I liked indie-stone but that seems dead.  nraas is, in many way better, certainly as far as control options are concerned.  But I liked indie story progressions better.  awesome just plain brings some serious control/power to the table, which I find invaluable sometimes.  nraas is amazing for script mods.  But to get complete flexibility, I need core mods.  I try to get maximum flexibility with minimum mods.