[Bug 2082] running Diablo v1.09 results in black screen..

Wine Bugs wine-bugs at winehq.org
Sat Oct 1 06:35:44 CDT 2005


http://bugs.winehq.org/show_bug.cgi?id=2082





------- Additional Comments From saulius.krasuckas at elst.vtu.lt  2005-01-10 06:35 -------
The bug remains.  Should I try to describe it using another words?  My setup is:

$ rpm -q XFree86 blackbox kernel glibc
| XFree86-4.3.0-45.fdr.3.rh80
| blackbox-0.65.0-fr2
| kernel-2.6.11-1.1369_FC4
| glibc-2.3.5-10

I run game in a fullscreen mode.

The game is launched.  It replays its intro video (using SMACK32 lib), then it
should display large Diablo Logo.  Here occurss bug point number

1 - I see black screen instead of Diablo Logo.

Actually logo can be seen if I switch to next application window and back.  Ok,
going futher.  After I press any key or after some timeout Main Menu of the game
should be display.  Here we have bug point number

2 - I see black screen instead of Main Menu.

Of course, previous tactics mostly works here too - I press Alt-Tab twice and
the see Main Menu was redrawn.  Still, that happens not every time.  On about a
50% of all cases nothing is redrawn and I see just a bitmap-copy of my terminal
window. :-(

Next. Diablo Mini-logo should be rendered above the menu buttons.  It isn't the
case, as this area stays black in a case of succesfull redrawing.  Bug point number

3 - Diablo Mini-logo isn't drawn at most of times.

You can go to another menu screens, and back, but Mino-logo most often stays
black.  Someone may be interested in the difference between this, updated
version (v1.09) of the game and original its version (v1.00), which draws some
garbage in Mini-logo area.  And garbage looks different every time you switch
game screens forth and back. I probably will file another bug report on this
(v1.00) with screenshots attached.

Now on menu.  It should be navigatable using mouse and keyboard, but that's a
hard task.  Keyboard input works, if screen before making input was redrawn OK,
but menu selection indicators stays static, when they should present dynamic
animation (of spinning pentagram) by itself. Though, if you move mouse over
selected menu item, static picture of animation frame sometimes jumps to the
next one.  Note that in v1.00 animation-frame switching is triggered every time
you move mouse over it.  Hence, bug point number

4 - menu selection animation doesn't work.

Mouse stuff...  It is impossible to select menu items by pressing mouse buttons.
 Just nothing happens what can be observed by a plain eye.  But there are
exceptions for some edit-boxes in one screen, where both buttos works OK.  Bug
point number

5 - mouse buttons don't work on most menu and listbox items, which are
self-made, I believe.

In some screens mouse pointer is drawn, but in most of areas it gets hidden.  In
the Main Menu screen it is hidden always.  Though its image can be 'captured' by
blindly moving mouse to the invisible area and switching forth to another X
window and back.  Bug point number

6 - in some screens or some screen areas mouse dissappears.

This can be caused by some strange technology of drawing standard windows
control on the DDraw surfaces (or so).  This can be best seen in the Multiplayer
screen battle.net subscreen, when I get some editboxes to input your name and
password.  I can click right mouse button, and get its standard context menu.  I
pres Esc and see editbox in a previous state, but a background around it stays
painted with a part of context menu, which has already died.  Maybe I name this
bug point number

7 - windows controls and DDraw surfaces do not mix well.

BTW, some nice textures (bitmaps?) are painted on the background of this
subscreen, but only after some intense and long switching.  This is Mandelbug,
as I have no idea how to make those nice bitmaps to be drawn.  It happens very
rarely.  And this is true for the Mini-logo on the main screen.  Bug point number

8 - very rarely all menu-screens stuff is drawn ok, but its quite rare and
stochastic case.

Maybe switching to the next workspace helps it (Ctrl-Alt-Tab)?  That's hard to
prove.  Anyhow, after such switching game loses its kbd input and the only thing
I can do is to killall -9 wine-preloader. :-/

9 - switching BlackBox workspaces disables keyboard input and the screen in most
 cases isn't redrawn at all.  


Now you tell me if I should file additional 9 or 8 bugreports. :-))

-- 
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.



More information about the wine-bugs mailing list