Diablo® III

Linux / Wine issues

make sure that you have your video memory size registry key for wine so that it knows how much video memory it has to use. I have had all kinds of problems with games recognizing my video card as being up to par until i set that key.

i play on a laptop:
i7 quad
8G ram
nvidia quattro 880M 1G
1920x1080 max settings no graphic lag with reg key.


That did it. After setting HKEY_CURRENT_USER\Software\Wine\Direct3D\VideoMemorySize to the string value "2048", I have no longer have any problems with "High" shadow quality at 1920x1080 full screen.

Thanks!


I found the wine registry, but I don't have a DIrect3D entry at all in the place indicated above. D3 does run, but I'd like to improve fps as much as possible. Any idea why Direct3D entry would be missing?
Reply Quote


That did it. After setting HKEY_CURRENT_USER\Software\Wine\Direct3D\VideoMemorySize to the string value "2048", I have no longer have any problems with "High" shadow quality at 1920x1080 full screen.

Thanks!


I found the wine registry, but I don't have a DIrect3D entry at all in the place indicated above. D3 does run, but I'd like to improve fps as much as possible. Any idea why Direct3D entry would be missing?


If you're using playonlinux, you can configure it in the "Display" tab of the Diablo III configuration. Else if you're editing the registry directly, just create a key named "Direct3D" in the right place, then inside the "Direct3D" key, create a "String Value" named "VideoMemorySize".
Reply Quote
06/11/2012 11:26 AMPosted by MountainMan
I read the thread, which is why I'm asking for additional help. setarch doesn't work, and according to the PlayOnLinux site, it's supposedly unnecessary if you have 1.5.5-DiabloIII_v3 installed, yet I'm still having a problem. Just wanted to know if anyone had any additional insight.


If the patched version is not working for you, I'd suggest making note of that on the Wine ticket (http://bugs.winehq.org/show_bug.cgi?id=30849).
    But before doing that:
  • Did you apply the ptrace_scope fix? "sysctl kernel.yama.ptrace_scope" should return the value "0".
  • Does it coincide with a significant rise in CPU usage by the "Diablo III" and "wineserver" processes?
  • Does "strace -e ptrace -p $(pgrep wineserver)" return an endless stream of ptrace system calls?
Reply Quote


I found the wine registry, but I don't have a DIrect3D entry at all in the place indicated above. D3 does run, but I'd like to improve fps as much as possible. Any idea why Direct3D entry would be missing?


If you're using playonlinux, you can configure it in the "Display" tab of the Diablo III configuration. Else if you're editing the registry directly, just create a key named "Direct3D" in the right place, then inside the "Direct3D" key, create a "String Value" named "VideoMemorySize".


Thanks, I tried that and the game still runs but I can't compare the performance. For some reason ctrl+R no longer displays fps after making this registry key...

Edit: restarting seems to have fixed that. fps seems about the same so I'm not sure if it made any difference.

On a different note, I am still getting glitches in text displayed in menus. For example in the Resume Game, Change Quest, Public Games, and Auction House buttons. The errors are sporadic and tolerable but I'm curious what the cause might be.
Edited by Lenymo#1288 on 6/11/2012 2:17 PM PDT
Reply Quote
Posts: 4,150
View profile
I read the thread, which is why I'm asking for additional help. setarch doesn't work, and according to the PlayOnLinux site, it's supposedly unnecessary if you have 1.5.5-DiabloIII_v3 installed, yet I'm still having a problem. Just wanted to know if anyone had any additional insight.


If the patched version is not working for you, I'd suggest making note of that on the Wine ticket (http://bugs.winehq.org/show_bug.cgi?id=30849).
    But before doing that:
  • Did you apply the ptrace_scope fix? "sysctl kernel.yama.ptrace_scope" should return the value "0".
  • Does it coincide with a significant rise in CPU usage by the "Diablo III" and "wineserver" processes?
  • Does "strace -e ptrace -p $(pgrep wineserver)" return an endless stream of ptrace system calls?

Thanks for the advice. My ptrace is returning a value of 1, so I guess I'll start there.

Edit: That was it. Changed it to 0 and now Diablo 3 runs. It's a little slow, though. Probably need to enable OpenGL somehow.
Edited by MountainMan#1630 on 6/11/2012 3:34 PM PDT
Reply Quote
Posts: 10
I found after the warden changes made setarch i386 -3 necessary that my framerate dropped significantly. Tonight though I tried using taskset -p f `pidof Diablo\ III.exe" to enable all the cores of my cpu again and to my surprise the game ran very well again. Whatever was making the game work badly on my 3-core processor before isn't affecting it now, I don't know if this is due to the setarch change or something else. Can anyone else confirm that they don't have to limit the game to one processor for performance reasons any longer?
Reply Quote
anybody esle getting a patch loop this morning ?

**forgot to read the other posts before posting myself** sorry :rollyeyes:
Edited by s3r3nity#1960 on 6/12/2012 6:35 AM PDT
Reply Quote
I don't seem to be having an issue quite like anyone else. I'm running the following:
Linux Mint 13 (Ubuntu 12.04)
AMD Radeon 6870
8GB RAM

I'm running the newest version of PlayOnLinux/Wine and the newest Catalyst drivers from AMD (12.4). When I start Diablo III, I see this on my screen: http://goo.gl/yBrzJ

Can anyone offer any suggestions?

Edit: I'm told this issue is related to fullscreen mode. I'll change that and report back the results.
Edited by revelous#1100 on 6/12/2012 7:22 AM PDT
Reply Quote
Im on Fedora 17 64bit, have nvidia drivers and wine 1.5.3. Didnt install anything extra via winetricks.
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
err:d3d:init_format_base_info Failed to allocate memory.
Direct3D9 is not available without OpenGL.
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
err:d3d:init_format_base_info Failed to allocate memory.
Direct3D9 is not available without OpenGL.
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
err:d3d:init_format_base_info Failed to allocate memory.
Direct3D9 is not available without OpenGL.
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
err:d3d:init_format_base_info Failed to allocate memory.
Direct3D9 is not available without OpenGL.
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
err:d3d:init_format_base_info Failed to allocate memory.
Direct3D9 is not available without OpenGL.
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
err:d3d:init_format_base_info Failed to allocate memory.
Direct3D9 is not available without OpenGL.
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
err:d3d:init_format_base_info Failed to allocate memory.
Direct3D9 is not available without OpenGL.
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
err:d3d:init_format_base_info Failed to allocate memory.
Direct3D9 is not available without OpenGL.
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
err:d3d:init_format_base_info Failed to allocate memory.
Direct3D9 is not available without OpenGL.
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
err:d3d:init_format_base_info Failed to allocate memory.
Direct3D9 is not available without OpenGL.
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
err:d3d:init_format_base_info Failed to allocate memory.
Direct3D9 is not available without OpenGL.
^Cfixme:console:CONSOLE_DefaultHandler Terminating process 62 on event 0
fixme:console:CONSOLE_DefaultHandler Terminating process 64 on event 0
ShutdownHandler called with CtrlType = 0
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
err:d3d:init_format_base_info Failed to allocate memory.
Direct3D9 is not available without OpenGL.
[jan@janpc ~]$ Application tried to create a window, but no driver could be loaded.
Unknown error (0).
wine: Unhandled exception 0x40000015 at address 0x7ef70023:0x00e96031 (thread 006e), starting debugger...
Agent is shutting down
X Error of failed request: BadPixmap (invalid Pixmap parameter)
Major opcode of failed request: 54 (X_FreePixmap)
Resource id in failed request: 0x2a00044
Serial number of failed request: 340
Current serial number in output stream: 343
Exiting with code 65535
fixme:console:CONSOLE_DefaultHandler Terminating process 48 on event 0
^C
[jan@janpc ~]$ taskset -c 1-3 setarch i386 -3 wine explorer /desktop=launcher.exe,1680x1050 /home/jan/.wine/drive_c/Program\ Files\ \(x86\)/Diablo\ III/Diablo\ III.exe -opengl -launch


What should I do?
Reply Quote
Im on Fedora 17 64bit, have nvidia drivers and wine 1.5.3. Didnt install anything extra via winetricks.
err:d3d_caps:WineD3D_CreateFakeGLContext Can't find a suitable iPixelFormat.
err:d3d:InitAdapters Failed to get a gl context for default adapter
err:d3d:init_format_base_info Failed to allocate memory.
Direct3D9 is not available without OpenGL.


What should I do?


Are the 32-bit nvidia libraries installed? A little bit of googling turned up this thread: http://www.playonlinux.com/en/topic-8943.html
Reply Quote
I have kmod-nividia installed. I suppose they are 64 bit.
Reply Quote
06/13/2012 11:02 AMPosted by JanBirsa
I have kmod-nividia installed. I suppose they are 64 bit.


I think the package you're looking for is this: xorg-x11-drv-nvidia-libs.i686

(I'm not a Fedora user, so I can't verify.)
Reply Quote
I removed kmod-nvidia and installed drivers from nvidia website...tho every time I get kernel updated I will have to recompile drivers right?
Reply Quote
Now I get this when trying to launch...
Argument[0]: 'C:/users/Public/Application Data/Battle.net/Agent/Agent.998/Agent.exe'
Argument[1]: '--locale=enUS'
Agent is running as Administrator.
Database Insert: /option
Database Insert: /agent
Database Insert: /
Database Insert: /version
Database Insert: /repair
Database Insert: /update
Database Insert: /install
Database Insert: /gamesession
Database Insert: /backfill
Database Insert: /game
Database Insert: /game/diablo3_engb
Database Insert: /game/client
Database Insert: /spawned
Database Insert: /agent/download
Database Insert: /register
fixme:process:GetLogicalProcessorInformation (0x33f2e4,0x33f8e4): stub
err:wininet:open_http_connection create_netconn failed: 10036
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
err:wininet:open_http_connection create_netconn failed: 10036
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
err:wininet:open_http_connection create_netconn failed: 10036
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
err:wininet:open_http_connection create_netconn failed: 10036
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
err:wininet:open_http_connection create_netconn failed: 10036
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixme:process:GetLogicalProcessorInformation (0xebce08,0xebd408): stub
fixme:process:GetLogicalProcessorInformation (0xebcdd8,0xebd3d8): stub
fixme:process:GetLogicalProcessorInformation (0xfbe334,0xfbe934): stub
fixme:process:GetLogicalProcessorInformation (0xfbe304,0xfbe904): stub
err:wininet:open_http_connection create_netconn failed: 10036
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
err:wininet:open_http_connection create_netconn failed: 10036
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
err:wininet:open_http_connection create_netconn failed: 10036
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
err:wininet:open_http_connection create_netconn failed: 10036
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixme:process:GetLogicalProcessorInformation (0x245e358,0x245e958): stub
fixme:process:GetLogicalProcessorInformation (0xfbe334,0xfbe934): stub
fixme:process:GetLogicalProcessorInformation (0xfbe304,0xfbe904): stub
Initialize HttpProtocol Server Called.
fixme:process:GetLogicalProcessorInformation (0x33f4e8,0x33fae8): stub
fixme:process:GetLogicalProcessorInformation (0x33f4c4,0x33fac4): stub
fixme:process:GetLogicalProcessorInformation (0x33f4c4,0x33fac4): stub
fixme:process:GetLogicalProcessorInformation (0x33f4c4,0x33fac4): stub
fixme:process:GetLogicalProcessorInformation (0x33f4c4,0x33fac4): stub
fixme:process:GetLogicalProcessorInformation (0x33f4c4,0x33fac4): stub
fixme:process:GetLogicalProcessorInformation (0x33f4c4,0x33fac4): stub
fixme:process:GetLogicalProcessorInformation (0x33f4c4,0x33fac4): stub
fixme:process:GetLogicalProcessorInformation (0x33f4c4,0x33fac4): stub
Agent started on port #1120
Executing operation: disable_firewall applicationPath="C:\users\Public\Application Data\Battle.net\Agent\Agent.998\Agent.exe" applicationName="Blizzard Agent"
fixme:hnetcfg:fw_profile_get_NotificationsDisabled 0x11caf8, 0x33f958
AgentAsAdmin failed to add a firewall exception for 'C:\users\Public\Application Data\Battle.net\Agent\Agent.998\Agent.exe'.
Registered Periodic Event: "auth validation event" with a resolution of 10000 and a start delay of 10000
Registered Event: "shutdown event"
Registered Event: "database flush event"
Request Issued: GET /agent

Response: 200
{
"update" : {},
"install" : {},
"backfill" : {},
"pid" : 47.000000,
"state" : 1007.000000,
"version" : "1.0.0.998",
"type" : "retail",
"authorization" : "87953667473DD122B45B851AD13A838C"
}


What am I missing? Wine 1.5.3
Reply Quote
Now I get this when trying to launch...

(snip)

What am I missing? Wine 1.5.3


That output looks pretty much normal (my playonlinux log has the same warnings in it, and it works just fine.)

I'm using wine 1.5.5, installed via playonlinux (they have a special patched version which works around a few Diablo3-specific issues.) Maybe you could give that a try (http://www.playonlinux.com/en/download.html)

I think you could have kept your kmod-nvidia package, and installed the xorg-x11-drv-nvidia-libs.i686 package in addition. The kmod package is the kernel module; the xorg-x11-drv package is the userspace libraries. Both are needed.
Reply Quote
It was working fine yesterday, but now it's broken again for me.

64-bit linux kernel, 32-bit sid user space
Linux xxxx 3.2.0-2-amd64 #1 SMP Fri Jun 1 19:39:45 UTC 2012 x86_64 GNU/Linux
wine-1.5.5

setarch i386 -3 doesn't work with 32-bit userspace, so that is no help.

symptoms are either

1) stuck at retrieving heros on login
2) removed from game
3) auction house stops responding


You might try applying one of the patches contributed to the wine ticket (http://bugs.winehq.org/show_bug.cgi?id=30849). The latest playonlinux wine build for Diablo3 (1.5.5-DiabloIII_v3) incorporates it already, so that would be the quickest way to see if the patch works.
Reply Quote
I already have:
Package 1:xorg-x11-drv-nvidia-libs-295.53-1.fc17.x86_64 already installed and latest version


Tho not i686...whats the difference? Can I have both?
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)

Reported!

[Close]