Compare the two renderings of the same point in the following code (this is just a reduced example, I know I could just zoom in the scene, it's not an option in original code):
Manipulate[Row[{
Graphics[Point[{0, x[t]}], PlotRange -> {{-0.1, 0.1}, {-0.1, 0.3}},
Axes -> False, ImageSize -> 10],
Graphics3D[Point[{0, x[t], 0}],
PlotRange -> {{-0.1, 0.1}, {-0.1, 0.3}, All}, Boxed -> False,
ImageSize -> 10, ViewVector -> {0, 0, 10^4}]
}], {t, 10, 100}, ControlPlacement -> Left,
Initialization :> (x[t_] = Abs@Sin[t]/t)]
The resulting two points animate like follows:
Here's a magnified version of the above animation to better see what happens:
You can see the point at left seems to move jerkily, while the one at right moves smoothly. After some time the left one stops moving, while the right one still does visibly move. This is due to antialiasing of positions, not just shape. 2D functions seem to round positions to integer screen coordinates, while 3D ones don't.
The second way with Graphics3D would be the best solution for me, but in some more complex 2D scenes the 3D engine takes too much time to render, making Manipulate unusable.
So my question is: is there any way to force 2D Graphics and functions like ListPlot antialias positions too, so that one didn't need to resort to 3D engine?


Initialization :> ( x[t_] := Abs@Sin[t]/t ) ]`
– Nasser Jan 31 '16 at 10:00=. This should really be=:. – Nasser Jan 31 '16 at 10:08pixeltool) on my animation. As for function definition, why should it be a delayed assignment (I guess you mean:=not=:)? It doesn't make any real difference here, and in general it isn't useful to completely reevaluate an expression for each argument unless the expression is not idempotent. – Ruslan Jan 31 '16 at 11:32