3 ms·
It's still now clear how small rounding change results with NaN. It would be understandable if some triangle would be off by one pixel on AMD and probably not n
by vbezhenar 6y ago
It's still now clear how small rounding change results with NaN. It would be understandable if some triangle would be off by one pixel on AMD and probably not noticeable.
So far it looks like a CPU bug which produces NaN on some input.
- mnarayan01 6y ago0/0 = NaN
- garmaine 6y agoGraphics uses a lot of stacked matrices. Small errors (more than just rounding, but within spec bounds) can add up to make the result non invertable. That results in NaNs.