http://bugs.winehq.org/show_bug.cgi?id=20277
Summary: Elder Scrolls: Oblivion slowdown and loss of
background music since introduction of mpg123
Product: Wine
Version: 1.1.29
Platform: PC
URL: http://appdb.winehq.org/objectManager.php?sClass=versi
on&iId=7506
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msacm32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: vit.hrachovy(a)sandbox.cz
/*
>From application comments/ on behalf of JFM Rivera.
Also - missing winemp3.acm category for the bug, so assigning to msacm32.
*/
Up to wine 1.1.28 the game works normally, however, testing the newer two
versions (1.1.29 and 1.1.30) produces the following:
1. Incredible game slowdown (like a slideshow). The game slows down to the
point that it takes several attempts to register a key press.
2. Loss of background music (though ambient sounds come through) using ALSA
output (same as the issue noted on the post below)
Using OSS output I get no sound, but the game is at normal speed. Using OSS and
launching the game with "padsp wine" results in ambient sounds returning, but
the slowdown is back. No setting I've tried so far has resulted in restoring
the background music.
Under wine 1.1.28 sound works (ALSA) and the game runs at full speed.
Workaround:
Take winemp3.acm.so from /usr/lib/wine on a 1.1.28 install, and put it in
/usr/lib/wine on a 1.1.29 install.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=5535
--- Comment #64 from Xavier Vachon <xvachon(a)gmail.com> 2010-07-09 22:16:11 ---
Still a bug with wine 1.2-rc7. This line came very often in my console output,
if any relevant.
err:gdi:alloc_gdi_handle out of GDI object handles, expect a crash
--
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.
http://bugs.winehq.org/show_bug.cgi?id=20669
Summary: Certain objects found in game cause EQ2 to crash.
Product: Wine
Version: 1.1.32
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ben(a)walkingriver.com
While wandering around through the game, it will suddenly crash. Almost every
time, it happens when an item comes into view. The objects that cause these
crashes are unknown, but include crafting stations and the ykeshan bear mount.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=19659
Summary: EverQuest 2: EQ2 Crashed shortly after entering game.
Product: Wine
Version: 1.1.27
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jonilh(a)gmail.com
This problem seams pressent in the 1.1.2* versions of Wine
1.1.18 is not a problem. Latest tested 1.1.27 where the crashes still remains.
In 1.1.18 and earlyer, pets wont move, doors dont show as open when you open
them. This for the first few minutes everytime I start the game.
In 1.1.18 and earlyer this just corrects itself afer a few minutes and after
that works fine for that session.
But in the later versions of wine when it used to correct itself the game
insted crashes with a errormessage from Wine saying it might be a bug in wine.
I hope this will give some hint to where the problem can be.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=5402
Anastasius Focht <focht(a)gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |focht(a)gmx.net
--- Comment #32 from Anastasius Focht <focht(a)gmx.net> 2010-07-09 17:28:12 ---
Hello,
--- quote ---
What's the simplest way to create a test case for this behaviour? Creating a
not
visible overlapped, and then a visible popup windows work same way under Wine
as they do under Windows (i.e. GetFocus() and GetActiveWindow() return same
active and focus windows). Are there any SetWindowPos, SetParent, ShowWindow
that required to replicate the bug?
--- quote ---
Well, it's a deviation of the tabstop+focus
assignment issue explained in bug 19052
(http://bugs.winehq.org/show_bug.cgi?id=19052#c8)
GetNextDlgTabItem() is still most likely the cause.
More (undocumented?) corner cases need to be handled.
The window hierarchy for the case here (using "PhotoStitch 3.1"):
---
(1) top level (main app window)
Title=PhotoStitch
Parent=Topmost
Style=0x4CF0000
(WS_OVERLAPPED|WS_MINIMIZEBOX|WS_MAXIMIZEBOX|WS_CLIPSIBLINGS|WS_SYSMENU|WS_THICKFRAME|WS_CAPTION)
ExtStyle=0x300 (WS_EX_WINDOWEDGE|WS_EX_CLIENTEDGE)
Class=Afx:400000:b:2020c:6:30238
(2) dialog control bar
Parent=(1)
Style=0x40000040 (DS_SETFONT|WS_CHILD)
Class=#32770
(3) OLE drop target window?
Parent=(2)
Style=0x50000000 (WS_CHILD|WS_VISIBLE)
Class=Afx:400000:b
(4) dialog control bar
Parent=(2)
Style=0x40000040 (DS_SETFONT|WS_CHILD)
Class=#32770
---
Both dialog control bars (2) and (4) are constructed using
CreateDialogIndirectParamA(), WM_INITDIALOG is sent twice (nested creation).
After creation of child dialog control bar the active window/input focus is
still NULL.
Because dialog control bar (4) contains no child control at this point, no
tabstop search is performed hence the approach from bug 19052 won't work here
(use first child if no suitable control with tabstop property is found).
I returned the dialog control HWND from DIALOG_GetNextTabItem() to have at
least a control to set focus on.
It helped "PhotoStitch 3.1" from comment #1 and "WYSIWYG Web Builder 5" from
comment #18 to successfully start.
I could not find a download for bug 18880 ("unable to run program GAUSS", dupe)
to test with.
Bug 13542 "Army Builder 3.1" is still a not fixed by both, needs further
investigation.
Regards
--
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.
http://bugs.winehq.org/show_bug.cgi?id=3023
Dan Kegel <dank(a)kegel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #25 from Dan Kegel <dank(a)kegel.com> 2010-07-09 15:55:28 ---
Eliot Blennerhassett sent in a patch,
http://www.winehq.org/pipermail/wine-patches/2010-July/090363.html
but Alexandre replied with "needs tests". Anyone who can
write a test that fails without that patch but passes with it,
please do!
--
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.
http://bugs.winehq.org/show_bug.cgi?id=23386
Summary: TF2 throws pixel shader 1.1 error when started with
-dxlevel 9
Product: Wine
Version: 1.2-rc4
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: cookiecaper(a)gmail.com
If I start TF2 with the option -dxlevel 9, the splash screen renders, and then
the game closes and an error message that says something like "Your graphics
hardware must support pixel shader 1.1 to play this game!" occurs.
It works completely fine with -dxlevel 81.
I've had this error for years, but I've been hearing more and more people talk
about playing with dxlevel 9 recently, claiming it runs great or even better
than dxlevel 81.
I have tried a new prefix, a new Steam directory, running inside and outside my
32-bit chroot, and none of these things have changed anything.
I am running ArchLinux with kernel 2.6.34, nvidia 256.35, GeForce GTX 285, but
as I said, I've had this trouble for years, even when using different nvidia
cards (previously had a 7900GTO). Through all the WINE updates, everything,
this has stayed constant. I'm currently running a version from git compiled
yesterday.
I'll attach a couple of snippets from a Steam run for your examination. Thanks
for looking, and thanks to everyone in IRC who helped, especially kevlarman.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=23579
Summary: Mouse pointer position problem with full-screen game
Product: Wine
Version: 1.2-rc6
Platform: x86
URL: http://www.flyordie.com/games/download/pacquest.html
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: markk(a)clara.co.uk
This bug applies to PacQuest 3D, which is downloadable from
http://www.flyordie.com/games/download/pacquest.html
The game uses full-screen mode, 800x600 resolution by default. Mouse pointer
movement is limited based on where the pointer was on the X desktop when the
program was run.
To demonstrate, download and install the game. Position the mouse pointer near
the bottom right of the X desktop (i.e. move your terminal window there) then
run the game. The game's mouse pointer is at the centre of the screen, but if
you move the mouse right and down, the pointer does not move much. That would
correspond to the X desktop pointer reaching the edge of the screen. Move the
mouse left and up until the pointer is at the top left of the screen, and
continue moving the mouse left and up. After doing that you can move the
pointer all over the screen.
--
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.
http://bugs.winehq.org/show_bug.cgi?id=6971
Vitaliy Margolen <vitaliy(a)kievinfo.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |markk(a)clara.co.uk
--- Comment #368 from Vitaliy Margolen <vitaliy(a)kievinfo.com> 2010-07-09 14:27:54 ---
*** Bug 23579 has been marked as a duplicate of this bug. ***
--
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.
http://bugs.winehq.org/show_bug.cgi?id=2467
--- Comment #131 from Matteo <bugs.kendatsuba(a)gmail.com> 2010-07-09 13:47:38 ---
Created an attachment (id=29467)
--> (http://bugs.winehq.org/attachment.cgi?id=29467)
hack for battle.net menus
The attached patch is a hack that fixes the problem (at least for me).
As stated in comment #129 the controls in battle.net menus are painted directly
to the screen by locking the primary ddraw surface. In wine's implementation
the primary surface ends up hidden under battle.net windows (see comment #111).
This hack blits from the primary surface to the foreground window every time
the primary surface gets updated. This is obviously very slow but does the
trick.
Please note that this is not a fix, it's only an ugly workaround made
specifically for this wonderful game. I've tested the patch on wine 1.0.1
(debian testing) and wine 1.2rc6, is there anyone willing to test it further?
--
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.