DMagic

@RealKerbal3x Besides scanning characteristics (max scanning altitude, scanning fov) the two higher tech versions also scan for anomalies. Part mass is definitely something that can be adjusted. @MAFman It looks like the new Jool shader is quite a bit more complicated than the normal planet shaders. I can get pretty decent results with a simple fix: It's not as good as the real thing (Jool now has 5 8k * 4k textures making up its visible surface ), but not terrible either. The sun has a different set of problems, though I think it would be reasonable to assume that cameras meant to image a normal planet wouldn't be able to map the sun, so maybe I'll leave that alone. @Kepler452b It should work fine, I've tested in 1.8.1 while trying to track down the performance problems some people have seen in heavily modded installs of KSP (without any success in repeating those problems) and it seems to work fine. Also, lots of fixes and improvements are coming to the resource overlays in the next version: New resource overlay legends and quick adjustment tools (low right of the big map, and bottom of the overlay window), along with some changes to make handling installs with lots of resources a little easier.

@One eyed Smile @TaintedLion Does this problem happen with Kopernicus? I've seen something like it before, it is related to how Kopernicus unloads the height maps for bodies that aren't nearby. SCANsat forces it to load when a map is being drawn, but I think there are some cases where it doesn't always work right. Switching the map to another body, if one is available, will usually fix the problem. @RealKerbal3x Hi res scans always "overwrite" low res scans when the map is being drawn. The low res scanner still functions, though, for the purposes of science and contracts. You can see the low res scan progress in the new big map scanning coverage indicators.

1. Still there, just like the image indicates, it's only available when stock scanning is not disabled. 2. A vessel with a MechJeb module with the landing guidance function enabled. 3. Resource Biome Lock toggled on means the biomes must be scanned from the surface for full accuracy. 4. All scanning means all scanning, there is no distinction between background vessel scanning and active vessel scanning. All scanning is performed through a single function, disabling this option will turn off that function.

@Brigadier @TaintedLion KSP version? SCANsat version? Do the maps work correctly in other scenes?

@SkiRich I think the max is 10 active contracts. But I haven't tested that, I'll have to look into it. You should be able to adjust it by changing this line in the contract file: https://github.com/S-C-A-N/SCANsat/blob/release/SCANassets/Resources/Contracts/ContractPackScanSatOfficial.cfg#L8 @DStaal @syngen @Waltert I'll have to look into how resources are handled there. It's possible that SCANsat is missing resource definitions if they are being changed at some point after KSP starts up. @jimmymcgoochie I haven't seen or heard other reports of this type of performance or crashing issue. I did quite a bit of testing with JNSQ in 1.8 for the latest version and didn't have any problems. There is the potential for certain planet packs to have slower map generation performance than others, as that is dependent on the complexity of the terrain that is generated (for instance, the stock Mun has much slower terrain map performance than other stock planets because of how the craters are generated), but that is generally relatively mild, and shouldn't lead to crashing. It's possible that you are having memory issues related to the problems that were fixed in the latest update, try version 20.2 to see if it improves things. @HebaruSan Thanks for looking into it. I leave out the settings file so that new updates don't override any existing files.

Definitely not, it's a little annoying that it asks this. @HebaruSan is there a way to tell CKAN not to generate this warning?

SCANsat version 20.2 is out; get it on Space Dock. This version should work in any KSP from 1.8 to 1.10.x. There was a memory leak related to the visual map textures that has been fixed and you should see less memory usage in general related to visual maps. Some compatibility issues with Kopernicus related to SCANsat visual maps and the scaled space (map view) planet textures have been fixed. A new feature has been added to the zoom map that lets the map remember the last-used zoom level and apply that whenever the map is opened again, it is found in the top-left corner of the map, the small magnifying glass icon. Scanning coverage indicators have been added to the big map. These indicate both the total scan coverage percentage for the selected celestial body for each scanner, and the scanning coverage at the mouse position when the mouse is inside the map (let me know if anyone has issues with the text colors on these bars). Old SCANsat parts should be available in the VAB/SPH in existing saved crafts. Some other minor issues have been addressed, the PluginData folder for the settings file will be generated if it is missing, and the French translations have been updated (thanks don_vip). New zoom level "remember" toggle in green in the top-left: New scanning coverage indicators in the big map: The scanner type is indicated on each bar. The grey fill color indicates scanning coverage for that scan type on the selected celestial body. The scan type text color indicates coverage at the mouse position when the mouse is inside the map (the text is white when the mouse is not in the map). You can hover the mouse over the coverage bar to see a tooltip with the scanning cover percentage.

@KIMCHI Thanks for the notice. The texture warnings just indicate that the texture can't be compressed, so it takes up a little more space in memory, but these are tiny textures so it doesn't really matter. Does the NRE from Basic dV pop up repeatedly, or just once? There are some issues with it works that sometimes causes these one-time errors to pop up that I need to look into. The other error for Basic Orbit should be an easy fix, though I'm not sure if it actually affects anything, I've seen happen in other places before.

I think it's again a matter of the specific tool used to save the files. The PS tools usually automatically flip them, but there could be others that don't. It should be easy enough to confirm, though.

@Kerbart It's not too surprising that the struts and fuel lines might not work right. Those parts are quite complicated and Squad added variants, so EVA Struts and EVA Transfer might both have to be updated.

@Tonas1997 Because dds textures are flipped vertically. Usually any program that can open dds files also had an option to unflip them.

For people with scanning disabled: The only way that message should be displayed is for the background scanning to have been turned off. Go to the settings menu and turn it back on. @DeadJohn For that specific instance the best way to measure the scan percentage of the lo resolution altimetry scan would be to open the main map, only activate the lo res scanner, then look at the percentage shown there: Any decent orbit of the planet will eventually generate enough of the scan to complete the contract.

@KSPrynk A simpler solution is just to edit the config of the higher tech versions of the multispectral and hi-res resource scanners so that they don't require the surface to be in daylight. Isn't the Mun tidally locked? @Pabliski11 Any corrections or improvements to the translations are welcome. The best way to handle is to make a pull request for the files on GitHub. Just messaging with a set of corrected files would also work.

@SkiRich I'm not sure what you mean about the BTDT part name, the new version should be scansat-exomars-1, the old one is SCANsat_Scanner32, and KSP confirms that it's loading both parts at startup. I'll have to load up a save file with the old BTDT to see if I can replicate what's going on. Scan data is not tied to a certain scanner part. The data is stored independently of parts and vessels. So if you've scanned something for low res altimetry, for instance, it will always remain scanned for that (unless you reset the data), regardless of what happens to the vessel or part that did the scanning. Contracts have been adjusted to account for the new scanner parts and types. I believe that all currently running scanners will need to be reactivated when upgrading from SCANsat version 18 to version 20. You would have to load the vessel, click on the scanner part, and restart the scanner (you may have to click 'Stop Scan' then 'Start Scan' to activate it). I will add a note about this in the first post and release posts. @royying The green stones are the small surface features, right? SCANsat doesn't actually show the smaller features (small being what KSP considers a small feature, not necessarily based on its size, but a factor of its in-game definition). I think there were too many of them when I was testing so they just covered the scanning window with icons and made it hard to scroll through them in the BTDT window.

@SkiRich I'll look into the BTDT issues. There could be something wrong with the config file for the old version. If it is loading okay then you should still be able to access it in the VAB by searching or filtering in sandbox or if you have already unlocked it. And you can always edit the old config. The big map readout indicator things were starting to get unwieldy with so many scan types. But I like them, too, I will see if there is some other way to fill that function. @royying Do they show up as unknown objects in the BTDT window? Or just not at all? It will show as unknown until you have used the robotic arm thing with them. @Tonka Crash Thanks for the feedback. I will look into attach nodes, that makes sense for several of the parts.

@Brigadier The PluginData directory is for the settings file. The file itself isn't included with the download package so that you don't overwrite your existing settings. In general you can probably leave that directory alone when upgrading. When there are new settings entries included in an update then they should be seamlessly integrated into the existing file.

Version 20.1 is out; get it on Space Dock. This version fixes some issues with certain planet packs for Kopernicus, and makes some adjustments to part tech tree position and balance. There are also a few minor bug fixes. It should also update to CKAN without issues.

It would basically require entirely remaking all of the UI components. Earlier versions of KSP use a different version of Unity that isn't compatible with the assets in current versions. There would probably be a number of other issues that would come up as well, but the UI alone would take a significant amount of effort.

As far as I can tell this is an issue specific to moving Kerbin around. For some reason KSP just doesn't see Kerbin as a proper moon of Jool, nor does it see as a regular planet with the sun being its parent. It's easy to fix by making a specific check for the home planet (and any of its moons) to be sure that it is included in any lists. The fix will be in the next version (soon). Does anyone know of other planet mods that re-parent Kerbin as a moon like this?

I think KSP will generate one of those achievement message in the stock message app. Otherwise I think the only way to track that sort of thing is with Contracts Window+, which will also show you all of those kinds of progress and discovery achievements. @Syntax I have no idea why people are excited about those ideal altitude plots. I never cared about that. I just follow the basic instructions in the SCANsat KSPedia entry for setting up a good orbit. Also note that thread and most of the replies are from 2014, so they might not still be relevant. They definitely don't take into account the new parts.

@jaunco325 I think you "discover" an anomaly according to KSP when you come within about 2km of it. SCANsat marks anomalies in grey when scanned from orbit, and yellow when scanned with the BTDT, but you wouldn't necessarily have to come within the KSP anomaly distance to trigger that.

@Tabris Most of the testing and development for this version was done using KSP 1.8.1 (while generally building against the KSP 1.9.1 assembly files). So it should work fine in 1.8 and above. @HebaruSan Thanks, I've updated the remote file and will fix the local file in the next version. @Smurfalot Thanks for the suggestions, further scanner balance was one of things I was still looking to work on for this update. @hoover2701 I'm not sure the extent to how Kerbalism interacts with SCANsat. I know it can control the scanner activation in the background based on EC availability (or did at some point), that should still be working fine, I tried to make all of those externally used methods maintain their functionality. The new visual scans are just a different scan type value. The bigger change is that the scanner type value format has changed from a 32bit integer to a 16bit integer. This means there are only 16 possible scanner types available instead of 32, but that isn't an issue, since all of the high resolution resource scan types have been collapsed into a single type. Using a smaller integer type allows for better performance and less data needing to be stored in the save file. @birdog357 Which planet pack are you using? I assume this in KSP 1.8.1.

Version 20.0 is out, check out the release thread for details. Most of the issues from the dev version have been fixed: the MechJeb integration should be functioning again, Breaking Ground surface features should be detected and displayed properly, and there have been some fixes and changes to resource scanning. @Smurfalot It sounds like you didn't scan with the resource scanners. There are dedicated low and high resolution resource scanners. The stock scan threshold value is taken from the low resolution resource scan, so once you scan more than 90% of the surface for low resolution resources, the stock resource scan will also be completed, allowing for use of the stock resource overlays and maps.

@birdog357 I'll have to look into that again. It should have been fixed a long time ago, but there may still be a problem. @MaxPeck The old models are still there, just hidden by default in the part list.

SCANsat version 20.0 is out; get it on Space Dock. This version has changes made to scanning database format Requires one-time update of saved scan data which will be performed the first time KSP loads a save file with SCANsat v20 or higher installed Downgrading to an older version of SCANsat will results in a loss of data This version has a complete overhaul of the scanners, with 15 amazing new parts by @Nertea! There is also a new visual map scanner mode, along with an overhaul of the scanner type combinations and scanner properties. Some scanners now require that the surface be in daylight to function. Many changes have been made to SCANsat resource scanning. Scanning is now handled by 2 sets of new parts: 3 high resolution resource scanners: and 2 combined multispectral scanners for low resolution resource scanning (stock scanner parts can also be used as before) All resource types are scanned by a single scanner type now, instead of having different scanner types for each resource Various changes have been made to how low and high resolution resource scans are differentiated Contracts have been updated for the new resource scan types Additional information has been added to the scanner part right-click menus and the VAB/SPH part list info box. The KSPedia entry has been fixed and has several new entries and new info. And lots of various minor improvements and bug fixes have been addressed. See the first post for a full list of changes. Note that other mods adding SCANsat parts may need changes to function correctly. The new scanner parts; low resolution altimetry scanners: High res altimetry scanners: Multispectral scanners: High res resource scanners: High res visual scanners: BTDT: The full album is here: https://imgur.com/a/qXQ22f4 New visual maps: New PAW info groups: