Вопрос Limit targets per tick

[kecupz]

how does this feature work?

 

[OXXXYMlRON]

Спойлер: e.g.

if (C::Get<bool>(Vars.bMiscLimitTargetsPerTick))
{
    for (int idx = 0, i < 16, i++) //we iterate through less entities than needed, therefore lowering the targets per tick scan.
        {
        
        ...
        }
}
else
{
    // do it normally lmao
}

 

[blarpkk]

Спойлер: e.g.

if (C::Get<bool>(Vars.bMiscLimitTargetsPerTick))
{
    for (int idx = 0, i < 16, i++) //we iterate through less entities than needed, therefore lowering the targets per tick scan.
        {
      
        ...
        }
}
else
{
    // do it normally lmao
}

This won't work, you're just going to iterate trough the same 15 entities every time lol

 

[OXXXYMlRON]

This won't work, you're just going to iterate trough the same 15 entities every time lol

yes, hence the "limit targets per tick". any problem lmao?

 

[BebeRexha]

records > 3
record.empty
records++

 

[OXXXYMlRON]

records > 3
record.empty
records++

lmao that's just wrong on so many levels

 

[blarpkk]

yes, hence the "limit targets per tick". any problem lmao?

the problem is that you are not limiting targets per tick you are just limiting the ragebot scan to 16 players, if you don't see any problem go back to learncpp.com please

 

[OXXXYMlRON]

the problem is that you are not limiting targets per tick you are just limiting the ragebot scan to 16 players, if you don't see any problem go back to learncpp.com please

are you fucking joking lmao, less players = less targets. learncpp.com

 

[3a7adka]

how does this feature work?

1. Find players that u can scan
2. Put it in array
3. Sort it (by fov maybe)
4. Use in scan only first elements of array (1-4)

 

[HDTRPlayzZ]

since no one here understood what was asked

const bool bFrameBelowTickRate = globals->iIntervalPerTick > Iglobals->flAbsFrameTime;
const bool bFrameBelowExpected = globals->iIntervalPerTick * 2 > globals->flAbsFrameTime

// give this the initial value of true
bool bTargetUpdateTick = true;

// we only wanna update constantly if our frames arent fucking dying lmfao
if ( bFrameBelowTickRate )
    bTargetUpdateTick = !( globals->iTickCount % 3 );
else if ( bFrameBelowExpected )
    bTargetUpdateTick = !( globals->iTickCount % 2 );

// then if our frames are bad and we dont wanna update every fucking tick so we dont run cs slideshow
if ( !bTargetUpdateTick )
    return;

Спойлер: e.g.

if (C::Get<bool>(Vars.bMiscLimitTargetsPerTick))
{
    for (int idx = 0, i < 16, i++) //we iterate through less entities than needed, therefore lowering the targets per tick scan.
        {
       
        ...
        }
}
else
{
    // do it normally lmao
}

I see what you did here lmfao but yeah meant i believe so anyway the amount of times you scan through entities per tick as that would make sense for fps reasons anyway lmao

 

[OXXXYMlRON]

since no one here understood what was asked

const bool bFrameBelowTickRate = globals->iIntervalPerTick > Iglobals->flAbsFrameTime;
const bool bFrameBelowExpected = globals->iIntervalPerTick * 2 > globals->flAbsFrameTime

// give this the initial value of true
bool bTargetUpdateTick = true;

// we only wanna update constantly if our frames arent fucking dying lmfao
if ( bFrameBelowTickRate )
    bTargetUpdateTick = !( globals->iTickCount % 3 );
else if ( bFrameBelowExpected )
    bTargetUpdateTick = !( globals->iTickCount % 2 );

// then if our frames are bad and we dont wanna update every fucking tick so we dont run cs slideshow
if ( !bTargetUpdateTick )
    return;

I see what you did here lmfao but yeah meant i believe so anyway the amount of times you scan through entities per tick as that would make sense for fps reasons anyway lmao

thats not limiting targets though, thats just scanning the same targets shittier

 

[HDTRPlayzZ]

thats not limiting targets though, thats just scanning the same targets shittier: roflanEbalo:

stopping your hitscan when certain things are reached then when they arent it continues effectively doing what this guy wants only updating hitscan when fps is good enough just run it in your target selection ez

 

[OXXXYMlRON]

stopping your hitscan when certain things are reached then when they arent it continues effectively doing what this guy wants only updating hitscan when fps is good enough

why would you stop your hitscan entirely? just scan thru less shit each tick lmao

 

[HDTRPlayzZ]

why would you stop your hitscan entirely? just scan thru less shit each tick lmao

only stops on the certain condition and if this guys pasting which most people do on this forums specifically legendware that wont help also its only stopping for a few ticks then continuing effectively limiting the targets hitscan cycles through per tick

 

[OXXXYMlRON]

only stops on the certain condition and if this guys pasting which most people do on this forums specifically legendware that wont help also its only stopping for a few ticks then continuing effectively limiting the targets hitscan cycles through per tick

yeah, it should stop on the condition of low fps :D

 

[HDTRPlayzZ]

yeah, it should stop on the condition of low fps :D

only reason why you should really want to do it imo anyway