As I just stumbled over this little issue, I thought it might be worth sharing.
So I am playing Diablo 3 using wine and was willing to give the just recently released PTR a shot. Having downloaded and installed the client using the awesome PlayOnLinux (which I absolutely recommend if you are into Linux gaming!), I wanted to use the same procedure as for the normal client for starting, i.e. directly launching “Diablo III.exe -launch” and automatically applying a few tweaks which get rid of ugly stuttering.
For the vanilla client, my launch script looks as follows:
#!/bin/bash
cd ~/.PlayOnLinux/wineprefix/DiabloIII/drive_c/Program\ Files/Diablo\ III
export WINEPREFIX=$HOME/.PlayOnLinux/wineprefix/DiabloIII
setarch i386 -3 ~/.PlayOnLinux/wine/linux-amd64/1.5.5-DiabloIII_v3/bin/wine "Diablo III.exe" -launch &
pid=$!
taskset -cp 1 $pid 1> log1.log 2> log2.log && fg
where taskset is used to limit the game to just one cpu core, as multicore usage seems to be just not as good as it should. Using the full four cores of my machine results in a somehow jittery experience.
So now I wanted to use just the same script for the PTR, as just having a shortcut for launching it is a nice thing. So I copied it and changed the paths appropriately, but what was that? It didn’t work when I started it via the script, but when I used the launcher, it did just fine. The error that appeared was the game telling me that a patch was available, but actually there wasn’t.
After some research (and just opening my eyes ;)) I discovered that the region is set to Europe as a default and “public test”, which would be the region of choice, was not available. So the PTR client tried to connect to the Europe realm, which of course does not match the client version. So the server tells me “hey, you gotta patch if you wanna connect to me!” and the client just goes like “okay :(“…
What to do? The solution is simple, as I found out after looking in the logs of the launcher: Another command line parameter has to be applied, namely “OnlineService.PTR=true”, making the final launch script look like this:
#!/bin/bash
cd ~/.PlayOnLinux/wineprefix/Diablo3_PTR/drive_c/Program\ Files/Diablo\ III\ Public\ Test
export WINEPREFIX=$HOME/.PlayOnLinux/wineprefix/Diablo3_PTR
setarch i386 -3 ~/.PlayOnLinux/wine/linux-amd64/1.5.5-DiabloIII_v3/bin/wine "Diablo III.exe" OnlineService.PTR=true -launch &
pid=$!
taskset -cp 1 $pid 1> log1.log 2> log2.log && fg
So now it’s gonna work fine, at least as soon as the PTR is back up :)




Recent Comments