Open NoXPhasma opened 5 years ago
This game would benefit from Media Foundation support maturing (fixme:mfplat:MFStartup (131184, 0): stub
).
Does this game have any issues playing cut-scenes/cinematics? It's not clear from the issue report.
If there are any cutscenes, then it won't be played. But I never had the impression that I missed something. However, the game probably won't have mfplat implemented if not needed, so there might some.
the mouse feels different in games
Issue transferred from https://github.com/ValveSoftware/Proton/issues/3769. @chorriwuarri posted on 2020-04-15T13:02:20:
hello, everyone
The first thing is to apologize for my English. I'll try to explain as best I can.
I would like to ask for your help. Can someone with dual boot with windows try to install the game aim lab in steam? the game is free
the idea is that you configure the game exactly the same on windows and linux, to test the mouse behavior, you can configure any task to 10 min, i suggest you try with motioshot and try on both OS
I have the feeling that in linux the mouse is more nerdy, however if I make a 360º turn, the mouse travels the same distance on the table
but if I play in linux 10 min when I play in windows I have the feeling that the mouse is heavier, but it can't be a problem of sensitivity because the mouse travels the same distance on the table
Would that mean there's some kind of acceleration in linux?
my mouse is g502 and my profile is flat
xinput list-props {1..50} 2>/dev/null | fgrep 'libinput Accel Profile Enabled ('
libinput Accel Profile Enabled (301): 0, 1
@kisak-valve Why did you close it? using aim lab was just an example, it happens with other games I also have wine-tkg + proton-raw-input patch and overwatch
I can't Alt-Tab out of Aim Lab and come back. It doesn't render any more, just a black screen. Have to force quit. Proton 6.3-6 .
The update released on 2021-10-11 broken Aim Lab under Proton (6.3-7). Only shows a black screen, with music/audio. Unplayable; can only Alt-F4.
The game is currently playable, but there are issues when changing visual settings. Most will not save, and the ones that do don't seem to be applying correctly.
The game is currently playable, but there are issues when changing visual settings. Most will not save, and the ones that do don't seem to be applying correctly.
The problem still persist.
The games Graphics menu settings doesn't show any resolutions other than 1920x1080 and shows the refresh rate as 1920x1080. Clicking the arrows freezes the game for about 15 seconds.
I play on 2560x1440 @ 240Hz which the game appears to be running at, Regardless of what the menu shows.
As others said, Visual settings don't apply because the game seems to not write the changes to the config file, changing other settings like Crosshair and Audio will write to config file normally.
Also changing any keybindings, doesn't write to the config file either. They lost when you quit.
Config location: ~/.local/share/Steam/steamapps/compatdata/714010/pfx/drive_c/users/steamuser/AppData/LocalLow/Statespace/aimlab_tb/WindowsPlayer_PlayerSettingsData.json
Proton 8.0-4 Log. The game is a black screen on Experimental.
Whitelist Request
System Information
steam-714010.log
I confirm:
Play
button in the Steam client is sufficient.Issues
Works fine out of the box, but crashes/freezes on exit and needs to be killed manually. You need to actually play a shoot-out, otherwise it won't crash on exit, most of the time. Launches the Unity crash handler in background on exit.