I'm having this odd problem with the latest and greatest windows glow mod from MSGO 2.0-- these http://www.dropbox.com/gallery/45643406/1/Windows%20Glow%20Problem?h=348d87 like to stay lit throughout the day. My order of windows-glow related mods is the following:

1. Windows Glow.esp
2. abotwindowsglow.esp
3. Windows Glow - Tribunal Eng.esp
4. Windows Glow - Bloodmoon Eng.esp
5. Windows Glow - Raven Rock eng.esp

I highly doubt it's a problem with the mods, as nothing in them has been touched; when I disable all of them the problem still persists, making me think it has something to do with my collection of textures and not the mods...

Just wondering if anyone else has encountered this problem; if so, how to fix it. Thanks guys.

I have this problem, didnt even notice it until you said it, no idea what is causing it.

IIRC the way that Windows Glow works is to enable the Windows Glow version of a building mesh (with lit windows) during the night and disable the mesh during the day. During the day, then, the normal Morrowind mesh is used and not the one from Windows Glow.

So, at a guess, either that script isn't working or you've installed a .NIF that replaces the Morrowind building mesh. As you say the problem persists without the Windows Glow plugins then I'd guess the problem's with a mesh. I don't know the name of that building mesh but you could find out by using ORI

Not the building, the windows stay illuminated.

You are both right since these windows are not part of the building and therefore only this is changed by night and day. Nevertheless Dragon32's suggestion that something disables the script is good.

Put winglow at the end of your loadorder and check again. Do you run mods like the lightning mod or true light and darkness?

Then replace the word "building" with "window" in my post.

Once you've found the mesh name you can look through your mod archives (if it's a pluginless replacer) or use a grep tool (Wingrep, InfoRapid Search & Replace, TextCrawler etc etc) to search your plugins for the name of the mesh.

Alternatively, just delete / rename the problem mesh.

Or what Sister said.

I'll get looking as soon as I can...unfortunately the week has arrived and with it work, a quick glance in-game makes it apparent that this mesh is indeed https://photos-2.dropbox.com/i/xl/8uUI0aHugll7KnKs4rPFneWlZYiBEhuhSLC-1meBu0I/45643406/1329879600/3a1a70c/MGE%20Screenshot%20002.png...I'll try the re-ordering as soon as I get to my gaming rig.

EDIT: On second thought, I apologize for being so brusque above. I really appreciate you guys for offering these suggestions.

Okay, the rundown:
Putting Windows Glow, then abotWindows glow at bottom of load order: same problem
Putting all Windows Glow mods at bottom of load order in specific order (see OP): same problem
Unchecking "true_lights_and_darkness": same problem
Mesh replacement from backed up, previously windows-glow-functional MW install (using MSGO 1.3): same problem (meshes/WGlow/ex_common_window_01 and meshes/WGlow/ex_common_window_02 are the meshes that don't work as they should, though this may not be a mesh problem as the files I replaced them with were the same size so I assume the same "unbroken" mesh.)
WindowsGlow.esp replacement from backed up, previously windows-glow-functional MW install (using MSGO 1.3): same problem.

a conundrum, to be sure...

any difference between a loaded and a fresh new game?

New game has it too...very strange. Abot, since you're very intimately familiar with the Windows Glow mods, is there any way a script may have been broken unintentionally? By another mod in a load order, I mean.

Also, anyone know how I could export a load list out of Wrye Mash? My ini load list is all alphabetized which does NOT resemble my actual load list in the slightest.

there are 2 script changing windows state, max_common_window_01 should enable _01 type windows at daytime, max_common_window_02 should enable _02 type windows at night.
if you see a _01 type windows at night or a _02 type window at daytime, something is probably not working as expected.
try a fresh new game (so you are sure to be testing mod problems, not save game problems) with just Windows Glow.esp loaded, if it works add another mod from the list
1 Windows Glow.esp
2. abotwindowsglow.esp
3. Windows Glow - Tribunal Eng.esp
4. Windows Glow - Bloodmoon Eng.esp
5. Windows Glow - Raven Rock eng.esp
and so on, you may find the problem if it is a mod
A fast way to get mod list in proper loading order is from Mash saves tab, click a save, right click the File header on left column, copy list

for anybody interested, I think I have found a possible reason of the problem: if you have these 2 meshes
Morrowind\Data Files\Meshes\x\Ex_Common_Window_01.nif
Morrowind\Data Files\Meshes\x\Ex_Common_Window_02.nif
probably they should not be in x folder but only in the WGlow folder, try renaming them to something else (e.g. _Ex_Common_Window_01.nif, Ex_Common_Window_02.nif) and restart Morrowind.

What about these files, abot:

Ex_common_window_01_dist
Ex_common_window_02_dist
Ex_common_window_03_dist

Should they be in the WGlow folder rather than the x folder?

I think they are distant lights (I think _dist is a MGE suffix) from http://www.gamesas.com/topic/1337836-wip-distant-lights-for-mge-xe/page__pid__20184076#entry20184076 so they are not related with windows glow and hopefully at the right place.

Thanks, abot!

Abot, that worked like a charm! Consider this thread solved! Thank you so much!