Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by DMagic

  1. Yes, that's the general pattern. The high resolution scanners mostly have lower fov than their lower resolution counterparts.
  2. @linuxgurugamer I commented on Github about it. FOV is a bit convoluted, but basically the scanning map is a 360*180 array of the whole number lat/long coordinates for the surface. The FOV defines how many whole number degrees around the vessel that will be scanned. https://github.com/S-C-A-N/SCANsat/blob/release/SCANsat/SCANcontroller.cs#L2539-L2611
  3. No they are saying this mod isn't supported anymore and won't work with newer versions of KAS. The Breaking Ground expansion provides a set of parts that are more or less the same as these (but without some of the hassle), so there isn't much of a point updating and supporting this mod.
  4. SCANsat version 20.4 is out; get it on Space Dock. This version prevents the overlay window from opening when it shouldn't.
  5. The reappearing overlay window will need a hotfix. Should be out in a few days.
  6. Version 20.3 is out; get it on Space Dock. This update fixes some issues with the big map data not being updated, drawing visual maps of the new gas giants, along with a few other bugs and issues related to resources, and some missing localization fields. It also includes some adjustments of part masses. It also includes new UI features related to resource overlays including small resource overlay color legends on the big map, zoom map, and planet overlay control window. The big map and overlay control window also feature quick tools to adjust the low concentration cutoff for re
  7. Update for the map data issues should be out next week. Just had an endless series of minor issues that I've found with the new update that have delayed things. @omG?! The old part models won't be replaced. Any active vessels or craft files will still use the old models. The models and scanners are all new parts, most with significant difference in size and shape, so they can't really be a direct replacement. Regarding problems with RO and maybe other planet packs. I'm thinking this may be a memory issue related to the new visual maps. An option to disable them might at least be usef
  8. Slope is one of those tricky things that can get pretty complicated. It's highly localized and there are many different ways of calculating the value and reporting the value. SCANsat just asks KSP for the terrain height at a few points surrounding the center point, I think something like 5m distance. This is a little bit expensive to calculate, but not really significant in the scheme of things. (This is for the little instrument data window, the slope map is another matter, and is generally far less accurate). I think Engineer looks at the angle of the actual surface geometry relati
  9. @Alex33212 I spent a long time trying to get this to work a few years ago. I remember discussing it with JPLRepo around the time ResearchBodies was updated with a similar feature. But for SCANsat I kept on running into two problems: Altering the visible maps like this required making lots of copies of the textures (of potentially several planets that could be in view at the same time) then altering them, which was memory intensive (maybe this isn't as important anymore). And a significant amount of the visible detail on a planet comes from the normal map. You can basically wipe
  10. @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 cam
  11. @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 se
  12. 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.
  13. @Brigadier @TaintedLion KSP version? SCANsat version? Do the maps work correctly in other scenes?
  14. @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 crashi
  15. Definitely not, it's a little annoying that it asks this. @HebaruSan is there a way to tell CKAN not to generate this warning?
  16. 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 m
  17. @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.
  18. 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.
  19. @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.
  20. @Tonas1997 Because dds textures are flipped vertically. Usually any program that can open dds files also had an option to unflip them.
  21. 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.
  22. @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.
  23. @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
  24. @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 s
  • Create New...