http://bugs.winehq.org/show_bug.cgi?id=6033 --- Comment #30 from Arthur Nascimento <tureba(a)gmail.com> 2008-02-10 10:33:29 --- Nice one juhos! I had noticed the fixme message on changing the depth but I didn't think it could cause all this. As a result I have been seeing several games take up 100% processor and I never knew why. It must be using the processor to translate the pixels from 24 to 16 or 8, on software level. Not a fix, but a workaround is to start another X when playing Fallout. That, along with your comment on the screen depth, solved most of my problems. The command I use is similar to this: xinit `which wine` /home/path/to/fallout2.exe -- :1 -depth 16 So I guess ddraw needs a better algorithm for that task or figure out how to do it on hardware level. Until then, perhaps the message could a little bit more helpful than it is now. Perhaps saying about the software translation and how it can consume system resources. The curent message is this: fixme:xrandr:X11DRV_XRandR_SetCurrentMode Cannot change screen BPP from 32 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.