motionsetr.blogg.se

Battlenet sign in
Battlenet sign in






battlenet sign in
  1. Battlenet sign in install#
  2. Battlenet sign in drivers#
  3. Battlenet sign in update#

Always, always use the individual game’s install script unless there isn’t one available.

battlenet sign in battlenet sign in

This did not resolve the issue.Īnd if you’re using the regular Battle.Net install script, don’t. Tried this for both lutris included wine versions as well as downgrading my system wine-staging (from 13-1 to 12-1 and 12-1-1). Ok, let me try this a bit more rigorously (than I did yesterday). If you want to install WoW, use the WoW lutris install script, so on and so forth. So, if you want to install Overwatch, use the OVERWATCH lutris script. You don’t get that with the normal Battle.Net install script. Overwatch’s install script not only includes specific tweaks, but also an additional script for updating shader caches after a game update.

Battlenet sign in update#

Three, individual install scripts often include special extra scripts to update shader caches and the like, Overwatch is one prime example. For two, the individual game install scripts often get updated far more frequently than the launcher ones. For one, certain games (including numerous Battle.Net games) require specific workarounds which are only included in the individual install script. Lutris provides them for a reason, otherwise you’d just get install scripts for the launcher and there wouldn’t BE any individual game install scripts. Select the next newest or next oldest version, and try again.Īnd if you’re using the regular Battle.Net install script, don’t. Just right-click on the game in Lutris (I’m assuming you’re using the specific game install script and not the install script), click “Configure,” then “Runner options,” then click the drop-down for wine version. I’ve found with some launchers, after updates an old wine version flat-out won’t work on that same prefix anymore, and I have to switch versions, and it works perfectly. is working fine for me, so this is a configuration issue. If none of that works, just try a different wine version. * Fedora: `gnutls gnutls-devel openldap openldap-devel libgpg-error sqlite2.i686 sqlite2.x86_64` (Both i686 and x86_64 versions) * Arch: `lib32-gnutls lib32-libldap lib32-libgpg-error lib32-sqlite lib32-libpulse` These dependencies may already be installed on your system, but it won't hurt to ensure you have them. # Additional dependencies required specifically for :

Battlenet sign in drivers#

Please follow the instructions on () page to get them.Īs Battle.Net is a D3D11 app, and some installers use DXVK by default, it's required to install dependencies and right drivers for it. Wine dependencies are **required** for Overwatch to work. Please choose an Ext4 drive as destination instead._** **_Battle.Net won't work correctly if it was installed on an NTFS partition. lutris/docs/blob/master/ # Battle.Netīattle.Net is the game launcher for Blizzard and Activision games. Let me know if/what info would be helpful, and what else I could try! I did a fresh install (seperate from my already set up battlenet) for hots and this separate install of battlenet faced the same issue (i.e the login connection).įor additional info i’ve included the lutris -d log (of my normal installation) here. I suspect the issue is with dns and or internet related (i’ve seen several threads on this forum that mention battlenet is particularly sticky with dns/ipv6), but while I did attempt to follow previous suggestions that were suggested on this forum, they seemed to have no effect. When i logged on today this is what I encountered. Up to yesterday, I had no issues running battlenet. OpenGL Core: 4.5 (Core Profile) Mesa 20.1.4Īdditional info from the submit an issue json. OpenGL Renderer: Mesa DRI Intel® HD Graphics 4600 (HSW GT2) Vendor: Intel Open Source Technology Center Model: Intel® Core™ i7-4700HQ CPU 2.40GHz The issue is when loading battlenet from lutris, i get the “cannot connect to server”.








Battlenet sign in