https://bugs.winehq.org/show_bug.cgi?id=43932
Bug ID: 43932
Summary: Fallout 4 (Steam): Low detailed LOD exterior Meshes
are rendered Inside interior cell
Product: Wine
Version: 2.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)spam.b2ag.de
Distribution: ---
There is a bug where in Fallout 4 low detailed LOD exterior meshes are rendered
inside interior cell. Screenshots of user "me." from inside the Museum in
Concord: https://imgur.com/a/v91oI
If one toggles clipping and views it from outside, than it seems there is some
artificial border which could well define which parts shouldn't get rendered. I
highlighted the border in the following screenshot. https://imgur.com/a/0xXhu
It looks like a real sharp shadow. Ground texture is the same on both sides of
the border, only lighting differs hugely. Maybe we are lacking some vertex
clipping of any form here.
One workaround is to disable LOD when inside of building by using "tll"
(ToggleLODLand) console command. It will also disable distant LOD meshes
outside of buildings. One needs to toggle it whenever entering or leaving
interior cells, which makes it a quite annoying workaround.
I was using Arch Linux Wine 2.18-staging with dsound-sleep-patch and AMD R9
280X GPU with Mesa 17.2 at time of writing.
--
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=44091
Bug ID: 44091
Summary: The Witcher: Enhanced Edition crashes during gameplay
Product: Wine
Version: 2.22
Hardware: x86
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
CC: piotr(a)codeweavers.com
Regression SHA1: 67926ec8c344db4250f1e74a5943d0b8a536e950
Distribution: ---
Created attachment 59807
--> https://bugs.winehq.org/attachment.cgi?id=59807
terminal output
I tested this bug with the GOG.com version of the game.
https://www.gog.com/game/the_witcher
The game loads to the menu properly, but it crashes frequently during gameplay.
Crashes occur:
- when starting a new game
- on area transitions
- when loading a previously saved game (some saved games load correctly though)
- when the Witcher enters Meditation mode (e.g. by a campfire).
The game works properly in Wine 2.22, this regression appears in the git
version.
Reverting the following commit fixes the problem for me:
commit 67926ec8c344db4250f1e74a5943d0b8a536e950
Author: Piotr Caban <piotr(a)codeweavers.com>
Date: Tue Nov 28 19:48:33 2017 +0100
msvcrt: Set errno when close() is called on already closed fd.
wine-2.22-47-g6f790606c0
Arch Linux x86_64
--
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=44022
Bug ID: 44022
Summary: The pixel format was invalid as specified (Minecraft
Java, Soldiers of Anarchy)
Product: Wine
Version: 1.9.20
Hardware: x86
OS: other
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: sergey.kz.main(a)gmail.com
OS: Android (ExaGear Windows)
Wine version: 1.9.20
Open app "Soldiers of Anarchy" - error "The pixel format was invalid as
specified"
Launch Java app "Minecraft" - error in log file
--
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=42128
Bug ID: 42128
Summary: Anime Studio Professional 8 hogs CPU after it's
closed.
Product: Wine
Version: 2.0-rc3
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: lanfrda1(a)gmail.com
CC: wine-bugs(a)winehq.org
Distribution: Ubuntu
Created attachment 56668
--> https://bugs.winehq.org/attachment.cgi?id=56668
Proof that it's using up the CPU.
When I close the program, the task isn't killed, and it hogs up a cpu thread to
100%, until I kill the process.
--
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=43406
Bug ID: 43406
Summary: NieR:Automata - Bloom to bright
Product: Wine
Version: 2.12
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: dark.shadow4(a)web.de
Distribution: ---
Created attachment 58749
--> https://bugs.winehq.org/attachment.cgi?id=58749
How it looks on linux
NieR:Automata is an 64Bit DX11 game on Steam. It has some rendering issues,
most areas of the game are to bright, especially the bloom.
Screenshots attached.
I made an apitrace, but unfortunately this comes at a whooping 1.4GB (543MB
compressed). If you still want it, I uploaded it here:
http://www.mediafire.com/file/me8dsk3asiuqoiw/automata.7z
I don't know if it's possible to trim apitraces at the start, but if so, please
tell me and I'll shrink it down. It's just that I can't skip those parts of the
game.
Screenshots from frame 2430(windows) and 2432(linux).
Using wine-2.12-staging on Arch Linux for my tests.
--
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=8051
--- Comment #157 from Alexandr Oleynikov <sashok.olen(a)gmail.com> ---
Works just fine too if I set vsm and psm to 3 through winetricks.
--
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=8051
Andy Clayton <q3aiml(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC|q3aiml(a)gmail.com |
--
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=2467
--- Comment #163 from Igor Polyakov <iop_jr(a)yahoo.com> ---
(In reply to imre Raudsepp from comment #162)
> I dont know if this is same problem but i am using wine 2.20
> Game menus select server Player lobby, create game ..get gamelist is
> rendering extremly slow. Like 20-30 sec. U can wait game list for min. Also
> u same u have to wait to see player names and pick race after joining game
> 20 sec. All goes for replays etc.
>
>
> But otherwise game is playable once u get game going
No, this is a completely separate bug. It's bug #43011
https://bugs.winehq.org/show_bug.cgi?id=43011
--
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=8051
--- Comment #156 from Alexandr Oleynikov <sashok.olen(a)gmail.com> ---
Yeah, that's what causing the problem. I set all mentions of useshaders in
Graphics Rules to true, and the bug disappeared.
The game runs flawlessly now. No visual problems or crashes at all.
--
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=2467
imre Raudsepp <justfunest(a)gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |justfunest(a)gmail.com
--- Comment #162 from imre Raudsepp <justfunest(a)gmail.com> ---
I dont know if this is same problem but i am using wine 2.20
Game menus select server Player lobby, create game ..get gamelist is rendering
extremly slow. Like 20-30 sec. U can wait game list for min. Also u same u have
to wait to see player names and pick race after joining game 20 sec. All goes
for replays etc.
But otherwise game is playable once u get game going
--
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.