[1.1.3] AntennaRange 1.11.4 - Enforce and Encourage Antenna Diversity

[toadicus]

LOL so lost in the math you have ( If you look closely, I'm actually doing math on them: @mass *= 0.25 multiplies the mass by 0.25, which makes it smaller. Same thing applies to the range.)

but the mass of the part is ( mass = 0.025 ) your @mass *= 0.25 multiplies the mass by 0.25 would you @mass -= 0.25 when scaling down ?

@mass *= 0.25 multiplies the declared mass by 0.25. In Squad's config, the mass is declared as 0.025, so my patch line will do 0.25 × 0.025 and the resulting mass of the part will be 0.00625. A "-=" operator would do subtraction; .025-.25=-0.225 and that's definitely not what we want.

Toadicus, thanks for the feedback. I've modified my configs accordingly.

Here are a couple more for people using ORIGAMI folding antennas:

@PART[NAU_ORI350Gm]:FOR[AntennaRange]
{
    %MODULE[ModuleDataTransmitter]
    {
        %name = ModuleLimitedDataTransmitter
        nominalRange = 350000000000
        maxPowerFactor = 8
        maxDataFactor = 4
    }
}

@PART[NAU_ORI69Gm]:FOR[AntennaRange]
{
    %MODULE[ModuleDataTransmitter]
    {
        %name = ModuleLimitedDataTransmitter
        nominalRange = 69000000000
        maxPowerFactor = 8
        maxDataFactor = 4
    }
}

Thanks for contributing! I should make a place for you guys to consolidate and maintain these configs.

[BudgetHedgehog]

but the mass of the part is ( mass = 0.025 ) your @mass *= 0.25 multiplies the mass by 0.25 would you @mass -= 0.25 when scaling down ?

No, because you're multiplying by a quarter (essentially, dividing by 4). If you multiply anything by <1, it becomes smaller. I don't know if MM can do subtraction, I think it only does multiplication. But as I said, to get a smaller number, you just multiply it by <1.

[toadicus]

No, because you're multiplying by a quarter (essentially, dividing by 4). If you multiply anything by <1, it becomes smaller. I don't know if MM can do subtraction, I think it only does multiplication. But as I said, to get a smaller number, you just multiply it by <1.

ModuleManager can do all basic arithmetic plus exponentiation:

                    switch (op)
                    {
                        case '*':
                            value = (os*s).ToString();
                            break;

                        case '/':
                            value = (os/s).ToString();
                            break;

                        case '+':
                            value = (os + s).ToString();
                            break;

                        case '-':
                            value = (os - s).ToString();
                            break;

                        case '!':
                            value = Math.Pow(os, s).ToString();
                            break;
                    }

[Mecripp]

Thanks for the math help guys hehe.

[BudgetHedgehog]

ModuleManager can do all basic arithmetic plus exponentiation

Well, isn't a nifty little trick. I stand corrected

[Kerbas_ad_astra]

Yet another patch, adding an antenna to the Universal Storage EVA-X pack (inspired by MonkeyWrench, using the same stats), because Kerbals should be able to radio back their reports (provided they remember to grab the radio, of course...).

@PART[US_R200_EVA_EVAX]:FOR[AntennaRange]{
    %MODULE[ModuleLimitedDataTransmitter] {
        name = ModuleLimitedDataTransmitter
        nominalRange = 5000
        maxPowerFactor = 8
        maxDataFactor = 4
        packetInterval = 0.3
        packetSize = 1
        packetResourceCost = 3.0
        requiredResource = ElectricCharge
    }
}

[Mecripp]

Yet another patch, adding an antenna to the Universal Storage EVA-X pack (inspired by MonkeyWrench, using the same stats), because Kerbals should be able to radio back their reports (provided they remember to grab the radio, of course...).

@PART[US_R200_EVA_EVAX]:FOR[AntennaRange]{
    %MODULE[ModuleLimitedDataTransmitter] {
        name = ModuleLimitedDataTransmitter
        nominalRange = 5000
        maxPowerFactor = 8
        maxDataFactor = 4
        packetInterval = 0.3
        packetSize = 1
        packetResourceCost = 3.0
        requiredResource = ElectricCharge
    }
}

HEHE been there done that lol and some where, I got alittle radio and done it to and alittle screen from something that poeple put MJ on forgot what the post was.

EDIT- Been Lazy and don't add all to my main file so some, I have are floating around somewhere in folders.

EDIT- I see, I did use a longer range but it was in the file, I have posted but, I like your range better will get around to dropping it.

Edited December 4, 2014 by Mecripp2

[toadicus]

I would like to request that all of you who are producing patches for popular consumption do so using "gist"s from github. You don't need to know anything about git; it's just a place to keep text files and track their history. I'll take a look at patches posted via gist and link to good ones in a spoiler on the OP. If I don't think they're good, I'll tell you why.

For an example, look at this totally bogus patch and its version history. You can even download the raw file with links like this one to make distribution easy.

Fun note: I've just finished an "EVAManager" plugin that lets me add modules and resources to EVA Kerbals... they should be able to transmit without picking up an antenna in the pseudo-near future.

[Mecripp]

I would like to request that all of you who are producing patches for popular consumption do so using "gist"s from github. You don't need to know anything about git; it's just a place to keep text files and track their history. I'll take a look at patches posted via gist and link to good ones in a spoiler on the OP. If I don't think they're good, I'll tell you why.

For an example, look at this totally bogus patch and its version history. You can even download the raw file with links like this one to make distribution easy.

Fun note: I've just finished an "EVAManager" plugin that lets me add modules and resources to EVA Kerbals... they should be able to transmit without picking up an antenna in the pseudo-near future.

O can't wait to play with it, Is there a OP on it ?

[toadicus]

I haven't released it yet; probably going to put it in Development for a bit and try to get feedback from other devs who might want to use it. I'll let you know here when I do.

[Kerbas_ad_astra]

Alright, here is the BoxSat config: https://gist.github.com/Kerbas-ad-astra/5395b0dd4808ccdd9a4b

And EVA-X: https://gist.github.com/Kerbas-ad-astra/5b99ab9e8fbcc8918c4f

I see that GitHub seems to think that I'm not a human (maybe because I'm a lean, mean, patching machine?), so let me know if you can't see the patches.

[Mecripp]

Alright, here is the BoxSat config: https://gist.github.com/Kerbas-ad-astra/5395b0dd4808ccdd9a4b

And EVA-X: https://gist.github.com/Kerbas-ad-astra/5b99ab9e8fbcc8918c4f

I see that GitHub seems to think that I'm not a human (maybe because I'm a lean, mean, patching machine?), so let me know if you can't see the patches.

Says ( Whoops )

[Kerbas_ad_astra]

What's really funny is that it does for me as well. Bummer! I guess I'll wait until they decide that I'm a human, or you can put them up.

[Mecripp]

What's really funny is that it does for me as well. Bummer! I guess I'll wait until they decide that I'm a human, or you can put them up.

Lets see if this worked Removed

EDIT- You can see it did you setup a sign in ?

EDIT- can you see this 1 Removed

Edited December 5, 2014 by Mecripp2

[Kerbas_ad_astra]

Looks good to me.

[Mecripp]

Looks good to me.

Can you edit any or add to it ? Removed

Edited December 4, 2014 by Mecripp2

[Kerbas_ad_astra]

I'm not seeing the robot warning anymore, and can see my own gists again (and they seem to be public -- I have the option to hide them).

I can fork your gist and edit that, but I'm not seeing an option to make a pull request.

[Mecripp]

I see it lol, I think.

EDIT- Could see your for a min and then lost them ?

Try this 1 https://github.com/Mecripp/Kerbal-/blob/master/AntennaRange%20Patches <--- think you can pull this 1 make change in all.

Edited December 4, 2014 by Mecripp2

[toadicus]

Gists do not support pull requests at this time, but forks retain version history. It's not perfect but it gets the job done.

I've left comments on all three gists I've seen posted so far.

Edit: If you guys want to use git instead that's fine with me; I'm happy to set up a github repo for 3rd party AntennaRange patches and let you do pull requests against it. But git's not everyone's cup of tea, so I don't want to force it on patch authors.

Edited December 4, 2014 by toadicus
Added git discussion. Fixed a typo.

[Mecripp]

Did alittle work on the file and didn't remember why, I override your tell seen, It's was the cut ranged one is what, I play with will try and brake it all down in parts.

https://github.com/Mecripp/Kerbal-/blob/bb4d1527c8b4c6725e30259bd2a9cf207c8567f5/AntennaRange%20Patches

EDIT- https://github.com/Mecripp/RT2-AntennaRange-Patch

Edited December 6, 2014 by Mecripp2

[toadicus]

No, those are both pass declarations and only one can apply. For each "mod", ModuleManager runs three passes in order: :BEFORE[], :FOR[], then :AFTER[]. I'm not sure what ModuleManager would do if you included both; either throw the patch away or just use the first, I'd guess. In any event, you should only use one pass declaration.

[Mecripp]

No, those are both pass declarations and only one can apply. For each "mod", ModuleManager runs three passes in order: :BEFORE[], :FOR[], then :AFTER[]. I'm not sure what ModuleManager would do if you included both; either throw the patch away or just use the first, I'd guess. In any event, you should only use one pass declaration.

O that was a brain fart ? know that from :NEEDS and :FOR it pretty much throw the patch away seen someone have that problem and thats what it was.

[toadicus]

AntennaRange has been updated to version 1.6! This version brings KSP 0.90 compatibility, and adds preliminary, in-testing support for transmission directly from EVA Kerbals.

NOTE: EVA Transmission is a really big change from a balance perspective. It is currently intentionally unbalanced, to the point that its use probably constitutes an exploit. Properly balancing this features A Big Deal, and interplay with life support mods (which widely vary in their treatment of ElectricCharge) is not trivial at all.

CHANGELOG:

v.1.6 [2014-12-15]
* Updated for KSP 0.90.0
* Adds preliminary, in-testing support for transmission directly from EVA Kerbals.

Edited December 16, 2014 by toadicus
Struck "probably" an exploit, because it is totally an exploit.

[KasperVld]

Interesting, what's your idea forward with that feature? Short range communications?

[cantab]

I can see that being neat to have. "Transmit one, store one" is a common technique to improve science yields, and being able to do that with surface samples without having to get back into the pod will be convenient.