ValveSoftware / ValveSoftware/Proton

Dance Collider (692690)

Open
#3,392 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Game compatibility - Unofficial
Dominant language
C++
Stars
32.8k
Forks
1.6k
PR merge metrics
PR metrics pending

Description

Compatibility Report

  • Name of the game with compatibility issues: Dance Collider
  • Steam AppID of the game: 692690

System Information

  • GPU: Vega 56
  • Driver/LLVM version: Mesa 19.3.1
  • Kernel version: Linux 5.4.2
  • Proton version: 3.16, 4.2, 4.11

I confirm:

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

Symptoms

Dance Collider works out of the box with Proton 4.11-12.
I did not test yet if the ocasional microlag when a lot of orbs appear is still there.

Dance Collider only works out of the box with proton 3.7 and not with 3.16, 4.2, or 4.11

For these Three versons it crashes with an error in the proton_log similar to this:

Unhandled exception: page fault on read access to 0x00000000 in 64-bit code (0x00007fdc5ce6f6e0).
0074:fixme:dbghelp:elf_search_auxv can't find symbol in module
Register dump:
 rip:00007fdc5ce6f6e0 rsp:000000000022e330 rbp:0000000000000005 eflags:00010246 (  R- --  I  Z- -P- )
 rax:0000000000000000 rbx:0000000000000000 rcx:000000007c8d7010 rdx:00007fdbf9ffd010
 rsi:000000007cf63350 rdi:0000000000000018  r8:000000007cf661f0  r9:0000000000000000 r10:000000000b1bdc80
 r11:00007fdc5cf1ef10 r12:00007fdc807eace0 r13:0000000000000000 r14:00000000189fb080 r15:0000000003869da0
Stack dump:
0x000000000022e330:  000000007cf661f0 0000000003869da0
0x000000000022e340:  000000001941f480 000000001941f480
0x000000000022e350:  0000000000000000 0000000000000001
0x000000000022e360:  000000000022e510 000000000022e550
0x000000000022e370:  0000000000000091 00000000198fdbc0
0x000000000022e380:  0000000000000000 000000000b1bdc80
0x000000000022e390:  000000000022e480 0000000000000000
0x000000000022e3a0:  0000000000000000 00007fdc5cf1efb7
0x000000000022e3b0:  00000000189fb080 4000aed1469058a8
0x000000000022e3c0:  0000000000000000 0000000000000000
0x000000000022e3d0:  0000000000000000 69746c697562203a
0x000000000022e3e0:  202c702528000a6e 0000000000000000
=>0 0x00007fdc5ce6f6e0 ivrrendermodels_load_into_texture_d3d11_async+0xb0() in vrclient_x64 (0x0000000000000005)
0x00007fdc5ce6f6e0 ivrrendermodels_load_into_texture_d3d11_async+0xb0 in vrclient_x64: movq    (%rbx),%rax

The issue lies in vrclient_x64.dll.so. After replacing the vrclient_x64.dll.so from Proton 4.11-11 with the one from Proton 3.7-8 the game runs without crashing after the company logo.

Reproduction

Crashing:
1. Start Dance Collider using Proton 3.16-9, 4.2-9, or 4.11-11
2. The game will crash shortly after the company logo has been displayed

Somewhat working with proton 3.7:
1. Start Dance Collider using Proton 3.7-8
2. The game will launch an be playable, but the enemy models will not load and the animations on the NPC's in the main menues will be missing

~~Working with Proton 4.11 + vrclient_x64.dll.so from proton 3.7:
1. Replace dist/lib64/wine/vrclient_x64.dll.so in Proton 4.11-11 with dist/lib64/wine/vrclient_x64.dll.so from Proton 3.7-8
2. The games seems to run perfectly fine like this

A step by step guide on how to pack a Dance Colldier specific proton without affecting other games is here:
https://gist.github.com/Matombo/fdd1c2164c72533a84492d1e54b9e5d9

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing issue #3392 and reproducing Dance Collider with the Proton versions listed in the report. The report says the game works with Proton 4.11-12 and provides no current failing test, named file, or unresolved change; confirm whether any compatibility problem remains before defining done.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.