https://bugs.winehq.org/show_bug.cgi?id=39196
Bug ID: 39196
Summary: Morrowind and Morrowind Graphics Extender (MGE):
shader problem
Product: Wine
Version: 1.7.50
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: tuupic(a)gmail.com
Distribution: ---
When I use third person view in game(and sometimes in first person too) if "HDR
shader" or "distand land" is enable picture will corrupted (see attached
screenshots)
Same problem with another graphic extender for morrowind: MGE XE
--
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.
https://bugs.winehq.org/show_bug.cgi?id=43970
Bug ID: 43970
Summary: Mouse is constrained to the borders of the screen when
looking around ingame.
Product: Wine-staging
Version: 2.19
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: libcg(a)protonmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
I've been using wine-staging 2.19 with DOOM 2016 and GTA 5. In both of those
games, looking around using the mouse will sometimes get stuck until I move the
mouse faster out. When going to the game menu, I can see that the cursor is
positioned at one end of the screen. When I place the cursor in the middle of
the screen and go back ingame, the mouse will move freely until I hit one
border of the screen with the cursor again.
It happens with both of these games. I tried DOOM with wine-staging 2.3 and hit
the same issue. Switching between GNOME and Xfce doesn't help.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=42765
Bug ID: 42765
Summary: Doom (2016) Sound suddenly shut down
Product: Wine-staging
Version: 2.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mathieu.nivoliez(a)laposte.net
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
Sounds does not appear in game or in the menu but it does at the start of
loading screens before being quickly shut down.
Could be link to this issue:
https://steamcommunity.com/app/353380/discussions/0/357287304417743078/
Pulseaudio already set on 48000 Mhz
--
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.
https://bugs.winehq.org/show_bug.cgi?id=38748
Bug ID: 38748
Summary: (dogfood) Chocolate Doom full screen does not always
work properly
Product: Wine
Version: 1.7.43
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mikeonthecomputer(a)gmail.com
Distribution: ---
Created attachment 51661
--> https://bugs.winehq.org/attachment.cgi?id=51661
Screenshot of broken full screen
The full screen setting of Chocolate Doom (which is default) will sometimes
display the screen offset, showing a part of my GNOME desktop and making the
game rather unusable for play. It seems to work correctly the most frequently
if the game is launched from the setup program, but that still doesn't always
work.
I've tested this with the 2.2.0 release, both with the official binaries
(http://www.chocolate-doom.org/downloads/2.2.0/) and my own 64-bit build with
x86_64-w64-mingw32; no difference between the two.
To Wine maintainers, for testing this bug, you can use the FreeDM IWAD so that
Chocolate Doom has a game to run: https://freedoom.github.io/download.html
--
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=13460
Summary: ZDoom: distorted graphics rendering
Product: Wine
Version: 1.0-rc2
Platform: PC-x86-64
URL: http://www.zdoom.org
OS/Version: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P5
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: aeichhorst(a)gmail.com
Created an attachment (id=13376)
--> (http://bugs.winehq.org/attachment.cgi?id=13376)
Hall of Mirrors effect on textures
When running ZDoom, the graphics rendering produces a "hall of mirrors" effect
on textures. This has no effect on gameplay, but is a big eyesore. Another
graphical problem that occurs is a "pixel coloration-distortion" that imposes
colors from one texture onto another. An example of this is when firing the
BFG9000 in Doom the walls will retain pixels of the BFG's green energy ball
color. This can be seen when pulling up the menu (hitting the Esc key) during
gameplay. The menu's yellowish background-shade produces the effect quite well.
I managed to get a screenshot of the "hall of mirrors" effect and is attached
to this report.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=38415
Bug ID: 38415
Summary: Switching weapons does not work after dying
Product: Wine
Version: 1.7.39
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: christopher(a)thielen.co
Distribution: ---
Here's a strange one:
Deus Ex works beautifully in Wine but I noticed after I die, beginning a new
game and pressing one of the keyboard buttons to switch weapons no longer works
as it did.
Wine/Deus Ex registers the key press because the Doom-style weapon switcher at
the bottom of the screen registers the new weapon but the game does not
actually switch weapons.
Using the same 1.112fm Deus Ex "Game of the Year" edition installer on Windows
XP and Windows 8, this bug does not occur, implying there's something fishy
with Wine instead.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=42061
Bug ID: 42061
Summary: DOOM(2016) has issues with multiple monitors - crashes
too
Product: Wine-staging
Version: 2.0-rc2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: spleefer90(a)gmail.com
CC: erich.e.hoover(a)wine-staging.com, michael(a)fds-team.de,
sebastian(a)fds-team.de
Distribution: ---
pacman -Q wine-staging-git
wine-staging-git atest.release.r0.ge05b5bf8+wine.2.0.rc2.r0.g56040acaa3-1
I have 2 monitors, both 1920x1080, one 144Hz(left,primary) and second one
60Hz(right,secondary).
Upon launching the game, my left monitor turns off and the game is launched on
the wrong monitor(right).
After messing around with the monitors(turning them back on and going into game
settings), trying to make DOOM run on the other monitor, the game crashes.
Crash error: http://pastebin.com/efU7w1An
I guess the crashing wouldn't be an issue if the game launched on the correct
monitor without turning anything off.
I'll attach full output soon.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=45766
Bug ID: 45766
Summary: Doom 3: BFG hangs during launch
Product: Wine
Version: 3.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sa(a)whiz.se
Distribution: ---
Created attachment 62220
--> https://bugs.winehq.org/attachment.cgi?id=62220
backtrace from gdb
I'm getting a reproducible hang each time I start Doom 3: BFG, GOG version.
(Yes, I know there's a native port!)
The hang happens after the intro videos are played, during the id/Bethesda
logos.
This title seems to require a compatibility context which Mesa just recently
started to support. Still, the game uses some none-spec OpenGL and requires
force_glsl_extensions_warn=true and
allow_glsl_builtin_variable_redeclaration=true to start.
An uneducated guess is something to do with audio? Those are the files the
process keeps open, but might just be a coincidence. (Audio is played during
the intro videos).
Native xact doesn't make a difference, disabling audio in Wine casues the game
to refuse to run.
Doesn't seem to be a regression, it is there as far back as 1.9.10 (the last
version with Platinum rating in AppDB)
Full backtrace from gdb is attached.
--
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.
https://bugs.winehq.org/show_bug.cgi?id=43984
Bug ID: 43984
Summary: Doom (2016) sometimes hangs upon exit
Product: Wine
Version: 2.19
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: laci(a)monda.hu
Distribution: ---
Generally speaking, Doom (2016) runs flawlessly, but sometimes when I quit it
hangs.
I can see the following in the console:
fixme:bcrypt:BCryptGenRandom ignoring selected algorithm
fixme:bcrypt:BCryptCreateHash ignoring object buffer
fixme:bcrypt:BCryptCreateHash ignoring object buffer
fixme:bcrypt:BCryptGenRandom ignoring selected algorithm
fixme:bcrypt:BCryptCreateHash ignoring object buffer
fixme:bcrypt:BCryptCreateHash ignoring object buffer
fixme:bcrypt:BCryptGenerateSymmetricKey ignoring object buffer
fixme:bcrypt:BCryptGenRandom ignoring selected algorithm
err:hid_report:process_hid_report Device reports coming in too fast, last
report not read yet!
err:hid_report:process_hid_report Device reports coming in too fast, last
report not read yet!
AL lib: (WW) ReleaseThreadCtx: 0x7f46405e8e10 current for thread being
destroyed
--
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.
https://bugs.winehq.org/show_bug.cgi?id=45375
Bug ID: 45375
Summary: Halo Online: Weird black display problems.
Product: Wine
Version: 3.10
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: conmanx360(a)gmail.com
Distribution: ---
This issue happens on certain maps in Halo Online depending on what your
current Z position is. Not all maps suffer from it, only certain ones do. If
you're above the Z position that it begins happening at, everything below
renders normally, but once you go below it, a portion of the frame becomes
black. It seems to be in a pattern. Not all objects are blacked out, either. So
there must be some sort of "priority".
Image examples here: https://imgur.com/a/176i4xr
--
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.