https://bugs.winehq.org/show_bug.cgi?id=39540
Bug ID: 39540
Summary: DirectInput, Xinput, Overall Controller support messed
up on OS X
Product: Wine
Version: 1.7.54
Hardware: x86
OS: Mac OS X
Status: UNCONFIRMED
Severity: major
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: adrian.koehres(a)gmx.net
I've tried …
[View More]many games now and nothing really works.
I tried a PS3 Dualshock Controller and also a Xbox360 controller. If the game
doesn't handle controller support by itself then there is no chance to get it
to work. Dinput breaks controller input completely in most cases and xinput
doesn't do anything at all.
I had games where the buttons were recognized, and the axes not. And games
where absolutely nothing was recognized. The controllers I testet worked
perfectly with native controller supporting games on OS X. As soon as I'm using
wine and the game isn't handling the controller by itself, its a pain.
For example Volgarr the Viking (I know there is a OS X port) works perfectly
when porting the Windows version with wine. The Controller gets detected
flawlessly without any problems. There is no need to install dinput/xinput
through winetricks as the game is doing that somehow by itself.
There is a game called TowerClimb when portet with wine on OS X, only the
buttons work. The axes and throttlers absolutely don't work. No matter if I
install dinput/xinput through winetricks.
I tried mapping the controller myself through regkey values but you need the
name of the divice for doing that. So using "WINEDEBUG=+dinput wine game.exe
2>&1 | grep joydev_enum_device" results in
"fixme:dinput:IDirectInputDevice2AImpl_EnumEffects
(this=0x7043d00,0x26c1a60,0x2702fb8,0x00000000): stub!"
Then I tried PrinceOfPersia: Sands Of Time where it was not possible to get any
controller working with it's wine port. Installed dinput/xinput. Nothing seems
to work though.
The Wine Control Panel Gamecontroller utility seems to recognize the
controllers though. Also different Windows Gamecontroller utilities seem to
recognize the controllers flawlessly when ported with wine. Programs which
handle the controller by themselves with their own dinput/xinput.dll's seem to
work well.
It's getting problematic when you have to use dinput/xinput through winetricks
as they don't seem to work.
I've tried many different versions on wine. Nothing works.
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=44228
Bug ID: 44228
Summary: prince of persia 3D crashes at play (installes ok)
Product: Wine
Version: 3.0-rc3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: cedric.dewijs(a)telfort.nl
Distribution: ---
Created attachment 60024
…
[View More]--> https://bugs.winehq.org/attachment.cgi?id=60024
backtrace created by wine itself
After installing, Prince of persia 3D crashes with an unhandled exception
uname -a
Linux archlinux 4.14.8-1-ARCH #1 SMP PREEMPT Wed Dec 20 21:27:44 UTC
2017 x86_64 GNU/Linux
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=44249
Bug ID: 44249
Summary: Can't play Diablo 2 (Battle.net) when Virtualization
in BIOS is disabled.
Product: Wine
Version: 2.22
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: asriroc(a)gmail.com
…
[View More]Distribution: ---
1. I have "Virtualization" as "Enable" in my BIOS (Compaq Presario F763NR
Notebook with the most recent BIOS version).
2. I installed a fresh Fedora 27 Cinnamon Spin with Linux
4.14.8-300.fc27.x86_64 kernel.
3. I installed NVIDIA 304.137
4. I installed Diablo 2 using WINE 2.22
At this point, I would be able to play Diablo 2 using Battle.net
5. I rebooted the notebook, and set "Disable" on the "Virtualization" in my
BIOS.
6. I tried to play Diablo 2, using WINE 2.22, but I won't be able to use
Battle.net
Now, if I rebooted and enabled my virtualization in my BIOS, Diablo 2 would
work again.
Thank you so much.
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=42223
Bug ID: 42223
Summary: I cant install AB Bulkmailer .. Please HELP me ...
Product: Wine
Version: 2.0-rc4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: bluebird456(a)vfemail.net
Distribution: ---
Created attachment 56863
-…
[View More]-> https://bugs.winehq.org/attachment.cgi?id=56863
AB BulkMailer install BUG
I want to install AB BulkMailer .
Which is a Windows app .
I tried to install the app , But error appears ...
I attached the detail in attached TEXT FILE ...
Please CHECK and PLEASE HELP ME ..
Please Fix the error BUG as soon as possible ...
I JUST want to use the app ...
--
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.
[View Less]
http://bugs.winehq.org/show_bug.cgi?id=35883
Bug ID: 35883
Summary: Horizon crashes with page fault
Product: Wine
Version: 1.7.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jmelton116(a)gmail.com
Created attachment 47912
--> http://bugs.winehq.org/attachment.cgi?…
[View More]id=47912
Backtrace generated by crash
Horizon seems to crash at random times with a page fault. There seems to be no
sort of consistency between what is occuring in game and when these occur, but
I could be wrong. These were encountered on the latest git version. Page
fault's backtrace is 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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=44146
Bug ID: 44146
Summary: Crysis 2: DX11 is a slideshow
Product: Wine
Version: 3.0-rc1
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: christian.frank(a)gmx.de
Distribution: ---
Hi,
trying to play Crysis 2 with DX11 is …
[View More]actually impossible, it is a complete
slideshow. Switching from DX9 to DX11 the FPS drop from ~ 40 to ~ 8 fps.
Tons of fixmes are spit out:
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[31]" might be used before being initialized
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 4.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 5.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 6.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 7.
0048:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader
#24:
0048:fixme:d3d_shader:print_glsl_info_log Vertex info
0048:fixme:d3d_shader:print_glsl_info_log -----------
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[1]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[2]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[3]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[4]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[5]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[6]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[7]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[8]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[9]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[10]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[11]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[12]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[13]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[14]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[15]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[16]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[17]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[18]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[19]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[20]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[21]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[22]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[23]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[24]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[25]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[26]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[27]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[28]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[29]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[30]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[31]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log
0048:fixme:d3d_shader:print_glsl_info_log Fragment info
0048:fixme:d3d_shader:print_glsl_info_log -------------
0048:fixme:d3d_shader:print_glsl_info_log 0(24) : warning C7050: "R0.yzw"
might be used before being initialized
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 4.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 5.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 6.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 7.
0048:fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier
0x800000c2.
0048:fixme:d3d_shader:shader_sm4_read_instruction_modifier Unhandled modifier
0x00155543.
0048:fixme:d3d_shader:print_glsl_info_log Info log received from GLSL shader
#27:
0048:fixme:d3d_shader:print_glsl_info_log Vertex info
0048:fixme:d3d_shader:print_glsl_info_log -----------
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[1].zw" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[2]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[3]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[4]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[5]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[6]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[7]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[8]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[9]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[10]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[11]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[12]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[13]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[14]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[15]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[16]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[17]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[18]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[19]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[20]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[21]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[22]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[23]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[24]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[25]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[26]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[27]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[28]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[29]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[30]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log 0(20) : warning C7050:
"vs_out[31]" might be used before being initialized
0048:fixme:d3d_shader:print_glsl_info_log
0048:fixme:d3d_shader:print_glsl_info_log Fragment info
0048:fixme:d3d_shader:print_glsl_info_log -------------
0048:fixme:d3d_shader:print_glsl_info_log 0(26) : warning C7050: "R0.yzw"
might be used before being initialized
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 4.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 5.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 6.
0043:fixme:d3d11:d3d_blend_state_create Color mask 0 not supported for render
target 7.
My GPU: Nvidia GTX 970 (384.98)
Memory: 16GB
CPU: Core i5 3570k
Opensuse Tumbleweed, latest Snapshot
Many thanks !
Christian
--
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.
[View Less]
http://bugs.winehq.org/show_bug.cgi?id=22755
Summary: Regression : win16 installer program of "de rouck"
freeze
Product: Wine
Version: 0.9.31.
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: kernel32
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: vincent.hardy.be(a)gmail.com
Created an attachment (id=28058)
--> (http:/…
[View More]/bugs.winehq.org/attachment.cgi?id=28058)
wine-1.1.31 screenshot
It works with wine-1.1.30.
With wine-1.1.31, see screenshot
Regression test says :
3b1186de5aeabd261e70dab8b78a730030075ca1 is the first bad commit
commit 3b1186de5aeabd261e70dab8b78a730030075ca1
Author: Alexandre Julliard <julliard(a)winehq.org>
Date: Wed Oct 7 17:14:10 2009 +0200
kernel32: Move the 16-bit string functions to kernel16.c.
:040000 040000 3412021b8c21c250ee3ccc60ce31c3f3f9365c50
3c5be0f4e2330e28e86e4b839447d40d88bf42f3 M dlls
--
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.
[View Less]
https://bugs.winehq.org/show_bug.cgi?id=44822
Bug ID: 44822
Summary: Warframe can't update / game can't run
Product: Wine
Version: 3.4
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: vblanton(a)gmail.com
Distribution: ---
Warframe can't get past updating process, hence …
[View More]game won't start. This is a
fresh install.
Installs fine via steam. Starts with workarounds:
winetricks: d3dx9 wininet winhttp xact hosts corefonts fontfix vcrun2015
Updating fails with the message "Update Failed! The content servers are
temporarily"
No workarounds have fixed this so far. Attempts to install other Visual C++
packages haven't helped. Various DLL overrides haven't helped.
--
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.
[View Less]
http://bugs.winehq.org/show_bug.cgi?id=33131
Bug #: 33131
Summary: taskkill doesn't support /fi (filtering) option
Product: Wine
Version: 1.5.25
Platform: x86-64
OS/Version: Linux
Status: NEW
Keywords: download
Severity: normal
Priority: P2
Component: programs
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: austinenglish(a)gmail.com
Blocks: 33130
…
[View More]Classification: Unclassified
Noticed while looking at bug 33130
0067:Call KERNEL32.CreateProcessW(00000000,008fcb00
L"C:\\windows\\system32\\taskkill.exe /F /Fi \"MODULES eq
AutoupdatePlugin.cpl\"
/T",00000000,00000000,00000000,00000400,00000000,00000000,008fb1fc,008fb240)
ret=7e4d517f
--
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.
[View Less]