perryh@xxxxxxxxxxxxxx schrieb:
Many older games that are programmed for Windows and DOS use
busy-wait polling for the input devices, such as the mouse ...
it is no wine problem, but a design decision of the makers
of the program ...
Granted it is primarily caused by the program, but I think Wine
*could* do something to reduce the impact: before returning
"no input available" from one of these polling (non-blocking)
APIs, sleep for, say, 1/10 of a second.
I am not too deep into those things. I know that about the CPU, because
I did see it with my own eyes for several games, especially DOS games or
Windows games, that are actually DOS games for the most part. Now for
windows there are several utilities available to set the priority of the
process, but I guess they would still need 100%, just make the game more
responsive. I am positive that this busy-wait polling has to go through
wine APIs at some time, But I don't know the wine sources and can't tell
where that should be, or if it is possible to limit the calls to them
there... that's something for the developers I think. And it would be a
feature request, not a bug report. Letting wine behave like windows is
not to be seen as bug in most cases ;)
bye Jochen
