You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a player space target is size 0.001 (and presumably smaller) the target becomes un-hittable. At this size, the target is too small to see at the default field of view, so the field of view needs to be set to ~10 degrees or smaller. Additionally, at the default sensitivity with 800-1000 DPI, the mouse can't always aim at the target, so for this testing I recommend lower sensitivity and/or setting the mouse DPI to a high value. I tried it at 19000 DPI since that was the max my mouse would do.
Here's a recommended target config for testing this.
Since the above target spawns under the cursor, you can easily test that it doesn't hit by not moving the mouse. If you want you can map the fire button to a key instead of the mouse and keep the mouse still. The issue appears related to the geometry being missed in the fire() call and not the aim being off from the user. It is possible that the aim of the fire ray is slightly off from the center of the aim, but I haven't found the root cause yet.
User @Daffa_Mafazi on twitter reported this issue (Thank you!).
The text was updated successfully, but these errors were encountered:
When a player space target is size 0.001 (and presumably smaller) the target becomes un-hittable. At this size, the target is too small to see at the default field of view, so the field of view needs to be set to ~10 degrees or smaller. Additionally, at the default sensitivity with 800-1000 DPI, the mouse can't always aim at the target, so for this testing I recommend lower sensitivity and/or setting the mouse DPI to a high value. I tried it at 19000 DPI since that was the max my mouse would do.
Here's a recommended target config for testing this.
And here's a session to test that target.
Since the above target spawns under the cursor, you can easily test that it doesn't hit by not moving the mouse. If you want you can map the fire button to a key instead of the mouse and keep the mouse still. The issue appears related to the geometry being missed in the
fire()
call and not the aim being off from the user. It is possible that the aim of the fire ray is slightly off from the center of the aim, but I haven't found the root cause yet.User @Daffa_Mafazi on twitter reported this issue (Thank you!).
The text was updated successfully, but these errors were encountered: