http://bugs.winehq.org/show_bug.cgi?id=58939
Bug ID: 58939
Summary: farcry 3 will not start
Product: Wine
Version: 10.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)list.winehq.org
Reporter: lars_martin4(a)hotmail.com
Distribution: ---
larsmartinhambro@ti0108q160-3438:~/Dokumenter/Far Cry 3/bin$ wine farcry3.exe
002c:fixme:winediag:loader_init wine-staging 10.18 is a testing version
containing experimental patches.
002c:fixme:winediag:loader_init Please mention your exact version when filing
bug reports on winehq.org.
003c:fixme:service:scmdatabase_autostart_services Auto-start service
L"HDDHealth" failed to start: 5
0024:fixme:winediag:loader_init wine-staging 10.18 is a testing version
containing experimental patches.
0024:fixme:winediag:loader_init Please mention your exact version when filing
bug reports on winehq.org.
0128:err:environ:init_peb starting
L"Z:\\home\\larsmartinhambro\\Dokumenter\\Far Cry 3\\bin\\farcry3.exe" in
experimental wow64 mode
0128:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented!
0128:fixme:msvcrt:__clean_type_info_names_internal (7A901E58) stub
larsmartinhambro@ti0108q160-3438:~/Dokumenter/Far Cry 3/bin$
012c:fixme:winediag:loader_init wine-staging 10.18 is a testing version
containing experimental patches.
012c:fixme:winediag:loader_init Please mention your exact version when filing
bug reports on winehq.org.
--
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=56759
Bug ID: 56759
Summary: Army Men: Colors are displayed incorrectly
Product: Wine
Version: 9.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bugzilla(a)cock.email
Distribution: ---
The first Army Men game has incorrect colors. This causes the cinematics to be
black, the in game colors to be crushed, for instance blue rivers become black
rivers, and the greens of the forest all become one color of green. It makes
things somewhat difficult to see. I have tested this on different computers
with different hardware to make sure. Someone mentioned it has something to do
with the bitmaps for the game not being converted properly.
--
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=58872
Bug ID: 58872
Summary: Activated windows (via alt-tab) are not raised
(sometimes).
Product: Wine
Version: 10.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: chiitoo(a)gentoo.org
Regression SHA1: 8094acfbfddf0681d6c9fa2d61788da7d7b781cf
Distribution: Gentoo
This might be invalid/a KWin-X11 issue, but so far it seems that after
8094acfbfdd [1], applications running via Wine sometimes "confuse" the window
manager with regards to what is the currently active window.
So far I can not re-produce the bad state at will, but it feels like it happens
quite often, starting with the mentioned commit, which looks like it might(?)
indeed have something to do with this.
What sometimes happens is, I have 1 game window in "full screen windowed" mode
in one monitor, and usually a second instance in a smaller window in another
monitor, though they may be in the same monitor sometimes too.
I then alt-tab to, for example, the Konsole terminal emulator, but the game
window stays visible, and any input goes into Konsole; even though it is not
visible, it is the active window.
I can then alt-tab more, and the bad state remains until I do... something...
possibly switch the active window using the mouse, or alt-tab through more
different windows. I haven't yet quite figured out what restores the state.
I don't think I updated KWin or anything else before this started happening,
and I spent quite a while with bisecting this, but as it is someawhats
random-like still, I can't say anything for sure yet.
Does the mentioned commit look like it could be related to this?
Thank you!
1.
https://gitlab.winehq.org/wine/wine/-/commit/8094acfbfddf0681d6c9fa2d61788d…
--
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=58906
Bug ID: 58906
Summary: Starcraft: Brood war is stuttering
Product: Wine
Version: 10.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: winehq(a)szaka.eu
Distribution: ---
Hi, since the commit 7abf4432a7dfdc044f0458f2457829038dc497f0 Starcraft runs at
5 FPS. The workarounds are either of:
- reverting Reverting it solves the problem.
- setting "HKCU\Software\Wine\X11 Driver" string "UseEGL" to "N".
--
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=58937
Bug ID: 58937
Summary: Serious Sam Classic: The Second Encounter: CRC
mismatch between Linux and Windows users.
Product: Wine
Version: 10.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)list.winehq.org
Reporter: bugzilla(a)cock.email
Distribution: ---
Some maps, possibly due to an overflow, not sure, will present the message "CRC
error in DIFF!" when attempting to join a Windows hosted server with WINE, or
when joining a WINE hosted server with Windows.
Another issue is that when WINE users are hosting, Windows users will
eventually get badsync errors and disconnect after 10 bad synchronization
attempts, but I have not seen other WINE users receiving badsync errors. When
Windows users are hosting, WINE players do not receive badsync errors.
One map which causes the "CRC error in DIFF!" for Windows players when
attempting to join a WINE hosted server is the "Beyond The Waterfalls" level of
the "Teotihuacan Map Pack".
--
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=58829
Bug ID: 58829
Summary: Harmony Assistant 9.9.9i
Product: Wine
Version: 10.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: dheorchestra(a)gmail.com
Distribution: ---
Created attachment 79500
--> http://bugs.winehq.org/attachment.cgi?id=79500
Harmony Assistant Windows Version 9.9.9i 64bits
I am not able to download and install the latest Windows version of Harmony
Assistant 9.9.9i.64 bits
This has not been a problem in the past.
--
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=58717
Bug ID: 58717
Summary: Camerabag Pro 2025.2 crashes with unhandled exception
(unimplemented function
mf.dll.MFTranscodeGetAudioOutputAvailableTypes) when
saving a video
Product: Wine
Version: 10.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: superian(a)gmail.com
Distribution: ---
Created attachment 79318
--> http://bugs.winehq.org/attachment.cgi?id=79318
backtrace.txt generated by WINE
New installation of WINE development version 10.15 on Linux Mint 22.2 (Ubuntu
Noble-based).
No winetricks used.
Installation OK. Can open an MP4 video (see #58716 for issue opening a JPEG).
Works well - can move within the video, make adjustments (alter contrast, white
balance, add vignette and light leak effects etc) with animated mouseover
previews of the effects - but crashes with the attached back trace on saving
the video after selecting size / format. Happens with asking for both .mov and
.mp4 output.
CameraBag Pro downloaded today from https://nevercenter.com/camerabag/download/
(runs as a 7 day free trial if you haven't bought a registration code)
sha1sum:
01d4daf1dd05ab426858e19191dbabfa855c2558
Install_CameraBag_Pro_2025_2_0_win.exe
--
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=58936
Bug ID: 58936
Summary: Installation of SharpEye fails
Product: Wine
Version: 10.10
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)list.winehq.org
Reporter: kapfell(a)gmx.de
Distribution: ---
Created attachment 79632
--> http://bugs.winehq.org/attachment.cgi?id=79632
error messages during SharpEye install
Installation of SharpEye (http://www.visiv.co.uk/,
https://appdb.winehq.org/objectManager.php?sClass=application&iId=1620)
fails with an error message.
(Installation works fine in Wine 9.0.)
--
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=56166
Bug ID: 56166
Summary: GDI performance regression after switching fonts to
syscall interface
Product: Wine
Version: 8.9
Hardware: x86-64
URL: https://developer.download.nvidia.com/SDK/9.5/Samples/
3dgraphics_samples.html#HLSL_HDR_FP16x2
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: win32u
Assignee: wine-bugs(a)winehq.org
Reporter: mirh(a)protonmail.ch
Regression SHA1: 9b5c916e4e8b90da795be93d8203743d76d22edb
Distribution: ---
Long story short, up to wine 8.8 you get about 2300fps with my 2080 and 9600K
in an old nvidia showcase. After that, it's more like 2150.
Of course it's just a little 7% difference, but it's completely reproducible,
so..
p.s. DXVK and the patch for bug 32323 are also needed to "unlock full speed"
(the sources clearly show a D3DXCreateFont call for Arial, but is it expected
to take a 40% framerate hit without the fonts otherwise?)
--
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.