Jump to content

Coffee Shock

Members
 View Profile  See their activity

  • Posts

    35

  • Joined

  • Last visited

 Content Type 

Posts posted by Coffee Shock

  2. No defeat alert

    in Report A Bug

    Posted

    you can't defeat alert someone if you have already nuked them that day and they do not have FSS to keep their soldiers above the defeat alert limit.

     

    I know that.
    In my case all my nukes were thwarted and the target have the FSS.

  4. Moon Hotspot

    in Gameplay Discussions

    Posted

    [quote name='Provost Zakharov' timestamp='1296388773' post='2611028']
    If you're interested in reducing the complexity of the search from 360*180 evaluations down to a much smaller number, you can compute a continuous approximation to the discrete problem as your initial guess, then just examine a small number of points around that. Of course it's not really necessary with fast computers, but perhaps you find it mathematically interesting.
    [/quote]
    There is a much easier way to reduce the number of possible hotspot locations as they aren’t as random as you may think.
    Hint: Plot all hotspots found so far. ;)




    My hotspot finding code, maybe it’s of some use to someone.

    [code]
    struct pos_t {
    double lat;
    double lng;
    int efficacy;
    } static const pos_data[] = {

    //Moon 2010-11
    {70.00000002, 7, 50},

    {19.31114335506464, -81.5625, 50},
    {-37.16031654673676, -101.25, 55},
    {17.978733095556155, 113.5546875, 50},

    {30.14512718337613, 146.953125, 58},

    {-9, -161, 93},
    {-34, 145, 67},
    {-12, -19, 50},
    {-17, -173, 96},
    {37.71859032558813, -129.375, 56},
    };


    static int calc_efficacy(double h_lat, double h_lng, double base_lat, double base_lng){
    const double pi = 3.14159265358979323846264338327950288;
    const double deg2rad = pi / 180;
    const double magic_constant = 39.5856603902019127; //pi*12.6 ???

    double h_lat_rad = h_lat * deg2rad;
    double h_long_rad = h_lng * deg2rad;
    double base_lat_rad = base_lat * deg2rad;
    double base_long_rad = base_lng * deg2rad;
    double distance = acos(sin(base_lat_rad) * sin(h_lat_rad) + cos(base_lat_rad) * cos(h_lat_rad) * cos(h_long_rad - base_long_rad));
    return std::max(int(100 - distance * magic_constant), 50);
    }

    void moon_mars_find_hotspot(){
    const int num_data_points = sizeof(pos_data) / sizeof(pos_data[0]);

    std::vector<pos_t> scores;
    for(int lat = -85; lat <= 85; lat++){
    for(int lng = -180; lng <= 180; lng++){
    int diff_sum = 0;
    for(int i = 0; i < num_data_points; i++){
    int efficacy = calc_efficacy(lat, lng, pos_data[i].lat, pos_data[i].lng);
    diff_sum += std::abs(efficacy - pos_data[i].efficacy);
    }
    pos_t tmp_pos = {lat, lng, diff_sum};
    scores.push_back(tmp_pos);
    }
    }

    int num_to_print = 30;
    int num_possible_hotspots = 0;
    std::vector<pos_t>::iterator it = scores.begin();
    for(; it != scores.end(); ++it){
    if(it->efficacy == 0){
    num_possible_hotspots++;
    if(num_to_print >= num_possible_hotspots){
    bool tilt = calc_efficacy(it->lat, it->lng, it->lat, it->lng) != 100;
    std::cout<<"lat="<<std::setw(5)<<it->lat<<(tilt ? "*" : " ")<<" lng="<<std::setw(5)<<it->lng<<std::endl;
    }
    }
    }
    std::cout<<"Possible hotspots: "<<num_possible_hotspots<<std::endl;
    }
    [/code]

  8. Moon Hotspot

    in Gameplay Discussions

    Posted

    OK smart guy, what did I miss? Please enlighten us.

    There was nothing wrong in your calculations but it was not a pure math problem.

    The hotspot is {-71, 67} but instead of making it a special case the game calculates the distance and any distance greater than zero is rounded down to 99%.

    In this case floating-point accuracy makes the distance non-zero even when the moon facility is exactly on the hotspot.

    I calculated the error from the correct position so that the distance calculation gives exactly zero.

  12. Moon Hotspot

    in Gameplay Discussions

    Posted

    moon radius in yards = 1899606

    distance to hotspot in yards = ARCCOS(SIN(base_lat*PI/180)*SIN(hotspot_lat*PI/180)+COS(base_lat*PI/180)*COS(hotspot_lat*PI/180)*COS((hotspot_lon*PI/180)-(base_lon*PI/180))) * moon radius in yards

    efficiency = ROUNDDOWN((1 - (distance to hotspot in yards / 4000000)) * 100)

    B)

  13. Moon Hotspot

    in Gameplay Discussions

    Posted · Edited by Coffee Shock

    This seems to work for me.

    moon diameter = 3474

    efficiency = max((1 - (distance to hot spot / moon diameter)) * 100, 50)

    That gives:

    for efficiency > 50

    distance to hot spot = (1 - (efficiency / 100)) * moon diameter

    Now it's easy to find the hot spot from three coordinates with trilateration. B)

    Edit: Incorrectly placed parentheses.

  16. Question Re: Secret Aid

    in Question Center

    Posted

    You can see how it looks here:

    http://www.cybernations.net/search_aid.asp...&Extended=1

    Only the person that you send the secret foreign aid to will know your identity. Successful 'Gather Intelligence' spy operations can expose the sender of a secret foreign aid agreement.

    Please don't add a spy op to discover who is sending secret aid.

    The whole idea of secret aid is to enable you to send aid in situations that would otherwise get you in trouble when sending aid, covertly breaking surrender terms supporting guerilla movements like Vox and similar.

    With the risk of discovery nobody will actually use secret aid just like nobody uses the regular spy ops in peacetime.

  17. Federal Aid Commission update

    in Gameplay Discussions

    Posted

    Please don't add a spy op to discover who is sending secret aid.

    The whole idea of secret aid is to enable you to send aid in situations that would otherwise get you in trouble when sending aid, covertly breaking surrender terms supporting guerilla movements like Vox and similar.

    With the risk of discovery nobody will actually use secret aid just like nobody uses the regular spy ops in peacetime.

  22. Since CN is boring and PC and TPF "hate" each other

    in Open World RP

    Posted · Edited by CoffeeShock

    It looks odd to me when I see two CM attacks give exactly the same infra damage numbers ... such as 17.70

    OOC: from the CN info. index page:

    Cruise Missiles - Cruise missiles cost a base of $20,000 and cost a base of $200 to maintain. The results of a cruise missile launch are generated randomly. The maximum number of tanks that can be destroyed with one cruise missile is 10. The maximum number of infrastructure that can be destroyed is 10. The maximum number of technology that can be destroyed is 2. Purchasing satellite improvements increases cruise missile effectiveness +10% each and allows damage infliction beyond the damage caps up to 15 tanks, 15 infrastructure, and 3 technology. You may launch up to 2 cruise missile attacks per battle front per day. Cruise missile attacks do not count against ground battle attacks or vice versa. The costs to maintain cruise missiles are tripled after 50 cruise missiles."

    What other modifier is not listed in that informational paragraph?

    Wow, you challenged twisted to a duel without knowing the basics of the combat system. :o

    The line between bravery and stupidity is indeed thin.

  25. The equations?

    in Gameplay Discussions

    Posted · Edited by CoffeeShock

    I don’t see any good reasons to keep the land purchase cost secret.

    Land Purchase Cost:

    • 0 - 19.99 = 0.0 * Purchased Land area + 400
    • 20 - 29.99 = 1.50 * Purchased Land area + 400
    • 30 - 59.99 = 2.00 * Purchased Land area + 400
    • 60 - 99.99 = 2.50 * Purchased Land area + 400
    • 100 - 149.99 = 3.00 * Purchased Land area + 400
    • 150 - 199.99 = 3.50 * Purchased Land area + 400
    • 200 - 249.99 = 5.00 * Purchased Land area + 400
    • 250 - 299.99 = 10.00 * Purchased Land area + 400
    • 300 - 399.99 = 15.00 * Purchased Land area + 400
    • 400 - 499.99 = 20.00 * Purchased Land area + 400
    • 500 - 799.99 = 25.00 * Purchased Land area + 400
    • 800 - 1199.99 = 30.00 * Purchased Land area + 400
    • 1200 - 1999.99 = 35.00 * Purchased Land area + 400
    • 2000 - 2999.99 = 40.00 * Purchased Land area + 400
    • 3000 - 3999.99 = 45.00 * Purchased Land area + 400
    • 4000 - 7999.99 = 55.00 * Purchased Land area + 400
    • 8000 - ????? = 75.00 * Purchased Land area + 400

×
×
  • Create New...