https://bugs.winehq.org/show_bug.cgi?id=43637
Bug ID: 43637
Summary: Fallout New Vegas: Crash on launch using 64-bit prefix
Product: Wine
Version: 2.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: iamtimscampi(a)gmail.com
Distribution: ---
Upon launching Fallout New Vegas (With or without New Vegas Script Extender) on
a 64-bit prefix, the game crashes after the initial splash screen.
On a 32-bit prefix, the game works as intended, without a crash.
This was tested both with Staging and regular versions of Wine, with and
without the "New Vegas Script Extender" addon.
While not necessary to play the game, a 64bit prefix is necessary for the new
version of Mod Organizer, a third party utility for the game that handles mod
loading. This crash prevents users from using the latest version of it
alongside the game.
--
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=38381
Bug ID: 38381
Summary: Fallout New Vegas (Steam Version) Crashes at Startup
on the Splash Screen
Product: Wine
Version: 1.7.40
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gordan(a)bobich.net
Distribution: ---
Created attachment 51228
--> https://bugs.winehq.org/attachment.cgi?id=51228
Fallout New Vegas Crash Backtrace
Fallout New Vegas (Steam Version) Crashes at Startup on the Splash Screen.
--
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=29736
Bug #: 29736
Summary: Fallout 2 crashes at "Please Stand By" screen.
Product: Wine
Version: 1.3.37
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mister_a(a)aol.com
Classification: Unclassified
Created attachment 38588
--> http://bugs.winehq.org/attachment.cgi?id=38588
FO2 in terminal
Look at attachments if you want to see the backlogs.
--
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=40838
Bug ID: 40838
Summary: I am able to install the Launcher. however as soon as
installation/updates are complete, the window crashes
into a small box at the upper right corner of my
screen, then crashes comepletely after that
Product: Wine
Version: 1.9.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ak11(a)cox.net
Distribution: ---
Created attachment 54811
--> https://bugs.winehq.org/attachment.cgi?id=54811
NO THIS IS NOT THE SAME CASE AS bug 40628....the logs are different
I am able to install the Launcher. however as soon as installation/updates are
complete, the window crashes into a small box at the upper right corner of my
screen, then crashes comepletely after that.
Any ideas? I hope its an easy fix, i almost have it working!
--
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=44211
Bug ID: 44211
Summary: Wine (2.21) doesn't work anymore on any game on
FreeBSD
Product: Wine
Version: 2.21
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adrien_fernandes2(a)hotmail.com
Created attachment 59990
--> https://bugs.winehq.org/attachment.cgi?id=59990
Output of AC with csmt
FreeBSD/amd64 11.1 (the release version in december 2017)
Wine staging 2.21 32 bits (built from a 32 bits chroot)
nVidia 765m (nvidia-driver-384.59)
12 GB RAM (even if 32 bits applications take less, you have the information)
from my 32 bits chroot, I installed the nVidia driver
libGL.so -> libGL-NVIDIA.so.1
libGL.so.1 -> libGL-NVIDIA.so.1
libGLESv2.so -> libGLESv2-NVIDIA.so.2
libGLESv2.so.2 -> libGLESv2-NVIDIA.so.2
It always worked that way four months ago (last time I was on my computer)
So actually I tried Streets of Rogue and Assassin's Creed. I copy the output of
AC so you can see what the terminal says me. I set CSMT on one try and disabled
it on the second. (Assassin's Creed always worked in the past, that's why I
give you its output)
--
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=35234
Bug ID: 35234
Summary: Fallout: New Vegas launcher crashes when selecting a
DLC by double click
Product: Wine
Version: 1.7.9
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
Classification: Unclassified
Created attachment 46995
--> http://bugs.winehq.org/attachment.cgi?id=46995
terminal output
I browsed Bugzilla's already closed and currently opened bug reports related to
Fallout: New Vegas/Fallout 3, but haven't find anything similar to this. It's
not a new bug because I can reproduce it with Wine 1.4.1, 1.6.1, 1.7.9 as well.
The problem: when you start Fallout:New Vegas, the launcher offers an option
named <Data Files> where you can enable/disable the installed DLCs. If I
double-click on the name of the DLC, Wine produces a crash as can be seen in
the attached log.
Single clicking on the name of the DLC doesn't produce the crash.
This was tested with a clean wineprefix, without any dll overrides, dwrite and
gameoverlayrenderer already disabled.
Fedora 19 x86
X.Org X Server 1.14.4
Nvidia binary drivers 325.15
--
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=31701
Bug #: 31701
Summary: Alan Wake crashes on start without native vcrun2008
Product: Wine
Version: 1.5.12
Platform: x86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: scott(a)open-vote.org
Classification: Unclassified
Created attachment 41667
--> http://bugs.winehq.org/attachment.cgi?id=41667
Console output
The steam version will automatically install vcrun2008, but the GoG version
will not.
Installing native vcrun2008 will work around the problem (and encounter other
problems)
--
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=45575
Bug ID: 45575
Summary: Skyrim: No controller input when multiple controllers
are connected
Product: Wine
Version: 3.13
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ahyattdev(a)icloud.com
Skyrim works fine when I have one wired Xbox 360 controller plugged in but when
I have another one also plugged into my machine that I am not using neither
controller works with the game.
I have tested what the behavior is on Windows and Skyrim works fine when
multiple Xbox controllers are connected. When running through Wine none of the
controllers give any input.
--
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=46151
Bug ID: 46151
Summary: XInput support doesn't support rumble on the DS4 (at
least)
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: epigramx(a)yahoo.com
Distribution: ---
That would be a neat feature and it's lacking right now. All Xbox Controllers
support two motors on the device. It appears that currently Wine doesn't
provide that data to applications. I was interested in the DS4 specifically out
of the box but I support the feature may be missing on the actual Xbox
controllers as well.
--
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=45688
Bug ID: 45688
Summary: Gamepad appears both as dinput and xinput (eg.
Valkyria Chronicles)
Product: Wine
Version: 3.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: gabriel.corona(a)enst-bretagne.fr
Distribution: ---
AFAIU, on Windows a gamepad appears either on DirectInput or on XInput.
Some games are helpful and automatically work with both. For example, Valkyria
Chronicles apparently automatically switches between DirectInput and Xinput
based on the latests input.
On Wine >= 3.3, every gamepad appears both on DirecrInput and XInput. This is
useful because the gamepad can work both on DirectInput and XInput gamed.
However, on Valkyria Chronicles (for example) the effect is that the game
switches randomly between the two modes because it apparently sees the same
gamepad from both APIs. This can be seen because the buttons displayes on
screen change from numbered key labels ("1", "2", "3", etc.) and XInput based
key labels ("A", "B", "C", "D").
In order to sucessfully run the game, I has to disable the gamepad from
DirectInput (using "wine control"). This works, but prevents running
DirectInput only games without reconfiguration.
A possible workaround would be to have an option to disable DirectInput
gamepads if both libraries are mapped in the same 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.