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.
https://bugs.winehq.org/show_bug.cgi?id=49051
Bug ID: 49051
Summary: Got "rawinput:RegisterRawInputDevices Unhandled flags
0x230 for device 0" in Fallout3 and NV
Product: Wine-staging
Version: 5.7
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: avenjames(a)live.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
As title description I got this problem since I updated version after 5.0
stable, from 5.1 to 5.7 stable/staging/dev, the game's cursor could hardly move
and unhandled at all.
I tested version 5.7 staging as usually as I did once notice the update's
coming, but this time I got messages:
0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0.
0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0.
0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0.
0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0.
I think it must be related to the problem that I have, any idea friends?
--
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=48754
Bug ID: 48754
Summary: Fallout New Vegas sound glitch\crackling\missing
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: avenjames(a)live.com
As title mentioning,
the audio effect missing or crackling sometimes,
the console showing
"
0071:fixme:qtdatahandler:myComponentRoutineProc unhandled select 0x28
0071:fixme:qtsplitter:QT_Process_Movie QuickTime cannot handle media
type(-2048)
"
these line happening continuously,
any idea to fix?
--
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.
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=48582
Bug ID: 48582
Summary: PlayStation Now: Controllers aren't detected with
Microsoft's native xinput1_3.dll
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: devilj(a)outlook.pt
Distribution: ---
Xbox One controllers (at least) aren't detected when using Microsoft's native
xinput1_3.dll, but they are working fine when using Wine's built-in version.
I captured a log using Wine's BUILT-IN implementation, but it doesn't say much.
The program polls "XInputGetStateEx" to get the state of indices 0 and 1:
004d:trace:xinput:XInputGetStateEx (index 0, state 0842FEB0)!
004d:trace:xinput:XInputGetStateEx (index 1, state 0842FEB0)!
And the respective +relay (using only the built-in module):
0040:Call xinput1_3.XInputGetStateEx(00000000,07edfeb0) ret=0048d99d
0040:Ret xinput1_3.XInputGetStateEx() retval=00000000 ret=0048d99d
0040:Call xinput1_3.XInputGetStateEx(00000001,07edfeb0) ret=0048d99d
0040:Ret xinput1_3.XInputGetStateEx() retval=0000048f ret=0048d99d
--
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.