Open rafaelsantos20 opened 6 years ago
Can confirm that I also don't have a steam overlay. The performance is ok, but I think I have some input lag sometimes which makes the game unplayble.
OS: Ubuntu 18.04.01 CPU: I5-4460 GPU: RX 580 DRIVER: Mesa 18.3.0
Game is totally unplayable and I don't have the Steam Overlay OS : Uubuntu 18.04 CPU: AMD Ryzen 5 1600X GPU: Nvidia Geforce 1050 Ti 3GB Driver Version: Nvidia Driver 396
Brawlhalla
Issue transferred from https://github.com/ValveSoftware/Proton/issues/470. @DarkArc posted on 2018-08-25T01:19:59:
Brawlhalla works well, with the exception of one issue. You have to put it into windowed mode, and not resize it, otherwise the game area won't render.
For instance with default full screen gameplay, you'll see nothing but a black screen. If you change to windowed mode, restart the game, and then play, everything will render/work properly.
my game opens fine in fullscreen mode but I still have really bad performance and input lag. (This goes for fullscreen and windowed mode. Maybe proton could be modified to work better with adobe air games?
It works ok to me. In Full Screen. No input lag* or slowdowns. System info
Hum... Steam overlay also doesn't work for me, but I think in all games I've tested it didn't work, so I didn't report it since I thought it was another problem. '-'
Maybe I should report it to the other games too.
@rafaeldoge2512 Maybe it would help if you post here the script for lutris (?)
*Edit: That was my first time playing it. Actually after further analysis it seems I indeed get input lag while playing with the mouse (it keeps attacking in one direction after I stopped doing so, but this does not happen consistently). I played several minutes with just the keyboard and strangely it doesn't seem to happen.
Any update @ValveSoftware
I've noticed that the game ran much better with Wine Staging, probably something that is going to be upstreamed soon.
Can confirm, I don't know since when because I tried it several months ago and it was laggy but testing it today with wine-staging 2.21 and it is smooth as windows.
Can confirm, I don't know since when because I tried it several months ago and it was laggy but testing it today with wine-staging 2.21 and it is smooth as windows.
So, does anyone have a good guess about when we could get this in the latest Proton beta?
Hello @jvschiavo, it would be good to know exactly what patches improve the game. Once you've isolated the patch set that matters, you could open a pull request to add them to the wine build used with Proton, but for the most part it's better to get the fixes merged into vanilla wine.
Steam Controller is annoying to configure as a result of not having the overlay:
BigPicture/BaseConfigurations/DesktopConfiguration
(As keyboard/mouse by default)Library/Brawlhalla/ManageGame/ControllerConfiguration
The game doesn't seem to work with my ds4, both wired and over bluetooth. I'm on proton 4.2-4.
Using Proton 4.2-7, this still faces major frame drops and input lag. This is (apparently) due to Proton not utilizing the Hardware Acceleration included in Brawlhalla. It is an Adobe Air game and therefore has a few different backend mechanics to most game. The game works perfectly through Lutris, and should therefore not be too hard to fix hypothetically.
I have the same issue on Proton 5.0-3, if I load Brawlhalla in fullscreen it'll black screen only (regardless if overlay is enabled or not), but if I force windowed mode it'll render the game but it'll be flickering.
Brawlhalla (291550) exits on startup
Issue transferred from https://github.com/ValveSoftware/Proton/issues/4630. @Kreyren posted on 2021-02-17T10:30:32:
Game exits on startup
PROTON_USE_WINED3D=1
to exclude https://github.com/ValveSoftware/Proton/issues/4629 and expect failure@ivyl With Proton 6.3-2 on Gnome Wayland, four Steam Controllers, and an Xbox One controller, the fifth controller is not recognized by Brawlhalla even at the main menu. This seems to occur for all my other Windows games that claim to support eight players as well (e.g. Cobalt). I confirm all five controllers can navigate BPM before launching the game, because sometimes Steam just loses track of Steam Controllers and they drop into lizard mode or something.
@ivyl With Proton 6.3-2 on Gnome Wayland, four Steam Controllers, and an Xbox One controller, the fifth controller is not recognized by Brawlhalla even at the main menu. This seems to occur for all my other Windows games that claim to support eight players as well (e.g. Cobalt). I confirm all five controllers can navigate BPM before launching the game, because sometimes Steam just loses track of Steam Controllers and they drop into lizard mode or something.
Could you test this on previous versions of Proton to see if the problem still happens?
Really bad teleporting
Issue transferred from https://github.com/ValveSoftware/Proton/issues/4758. @YeetBucket245 posted on 2021-04-16T13:38:01:
Brawlhalla is teleporting a lot for me. My internet is fine but some people are in 5 places at the same time
Really bad teleporting
Issue transferred from #4758. @YeetBucket245 posted on 2021-04-16T13:38:01:
Brawlhalla is teleporting a lot for me. My internet is fine but some people are in 5 places at the same time
FWIW based on my experience that's bcs of the internet connection or game not having stable frametimes.
@ivyl With Proton 6.3-2 on Gnome Wayland, four Steam Controllers, and an Xbox One controller, the fifth controller is not recognized by Brawlhalla even at the main menu. This seems to occur for all my other Windows games that claim to support eight players as well (e.g. Cobalt). I confirm all five controllers can navigate BPM before launching the game, because sometimes Steam just loses track of Steam Controllers and they drop into lizard mode or something.
I've briefly checked this on Windows. As far as I can tell Brawhalla uses xinput for the supported devices, which is limited to 4 controllers. It doesn't use dinput/HID for the extra ones like some other games do. So the only option to have more than 4 players is to use keyboard or non-xinput (e.g. Sony) controllers without mapping if those are supported by the game.
Brawlhalla not working through proton, but works fine when using wine, any idea how to solve this, the game instantly crashes, here's my log =
Hello @atreyaved, these look like the relevant lines from your log:
warn:seh:dispatch_exception EXCEPTION_ILLEGAL_INSTRUCTION exception (code=c000001d) raised
wine: Unhandled illegal instruction at address 0000000140002D99 (thread 002c), starting debugger...
This usually tells us that Proton or the game is trying to use a CPU command that your hardware doesn't support. In your case it's fairly early too, and I wouldn't be surprised if you have the same issue when using Proton with other games.
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.
@kisak-valve here's my system information (it's pretty terrible) https://gist.github.com/atreyaved/354d8d2b26b7715b34ff96081385233b btw. brawlhalla works flawless on windows
It crashes on rdtscp
instruction in wineboot.exe. The processor is too old and doesn't support it.
Can you try with Proton 6.3-6? Right now you are on experimental which includes some... experimental work on QueryPerformanceCounter()
backed by rdtscp
.
@ivyl same problem occurs with 6.3-6
@atreyaved Can you share logs for the crash with 6.3-7? I think this may be a different problem, as we don't use rdtscp
there as far as I can tell. The -7 released just few hours ago, but it should not make any difference vs -6.
And yes, we are working on making sure that the usage of rdtscp
will be guarded correctly based on CPU features in Experimental :-)
@ivyl here ya go - https://gist.github.com/atreyaved/0a4be3520ab1c1fe1e5a48fecfcddcf2
Hello @atreyaved, your Proton log shows us that you're still testing with Proton Experimental. Please retest with Proton 6.3.
@kisak-valve its set to 6.3-7 on steam play, i even double checked
Your log disagrees, you can check what version Steam is configured to use by going to the game in Steam's library view, then clicking the ⓘ on the right side. In the additional information, it should have a line that reads "Runs on this computer via Steam Play. Proton Experimental selected by you for this title." I'm guessing that you've configured the game to use Proton Experimental using the per-game override in the game's properties, but then double checked the global Steam Play settings.
@kisak-valve would u be able to contact me on discord? Atreyaved#2561
I was able to solve the problem by switching back to experimental, still confused how that worked out
@atreyaved I'm also not sure how you fixed the problem. The bug where older CPUs were triggering a failure has been fixed with the most recent experimental release (experimental-6.3-20211011b) so you shouldn't run into this anymore :)
@alasky17 it works just fine with the latest experimental release, thanks!
Eac proton / steam's overlay
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5286. @hydrasho posted on 2021-11-05T09:37:27:
Hello I tried brawlhalla with these two options: -noeac and without it
The game works well with both options.
however the steam overlay no longer works when eac is activated, and neither do the joysticks! I saw other report of this one on protonDb and on other computer.
DualShock 4 don't work with the game when using Proton 6.3-7. And EAC only work with this version.
Hi @Francehelder
DualShock 4 works for me just fine with Proton 6.3-7. I've tried both wired and bluetooth modes.
Can you start the game with PROTON_LOG=1 WINEDEBUG=+pid,+tid,+dinput,+hid,+plugplay %command%
on 6.3-7 and Experimental and attach both logs?
Hi @ivyl. I'm using DS4 on bluetooth mode.
@Francehelder thanks for the logs. There were enough to give me some clue about what's going on.
Looks like you are using Steam Input. On Linux it creates a virtual input device using uinput. As far as I understand it's Steam Overlay's responsibility to actually feed the uinput device with the mapped events. On Linux that's achieved by preloading an .so
and having gameoverlayui
process running. Not sure which part is exactly responsible for this.
I've check and as I launch the game I actually get events from the virtual controller but as it progresses with loading (and presumably EAC kicks in) they just abruptly stop. I don't think we can do much about it on the Proton/Wine side as those are native Linux parts of Steam. I believe it's up to EAC and Steam developers to solve this. @kisak-valve may be able to help with that.
In the meantime you can disable Steam Input and the controller should work. You can do that on per-game basis in Game's Properties -> Controller -> Override for Brawlhalla.
I disabled Steam input and it works. Thanks @ivyl.
I disabled Steam input and it works. Thanks @ivyl.
Note that it does not work with Steam Controller. I think that Steam controller need the Overlay to map input.
I am trying to use two (or more) Dualshock 4 controllers, but connecting more than one at a time makes the game unplayable. In such case, input is only detected from a single controller, with additional "ghost" inputs equal to the number of additional controllers plugged in.
So, if I have two controllers connected — one controller doesn't do anything, but pressing a button on the second controller registers that input twice. If I have three controllers — two controllers do not do anything, but pressing a button on the last controller will register that input three times.
Adding -noeac
, -multikeyboard
or changing Proton version does not help. Works fine with a single controller.
System information: https://gist.github.com/valters-tomsons/2d3fb4baa28505db719149116b609031 Log: steam-291550.log
Edit: Seems like a game bug, also happens on Windows 11.
Brawlhalla not starting. Blackscreen on startup, crashes after ~10 seconds.
Issue transferred from https://github.com/ValveSoftware/Proton/issues/5418. @ArcSpammer posted on 2021-12-17T22:20:12:
I tried a couple different fixes/workarounds such as:
Error I got on proton log (on the last line): "pid 18728 != 18727, skipping destrruction (fork without exec?)"
System information:
Using proton with steam (native), I don't know what else to try. I am an archlinux noob btw.
this issue is also affecting brawhalla
glibc 2.36-2 solved this problem on arch linux.
Replying to kisak-valve's comment (which was transferred from #5418)
I've had exactly the same issue, and actually have fairly similar specifications (running an Acer Nitro 5 AN515-52 laptop, with GTX 1050 and Intel UHD Graphics 630), though besides the desktop environment and other differences.
Allow me to explain myself how I found out the solution and what's about it:
Anyways, while I was looking for solutions (incl. that I found myself trying all solutions of yours), seeing that in ProtonDB – most people were reporting the game ran rather flawlessly, I tried to run other games, and I found out that Proton wasn't using the NVIDIA GPU (at least in Bloons TD 6).
I found one comment in Reddit that implied that the cause may have been the fact that because gaming laptops currently use NVIDIA Optimus (in ArchWiki) to use both the discrete and integrated GPUs on a laptop, the way to switch to NVIDIA only is through PRIME offloading (id.), which is actually the preferred/official way to do so (see id.).
Now, here's the actual solution — at least for me though:
As I am using NVIDIA's proprietary drivers (since they're actually faster than like nouveau), the solution takes place by using prime-run, which can be downloaded from the nvidia-prime package (see).
In a nutshell:
You may need to run prime-run steam
or set prime run %command%
globally inside Steam settings if you want every game to just use the NVIDIA GPU; otherwise, you can set prime-run per game (see this also) — only if you have the propietary drivers (i.e. the nvidia package).
This is because PRIME isn't enabled automatically (see), even though some games/programs or Proton itself may enable the use of the GPU readily (also this comment).
This solution worked at least for me; I cannot guarantee it does for you (or any other with the same issue), but I am hopeful it does ~(if it does for anyone)~
Anyways, it's rather weird that it doesn't launch correctly without the GPU enabled, and it does when PRIME is; I would rather let this issue as "Here be dragons", even though I tried to debug it and actually just found the logs (i.e. unknown exception) I was looking into was likely a Windows-native bug (which I could report to Wine directly, but will see) — in any case, I will still leave the logs of the game loaded both with/without EAC enabled, just in case someone is curious.
Here the logs, and how they were logged:
PROTON_LOG=1 WINEDEBUG="+timestamp,+pid,+tid,+seh,+debugstr,+module,+relay" %command% -noeac
:
(WINEDEBUG based on this, and this) Google Drive
(this file is monstrous, 900k lines, and weighs about 80MB, beware!) ~(plus I hate Google, and I found no other "easy" way)~.
PROTON_LOG=1
: Gist
By the way, similar issues have been reported for other games, such as for PICO Park, and maybe others (~which I cannot find and lost links of~); though the causes and solutions were fairly different.
- OS: Arch Linux x86_64
- Model: Acer Nitro 5 AN515-52
- Kernel: 5.19.8-zen1-1-zen
- Window Manager: Hyprland (uses Wayland)
- CPU: Intel i5-8300H
- Integrated GPU: Intel CoffeeLake-H GT2 [UHD Graphics 630]
- Discrete GPU: NVIDIA GeForce GTX 1050 Mobile
Just in case anyone is curious, if you look the logs or some.
this issue is also affecting brawhalla
glibc 2.36-2 solved this problem on arch linux.
how do you solve it on fedora???
this issue is also affecting brawhalla
glibc 2.36-2 solved this problem on arch linux.
how do you solve it on fedora???
@Radical4ever i don't use fedora, the only thing i found out about on how to solve this on fedora was this post on reddit
this issue is also affecting brawhalla
glibc 2.36-2 solved this problem on arch linux.
how do you solve it on fedora???
@Radical4ever i don't use fedora, the only thing i found out about on how to solve this on fedora was this post on reddit
is not going to work its using an old version of glibc and the author of the patched app put it as deprecated
Hello, in my brothers PC (Artix Linux) Proton suddenly doesn't work. On launching the game without -noeac no window appears and game simply closes, with -noeac option it just shows a black window then closes. I tried GE Proton, changing amdvlk to vulkan-radeon, deleting compatdata folder, verifying game, and updating system
Edit: It was lib32-amdvlk and amdvlk fault, changed to vulkan-radeon and works
Tried to run brawlhalla, altough it runs, it doesn't have the steam overlay neither the fps counter, it also has overall bad perfomance compared to the esync build of Lutris.
OS: Arch Linux rolling DE: KDE CPU: Intel Core i3-2100 (Sandy Bridge) GPU: Intel HD Graphics 2000 Driver Version: Mesa 18.1.6 Steam Runtime disabled