Исходник Correct bt ticks calculation for lw

[flengo]

int aim::calc_bt_ticks() {
    auto records = &player_records[final_target.record->player->EntIndex()];

    for (auto i = 0; i < records->size(); i++)
    {
        auto record = &records->at(i);

        if (record->simulation_time == final_target.record->simulation_time)
            return i;
    }
}

auto backtrack_ticks = calc_bt_ticks();

возможно вронг

 

[djw666]

int aim::calc_bt_ticks() {

    auto player = final_target.record->player;
    auto records = &player_records[player->EntIndex()];

    auto rec = 0;

    for (auto i = 0; i < records->size(); ++i)
    {
        auto record = &records->at(i);

        if (record->simulation_time != final_target.record->simulation_time) {
            rec++;
            continue;
        }
   

        return rec;
    }


}

auto backtrack_ticks = calc_bt_ticks();

возможно вронг

хуйня разве нет?

 

[flengo]

хуйня разве нет?

попробуй включить фейкпинг и увидишь что у тебя неправильно считается потому что записи бектрека добавляются, а также первый валидный тик при дт чекни
запостил просто чтобы люди заметили проблему и все

 

[HDTRPlayzZ]

try to turn on fakeping and you will see that it is incorrect for you because the backtrack records are added, as well as the first valid tick when checking dt
posted just so people noticed the problem and that's it

fake latency increases the backtrack window so whats the point in removing that? inaccurate backtrack tick when using fake ping?

bullshit isn't it?

yes its useless and gives wrong bt tick with increased bt window due to fake latency

 

[flengo]

fake latency increases the backtrack window so whats the point in removing that? inaccurate backtrack tick when using fake ping?

yes its useless and gives wrong bt tick with increased bt window due to fake latency

lw default's will clamp it to 12 + max_shift, so my one correctly displays tick cuz it directly returns value from real player records
so its absolutely accurate way to calc ticks
also notice that each record has its unique simtime for player)

 

[stamidy]

lw default's will clamp it to 12 + max_shift, so my one correctly displays tick cuz it directly returns value from real player records
so its absolutely accurate way to calc ticks
also notice that each record has its unique simtime for player)

    auto tickcount = math.time_to_ticks(m_best_record.m_simtime + globals.m_lerptime);
    auto backtrackedticks = tickcount - globals.m_command->tick_count;

rocket science innit

 

[flengo]

    auto tickcount = math.time_to_ticks(m_best_record.m_simtime + globals.m_lerptime);
    auto backtrackedticks = tickcount - globals.m_command->tick_count;

rocket science innit

p asf

 

[Dadae]

bro this is insane

bro this is insane

im hitting backtrack like cray xd

 

[mj12]

Хрень, для хитлогов максимум. там и так нормальный бектрек и он делается одной строчкой
cmd->m_tickcount = TIME_TO_TICKS(final_target.record->simulation_time + util::get_interpolation());

 

[flengo]

Хрень, для хитлогов максимум. там и так нормальный бектрек и он делается одной строчкой
cmd->m_tickcount = TIME_TO_TICKS(final_target.record->simulation_time + util::get_interpolation());

там калькуляция тиков бектрекнутых, а не это немного

 

[flengo]

    auto tickcount = math.time_to_ticks(m_best_record.m_simtime + globals.m_lerptime);
    auto backtrackedticks = tickcount - globals.m_command->tick_count;

rocket science innit

upd : ur way dsnt work jst checked
lol didnt notice for the 1st time it's alws 0

 

[stamidy]

upd : ur way dsnt work jst checked
lol didnt notice for the 1st time it's alws 0

Youre doing something wrong then.

 

[flengo]

Youre doing something wrong then.

upd: ure right sry