VenusEnvyXP

My apologies. I have not used Pastebin before. Here is a link to Google drive with the changelog. I've also included a screen shot of the two files with different sizes. The one on the left is GitHub, the one on the right is Curse. Thanks in advance. edit: ***RESOLVED. After @DMagic confirmed the size of mod on their computer (8,156,074 bytes) and where they downloaded their mod from (Github), I re-downloaded ScanSAT from Github and re-installed and the issue seems to be resolved after initial testing. My apologies for wasting forum time; I had uninstalled and reinstalled ScanSAT from various sources and uninstalled and reinstalled Kerbal prior to posting with no effect. Not sure why it resolved issue now. Thanks @DMagic.***

I've been sent here by Reddit, who suggested I might find help here. SCANsat problems - Kerbal version installed is 1.3.1 - SCANsat version installed is 18.1 downloaded from Curse - veteran Kerbal player I recently (in the past week) revisited Kerbal after being away for a while. Updated all my mods. Noticed SCANsat is not working. Symptoms: SCANsat items provide no additional info on right click (either in inventory or on rocket), SCANsat items in orbit, when double clicked, only say "No target", no effect on right click, no SCANsat tab anywhere in window, no SCANsat map access. The only way I know that Kerbal is picking up the mod is that the SCANsat items are available in the hanger and the SCANsat tutorial is available in the help menu. Installation path is Kerbal Space Program/GameData/SCANsat Troubleshooting: I uninstalled and reinstalled Kerbal and re-downloaded SCANsat from an alternative site (Github). No other mods. No effect, still not working Note: The files from Curse and the files from Github were different sizes. Both are supposed to be version 18.1. (SCANsat folder-just the mod folder-7,539,626 bytes and 8,156,074 bytes respectively). Neither work. Not sure what size the most recent build is supposed to be. Might be important to note I only started playing again recently, since after the most recent release of SCANsat (October 11). Wondering if it may be a problem with the current build, but can't find anyone having this issue anywhere else. Thanks in advance! Edit: Link to output log - (Google link replaced an incomplete Pastebin post) please note that mechjeb was installed to see if by some miracle it solved the SCANsat problem. It didn't. Symptoms are the same.