Open taisph opened 4 years ago
Hello @taisph, looks like this game would benefit from support for Media Foundation maturing.
I've been able to get around the black screen by disabling the splash screens by editing the ~/.steam/steamapps/common/Hardspace Shipbreaker/config.ini
and setting SkipSplashScreen=true
. This allowed the game to continue to the "employee signup process" after which it stalled again on a blank white screen. Quitting (Alt+F4) and starting the game again allowed me to proceed and actually play the game - which so far runs great without any noticeable issues. ~35 FPS at 2560x1440 on GTX 1070.
With MF (through proton-ge) the game works well, but alt-tabbing in any way stops the game from reacting to keyboard input until I restart, for me.
Besides an intro video black screen which you can click through, the game runs fine (from what I can tell) with Proton Experimental.
I do get hangs/lockups anywhere from 30min-2hrs playing but these seem to be related to the AMDGPU driver or this game specifically + AMDGPU as I don't see these crashes with any other games.
Hello @hlarsen, please copy your system information from Steam (Steam
-> Help
-> System Information
) and put it in a gist, then include a link to the gist in this issue report.
The game runs for me using Proton: Experimental and no tweaks - but even on minimum settings it runs at <10 FPS. I have a Ryzen 1700 and GT 1060 3GB - VRAM is entirely full. Any performance tips?
Tested on a Steam Deck on Proton Experimental and ran at ~30-40 fps while playing. Text is too small in some spots at default settings, and the graphics settings have to be turned down for better performance.
Runs mostly fine with Ryzen 1700X and Vega 64 on Fedora 35 with Proton: Experimental on a 4K screen will 1080p resolution. Two issues:
Hello @mordae, can you check if setting the game's launch options to WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%
has an effect on the video corruption?
Hello @mordae, can you check if setting the game's launch options to
WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%
has an effect on the video corruption?
It has fixed the issue.
Also, the font blurriness has probably something to do with your new upscaling method, because WINE_FULLSCREEN_FSR_STRENGTH=2
helps a bunch (still a little blurry, but readable).
@mordae Your comment about the font blurriness being related to the new upscaling method indicates that there are older proton versions that do not have blurry font by default... do you know any proton version that does not have the font blur to compare against 7.0, and if so, what version(s)?
@alasky17: The game only launched with Experimental for me. Sorry for speculating.
@mordae No worries, you may well be right :) It is just harder to investigate without a previous working version. Could you upload some screenshots so I know what to look for with the font blurriness?
Hardspace Shipbreaker (1161580)
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5883. @maddoodles posted on 2022-06-04T00:18:49:
Proton Log: steam-1161580.log
Online Play: try to connect view Leaderboards or current RACE ship.
This is due to the use of SOCK_RAW sockets when attempting to communicate with their servers.
Online Play: try to connect view Leaderboards or current RACE ship.
This is due to the use of SOCK_RAW sockets when attempting to communicate with their servers.
Is there anything that can be done on the user end to fix this at all?
You need to give wineserver permission to use raw sockets
sudo /sbin/setcap -v cap_net_raw,cap_net_admin=eip wineserver
NOTES:
Depending on you Distro, this might need to be done as well. Allow ICMP privileges
Thank you, I, unfortunately, am not sure what I need to do to get it working correctly. I assume I need to get it pointing to the correct proton version, as running it as is just gives me:
wineserver differs in [pie]
I'll fully admit to having very little clue what most of this means to be honest, I'm just following instructions.
(Googling the above message gives me nothing useful, and the code in your post gets me literally zero results so I can't even try and muddle this out myself lol)
Sorry, copy paste error. The -v should not be there.
sudo /sbin/setcap cap_net_raw,cap_net_admin=eip wineserver
I've run that in the relevant Proton folders where the wineserver file is, unfortunately it has not fixed the issue
On Archlinux pointing to Proton 7.0:
sudo /sbin/setcap cap_net_raw,cap_net_admin=eip ~"/.local/share/Steam/steamapps/common/Proton 7.0/dist/bin/wineserver"
Does not seem to make the change as the caps are switched anyway
getcap ~"/.local/share/Steam/steamapps/common/Proton 7.0/dist/bin/wineserver"
~/.local/share/Steam/steamapps/common/Proton 7.0/dist/bin/wineserver cap_net_admin,cap_net_raw=eip
See? We want $eip to be assigned to cap_net_admin:
cap_net_raw,cap_net_admin=eip
but $eip remains assigned to cap_net_raw
cap_net_admin,cap_net_raw=eip
ipv4 ping range is ok:
net.ipv4.ping_group_range = 0 2147483647
I'm sure I'm running Hardspace with this wineserver, simple check with 'ps -ef | grep wineserver' when it's running. Does not fix the leaderboards/race issue.
EDIT: I probably misunderstood how getcap command shows the data, it seems to be set correctly. However this changes nothing, I am not sure if the issue is related to SOCK_RAW socket.
Symptoms
- Cutscenes after the intro cutscene starting a new Career Mode game skip
Reproduction
- Cutscenes: get to a point where a cutscene beyond the first plays (End of Act 3 or Epilogue)
@maddoodles We added h264 support for this game which I'm hoping will fix this. Could you see if you can still reproduce this problem? I don't have a saved game that far in ...
@alasky17 Yup, I can confirm that cutscenes appear to work now. :)
Do we know if we're any closer to online play working? I realise a potential fix was posted above but I have no idea what I'm doing with that so I'm hoping a fix on Proton's end is coming. :sweat_smile:
@maddoodles This bug is currently in progress but I do not have a specific ETA. When it does get fixed, it will be in the experimental changelog :)
@maddoodles The experimental release today should fix the online play/server connection failure :)
@alasky17 Outstanding, I'll give it a test ASAP. You folks are doing amazing work! EDIT: That does indeed appear to be working!
@alasky17 can confirm, thanks. Cutter's R.A.C.E. view and submits results works as well as Leaderboards.
Besides the not-perfect performance, due to probably unoptimized UnityEngine, that should be all issues fixed.
The game locks up, audio continues playing for several seconds and a crash dump upload screen is displayed, followed by the game exiting back to Steam.
Attempt to use the Grapple tool on any object.
Note: I also found a report of this issue on the Steam forums here.
I can confirm the above issue with freezing when using the grapple tool (same for tether I guess). With GE_Proton7_24 (installed via protonup) I can access the leaderboards and Cutter's race and in Free Run the game worked fine, but when I attempted Cutter's race at the first instance of the effect the game crashed. Probably the same for the career mode as well.
I also have the above issue on Steam deck using Proton Experimental. Currently playing using Proton 6.3-8, however I can‘t access online features with that build.
Update: I just noticed that Proton 7.0-4 was released, this fixed both the crashes as well as Cutter‘s R.A.C.E!
Symptoms
The game locks up, audio continues playing for several seconds and a crash dump upload screen is displayed, followed by the game exiting back to Steam.
Reproduction
Attempt to use the Grapple tool on any object.
@rileyinman Is this also fixed for you with 7.0-4? If not, could you also try current proton experimental and make sure it is still crashing?
@alasky17 I can confirm 7.0-4 fixes the issue for me, thank you! It seems one of the users who reported the same problem on the Steam community forums is still having issues (https://steamcommunity.com/app/1161580/discussions/0/3458220484829484365/#c3439081454522835743), but I'm not sure how their setup may differ from mine.
@rileyinman Thank you for the heads up about the community forum post. I was able to reproduce that failure and file a bug :)
Hardspace: Shipbreaker - tutorial overlay stuck on screen
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6170. @bitcharmer posted on 2022-09-19T08:18:56:
The tutorial overlay with key bindings stuck on screen. During training/tutorial shifts the game displays helpful information in an overlay in bottom left part of the screen. Unfortunately this overlay remains persistent across shifts and ships. I first encountered this very early into the game. Back then it was some key binding info for flashlight, etc. I "worked around" it by starting a new career and unchecking tutorial. However after purchasing demo charges upgrade and going into the next shift the ">> Demo charge manual" overlay appears and stays persistent as described above.
Start a new career with tutorials enabled, get to the point with keyboard hints for flashlight OR Start a game with tutorials disables and get to the point where demo charges are available. The overlay will stay on screen and won't disappear.
Hardspace Shipbreakers works but with 4+ min loading time
Issue transferred from https://github.com/ValveSoftware/Proton/issues/6182. @matthewv1998 posted on 2022-09-23T19:57:58:
Steam Deck OS VER: 3.3.1 Os Build 20220817.1 Kernal ver: 5.13.0-valve21.1-1-neptune-02211-gc54cda5a36f3
shipbreakers works, however it has a Excessive load time to get into the menu, between 3 ane 4 minutes before the main menu works.
simply just launch the game, and wait.
I'm experiencing the very long 4+ min load time as well on Experimental, 7.0-4, and 6.3-8.
Additionally, I'll mention I'm still getting the immediate crash when using the grapple on Experimental and 7.0-4. Game seems to work pretty well on 6.3-8, aside from the very long load times. (It's installed to the internal 512GB drive.)
Hello @naim, please add PROTON_LOG=1 %command%
to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam
-> Help
-> System Information
) and put it in a gist, then include a link to the gist in this issue report.
Sure thing — thanks for the response and directions. Here's the Proton log. This was done without forcing any particular Proton version, so I'm guessing it was using 7.0-4. Crash happened as expected when I went to use the grapple after loading into a level.
Here's the system information report from my Steam Deck: https://gist.github.com/naim/66b7471dccf59310f8a1eabf6544ab0d
@naim You are still getting the crash because it hasn't been fixed yet. Someone already took a look and it is not a simple bug to fix - unfortunately I can't give you an accurate timeline on when it will be fixed. When it is fixed, it will likely show up as a line in the changelog and I will try to update here as well :)
Sounds good. No rush at all — it's playable with 6.3-8 and I know how complex some of these fixes can be. I had read some conflicting reports from folks online saying it was working for them, so I wanted to report.
Appreciate the quick response!
Have there been any fixes for this game since last year or did the devs took "no rush at all" to heart? :)
@bitcharmer I believe that the grapple freeze is no longer happening. Please let me know if you still see the failure when using the grapple.
I've been experiencing this issue for over a year. Is there a specific fix ?
I've been experiencing this issue for over a year. Is there a specific fix ?
Are you talking about the shader compilation short freeze? When using grapple in a mission for the first time?
@ohheysean I was no longer able to reproduce starting with Proton 7.0-x. There was no specific fix so I figured that general updates either on the game side or Proton side fixed it. Could you be more specific about which issue you are talking about and where you are seeing it? Could you also please copy your system information from Steam (Steam -> Help -> System Information and Steam -> Help -> Steam Runtime Diagnostics) and put each in a gist, then include a link to the gists in this issue report.
Compatibility Report
System Information
GPU: GeForce GTX 1070
Driver/LLVM version: nvidia 440.82
Kernel version: 5.3.0-59-generic #53~18.04.1-Ubuntu SMP Thu Jun 4 14:58:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Link to full system information report as Gist: https://gist.github.com/taisph/8b0d2b952a62ea87ab6d25e1a1129259
Proton version: 5.0-9
I confirm:
steam-1161580.log
Symptoms
Runs showing the copyright screen and photosensitivity warning, ends up on a black screen with a yellow triangle mouse pointer. Sound is playing but nothing else happens. Alt+F4 quits the game.
Reproduction
Run the game.