http://bugs.winehq.org/show_bug.cgi?id=16636
Summary: Black & White 2 Graphics Glitches and Crash
Product: Wine
Version: CVS/GIT
Platform: Other
OS/Version: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: ryanshow(a)gmail.com
Created an attachment (id=18212)
--> (http://bugs.winehq.org/attachment.cgi?id=18212)
a zipped logfile, made from the command "wine white.exe > bw2err.log 2>&1"
I have the latest wine git as of December 26th 2008. I installed Black and
White 2, with both the version 1.1 and 1.2 patches. I also installed the No-CD
patch for SecuROM reasons.
The game opens just fine. The menus work great. The intro video works great
as well. After the video the game loads and that's where the graphical
glitches begin.
It looks as if there are two seperate rendering schemes going on at the same
time. One of the schemes only renders the game's water, and the other renders
the game's land. I have the game in a 800x600 virtual wine desktop, and the
water rendering portion seems to occupy a 640x480 square in the bottom left
corner of the game. The rest is occupied by the land rendering. Interactive
objects such as the game's "creature" the player hand, and scrolls seem to be
unaffected by this issue. I've also attached a screenshot so that what I'm
saying might be better understood.
The second issue is that the game crashes not long after selecting a creature.
If you skip the tutorial island and go straight to the mainland (by pressing
ESC). The game will progress into an in-game video where you're flying over a
reddish sea to an island. Half-way to that island the game crashes.
The attached log files seem to indicate that I'm running out of memory, but my
computer's memory shouldn't be an issue. I'm running Ubuntu Intrepid 64 bit
with 4 gigs of ram and an nVidia 8600 GTS with 512MB of vram.
Also, for some reason when I attempted to direct the output of stdout and
stderr to the log file, the debug output wasn't fully captured. I've included
the history of my bash prompt so that it shows the debug output of the previous
run as well, which had identical results to the one I captured in the log file.
--
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=24435
Summary: time not set by SendInput() if 0
Product: Wine
Version: 1.3.1
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: user32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: jUrner(a)arcor.de
Created an attachment (id=30814)
--> (http://bugs.winehq.org/attachment.cgi?id=30814)
python test case
in my application i used to synthesize mouse events by using
user32.mouse_event(). when switching to SendInput() i got got unexpected
behviour from the target of the mouse events. digging into wines sources it
looks like SendInput does not set the "time" member of the struct if 0,
mouse_event() does. setting this member in my calls to SendInput fixed the
problem.
i guess this is a slight inconsistency that goes unnoticed most of the time. in
my case, coding an automation tool for poker sites, the target window may have
all kinds of tests in place to detect botters.
see: http://msdn.microsoft.com/en-us/library/ms646273%28v=VS.85%29.aspx
"The time stamp for the event, in milliseconds. If this parameter is zero, the
system will provide its own time stamp. "
attatched python test case
install python 2.6 via winetricks and run >>wine c:/Python26/python.exe
testcase-SendInput-time-not-set.py
output should be:
send MOUSEEVENTF_LEFTDOWN via mouse_event()
send MOUSEEVENTF_LEFTUP via SendInput()
received WM_LBUTTONDOWN - msg.time: <any greater zero>
received WM_LBUTTONUP - msg.time: 0
--
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=20865
Summary: Steam login window jumps around the screen when moved
Product: Wine
Version: 1.1.33
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austin.lund(a)gmail.com
When running steam in Wine, at login screen if you move the window around, it
appears to jump across the screen in a jerky manner, especially if the cursor
is moved quickly.
A trace using WINEDEBUG='+tid,+event,+x11drv,+win,+relay' (attached) shows that
sometimes the X11 driver is getting ConfigureNotify messages after the window
has moved but they seem to contain the wrong values for the position on the
window. Sometimes the window is moved by the ConfigureNotify handler back to
where it was originally, just for Steam to move it again.
It is possible to see this if you parse the log with: grep -E
'win:SetWindowPos|x11drv:sync_window_position|event:X11DRV_ConfigureNotify'
--
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=8025
--- Comment #61 from dvarnai(a)gmail.com 2010-09-30 11:07:37 CDT ---
(In reply to comment #60)
> (In reply to comment #58)
> > (In reply to comment #56)
> > > I finally found solution for this issue, from obvious reasons you need to set
> > ...
> > > set Windows XP but it probably will work also I will test that later.
> >
> > Could you add which gpu and driver you use (e.g. here: x1400(R500), radeon-git,
> > kms, gallium)
>
> i tested it too, hd4670, catalyst 10.10beta and it really works
or not, fsck im bad at testing lol
--
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=22321
Summary: Spotify cant cant be maximized
Product: Wine
Version: 1.1.42
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: Eldmannen+wine(a)gmail.com
The maximize button in the Spotify title bar does not work.
When I click it, Spotify stays the same size but gets moved to the top-left
corner.
--
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=20993
Summary: Spotify window does not maximise
Product: Wine
Version: 1.1.34
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: leighmanthegreat(a)hotmail.com
Created an attachment (id=25169)
--> (http://bugs.winehq.org/attachment.cgi?id=25169)
terminal output when clicking the maximise button
Clicking the maximise button just blinks the window, it does not maximise.
--
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=8025
--- Comment #60 from dvarnai(a)gmail.com 2010-09-30 08:17:04 CDT ---
(In reply to comment #58)
> (In reply to comment #56)
> > I finally found solution for this issue, from obvious reasons you need to set
> ...
> > set Windows XP but it probably will work also I will test that later.
>
> Could you add which gpu and driver you use (e.g. here: x1400(R500), radeon-git,
> kms, gallium)
i tested it too, hd4670, catalyst 10.10beta and it really works
--
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=3467
--- Comment #31 from leighman <leighmanthegreat(a)hotmail.com> 2010-09-30 06:24:33 CDT ---
Sorry, the report seems to refer to SK2 which was the second link I posted,
don't think the first is actually relevant.
--
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=8025
--- Comment #59 from Riot777 <riot777(a)gmail.com> 2010-09-30 04:36:36 CDT ---
(In reply to comment #58)
> Could you add which gpu and driver you use (e.g. here: x1400(R500), radeon-git,
> kms, gallium)
I'm using FGLRX 8.78 on Ubuntu x86_64 with Radeon 4200 card.
--
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.