ContractPack-RemoteTech icon indicating copy to clipboard operation
ContractPack-RemoteTech copied to clipboard

Minmus 95% coverage satisfied with one probe

Open robert-cassidy opened this issue 9 years ago • 3 comments

I didn't noticed until well after it cleared, but I just had a 95% coverage contract clear with only a single ship in orbit. It was equipped with a medium dish and a comm16 and in a polar orbit 15km peri, 100km apo. It was working on a D3Science 150 day magnetometer scan contract. I had no other ships in Minmus system.

Version 1.1.3 on KSP 1.0.2 on MacOS X 10.10.3 installed via CKAN.

I'll see if I can replicate on Mun.

robert-cassidy avatar May 10 '15 16:05 robert-cassidy

Let me know if you replicate - I have a feeling you got lucky. In terms of how it works, there are 20 points on each that are sampled to check if they have coverage. The check is done slowly in the background, if the contract is active the check will take something like a minute. So it's entirely possible to get and keep ~95% coverage with two satellites if the one satellite is on the backside for long enough.

The "testing time" bit is meant to mitigate that. And on the other side, sometimes things just go wonky - which is why it looks for 95% coverage instead of 100%. I'm inclined to say that yours is an edge case... but if you do manage to reproduce on the Mun let me know... as that may mean that I do need to change something.

jrossignol avatar May 11 '15 02:05 jrossignol

I can reproduce this if I time warp at max speed (I restrict launches to once every 10 days, using a recurring KAC timer). When I warp to my next launch window, it'll say the contract is complete even though I only had one satellite up.

jberkman avatar Jun 15 '15 04:06 jberkman

That makes sense in my case. I'm using KerbalConstructionTime so I have similar 10Kx warp windows. I wonder if RT breaks down at high warp in the same way that resource consumption breaks down?

robert-cassidy avatar Jun 15 '15 04:06 robert-cassidy