http://bugs.winehq.org/show_bug.cgi?id=5872
the3dfxdude(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tonglebeak(a)gmail.com
------- Additional Comments From the3dfxdude(a)gmail.com 2006-11-08 17:45 -------
*** Bug 5919 has been marked as a duplicate of this bug. ***
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5919
the3dfxdude(a)gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From the3dfxdude(a)gmail.com 2006-11-08 17:45 -------
Dupe. Yes, the dinput error is because of an old registry, but nothing to do
with the problem.
*** This bug has been marked as a duplicate of 5872 ***
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5253
------- Additional Comments From the3dfxdude(a)gmail.com 2006-11-08 17:42 -------
MGSX, seeing you are the reporter, can you set the DirectDrawRender = gdi and
remove sserife.fon??
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=5253
------- Additional Comments From the3dfxdude(a)gmail.com 2006-11-08 17:41 -------
To use OpenGL as directdraw renderer, you must have the latest wine 0.9.19, and
should have an Nvidia GF2 - FX (no later) card.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=5707
------- Additional Comments From alex(a)thehandofagony.com 2006-11-08 17:33 -------
I must admit that if I had not tested this on a slower machine than the
Pentium IV, I would probably not have noticed the difference. On the Celeron
2.8 GHz, the difference is quite clear. And if you consider that this game is
supposed to run fine on a 300-500 MHz computer . . .
The following results are from the Celeron.
In Wine 0.9.19, Settlers IV consumes around 65% of the CPU when I let it alone
with the console window on top of it. If I start scrolling around, this usage
increases to around 96%. X and wineserver use almost nothing (they are not on
the list most of the time; the most I could see X using was 0.3%.
In Wine 0.9.15, Settlers IV also consumes around 65%, but this usage does NOT
increase if I scroll the map, which sort of explains why the game is slower
when scrolling between the old and new code.
In 0.9.15, if I mouse the mouse, X usage goes from 22% to around 15%, and
wineserver usage goes up from around nothing to 1.3%.
Still, scrolling in 0.9.16+ is much slower than in 0.9.15-.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
http://bugs.winehq.org/show_bug.cgi?id=5833
------- Additional Comments From adi.l(a)bluewin.ch 2006-11-08 17:29 -------
It still happens with 9.19 i'll attach the new console output
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=4256
alex(a)thehandofagony.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #1638 is|0 |1
obsolete| |
------- Additional Comments From alex(a)thehandofagony.com 2006-11-08 17:05 -------
Created an attachment (id=3259)
--> (http://bugs.winehq.org/attachment.cgi?id=3259&action=view)
Console output with +mciavi from GIT 2006-08-11
Console output from current GIT (2006-08-11), with +mciavi.
Without any debug channels, the only output is this, one fixme for each of the
two films it tries to play
fixme:mciavi:MCIAVI_mciPlay Unsupported flag 02000003
fixme:mciavi:MCIAVI_mciPlay Unsupported flag 02000003
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=5820
------- Additional Comments From stefan.siebert(a)web.de 2006-11-08 16:42 -------
Patch should be ready tomorrow.
DIALOG_CreateIndirect was missing DLGC_HASSETSEL implementation on initialization.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.winehq.org/show_bug.cgi?id=3460
------- Additional Comments From rob(a)codeweavers.com 2006-11-08 15:27 -------
I don't see this bug myself, but it doesn't look like COM is doing anything
wrong. I think a +relay log will be necessary to examine what is going on in the
server function being executed (essentially between the CoInitializeEx and
CoUninitialize calls in the log you posted).
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are on the CC list for the bug, or are watching someone who is.