Closed Supreeeme closed 4 years ago
Hello @YungDaVinci, please add PROTON_LOG=1 %command%
to the game's launch options, reproduce the regression, and drag and drop the generated $HOME/steam-$APPID.log into the comment box.
Ah sorry, forgot granblue-5.0.log
Thought it would be worth noting that online functionality works using vanilla Wine 5.4 + DXVK but not using GloriousEggroll's custom Proton 5.4 build.
Fixed in 5.0-5.
Compatibility Issue
Name of the game with compatibility issues: Granblue Fantasy: Versus
Steam AppID of the game: 1090630
System Information
GPU:1080 TI
Driver/LLVM version: nvidia 465
Kernel version: 5.10
Proton version: 7.0
Controller: custom hit-box using Universal Fight board
Issue, When using a Universal fight board controller, I cannot set the controls in game while steam input is disabled. Changing the controls with my ps4 fight stick works fine.
Reproduce Disable steam input Start up the game using Proton 7 using a controller that has a Universal fight board Go to the system settings Try to change your controls in the controller settings
Game locks up / becomes unresponsive when viewing the command list. Also has gotten stuck on the loading screen after exiting training, however I have not reproduced it.
Hi @Supreeeme, I've tagged you here in case you are no longer following this issue. This issue tracker maintains one issue per unofficial game, so I believe that other compatibility reports/feedback as above would go here, but they may be overlooked if this issue is closed. Could you please re-open this issue when you get a chance? Thank you.
Hello @kibivolt, if there's no open compatibility report for a game, then you can go ahead an open a new compatibility report to track the game title.
I've created a new report for the game here. Sorry for the confusion.
Compatibility Report
System Information
I confirm:
Symptoms
Attempting to queue up an online match in Proton 5.0-4 results in the game instantly removing you from the queue and saying connection was lost. This problem is not present in 4.11-13. ProtonDB reports suggest it works without any extra configuration on other systems. Problem is present in both native runtime and the packaged runtime.
Reproduction