![]() It's possible that I'm too low or too high on that formula, but selection bias makes it hard to subjectively tell. How many depends on how many configured contracts there are. Each class of contract has its own rules for when it can generate a contract, and how many are simultaneously allowed (although in 0.90 Arsonide was kind enough to expose the max count "ma圎xistant" through GameData/Squad/Contracts/Contract.cfg).Ĭontract Configurator only has a single contract class, so I cheat this system a little bit by adding multiple copies of it to the stock selection list. The stock system works by asking each contract class whether it can generate a new contract (it randomly selects which one to ask). The weight unfortunately only applies to ContractConfigurator contracts - it's a weighting against other CC contracts. Is it worthwhile weighting all custom contracts higher than 1.0? (presuming everyone would prefer to see any other contract ahead of a part testing contract?) I think that visual indication of coverage would be a great feature for RemoteTech, and you should ask those guys about it.Īs far as the actual contract pre-requisites, I posted that a few pages back:Īlso I'm wondering how the stock contracts are weighted. the pretty stuff you get in Cyrik's Map Resource Overlay for SCANsat. I have no plans for a way to show the coverage, especially since it wouldn't look very pretty (a few random scattered points, vs. So that's why it can take some time before some contracts appear or before the contracts that rely on coverage get completed. Oh and it can only do the checks in flight or in the tracking station - RemoteTech isn't active elsewhere. So it checks the coverage fairly slowly - it's rougly two checks every second, such that it takes a little more than two minutes to do a full pass. If I did a full coverage pass all at once (16 bodies * 20 points = 320 checks), it takes about 2-3 seconds on my machine. The coverage system will place a fake satellite at each sample point, and ask RemoteTech if that satellite has a connection to back home. The points are distributed across the planet, but all within a -45 to 45 latitude (to be very generous and allow a tight network to be considered 100% coverage). ![]() The coverage works by sampling 20 points on each celestial body. I also saw my first custom contract appear, yay!Īctually, that's a good question. I guess the general question stands but as long as my concept of coverage generally matches it doesn't seem like a big deal. ![]() UPDATE: So I was just offered the Mun network contract so I obviously do have coverage. It hasn't appeared yet, and I just wanted make sure the requirements are met on the Kerbin side. I have a 5 satellite constellation around Kerbin and after declining the initial contract I'm ready for the second. How is coverage worked out? And is there any way see the coverage CC thinks a body has? I have question about this contract pack (Well, I guess it is really a ContractConfigurator question, but relevant to people with this Contract Pack.). Thanks so much for brining this one up, be sure to let me know in the thread if you have further issues. Contract Configurator 0.5.2 is up and fixes this issue. Basically the Target: Kerbin and Target: Active Vessel are mutually exclusive and are not supposed to show up in the same parameter. I'd changed how some stuff works and never when back and verified this contract. So what does the contract want me to do? Why doesn't it complete?Īh, when I finally got a chance to look at this, I see it's broken. My comsats work fine, and cover 100% of kerbin for any new vessel with the required range. and what do "range: in range of kerbin" and "count: at least 1" even mean? They always stay red, no matter how many antennas I power up.Īlso: for any following comsat (II and III), it won't check green their "direct connection" to the previous comsat, although the connection is undoubtfully established. It's activated and powered, or that it has the minimum range. It won't check that I have an antenna, or that But if I target (with another dish) the "active vessel" and turn on any amount of antennas to do the same, this will always stay red and won't register. If I target a dish (with >45 Gm) at kerbin, this requirement also checks green. Can't someone explain (or "translate") what I have to do in order for it to fulfill all the requirements? Contract is filled with ALOT of requirements which aren't really clear from the short description.įor example: My first comsat has a connection to KSC and is in the right orbit, those requirements are green. Just the very first contract ( ) won't register or something. Nah, I've been using RemoteTech for quite some time and I have no problems to establish the other contracts (like 90% mun coverage etc.). It sounds like you're new to RemoteTech - try checking out their Tutorials page.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |