From 4c9cff9b1faca1aa71089969094b330fe641e1da Mon Sep 17 00:00:00 2001 From: aybe Date: Sat, 17 Oct 2020 02:08:52 +0200 Subject: [PATCH] Revert "[MIGRATED] [PATCH 1/4] more bug notes" This reverts commit d5dc06fe859bacab234926346c123a368e06cff7. --- docs/BUGS/Impact Studios - Legend.txt | 23 ----------------------- 1 file changed, 23 deletions(-) delete mode 100644 docs/BUGS/Impact Studios - Legend.txt diff --git a/docs/BUGS/Impact Studios - Legend.txt b/docs/BUGS/Impact Studios - Legend.txt deleted file mode 100644 index c9a1de525..000000000 --- a/docs/BUGS/Impact Studios - Legend.txt +++ /dev/null @@ -1,23 +0,0 @@ -Impact Studio - Legends - -BUG: Demo timing runs at half speed, eventually malfunctions and gets - stuck in the double-lens section of the demo. - -If you run the demo and the bouncing ball and rotozoomer sections run -slowly, then you are seeing the bug in effect and you should consider -exiting out because the demo will glitch at the lens section and -never progress past it. - - - It's not a PIT issue, I tried hacking the PIT to halve the interval. - All that does is cause the music to play twice as fast but has no - effect on the frame rate. - - - So what IS the demo using for a timer source then? The RTC? - - - I remember this bug first showing up in DOSBox 0.74, previous - versions of DOSBox (0.72) ran the demo perfectly fine, which is - how I was able to do the demoscene capture for the demoscene - collection DVD on scene.org. So what did previous versions of - DOSBox do right that DOSBox 0.74 (and therefore DOSBox-X) does - wrong? -