https://bugs.winehq.org/show_bug.cgi?id=41265
Bug ID: 41265
Summary: Far Cry 1: game crashes when using mouse wheel
Product: Wine
Version: 1.9.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: DanBrake0819(a)freenet.de
Distribution: ---
Created attachment 55565
--> https://bugs.winehq.org/attachment.cgi?id=55565
logfile
Far Cry 1.4 (and unofficial 1.5 patch) crashes when using the mouse wheel. It
happens in the latest Wine version (1.9.18). I also tested the latest stable
version (1.8.4) and an older stable version (1.6.2)... the same thing: crash
when using the mouse wheel.
--
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=42378
Bug ID: 42378
Summary: Diablo 3 2.4.3 - incorrect and slow rendering on x64
client
Product: Wine
Version: 2.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3dx11
Assignee: wine-bugs(a)winehq.org
Reporter: f.volejnik(a)gmail.com
Distribution: ---
Created attachment 57164
--> https://bugs.winehq.org/attachment.cgi?id=57164
Wine-staging 2.0 log of diablo3 running the d3d11 x64 client.
Since the release wine-staging 2.0, diablo 3 is able to start in the 64bit
mode, which utilizes d3d11 for rendering (Thanks!).
It is not without issues, yet, though.
Namely, the performance is really bad, on my machine (core i5, GTX 770) it
renders about 3 frames per second (whereas the 32bit version runs with >60
FPS). The rendering is not without issues, too. Characters look matte and dark,
very different look from the one one sees in the 32bit client.
I am attaching a log from my machine (Arch linux, 64bit, nvidia blob 375.26,
wine-staging 2.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=44783
Bug ID: 44783
Summary: Jedi Knight Dark Forces II/Mysteries of the Sith,
choppy audio causing very poor performance
Product: Wine
Version: 3.4
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: libsanorec(a)hotmail.com
Distribution: ---
After a somewhat recent upgrade in Wine (don't remember from what version
though, but it was a very old one), I've been having problems with audio in
both JK and MotS, where sounds playing in-game will lower fps significantly and
sound very choppy.
In Jedi Knight, causing sounds to play continuously (say, by firing a very fast
gun right into a wall) will cause the framerate to drop drastically, from the
usual already very low average of 30fps to around 10fps. Needless to say, the
sound will become increasingly choppy the lower the framerate is. The problem
is less present but still there when playing the game without 3d Acceleration,
and the average FPS is a lot higher as well.
I normally use JACK audio with a Pulse Audio module, but having JACK on or off
doesn't seem to make any difference in game performance. Changing the Wine
audio driver to winealsa or winepulse also didn't have any noticeable
difference. I however did not experience any such performance drops when
running the game with Wine audio disabled.
Running from console won't cause any error or "fixme" messages to print when
choppiness happens.
In MotS the problem is even worse: audio choppiness happens in almost every
frame, leading to short freezes and overall complete unplayability. I believe
this might have something to do with the sample rate for the sounds in these
games: JK uses 22050Hz and MotS uses 11025Hz.
After resetting the ".wine" directory, overall performance seems much better
(still around 30fps, but far more stable), but the audio is still very choppy.
--
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=43046
Bug ID: 43046
Summary: Civilization VI (Windows version) - Crashed on startup
Product: Wine
Version: 2.8
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: runemadsen16(a)hotmail.com
Distribution: ---
Created attachment 58208
--> https://bugs.winehq.org/attachment.cgi?id=58208
The output from wine (without fixme messages)
Trying to run Civilization VI (Windows version) with wine-2.8 (also tried with
wine-2.8 staging, same result) on Ubuntu, the game crashing, showing a black
screen and starting "Firaxis Crash Reporter", however not visible until the
Civilization process has been killed.
I am running it with (starting it as a DX11 game):
env WINEDEBUG=error+all,fixme-all env WINEPREFIX="[dir]" wine
C:\\windows\\command\\start.exe steam://rungameid/289070 >> games-log.txt 2>&1
The content of games-log.txt has been 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.
http://bugs.winehq.org/show_bug.cgi?id=24011
Summary: Trackmania Nations Forever graphics test does not work
Product: Wine
Version: 1.3.0
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: diafero(a)arcor.de
On first startup, Trackmania Nations Forever (free download at
http://www.trackmania.com/index.php?rub=downloads ) usually makes a benchmark
to set useful graphics detail settings. However, this does not work on wine:
Instead of a benchmark, the actual full game is started. When I quit, the
launcher tells me that the graphics data could not be found. I then get the
normal launcher, and can start the game again. This happens each time I start
the launcher.
Trackmania United Forever has the same issue.
--
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=43051
Bug ID: 43051
Summary: Rise of the Tomb Raider needs unimplemented function
msvcr110.dll.__crtCapturePreviousContext
Product: Wine
Version: 2.8
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: msvcrt
Assignee: wine-bugs(a)winehq.org
Reporter: fincer89(a)hotmail.com
Distribution: ---
Created attachment 58214
--> https://bugs.winehq.org/attachment.cgi?id=58214
ROTTR, unimplemented function msvcr110.dll.__crtCapturePreviousContext
As stated in the title, Rise of the Tomb Raider (64-bit Steam game) requires
unimplemented function msvcr110.dll.__crtCapturePreviousContext
Basically, Wine complains about:
wine: Call from 0x7b4567ea to unimplemented function
msvcr110.dll.__crtCapturePreviousContext, aborting
Lack of the function makes playing the game impossible (you can still access
the main menu but go no further).
Short log (relevant part) as an attachment.
Full log file here:
https://www.dropbox.com/s/s2ft59wg8jv81hn/rottr-unimplemented-msvcr110-func…
Full log includes the following steps:
1) Launching 64-bit Steam client
2) Launching the game
3) Accessing the main menu
4) Trying to start a new game
5) ROTTR doesn't show the intro movie which is presented before the actual
gameplay. Only black screen appears.
6) Killing ROTTR.exe & quitting Steam client
--
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=19241
Summary: winemenubuilder crashes when running any application
including notepad
Product: Wine
Version: 1.1.25
Platform: PC
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: tmhikaru(a)gmail.com
Created an attachment (id=22260)
--> (http://bugs.winehq.org/attachment.cgi?id=22260)
snapshot of the crash dialog
whenever I run any application, winemenubuilder crashes. Disabling it via
winecfg in the libraries section (specifically putting winemenubuilder.exe and
toggling it to disabled) makes wine complain that it can't find the component
but it no longer crashes.
For a basic reproducable test I'll be running 'wine notepad' as an example
here.
I don't know what this component does or what it's a part of, but this crash
did not happen under any previous version of wine.
I'll be attaching a picture of the crash dialog as well as the stderr
information.
--
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=43994
Bug ID: 43994
Summary: page fault when running droid4x-0-9-0.exe
Product: Wine
Version: 2.0.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kenorb(a)gmail.com
Distribution: ---
File URL: https://droid4x.en.softonic.com/download
$ wine droid4x-0-9-0.exe
wine: Unhandled page fault on read access to 0x00000001 at address 0x4b10d0
(thread 0009), starting debugger...
fixme:service:QueryServiceConfig2W Level 6 not implemented
Unhandled exception: page fault on read access to 0x00000001 in 32-bit code
(0x004b10d0).
Backtrace:
=>0 0x004b10d0 in droid4x-0-9-0 (+0xb10d0) (0x0032ccfc)
1 0x0040b15a in droid4x-0-9-0 (+0xb159) (0x0032cfb4)
--
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=43096
Bug ID: 43096
Summary: rtpMidi cannot install.
Product: Wine
Version: 1.6.1
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: massivenaked(a)yahoo.com
rtpMidi cannot install.
this is log.
[0036:0037][2017-05-27T22:59:07]i323: Registering package dependency provider:
{80D8C295-E035-4C68-B4F3-0DB34393A2C2}, version: 1.2.11.41, package:
teVirtualMIDI32MSI
[0036:0037][2017-05-27T22:59:07]i301: Applying execute package:
teVirtualMIDI32MSI, action: Install, path: C:\users\Public\Application
Data\Package
Cache\{80D8C295-E035-4C68-B4F3-0DB34393A2C2}v1.2.11.41\teVM32Burn.msi,
arguments: ' ALLUSERS="1" ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7"
USING_BURN="yes" SUPPRESSWHQL="1"'
[0036:0037][2017-05-27T22:59:57]e000: Error 0x80070643: Failed to install MSI
package.
[0036:0037][2017-05-27T22:59:57]e000: Error 0x80070643: Failed to execute MSI
package.
[0031:0032][2017-05-27T22:59:57]e000: Error 0x80070643: Failed to configure
per-machine MSI package.
[0031:0032][2017-05-27T22:59:57]i319: Applied execute package:
teVirtualMIDI32MSI, result: 0x80070643, restart: None
[0031:0032][2017-05-27T22:59:57]e000: Error 0x80070643: Failed to execute MSI
package.
[0036:0037][2017-05-27T22:59:57]e000: Error 0x8007000e: Failed to allocate data
for message.
[0036:0037][2017-05-27T22:59:57]e000: Error 0x8007000e: Failed to get message
over pipe
[0036:0037][2017-05-27T22:59:57]e000: Error 0x8007000e: Failed to pump messages
in child process.
[0031:0032][2017-05-27T22:59:57]i319: Applied rollback package:
teVirtualMIDI32MSI, result: 0x0, restart: None
[0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to write message
type to pipe.
[0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to write send
message to pipe.
[0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to send
BURN_ELEVATION_MESSAGE_TYPE_EXECUTE_PACKAGE_PROVIDER message to per-machine
process.
[0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to register the
package provider on per-machine package.
[0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to write message
type to pipe.
[0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to write send
message to pipe.
[0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to send message
to per-machine process.
[0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to end session
in per-machine process.
[0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to write message
type to pipe.
[0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to write send
message to pipe.
[0031:0032][2017-05-27T22:59:57]e000: Error 0x800700e9: Failed to send message
to per-machine process.
[0031:0032][2017-05-27T22:59:58]i399: Apply complete, result: 0x80070643,
restart: None, ba requested restart: No
--
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.