Marcel Märtens e4e5c6e55b massivly switch clock algorithm. ... - before we had a Clock that tried to average multiple ticks and predict the next sleep. This system is massivly bugged. a) We know exactly how long the busy time took, so we dont need to predict anything in the first place b) Preduction was totally unrealistic after a single lag spike c) When a very slow tick happens, we dont benefit from 10 fast ticks. - Instead we just try to keep the tick time exact what we expect. If we can't manage a constant tick time because we are to slow, the systems have to "catch" this via the `dt` anyway.		2020-11-10 18:31:42 +01:00
..
benches	Remove spurious uses of Vox.	2020-09-26 16:30:40 +02:00
examples	(See sharp/lod-history) LOD, shadows, greedy meshing, new lighting, perf	2020-08-20 20:34:59 +02:00
src	massivly switch clock algorithm.	2020-11-10 18:31:42 +01:00
build.rs	feat(voxygen): add logo for windows executable	2019-10-02 16:57:08 +02:00
Cargo.toml	ci cleanup, dependency update	2020-11-06 14:34:42 +01:00
clippy.toml	(See sharp/lod-history) LOD, shadows, greedy meshing, new lighting, perf	2020-08-20 20:34:59 +02:00