Aacini wrote:Let me clear a couple points:
- Of course, there are a lot of other details we could test, like use native screen resolutions, or use different CPU cores (via Task-Manager or "start" /AFFINITY), and a long et cetera... However, all these "Different methods to decrease the screen flicker" are NOT the matter of this thread!
- This topic was created by einstein1969 in order to publish an antiflicker method devised by him, that is based on the following points:
- Fact: Windows 7 featured a new method "to group multiple software timer expirations into a single period of processing", that MS called "timer coalescing".
- Hypothesis: The timer used to update the %time% cmd.exe dynamic variable have a resolution of about 15.6 ms because it uses Windows 7 timer coalescing feature. The method used by cmd.exe to show characters in the window screen also use timer coalescing. In this way, if the display of characters in the screen is delayed until the %time% variable change, the screen flicker should decrease. This is called the "timer coalescing" antiflicker method.
I replied with my point that the Windows 7 "timer coalescing" feature have no relation with %time% variable nor with the display of characters on the screen, but that any decrease in the screen refresh rate (like a wait for a change on %time% variable) will decrease the flicker.
Although a test proved that this method don't works on my computer (nor in aGerman's one), einstein1969 insisted on his theory and diverged the cause of the flicker to other factors ("Peraph on monocore machine the timer colescing work well ?"; as corollary: the timer coalescing dont work on multicore machines). After this reply, @penpen posted this:penpen wrote:On my win10 it depends on the core which is used to execute it:
On one core there is flickering (and a frame rate of ~68fps), on the other i have ~96 fps and only rare flicker.
How could I know that this reply is not about the "timer coalescing" antiflicker method, but about an entirely different matter?
IMHO the replies that are unrelated to the topic should include some kind of advice, in order to avoid confusions...
I have used in my project a anti-flicker method that work on " Windows seven".
But i have discovered that there is a case that this not work well.
The method used in the game SNAKE of Dave Benham is to draw FAST and little.
This method work on xp and over.
The fastest method for draw is using the ECHO with multiple line Buffer.
I have seen that other user use a one ECHO with LF separator and seem faster.
Than I have discovered a method for antiflickering on window Seven that use a timers coalescing.
Recently i have discovered that this not work well in cases of APPLICATION active. Esample: Browser, Windows Audio/Video Players, some kinds of configurations.
I use a configuration with not DESKTOP COMPOSITION (AERO)!
When this is active the antiflicker don't work. It's possible disable in compatible option of executable but i have not tried.
Can someone try this?