To work properly, the windows need one side facing a roofed area and the other facing an unroofed one. To calculate this, they take into consideration the first line of tiles on either side. The exterior can't be determined if there are unroofed tiles on both sides or if the number of roofed tiles is the same on both sides.

Love the mod. So much so I planned my entire base around having an underground garden indoors with windows to the rooms around it, but the windows cannot determine which side is the exterior. Would it be possible to get an option to manually specify the exterior when the window can't determine it? Cheers.

Tia: nope, they just wouldn't work. You absolutely need to set up the windows the way I described on my last comment above. Only exception is, with the latest update, you can use a transparent roof from Expanded Roofing or Raise the Roof on the exterior side.

Hmm. Alright. I've got Expanded Roofing so I might remove a single overhead mountain block from the "external" side for each window and throwing some transparents in. It's... a mirror lined skylight vent... Yes.

Cheers.

Hi! I've had the same issue. Tracked it down to an interaction with Dub's Minimap. Once uninstalled, all my windows would correctly detect "outside"

oh boy, this really is a bummer, i always build some roof overhang so pawns do not get wet when moving along paths besides buildings. i mean, rimworld knows for every tile, if it's "indoors" or "outdoors" - why not use that instead of the roof thing??? (or additionally, when "cannot determine" occurs?)

Originally posted by TheologyOfDeath:

Hi! I've had the same issue. Tracked it down to an interaction with Dub's Minimap. Once uninstalled, all my windows would correctly detect "outside"

That could MAYBE be because all of Dub's mods include a 0harmony.dll for versions 1.1+ (only needed for version 1.0). Try making a local copy and remove/rename that dll (and accompanying .xml) from the assemblies folder for whatever version of rimworld you're using.

I also add the following to the About.xml (although I'm not sure if it's 100% required, that's how it's supposed to be done):

<modDependencies>
<li>
<packageId>brrainz.harmony</packageId>
<displayName>Harmony</displayName> <steamWorkshopUrl>steam://url/CommunityFilePage/2009463077</steamWorkshopUrl> <downloadUrl>https://github.com/pardeike/HarmonyRimWorld/releases/latest</downloadUrl>
</li>
</modDependencies>

A significant number of mods have that same problem. I've made it a habit of looking at the files of EVERY mod I download to fix that issue. Off the top of my head, all of Dub's mods and Autolink, but there's many other popular mods like that... Achtung, as well.

I only started doing this when I noticed it was Autolink causing a weird ass issue with my base having infinite power (might have only been a text ui glitch, I dunno). Removing the .dll and .xml fixed the issue, and Autolink worked perfectly. It's a real pain in the ass, and I should probably just write a program to do it for me.

That is not it.
As long as you load the Harmony mod at the correct position, at the top of your list, NO OTHER 0harmony.dll is going to be loaded, no matter what. That was actually the whole issue leading to the creation of the independent Harmony mod in the first place. Leaving or deleting the dlls of individual mods will have no effects whatsoever. And I certainly don't advise that.
To get a sense of how bad you miss the mark with this, the Achtung mod you mention was developed by the very author of Harmony. You owe him the very existence of 90% of all mods!!