http://bugs.winehq.org/show_bug.cgi?id=19153
Summary: DX3 game does not recognize graphics capabilities
Product: Wine
Version: 1.1.24
Platform: PC
URL: http://appdb.winehq.org/objectManager.php?sClass=versi
on&iId=9396
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: bobbyg(a)gmx.net
Resident Evil 1 does not start giving the error "Failed to initialize the
Graphics Hardware Device.(3)". It's a DirectX 3 game using immediate mode.
After some debugging I found that it relies on 3 (three) entries returned by
EnumDevices whereas wine returns only the Direct3D HAL entry in this case
(d3dversion == 1). Removing the if-clause in ddraw/direct3d.c and duplicating
the HAL entry solves the problem and the game actually runs almost perfectly
(Garbage -> Platinum).
I checked a Windows installation which returns "HAL", "RGB Emulation" and "Ramp
Emulation" but the comments in the file suggest that not all games are happy
about that. So how to fix this properly?
--
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=20456
Summary: FEAR's installer will not let me enter the serial
number
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: wylda(a)volny.cz
Hi, F.E.A.R. installer requires entering serial number. It has several fields
for entering 4 characters (clasic 1234-5678-9abc-def0-1234).
I can enter:
* 4 "narrow" chars like 1111, iiii, etc.
or
* only 3 "fat" chars like AAA, CCC, etc.
or
* only 2 "extra fat" like WW
There are other pepole affected in AppDB:
http://appdb.winehq.org/objectManager.php?sClass=version&iId=5159&iTestingI…http://appdb.winehq.org/objectManager.php?sClass=version&iId=5159&iTestingI…
Based on other confirmations in AppDB consider UNCONFIRMED->NEW. Tested wine
versions: 0.9.50, 0.9.60, 1.0.1, 1.1.7, 1.1.10, 1.1.13, 1.1.22, 1.1.29, 1.1.31,
1.1.32 ...so it probably never worked correctly.
This is show stopper. I own two original and none is usable under wine because
of too wide chars in serial :-/
--
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=18382
Summary: SubEdit fails to start
Product: Wine
Version: 1.1.20
Platform: PC
URL: http://matinf.pcz.pl/~subedit/download/subedit_b4072_ins
tall.exe
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: lukasz.wojnilowicz(a)gmail.com
Created an attachment (id=20962)
--> (http://bugs.winehq.org/attachment.cgi?id=20962)
Fatal error
I'm using Wine 1.1.20 (compiled from source using gcc version 4.3.2 20081105
(Red Hat 4.3.2-7) ) on Fedora 10 i386.
The problem is that SubEdit fails to start and shows fatal error.
--
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=25689
Summary: Combat Mission: Barbarossa to Berlin - failing to
initialize graphics
Product: Wine
Version: 1.3.10
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mat69(a)gmx.net
Created an attachment (id=32722)
--> (http://bugs.winehq.org/attachment.cgi?id=32722)
terminal output when starting cmbb
I installed CMBB and updated to 1.03, using a crack made it possible to avoid
BUG:219.
Trying to start I get a message complaining that Direct3D graphics could not be
recognised.
Attached is the terminal output.
--
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=24308
Summary: Fullscreen fails for MechWarrior 4 games (Only one D3D
device per DirectDraw object)
Product: Wine
Version: 1.3.2
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-ddraw
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: georg298(a)gmx.de
For all MechWarrior 4 games, fullscreen fails with message
fixme:ddraw:d3d7_CreateDevice Only one Direct3D device per DirectDraw object
supported.
Obviously, the game falls back to window'ed mode, as
static HRESULT WINAPI d3d7_CreateDevice(IDirect3D7 *iface, REFCLSID riid,
IDirectDrawSurface7 *surface, IDirect3DDevice7 **device)
returns
DDERR_INVALIDPARAMS
changing this behaviour (returning D3D_OK instead):
if (ddraw->d3ddevice)
{
FIXME("Only one Direct3D device per DirectDraw object supported.\n");
LeaveCriticalSection(&ddraw_cs);
return D3D_OK;
// return DDERR_INVALIDPARAMS;
}
makes fullscreen work for these games.
Probably it's not "legal" to return D3D_OK in this case, but maybe there is a
real solution for this problem?
--
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=29071
Bug #: 29071
Summary: Falcon BMS 4: Low FPS on Wine 1.3.32
Product: Wine
Version: 1.3.32
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: directx-d3d
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: victhor.foster(a)gmail.com
Classification: Unclassified
Created attachment 37463
--> http://bugs.winehq.org/attachment.cgi?id=37463
In-game graphics settings window
Falcon 4 BMS runs with a very low framerate(5-7 FPS as reported by the in-game
FPS indicator) in Wine 1.3.32. However, in Wine 1.2.3, the game runs at 20-23
FPS.
The scene used for the tests was the same(default "Korea" theater, game was
started using "instant action" > "commit" button). Attached is a screenshot of
the settings window, the settings used were exactly the same for both Wine
versions.
I would just use 1.2.3 for the time being if it wasn't for a annoying bug,
where switching to another window while the game is being played(Alt+Tab)
causes the gameplay window to turn black(on menu windows, this doesn't happen).
This does not happen on 1.3.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.
http://bugs.winehq.org/show_bug.cgi?id=21267
Summary: Fallout 3 GOTY: Crashes Randomly
Product: Wine
Version: 1.1.35
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: hibbsncc1701(a)yahoo.com
Created an attachment (id=25570)
--> (http://bugs.winehq.org/attachment.cgi?id=25570)
The Console log after a crash during the black screen after the opening video.
Fallout 3 Game of the Year Edition will crash in semi-random places when
starting a New game. Some of these places include the black screen right after
the opening video, after inputting the player's name, after customizing the
character, During the Birthday scene when you are shooting the radroach with
your BB Gun, etc. It seams to be a script executing error as the game is
usually supposed to be doing something (ie. controlling the radroach so it
doesn't attack the player, moving an NPC somewhere, setting game values(player
name, how the player looks) when it stops. The Game has two different crashes
for these events, but only one shows at anytime. The first one is obvious and
the rarest a Message box pops up saying the Program encountered an error an
needs to close. A stacktrace is able to be retrieved in this case. The second
one is a freeze, ie the game is no longer controllable by the user, and the
render has stopped. Music and sound effects (such as talking) still work until
the program is killed, but the player cannot make any sound effects such as
walking or shooting a gun. The game's menus are also disabled.
I've followed the hq's guides on getting the program to run, with the small
exception of manually installing the Games for Windows Live client and .Net
Framework. As the game's installer hangs when the installer for those
components have crashed, and thus must be killed to allow the installer to
continue.
It must be noted that a save game made after Vault 101 will work normally. It's
unknown if it's the result of the save being from another computer with the
game running normally or just after Vault 101 because i can't get the game past
Vault 101 when starting a new game.
System Specs:
Mandriva Linux 2010.0 X86_64
Intel Core 2 Quadcore
Latest Nvidia Drivers as of 1/5/2010
Wine 1.1.35 Mandriva Linux Repo
(If anyone needs more just ask.)
--
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=26706
Summary: SolidWorks: Some tools cannot be activated
Product: Wine
Version: 1.3.17
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: maarten.bezemer(a)gmail.com
When clicking on the toolbar button or the menu item to activate a tool,
nothing happens.
Known tools which do not work:
- Plane (menu Insert -> Reference Geometry -> Plane)
- Convert Entities (menu Tools -> Sketch Tools -> Convert Entities)
But there are probably more occurences...?
Steps to reproduce:
- Start designing a new part
- Click the new plane button
Actual results:
Nothing happens
Expected results:
After clicking the button a new plane pane should show to fill in the
properties of the new plane and to actually create it.
--
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=26873
Summary: Dekaron: crashes when starting the game from the
launcher
Product: Wine
Version: 1.3.17
Platform: x86-64
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: simondani91(a)gmail.com
Created an attachment (id=34257)
--> (http://bugs.winehq.org/attachment.cgi?id=34257)
This is the backtrace from the console
Dekaron launcher works fine, but the game itself crashes just when I try to
start.
--
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=26839
Summary: 888 Poker Crashes after login and password entered
Product: Wine
Version: 1.3.18
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: nmorozov(a)atlas-print.ru
Created an attachment (id=34200)
--> (http://bugs.winehq.org/attachment.cgi?id=34200)
Crash screenshot
888 Poker Crashes after login and password entered, If just wait 888 poker
reports "server unreacheble" but show player on tables and some more info. Ater
I login i see my Name my status and that got crash (see screenshor) and 888
poker client hangs
--
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.