I'm not sure what in the training set causes the models to do this, even in my own experience I'll be specific about the feature I'm building and the model will add an unnecessary status message for no reason.
Show HN: A new kind of FPS aim trainer
41–50 of 52 posts
Re: Show HN: A new kind of FPS aim trainer
#42Re: Show HN: A new kind of FPS aim trainer
#43Re: Show HN: A new kind of FPS aim trainer
#44Re: Show HN: A new kind of FPS aim trainer
#45Re: Show HN: A new kind of FPS aim trainer
#46Re: Show HN: A new kind of FPS aim trainer
#47Earlier quoted context omitted.
Are you using it on chromium? It's the only browser I get raw mouse events from right now, so other browsers tend to be more choppy. As for the habits, the point of this program is that it ultimately admits that far domain transfer for aim trainers is difficult regardless of what you do, so it tries to optimize in an absolute sense your motor control over your mouse. That way, regardless of scenario you'll have smoot…
Yeah I tried Firefox and Chrome EDIT: Maybe take some inspiration from Three.js? This demo works fine for Firefox and Chrome with a nice, smooth cursor that I'm used to https://threejsdemos.com/demos/camera/first-person
Re: Show HN: A new kind of FPS aim trainer
#48So cool! but somehow the simulation does not work on firefox. the crosshair is just stuck in the middle
Re: Show HN: A new kind of FPS aim trainer
#49the calibrated sensitivity is correct but the in-game sensitivity is waaaaay higher, it's a bug
Re: Show HN: A new kind of FPS aim trainer
#50This seems to suffer from what a lot of vibe coded projects suffer from, which is just a whole lot of unnecessary text everywhere. I find one shot outputs always have a lot of jargon, extra "micro copy" and displays the same information multiple times in multiple places. It makes it difficult at a glance to understand what you're looking at. I'm not sure what in the training set causes the models to do this, even in…