Destiny 2 (1085660)

[Vildravn]

Compatibility Report

• Name of the game with compatibility issues: Destiny 2
• Steam AppID of the game: 1085660

System Information

• GPU: GTX 1060
• Driver/LLVM version: nvidia 435.21
• Kernel version: 5.2.17-200.fc30.x86_64
• Link to full system information report: https://gist.github.com/Vildravn/2214afd843ef0b26bd8381310b14a829
• Proton version: 3.16-9, 4.2-9, 4.11-6

I confirm:

• [x] that I haven't found an existing compatibility report for this game.
• [x] that I have checked whether there are updates for my system available.

steam-1085660.log

Symptoms

Process starts, game window never displays and process exits after a short while.

Reproduction

1. Launch Destiny 2 with Proton
2. Observe that Steam reports the game as Running
3. No window ever appears
4. The process exits after a while

[solenum]

You beat me to it, same issues here.

steam-1085660.log

Edit; Fair warning to everyone attempting to get the game working, just keep in mind that virtually everyone that has been successful in getting the game running on wine in the past has been banned, and evidently none of those bans have ever been lifted.

[Feavers]

OS................: Ubuntu 18.04.3 LTS (Bionic Beaver, linux 5.2.18-050218-generic) CPU...............: AMD Ryzen 5 2600X Six-Core Processor (4217MHz) Memory............: 31GiB GPU...............: Vega 56 (AMD/ATI Vega 10 XT [Radeon RX Vega 64] (1002:687f (ven:dev), rev. 0xc3))

• Kernel driver..: amdgpu
• Driver.........: 4.5, Mesa 19.2.0-devel - padoka PPA (mesa (unstable))
• Memory.........: 8176MB Steam package ver: 1569883362 Proton version....: proton-4.11-6

Same as above. Doesn't seem to launch. Only tested changing version from Win7 to Win10.. steam-1085660.log

[Xinayder]

You beat me to it, same issues here.

steam-1085660.log

Edit; Fair warning to everyone attempting to get the game working, just keep in mind that virtually everyone that has been successful in getting the game running on wine in the past has been banned, and evidently none of those bans have ever been lifted.

When Destiny was still under Battle.net and Bungie was under the influence of Activision. With that said, I suspect Linux users might not get banned for trying to run the game on Steam (also, those that managed to "play" the game before did it by deactivating the anti-cheat, which is a reason to be banned).

EDIT: according to https://www.bungie.net/en/Help/Article/11929

Steam Play Proton: Destiny 2 is not compatible with Steam Play's Proton.

[Feavers]

You beat me to it, same issues here. steam-1085660.log Edit; Fair warning to everyone attempting to get the game working, just keep in mind that virtually everyone that has been successful in getting the game running on wine in the past has been banned, and evidently none of those bans have ever been lifted.

When Destiny was still under Battle.net and Bungie was under the influence of Activision. With that said, I suspect Linux users might not get banned for trying to run the game on Steam (also, those that managed to "play" the game before did it by deactivating the anti-cheat, which is a reason to be banned).

EDIT: according to https://www.bungie.net/en/Help/Article/11929

Steam Play Proton: Destiny 2 is not compatible with Steam Play's Proton.

Uninstall it is then ;(

[garrixd]

Wonder if it since it's on steam and all ever have Proton developed for it

[Xinayder]

You beat me to it, same issues here. steam-1085660.log Edit; Fair warning to everyone attempting to get the game working, just keep in mind that virtually everyone that has been successful in getting the game running on wine in the past has been banned, and evidently none of those bans have ever been lifted.

When Destiny was still under Battle.net and Bungie was under the influence of Activision. With that said, I suspect Linux users might not get banned for trying to run the game on Steam (also, those that managed to "play" the game before did it by deactivating the anti-cheat, which is a reason to be banned). EDIT: according to https://www.bungie.net/en/Help/Article/11929

Steam Play Proton: Destiny 2 is not compatible with Steam Play's Proton.

Uninstall it is then ;(

Wonder if it since it's on steam and all ever have Proton developed for it

Google Stadia launches next month and Destiny is supported, so I think it's only a matter of time before we're able to play it via Proton.

[n00b3rpwn4g3]

I have the same problem 4.11-6 and 4.2-9. Also, regarding the Bungie help article, I wonder if they meant it as "the game is not currently compatible with proton" or "the game will not be made compatible with proton in the future". I'm hoping it's just a temporary, fixable incompatibility.

[fls2018]

Google Stadia launches next month and Destiny is supported, so I think it's only a matter of time before we're able to play it via Proton.

Stadia != Proton compatibility or a public native port.

Edit; Fair warning to everyone attempting to get the game working, just keep in mind that virtually everyone that has been successful in getting the game running on wine in the past has been banned, and evidently none of those bans have ever been lifted.

Issue with prior attempts is someone commented out a callback rather than find an actual solution, that said Bungie appear to be strict on what they allow and resort to restrictions & bans off the bat. Even debugging this might get you banned.

https://bugs.winehq.org/show_bug.cgi?id=44061

[jph168]

Proton Log steam-1085660.log.zip

Reproduction

Launch Destiny 2<Crashes Instantly.

System Information

• CPU: AMD Ryzen Threadripper 1950X 16-Core
• GPU: NVIDIA GeForce GTX 1080 Ti
• Driver/LLVM version: nvidia 435.21
• Kernel version: 5.2.11-1
• Proton version: 4.11-6
• Distro: Manjaro Linux

[jas0n098]

It's also worth nothing that the patch (that comments out the callback) still doesn't get the game to start, confirming dereklesho52's findings on the WineHQ Bugzilla

EDIT: steam-1085660.log

With callback patch. It's mostly identical with all other logs here

[Xinayder]

Here's my log with fsync, esync disabled, gamemode, dxvk and winedbg override: https://gist.github.com/RockyTV/11bf52586fc3c644ed24a7ab83f7c80b

[tunanachos]

You beat me to it, same issues here.

steam-1085660.log

Edit; Fair warning to everyone attempting to get the game working, just keep in mind that virtually everyone that has been successful in getting the game running on wine in the past has been banned, and evidently none of those bans have ever been lifted.

Thanks for the heads up..! That's insane. Might leave it a while before giving this a go lol

[Jimmyb1126]

You beat me to it, same issues here. steam-1085660.log Edit; Fair warning to everyone attempting to get the game working, just keep in mind that virtually everyone that has been successful in getting the game running on wine in the past has been banned, and evidently none of those bans have ever been lifted.

Thanks for the heads up..! That's insane. Might leave it a while before giving this a go lol

I think it's still worth trying to find a solution. If it doesn't work at all with Proton then Bungie probably wouldn't consider lifting the ban.

[scottAnselmo]

For what it's worth, I've played Overwatch and Heroes of the Storm for a year, year and a half on Wine by means of Lutris w/o a ban from the hydra that was Blizzard/Activision/Bungie. Given Destiny 2's new free model it doesn't make much sense to me for them to isolate income flows via ingame purchases or Shadowkeep/season pass purchases, especially if Valve gets Destiny 2 to run with Proton. I suspect Valve would put pressure on Bungie to not punish users for playing via Proton, but I tend to be an optimist.

[fls2018]

For what it's worth, I've played Overwatch and Heroes of the Storm for a year, year and a half on Wine by means of Lutris w/o a ban from the hydra that was Blizzard/Activision/Bungie. Given Destiny 2's new free model it doesn't make much sense to me for them to isolate income flows via ingame purchases or Shadowkeep/season pass purchases, especially if Valve gets Destiny 2 to run with Proton. I suspect Valve would put pressure on Bungie to not punish users for playing via Proton, but I tend to be an optimist.

Bungie's anti cheat solution is completely in-house, they didn't use whatever Blizzard uses otherwise this wouldn't of been an issue.

[n00b3rpwn4g3]

Just for reference, the protondb site lists Destiny 2 as being completely nonfunctional as well, and the user reports have some information about their logs that may help describe what the problem is, so here's that page if anyone's curious: https://www.protondb.com/app/1085660

[n00b3rpwn4g3]

Also, here's a gist of portion of my log file that I think would be relevant, it's where the error begins but before the register dump and other things: https://gist.github.com/n00b3rpwn4g3/d428958db931675db38ca993e8b1a341 If needed, I can post my whole log file as well, I just did not want to initially in case it has sensitive information but I don't know that for sure.

[rdunski]

I spent last night fiddling with Winetricks, Wincfg, and Proton launch options to try and get the game executable to load the dlls correctly and get something more in depth so someone can figure this out. I first googled the error code that the NtException throws:

trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x12d1220 ip=12d1220 tid=0031

And it appears that the dlls are trying to access invalid memory or memory they have no access to.

See: https://stackoverflow.com/questions/17168982/exception-error-c0000005-in-vc

I had to do some trial and error with dll overrides in order to get something past this snippet, which appears to be common in most peoples proton logs:

trace:loaddll:load_builtin_dll Loaded L"C:\\windows\\system32\\api-ms-win-core-fibers-l1-1-1.dll" at 0x7fa632ea0000: builtin

So, after hours of guessing and checking, this dll override (through wincfg or user.reg in the steamapps/compatdata/1085660/pfx/user.reg file) list is what got me the furthest:

"concrt140"="native"
"d3dcompiler_47"="builtin"
"hid"="native,builtin"
"msvcp100"="native,builtin"
"msvcp110"="native,builtin"
"msvcp120"="native,builtin"
"msvcp140"="builtin"
"msvcr100"="native,builtin"
"msvcr110"="native,builtin"
"msvcr120"="native"
"msvcr140"="builtin"
"vcruntime140"="builtin"

I had to install vcrun2013 and vcrun2017 through winetricks for the dlls to load correctly.

This got me up to this snippet in the log:

262302.003:0030:0031:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\msvcr120.dll" at 0x800000: native
262302.004:0030:0031:fixme:reg:GetEnabledXStateFeatures 
262302.004:0030:0031:trace:loaddll:load_native_dll Loaded L"C:\\windows\\system32\\concrt140.dll" at 0x180000000: native
262317.302:0030:0031:fixme:heap:RtlSetHeapInformation (nil) 1 (nil) 0 stub
262317.314:0030:0031:trace:seh:NtRaiseException code=c0000005 flags=0 addr=0x12d1220 ip=12d1220 tid=0031

Messing around with proton versions, launch options, or other dll overrides didn't help, but using winetricks to "Change settings" on the prefix, I checked forcemono and heapcheck. This got the proccess to get much further than before, running for about 1 minute until it zombified itself. I would post the full log but the file was ~500MB. The interesting part was at the end though:

262347.873:0030:0031:err:seh:setup_exception stack overflow 1696 bytes in thread 0031 eip 00007f19c974b529 esp 0000000000130f70 stack 0x130000-0x131000-0x530000

This leads me to believe that the problem doesn't necessarily fall on proton itself. It seems that wine has trouble translating the executable's memory allocation and stack, which leads to an overflow and various access violation errors.

Hopefully this helps someone to fix it, cause this is beyond my level of expertise, and spending 8 hours debugging this has me hoping for a coffee break :)

System Information

• CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
• GPU: Nvidia GeForce 1060 6GB
• Driver Version: 430.40
• Proton Version: 4-11.6
• Kernel Version: 4.19.69-1
• Distro: Manjaro Linux

[n00b3rpwn4g3]

I have windows on another hard drive, would it be helpful to try and make a log of what it does when it functions normally? If so, is there any particular software to make a log like the one proton/wine makes, or even a built-in way for steam to tell the game to make a log file?

[fls2018]

To add again to the ban warnings, here's an official stance on Proton:

https://www.bungie.net/en/Forums/Post/253736828?sort=0&page=0&path=1

Destiny 2 on PC only supports Windows. Linux via Proton is not supported and is considered a modified operating system, as is Wine and other emulation services.

Also another warning against those attempting to debug it, probably not best to do so on your main accounts or hardware as they will pick it up even if it's just winedebug/proton logging. An example of what they ban for:

Your account was banned on Oct 2nd for targeting the Destiny process with a tool designed to read and modify the memory of running processes. Your ban has been reviewed and upheld.

https://www.bungie.net/en/Forums/Post/253758789?sort=0&page=0&path=1

I'd advise not to touch this game in proton unless there's a change in stance as they take no prisoners.

[Xinayder]

To add again to the ban warnings, here's an official stance on Proton:

https://www.bungie.net/en/Forums/Post/253736828?sort=0&page=0&path=1

Destiny 2 on PC only supports Windows. Linux via Proton is not supported and is considered a modified operating system, as is Wine and other emulation services.

Also another warning against those attempting to debug it, probably not best to do so on your main accounts or hardware as they will pick it up even if it's just winedebug/proton logging. An example of what they ban for:

Your account was banned on Oct 2nd for targeting the Destiny process with a tool designed to read and modify the memory of running processes. Your ban has been reviewed and upheld.

https://www.bungie.net/en/Forums/Post/253758789?sort=0&page=0&path=1

I'd advise not to touch this game in proton unless there's a change in stance as they take no prisoners.

That's interesting, I wonder how the game will run on Stadia if it doesn't run with Wine and we're not allowed to debug and test it to find a way to get it working.

[Jimmyb1126]

I'd advise not to touch this game in proton unless there's a change in stance as they take no prisoners

It wouldn't be a bad idea to try to get it working on an alternate account though. That way we can pitch it to Bungie that it works successfully and that they wouldn't have to do anything on their part besides lift the ban.

Besides, I'm sure Bungie would accept appeals if you mention that you were using wine/proton. The only reason why the ban is in place is to avoid cheating by changing the DLLs.

[Eoin-ONeill-Yokai]

To add again to the ban warnings, here's an official stance on Proton: https://www.bungie.net/en/Forums/Post/253736828?sort=0&page=0&path=1

Destiny 2 on PC only supports Windows. Linux via Proton is not supported and is considered a modified operating system, as is Wine and other emulation services.

Also another warning against those attempting to debug it, probably not best to do so on your main accounts or hardware as they will pick it up even if it's just winedebug/proton logging. An example of what they ban for:

Your account was banned on Oct 2nd for targeting the Destiny process with a tool designed to read and modify the memory of running processes. Your ban has been reviewed and upheld.

https://www.bungie.net/en/Forums/Post/253758789?sort=0&page=0&path=1 I'd advise not to touch this game in proton unless there's a change in stance as they take no prisoners.

That's interesting, I wonder how the game will run on Stadia if it doesn't run with Wine and we're not allowed to debug and test it to find a way to get it working.

They probably have a native version for Stadia. Whether or not that will ever be released to the public though is up to them.

[solenum]

It wouldn't be a bad idea to try to get it working on an alternate account though.

I would do some investigating into how the bans are handled first, on the off chance they use other meta-data to prevent you from creating another account and playing (Hardware ID, IP's, etc. Dead by Daylight for example, handles its bans in a similar way).

Besides, I'm sure Bungie would accept appeals if you mention that you were using wine/proton. The only reason why the ban is in place is to avoid cheating by changing the DLLs.

From what I've seen all of the appeals mentioned this and they still double down on not lifting the bans.

[fls2018]

I would do some investigating into how the bans are handled first, on the off chance they use other meta-data to prevent you from creating another account and playing (Hardware ID, IP's, etc. Dead by Daylight for example, handles its bans in a similar way).

From the FAQ they do device ban also, unsure how this affects wine/linux: https://www.bungie.net/en/Help/Article/11929

From what I've seen all of the appeals mentioned this and they still double down on not lifting the bans.

Just reading the first paragraph of that FAQ shows how strict they are, even having a dodgy internet connection can net you a ban. If you're ISP ends up having issues while playing you could end up having a two week restriction or even losing your account permanently.

Also reading BNGSecurity's replies to the banned is interesting to find things people are getting banned for, here's one person getting banned for having developer tools open in the background:

https://www.bungie.net/en/Forums/Post/253019701?sort=0&page=0&path=1

[solenum]

Also reading BNGSecurity's replies to the banned is interesting to find things people are getting banned for

Indeed, I thought it was a joke when people where claiming that bans where being given out for unstable/bad connections, but it appears to be true.

Honestly, don't even bother debugging this one unless you fully understand the risks and want to take one for the team, permanently.

[solenum]

Update, as per this response it appears that if you manage to get the game running in wine/proton, even without modifying/patching the game you'll be risking a ban in the case that the anticheat doesn't fire up and run correctly, which is often the case with a lot of games.

For example, a lot of EAC and BattleEye games can fire up but you soon get kicked out due to the anticheat not running correctly or at all, based on this response you can assume you'll get banned, not just kicked out of the game.

[rdunski]

Also might be worth pointing out that BNGSecurity said that "static" debugging of the process is allowed but using the network level of the process is what gets you the hammer (at least that's what I got out of it). So someone can try to figure this out if they turn off their computer's network.

Source: https://www.bungie.net/en/Forums/Post/253019701?sort=0&page=0&path=1

(From fls2018's comment)

EDIT: When I tried debugging this myself, I didn't disable my network, but the process never got far enough to actually launch anything. I eventually caved and dual booted windows just to play D2 and my account wasn't banned after the debugging. Hopefully a vote of confidence for this theory.

[stralytic]

Please support this petition: https://www.change.org/p/bungie-inc-allow-linux-users-to-play-destiny-2

[codeman101]

You beat me to it, same issues here.

steam-1085660.log

Edit; Fair warning to everyone attempting to get the game working, just keep in mind that virtually everyone that has been successful in getting the game running on wine in the past has been banned, and evidently none of those bans have ever been lifted.

@exezin

I couldn't believe when I read your post here. IMO Activation should be boycotted for it.