[DEV][0.24.x][Jul 24] SCANsat v7.0rc4 -- Real Scanning, Real Science, at Warp Speed!

[technogeeky]

I have edited the first post to issue the standard warning about ModStatistics.

[DMagic]

Release Candidate 2.5 has been posted on GitHub.

This is primarily an update for the new version of RasterPropMonitor.

The folder structure has changed, you must delete the existing SCANsat folder and copy over the new version. You must also copy over the version of SCANsatRPM from the RasterPropMonitor package.

- Updated for RPM v0.17

- Fixed a bug with map caching

- Fixed a bug with the small map opening on exiting timewarp with the non-toolbar version

- Active scanners will start already deployed instead of playing the animation on startup

- Internal version number, and version logging changes

Edited July 1, 2014 by DMagic

[Trailers]

Hello

I just updated the RasterPropMonitor to the new version (which is still quite beta as I understood it), and now I have no idea which SCANsatRPM I should take. Yours or the new one? The one from the 0.17 version of RPM is 1kB bigger. Thank you for answering

EDIT: sry, didn't see the post on top of this one.. Everything cleared ^^

[Agathorn]

I have to agree with some others here in regards to my dislike of Modstatistics. I deleted Kethane because of it. It honestly serves little purpose and feels very much like spyware. Until such time as 1) I can see EXACTLY what is being sent and 2) The collected data is made available to the PUBLIC and not just mod authors, then I will treat this as nastyware. I'm technically inclined enough to remove it, but not everyone is.

I am glad to see ORS integration into SCANsat though. I was thinking of doing that myself but you saved me the trouble.

[technogeeky]

I have to agree with some others here in regards to my dislike of Modstatistics. I deleted Kethane because of it. It honestly serves little purpose and feels very much like spyware. Until such time as 1) I can see EXACTLY what is being sent and 2) The collected data is made available to the PUBLIC and not just mod authors, then I will treat this as nastyware. I'm technically inclined enough to remove it, but not everyone is.

I am glad to see ORS integration into SCANsat though. I was thinking of doing that myself but you saved me the trouble.

The reason that both DMagic and I agreed with adding ModStatistics in the first place is because it only takes a few minutes to review the source code for it (it's all in one file; and the data gathering only consists of one function).

We both indepdendently reviewed the code and agreed that it was safe and not spying on anybody. As far as I understand, the only private information that can be gleaned from the submission of the report is that the act of submission will connect to a remote server; and in doing so you must reveal your IP. However; any mod which connects to any remove server will do the same (and several do; for instance, to check for updates). However, Majiir made it clear to us that he's not even recording the IPs.

The section of the relevant function is here.

Calling this spyware or nastyware is either propaganda or nonsense. Several data points which would help developers but would also carry a risk of de-anonymizing the results have already been considered and rejected. It's anonymous.

It collects only a tiny bit of information about what .dll files your game is using, and when crashes are happening. If you don't like it, you can delete it or opt out -- no functionality to you will be lost.

[rdwulfe]

So, question... Is ScanSAT supposed to record static under some conditions? I sent a satellite, equipped with both Biome and LowRes, to Moho. The LoRes scanner worked fine, but the Biome Scanner has only produced a map full of static. On the big map, the BIO scanner's indicator shows up red.

[technogeeky]

So, question... Is ScanSAT supposed to record static under some conditions? I sent a satellite, equipped with both Biome and LowRes, to Moho. The LoRes scanner worked fine, but the Biome Scanner has only produced a map full of static. On the big map, the BIO scanner's indicator shows up red.

It records static when you are low on power (or are about to be low, during a time warp); or when you use a scanner on a place that doesn't have that resource to scan (ie, Moho doesn't have a biome). In this case, it's probably the latter.

[Mecripp]

Is there away, I can make the show on the scanner screen ?

[Cashen]

Can anyone confirm that SCANsatRPM.dll works with the latest version (0.17) or RPM? Because I'm getting this error:

Before you ask, the craft had a MapTranq part attached to it. Note: The MJ-RPM light was also not green, but I was able to fix that by updating to the latest MJ. The error shown above happens with the 0.6 release of SCANsat or the Dev release in this thread.

[Mecripp]

Can anyone confirm that SCANsatRPM.dll works with the latest version (0.17) or RPM? Because I'm getting this error:

http://howling-coyote.org/ksp/UKSMASEC/0.png

http://howling-coyote.org/ksp/UKSMASEC/2.png

http://howling-coyote.org/ksp/UKSMASEC/4.png

Before you ask, the craft had a MapTranq part attached to it. Note: The MJ-RPM light was also not green, but I was able to fix that by updating to the latest MJ. The error shown above happens with the 0.6 release of SCANsat or the Dev release in this thread.

Yes it does did you click on part and open map maybe ?

EDIT- And don't know what the MJRPM.dll is there that comes with RPM .17 but, I also have KSP/GameData/MechJeb2RPM and see you have ScanSatRPM.dll but you don't show ScanSat.dll but sure you have it.

EDIT- I have ScanSat Map works but not MJ on the RPM

Edited July 7, 2014 by Mecripp2

[DMagic]

Can anyone confirm that SCANsatRPM.dll works with the latest version (0.17) or RPM? Because I'm getting this error:

It should work with the latest dev version. I need the versions for all three files, SCANsat, SCANsatRPM, and RPM to know for sure what's going on. If you're using the latest dev version of SCANsat v7rc2.5, then the KSP.log file would be the most helpful.

[Cashen]

It should work with the latest dev version. I need the versions for all three files, SCANsat, SCANsatRPM, and RPM to know for sure what's going on. If you're using the latest dev version of SCANsat v7rc2.5, then the KSP.log file would be the most helpful.

Using SCANsat v7rc2.4 (the one on the first page of this thread) and RPM 0.17 (also on the first page of its thread). I uploaded a KSP.log file here.

[DMagic]

Using SCANsat v7rc2.4 (the one on the first page of this thread) and RPM 0.17 (also on the first page of its thread).

That is, unfortunately, not the latest version of SCANsat. Get v7rc2.5 on the previous page, or at the top of the GitHub release page. Use the version of SCANsatRPM included in this update, not the one included with RPM.

v7rc2.4 will not work with v0.17 of RPM, only SCANsat v7rc2.5 has been specifically updated for RPM v0.17.

For SCANsat v6 the version of SCANsatRPM included with RPM should work (this version nonsense shouldn't be a problem for that much longer).

Your version of Kethane is also out-of-date and won't work with the SCANsat overlays; for that you'll need the latest version: Kethane 0.8.6 (this won't have any effect on SCANsatRPM or RPM).

Is there away, I can make the show on the scanner screen

I'm not sure what this means. Do you want to display some kind of grid on the SCANsat map, presumably one different from the current grid? Or do you mean some different kind of map projection?

Edited July 7, 2014 by DMagic

[Mecripp]

Using SCANsat v7rc2.4 (the one on the first page of this thread) and RPM 0.17 (also on the first page of its thread). I uploaded a KSP.log file here.

Cashen Try this zip up or take a Hyomoto file.

Edit- maybe JSI update is running after Hyomoto patch.

Edited July 7, 2014 by Mecripp2

[Cashen]

That is, unfortunately, not the latest version of SCANsat. Get v7rc2.5 on the previous page, or at the top of the GitHub release page. Use the version of SCANsatRPM included in this update, not the one included with RPM.

v7rc2.4 will not work with v0.17 of RPM, only SCANsat v7rc2.5 has been specifically updated for RPM v0.17.

For SCANsat v6 the version of SCANsatRPM included with RPM should work (this version nonsense shouldn't be a problem for that much longer).

Your version of Kethane is also out-of-date and won't work with the SCANsat overlays; for that you'll need the latest version: Kethane 0.8.6 (this won't have any effect on SCANsatRPM or RPM).

I'm not sure what this means. Do you want to display some kind of grid on the SCANsat map, presumably one different from the current grid? Or do you mean some different kind of map projection?

Thanks for the help. Updating SCANsat and Kethane now.

EDIT: That worked. Thanks again.

Edited July 7, 2014 by Cashen

[KerbMav]

I am at a loss here ... does SCANsat now scan for ressources (in the background like the maps) or only show them on its maps?

[DMagic]

I am at a loss here ... does SCANsat now scan for ressources (in the background like the maps) or only show them on its maps?

Yes and yes

Using the Module Manager configs included in the download you can scan for resources in the same way that you would use regular SCANsat sensors; background scanning works and everything is persistent.

With Kethane type resources you can also use SCANsat to show only what has been scanned using the regular Kethane sensors. By either removing the Module Manager configs, or simply not activating the SCANsat module on the sensors, SCANsat will be used to passively show existing Kethane scanning data on your maps.

For ORS resources you must use the included Module Manager configs to record scanning and to see any resource data on your maps.

[KerbMav]

Joy and jubilation!

[technogeeky]

I've updated the first post: please note this update reflects DMagic's update from several (12) days ago. Sorry for the delay.

[Dragonchampion]

Is this released for .24/Kethane 8.8?

[technogeeky]

Is this released for .24/Kethane 8.8?

We have not released a 0.24 version yet, no. This doesn't mean that the existing version won't work, however.

[Olympic1]

We have not released a 0.24 version yet, no. This doesn't mean that the existing version won't work, however.

, Then I'll wait

[DMagic]

Update released for KSP v 0.24 on GitHub.

- Updated for KSP v 0.24

- Folder structure significantly changed; you must delete any old SCANsat installations

- SCANsatRPM integrated into standard SCANsat

-You must delete any SCANsatRPM folders; do not install SCANsatRPM from any source

- Updated to support Kethane 0.8.8

- Modular Kolonization Module Manager configs removed; these are handled on the MKS side now.

- Many internal changes, mostly non user-side

- ModStatistics updated to 1.0.3

There are lots of folder structure changes, including the removal of SCANsatRPM. Just delete the entire SCANsat and SCANsatRPM folders when installing this. SCANsatRPM is no longer required for RasterPropMonitor compatibility, delete all copies of the SCANsatRPM.dll file and don't install others from any source.

There are a lot of internal changes, everything seems to be working ok, but let me know if anything weird happens.

Significantly, the backup cache for the old style of persistent map storage has been removed. I haven't seen any problems with the new style so this should be ok, but be aware of this if you are updating from SCANsat v6 or from before release candidate 2 for SCANsat v7; you may want to make a backup of your existing persistent file.

Edited July 18, 2014 by DMagic

[Olympic1]

Update released for KSP v 0.24 on GitHub.

- Updated for KSP v 0.24

- Folder structure significantly changed; you must delete any old SCANsat installations

- SCANsatRPM integrated into standard SCANsat

-You must delete any SCANsatRPM folders; do not install SCANsatRPM from any source

- Updated to support Kethane 0.8.8

- Modular Kolonization Module Manager configs removed; these are handled on the MKS side now.

- Many internal changes, mostly non user-side

- ModStatistics updated to 1.0.3

There are lots of folder structure changes, including the removal of SCANsatRPM. Just delete the entire SCANsat and SCANsatRPM folders when installing this. SCANsatRPM is no longer required for RasterPropMonitor compatibility, delete all copies of the SCANsatRPM.dll file and don't install others from any source.

There are a lot of internal changes, everything seems to be working ok, but let me know if anything weird happens.

Significantly, the backup cache for the old style of persistent map storage has been removed. I haven't seen any problems with the new style so this should be ok, but be aware of this if you are updating from SCANsat v6 or from before release candidate 2 for SCANsat v7; you may want to make a backup of your existing persistent file.

yeey............

[ecat]

Thank the Nine, and DMagic makes 10

I just cannot send my poor Kerbals to a planet or moon without having at least one scanning satellite in orbit. Jeb was becoming so bored testing decouplers I dread to think what he would have got up to if not for this timely intervention.