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

[RoverDude]

Video on how to use ORS/SCANSat with Karbonite:

https://www.youtube.com/watch?v=lMozN4jpxbU&feature=youtu.be

[Aethon]

Huh? Love the mod and the cross functionality with other mods. Looking forward to Karbonite/ScanSat.

After watching the above vid. I realized I haven't seen the ScanSat button in my game. I'm going back in to see if I can find it. Been wondering how to turn the map on in ships with no Scan parts.

[leops1984]

(I originally posted this in the Karbonite thread, reposting it here slightly modified to make grammatical sense)

Help - I am having some difficulty in getting the Karbonite integration working. I followed the instructions in the Youtube video that RoverDude posted. However, when I try to turn on the Karbonite overlay in the big SCANsat map, the whole window goes transparent gray. None of the SCANsat buttons are there, etcetera. If I turn off the ORS layer, the window returns to normal. I honestly have no idea what's going on here.

[technogeeky]

(I originally posted this in the Karbonite thread, reposting it here slightly modified to make grammatical sense)

Help - I am having some difficulty in getting the Karbonite integration working. I followed the instructions in the Youtube video that RoverDude posted. However, when I try to turn on the Karbonite overlay in the big SCANsat map, the whole window goes transparent gray. None of the SCANsat buttons are there, etcetera. If I turn off the ORS layer, the window returns to normal. I honestly have no idea what's going on here.

This is probably a bug. Please submit a screenshot or two, and your KSP.log.

[impyre]

I came across a very obscure bug and it crashed the game. Here's the deal, when using scansat v7 rc4 alongside FinalFrontier 0.5.6 (and 0.5.1, i checked if updating FF would fix it, but it doesn't). I did a couple tests:

FF 0.5.1 + SCANsat7 rc4 = crash

FF 0.5.1 without SCANsat = fine

SCANsat7 rc4 without FF = fine

FF 0.5.1 + SCANsat 6.1 = fine

All tests were performed on pre-existing saves and new games (career mode) with exact same results. All tests were also repeated once I updated FF from 0.5.1 to 0.5.6, again with the same results.

Link to error info: https://www.dropbox.com/s/5zt4mwel3h1s382/error%20info.zip

As a bit of additional info, I'm running the latest x64 version of KSP on a windows 7 machine.

I'm by no means a coder, but I saw in the error log that the last thing going on before the crash was that FF was trying to draw its icons so I figured that the problem was something to do with FF, and the only thing I'd changed was upgrading SCANsat6.1 to dev version 7 rc 4 (due to realizing that it was the version required for the SCANsat integration with karbonite).

[DMagic]

I came across a very obscure bug and it crashed the game. Here's the deal, when using scansat v7 rc4 alongside FinalFrontier 0.5.6 (and 0.5.1, i checked if updating FF would fix it, but it doesn't). I did a couple tests:

Your log files indicate that you have a copy of SCANsat v7.0 release candidate 2.5 in your GameData/SCANsat/Plugins folder. Delete the entire SCANsat folder and start over, make sure you don't have any other copies of SCANsat.dll hanging around either.

[SCANlogger] Assembly: SCANsat found; Version: 1.0.6.0; Informational Version: v7.0rc2.5; Location: SCANsat/Plugins

[impyre]

It's mislabeled for some reason... it is indeed the latest version. In fact, today is the first time I ever downloaded it.

EDIT: in case you were wondering... it does indeed work with FF uninstalled... as I mentioned. Including the ORS scanning feature (well, it's present, but not working as expected... I suspect that's an issue related to my karbonite install though.)

[DMagic]

It's mislabeled for some reason... it is indeed the latest version. In fact, today is the first time I ever downloaded it.

EDIT: in case you were wondering... it does indeed work with FF uninstalled... as I mentioned. Including the ORS scanning feature (well, it's present, but not working as expected... I suspect that's an issue related to my karbonite install though.)

The version label is hard-coded, there's no way it could be mislabeled by the user without a great deal of effort. And any version prior to v7rc4 won't work with Karbonite.

[Mecripp]

I came across a very obscure bug and it crashed the game. Here's the deal, when using scansat v7 rc4 alongside FinalFrontier 0.5.6 (and 0.5.1, i checked if updating FF would fix it, but it doesn't). I did a couple tests:

FF 0.5.1 + SCANsat7 rc4 = crash

FF 0.5.1 without SCANsat = fine

SCANsat7 rc4 without FF = fine

FF 0.5.1 + SCANsat 6.1 = fine

All tests were performed on pre-existing saves and new games (career mode) with exact same results. All tests were also repeated once I updated FF from 0.5.1 to 0.5.6, again with the same results.

Link to error info: https://www.dropbox.com/s/5zt4mwel3h1s382/error%20info.zip

As a bit of additional info, I'm running the latest x64 version of KSP on a windows 7 machine.

I'm by no means a coder, but I saw in the error log that the last thing going on before the crash was that FF was trying to draw its icons so I figured that the problem was something to do with FF, and the only thing I'd changed was upgrading SCANsat6.1 to dev version 7 rc 4 (due to realizing that it was the version required for the SCANsat integration with karbonite).

Thanks impyre that fix my problem with ScanSat bad part is had to take out FF mod.

Edit- As with it ScanSat was dead nothing worked could use a older Ver but them no Karbonite showed on scansat.

Edit- and this was the error spamming the log with FF mod installed

NullReferenceException: Object reference not set to an instance of an object

at SCANsat.SCANsat.OnUpdate () [0x00000] in <filename unknown>:0

at Part.ModulesOnUpdate () [0x00000] in <filename unknown>:0

at Part.Update () [0x00000] in <filename unknown>:0

(Filename: Line: 4294967295)

Edited August 6, 2014 by Mecripp2

[impyre]

The version label is hard-coded, there's no way it could be mislabeled by the user without a great deal of effort. And any version prior to v7rc4 won't work with Karbonite.

Look man, I downloaded off the dev rc4 link... unless he linked the wrong file... I've listed it accurately. If you truly doubt my sincerity or competency, you're more than welcome to try for yourself and post your results.

EDIT: I just realized you said "mislabeled by the user"... I never said *I* mislabeled it... I said it was mislabeled... as in the dev hasn't updated the version numbers in the mod itself, it also reports the wrong version in-game as well.

EDIT2: When I called it version 7 rc 4, I use that version because it's how it was listed by the dev in the link, not because that's the version on any of the files.

Edited August 6, 2014 by impyre

[impyre]

Thanks impyre that fix my problem with ScanSat bad part is had to take out FF mod.

Edit- As with it ScanSat was dead nothing worked could use a older Ver but them no Karbonite showed on scansat.

Edit- and this was the error spamming the log with FF mod installed

On that note, I was unable to get this working with an old save (after removing FF) without first stripping all the FF stuff from the save manually (I also deleted old map info just in case).

[Mecripp]

@DMagic in the before this think it was DEV V7rc3 the 1 just before this 1 Karbonite shows in the setting on ScanSat but didn't show it on the map.

EDIT- @impyre you using ModuleManager.2.2.0 or the older ModuleManager that make a save file with that 1 you could go in and delete the save MM files?

Edited August 6, 2014 by Mecripp2

[Psykikk]

@DMagic in the before this think it was DEV V7rc3 the 1 just before this 1 Karbonite shows in the setting on ScanSat but didn't show it on the map.

EDIT- @impyre you using ModuleManager.2.2.0 or the older ModuleManager that make a save file with that 1 you could go in and delete the save MM files?

since MapTraQ is no longer working, how d I access the scansat map now ?

is toolbar a necessity now ?

thanks in advance

[Mecripp]

since MapTraQ is no longer working, how d I access the scansat map now ?

is toolbar a necessity now ?

thanks in advance

That would be a yes but think they still have the part in the pack so would think you could click on the part.

EDIT- sorry, I use toolbar but that would be my best guess

EDIT- well it shows MapTraQ in the parts folder and as a Texture but no part is showing up in the VAB.

Edited August 6, 2014 by Mecripp2

[impyre]

using MM 2.2.1

[impyre]

@DMagic in the before this think it was DEV V7rc3 the 1 just before this 1 Karbonite shows in the setting on ScanSat but didn't show it on the map.

EDIT- @impyre you using ModuleManager.2.2.0 or the older ModuleManager that make a save file with that 1 you could go in and delete the save MM files?

I'm having the same problem with the map not actually showing the resources. The settings to show karbonite are available, and the scanner does indeed work as a SCANsat sensor, but under sensors it lists no data while scanning. It's almost as if the scanner isn't configured properly. I'm still trying to figure out what the cause is.

[Mecripp]

I'm having the same problem with the map not actually showing the resources. The settings to show karbonite are available, and the scanner does indeed work as a SCANsat sensor, but under sensors it lists no data while scanning. It's almost as if the scanner isn't configured properly. I'm still trying to figure out what the cause is.

You still can't get it to work ? with out FF installed.

EDIT- With ScanSat v7.orc4

Edited August 6, 2014 by Mecripp2

[DMagic]

since MapTraQ is no longer working, how d I access the scansat map now ?

is toolbar a necessity now ?

thanks in advance

It's not strictly necessary, you can right-click on any SCANsat part and click Start Scan, or whatever the current button says, that should open the small map.

But there is no way to open the maps on a vessel without a SCANsat part. The toolbar isn't required, but it is recommended.

@DMagic in the before this think it was DEV V7rc3 the 1 just before this 1 Karbonite shows in the setting on ScanSat but didn't show it on the map.

Yes, it will show up in the settings menu in all versions, but it won't scan or display. The settings menu just loads all of the ORS resources from any ORS config files that are present; the actual scanning is handled differently and requires explicit support.

Look man, I downloaded off the dev rc4 link... unless he linked the wrong file... I've listed it accurately. If you truly doubt my sincerity or competency, you're more than welcome to try for yourself and post your results.

I downloaded rc4 from the link on the first post, both from the direct download link, and from the GitHub page, and everything worked fine. I downloaded Final Frontier and it worked ok on x64, I got some debug spam (the NRE pointed to Event-something something) when I loaded an old vessel, but that all went away after launching a new vessel. Karbonite works fine too.

Note the version numbers plastered all over the maps, if those don't say v7rc4 then the .dll is the wrong version (there is an issue on Linux where the version number shows up differently, but that's not the case here), Karbonite won't work, and it's likely that other problems may arise, too.

And as the person who was actually making those changes to the assembly version I am quite certain that the files included in the latest release are not wrong.

Edited August 6, 2014 by DMagic

[impyre]

Okay, I'm going to try again. I'll let you know what happens.

[impyre]

Well... it seems that while I was accusing you of doubting my competency... I forgot to check it myself first. It was really awesome of you to not only continue to help me, but also stay patient in spite of me being a jerk. Thank you for your help and time. Sorry for being lame.

[leops1984]

This is probably a bug. Please submit a screenshot or two, and your KSP.log.

Okay, here's the setup: scanning satellite with both low-res SCANsat scanner and the Karbonite scanner. In a sub-100km orbit. Without the ORS layer checked, it looks like this:

Then when you check the layer, for just the briefest moment, it's this:

Then after that:

The KSP.log file is huge - it's 14MB. This particular sequence repeats itself a lot, though

[LOG 20:00:48.362] [ORS] Loading Planetary Resource Data. Length: 14

[LOG 20:00:48.364] [ORS] Loading Planetary Resource Data for Kerbin

[EXC 20:00:48.366] UnityException: Texture 'UmbraSpaceIndustries/Karbonite/ORS/Kerbin_Karbonite' is not readable, the texture memory can not be accessed from scripts. You can make the texture readable in the Texture Import Settings.

The full log is here: https://spideroak.com/browse/share/lorem_ipsum_dolor/ksplog/ksplog/

Edited August 6, 2014 by leops1984

[Crater]

(((editing somehow caused a double-post)))

Edited August 6, 2014 by Crater

[Crater]

Okay, here's the setup: scanning satellite with both low-res SCANsat scanner and the Karbonite scanner. In a sub-100km orbit. Without the ORS layer checked, it looks like this:

http://i.imgur.com/yAwVyVa.png

Then when you check the layer, for just the briefest moment, it's this:

http://i.imgur.com/HpnEn54.png

Then after that:

http://i.imgur.com/UnGZ3Xf.png

The KSP.log file is huge - it's 14MB. This particular sequence repeats itself a lot, though

The full log is here: https://spideroak.com/browse/share/lorem_ipsum_dolor/ksplog/ksplog/

Are you using TextureReplacer?

Edit: Actually, I was thinking of ATM. By default, ATM loads all textures into graphics memory, and not into normal memory, to save space....

### Offload the texture from RAM into Graphics memory.

### this will mean the textures cannot be sampled by

### the scripts, but saves a LOT of memory. MBMs are

### not readable by default.

make_not_readable = true

I would very strongly suspect that is the cause of the error message that you are seeing, whether or not it is the cause of your map failing.

Edit 2: If that is the cause, you could try adding the following two files ... pretty much anywhere should work

ATM_MKS.cfg

ACTIVE_TEXTURE_MANAGER_CONFIG
{
	folder = UmbraSpaceIndustries/MKS/ORS
	enabled = true
	make_not_readable = false
	mipmaps = false
	scale = 1
	max_size = 0
}

ATM_Karbonite.cfg

ACTIVE_TEXTURE_MANAGER_CONFIG
{
	folder = UmbraSpaceIndustries/Karbonite/ORS
	enabled = true
	make_not_readable = false
	mipmaps = false
	scale = 1
	max_size = 0
}

I'm at work, so I can't test, but let me know

Edit 3: After a little more looking, I think the correct syntax for the file would be

ATM_USI.cfg

ACTIVE_TEXTURE_MANAGER_CONFIG
{
    folder = UmbraSpaceIndustries
    enabled  = true
    OVERRIDES
    {
        UmbraSpaceIndustries/Karbonite/ORS/.*
        {
            make_not_readable = false
            mipmaps = false
            compress = true
            scale = 1
            max_size = 0
        }
        UmbraSpaceIndustries/MKS/ORS/.*
        {
            make_not_readable = false
            mipmaps = false
            compress = true
            scale = 1
            max_size = 0
        }
    }
}

Edited August 6, 2014 by Crater

[DMagic]

Are you using TextureReplacer?

Edit: Actually, I was thinking of ATM. By default, ATM loads all textures into graphics memory, and not into normal memory, to save space....

I would very strongly suspect that is the cause of the error message that you are seeing, whether or not it is the cause of your map failing.

I've seen this before, but never been able to replicate it. I don't know why it causes such serious errors, but it appears to be caused by ORS failing to load the resource map texture for some reason. The best way to handle this is probably getting ORS to make sure that its maps are actually loaded before it starts doing stuff with them.

[Mecripp]

@DMagic I did reinstall FF to the new's ver and all works now don't know what the deal was but thanks for your time.