Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Child of Light (256290) #2463

Open
Cxpher opened this issue Mar 27, 2019 · 14 comments
Open

Child of Light (256290) #2463

Cxpher opened this issue Mar 27, 2019 · 14 comments
Labels
DXVK/D3D9 🐸 Regression from enabling DXVK/D3D9 by default Game compatibility - Unofficial Games not expected to work without issues XAudio2 Uses the XAudio2 subsystem

Comments

@Cxpher
Copy link

Cxpher commented Mar 27, 2019

Steam App ID :
256290

Description of issue :
When launching with Proton, Uplay becomes a zombie process and the game is stuck indefinitely without starting.

Have to find the zombie process and kill it or force kill it by restarting Steam.

System Information :
CPU: i7-3770k
GPU: GTX 670 FTW
Driver/LLVM version: NVIDIA 418.56
Distro version: Arch Linux
Proton version: 4.2-1

@kisak-valve kisak-valve added the Game compatibility - Unofficial Games not expected to work without issues label Mar 27, 2019
@kisak-valve kisak-valve changed the title Child of Light Child of Light (256290) Mar 27, 2019
@kisak-valve
Copy link
Member

Hello @Cxpher, please disable uplay's overlay, then add PROTON_LOG=1 %command% to the game's launch options and drag and drop the generated $HOME/steam-$APPID.log into the comment box.

@Cxpher
Copy link
Author

Cxpher commented Mar 28, 2019 via email

@Cxpher
Copy link
Author

Cxpher commented Mar 28, 2019

I need to kill upc.exe and then the zombie process comes to live and starts the game.

However..

Three minor issues:

1: I can't get rid of the box in the upper right corner "Press Shift+F2 while in game to activate the overlay" while in game. Can't disable the Uplay overlay unless anyone has a better way? The Uplay client on the desktop via wine won't respond to any clicks

2: There is a black square appearing at the center of the screen at the beginning of each fight which fades away quickly. So it doesn't interfere with the gameplay

@omicron-b
Copy link

omicron-b commented Mar 28, 2019

CPU: AMD Ryzen 5 2600x
GPU: Nvidia GTX 1060 6G
Driver/LLVM version: NVIDIA 418.56
Distro version: Ubuntu 18.04
Proton version: 4.2-1
System info: Gist

Uplay works fine for me, I right clicked in that window
Screenshot from 2019-03-28 08-40-10
went to settings and disabled Uplay overlay and as much other options as possible, like notifications, friends, etc. except Cloud saves. So, no Uplay box on my screen.

Game also works fine so far, including Steam controller, with the exception of same black square as @Cxpher reported

Attached is log with black square
steam-256290.log

@Cxpher
Copy link
Author

Cxpher commented Mar 28, 2019 via email

@kisak-valve kisak-valve added the XAudio2 Uses the XAudio2 subsystem label Mar 28, 2019
@ApollonWrock
Copy link

No such window shows up on my end.
Game prepares for start for a while but closes eventually.
steam-256290.log

@Cxpher
Copy link
Author

Cxpher commented Mar 29, 2019 via email

@zzhiyi
Copy link
Contributor

zzhiyi commented Mar 29, 2019

Uplay update, the following commits are need to get uplay working again. Should be fix by next proton update.
https://source.winehq.org/git/wine.git/commitdiff/df3dd6612c2098e347cad88c90853cf3892e4301
https://source.winehq.org/git/wine.git/commitdiff/d2d52717af2a64196d9bc983ba8b75e64c05c3f8

@ApollonWrock
Copy link

I actually changed versions and verified cache (some random actions)

For some reason it seems to work now. Uplay does show up correctly, I can log in, the games show up and I can play :)
Ubuntu 18, proton 4.2-1

@Cxpher
Copy link
Author

Cxpher commented Apr 22, 2019

Disabling uplay overlay works.

Only thing left now is that black box.

@Cxpher
Copy link
Author

Cxpher commented Jun 16, 2019

Black box still appears at the beginning of fights in 4.2-7. Should i open another bug report for that?

@omicron-b
Copy link

@Cxpher no, the policy is 1 report per non officially supported game

@Yar4e
Copy link

Yar4e commented Jul 7, 2019

Uplay don't becomes a zombie process for me and i don't saw any black boxes at beginning of fights, but i have a little bit crackling sound ingame and fps drops.
steam-256290.log.zip
steam_sys_info.txt

@FurretUber
Copy link

FurretUber commented May 1, 2020

Comparing D9VK with Wine D3D9, I noticed that D9VK uses much less CPU resources: htop shows 200% CPU usage with Wine D3D9 and 140% with D9VK. Framerate with D9VK is generally 45 FPS, can reach 60 sometimes. With Wine D3D9, framerate is around 30, on very rare occasions reaches 50. I wonder what is the CPU load and frame rate when playing on Windows.

There is one difference I found: Aurora is different using D9VK, as if a different filter is being used. As Aurora's model is the only 3D model, it seems this difference is exclusive to Aurora. Enemies are the same, the backgrounds are the same: at least I couldn't find any any differences. The following images are cropped to make the comparison.

Wine D3D9:

image

D9VK:

image

About UPlay, after setting to save the log in credentials, it opens the game directly, working as intended.

System specifications: https://gist.github.com/FurretUber/5b15c8267a44a85547317c95553a3b90

Edit: I did some tests on Windows. I stopped in one place where I noticed Child of Light was running at 60 FPS with very high GPU load (94% was the minimum observed) and around 25% CPU load (the equivalent for htop 100%, considering this is a four threads processor). It would very rarely go down to 57 FPS, but kept nearly all the time at 60 FPS. That same place on Linux caused a htop 140% CPU load with 100% GPU load and around 45 FPS. I believe this gives a reliable picture of the current performance impact.

There is the advantage that my gamepad works on Linux (including vibration) but doesn't on Windows.

@kisak-valve kisak-valve added the DXVK/D3D9 🐸 Regression from enabling DXVK/D3D9 by default label May 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DXVK/D3D9 🐸 Regression from enabling DXVK/D3D9 by default Game compatibility - Unofficial Games not expected to work without issues XAudio2 Uses the XAudio2 subsystem
Projects
None yet
Development

No branches or pull requests

7 participants