[Freudstein]

Hi, in https://wiki.eduke32...Asked_Questions it's stated:

"Q: Why is aiming at objects so imprecise? The issue occurs only with the Polymost renderer and has its cause in the way it determines the aimed-at object: based on the mouse position on the screen, it constructs a direction vector and calls hitscan. Both steps are a cause of imprecision. The classic BUILD and the Polymer renderers determine the aimed-at object (roughly) by querying what object was drawn at the mouse position, and thus are pixel-perfect. If you prefer to use Polymost, try avoiding aiming at objects at the border of the screen and looking up or down, since the aiming method is particularly ill-behaved in these cases. *update: actually it's a bug that need to be fixed some time.c

Is this still true as of today? I've briefly played with Polymost and haven't noticed it yet. If it is, I think it should be documented somewhere more prominent instead of being buried as a footnote on a FAQ few people will read.

[Hendricks266]

This is referring to the level editor, not the game.

[Freudstein]

Ah, I see. Thanks!