Proton: Lego Star Wars: The Complete Saga (32440)

[Lucky-Lynx]

I tested Lego Star Wars: The Complete Saga and it rang great for the first level, haven't played further. Only issue I came across was that any background music would loop after the first few seconds and not play through cut scenes and in-game.

Tested on Linux Mint 18.3, Kernel 4.4.0-124-generic, Proton 3.7-4 Beta, NVIDIA 396.54, i5 4690, GTX 1080

[Steveice10]

Note that you can avoid this with "PROTON_NO_ESYNC=1"

[Lucky-Lynx]

Can confirm that adding "PROTON_NO_ESYNC=1 %command%" as a Launch Option under Properties for the game in Steam appears to have completely fixed the issue.

[hzulla]

The gamepad isn't detected inside the game on my machine: System info. Meanwhile, Lego Star Wars The Last Jedi on the same machine does detect it.

[wberrier]

About gamepads, under wine this game suffers from this bug: https://bugs.winehq.org/show_bug.cgi?id=42137

I had been meaning to test under proton. But, if it doesn't suffer from the above bug, it sounds like maybe dinput isn't supported with proton?

[kisak-valve]

Lego Star Wars - The Complete Saga

Issue transferred from https://github.com/ValveSoftware/Proton/issues/2033.
@Leon422 posted on 2018-11-25T23:18:07:

Whitelist Request

• Name of the game to be whitelisted: Lego Star Wars - The Complete Saga
• Steam AppID of the game: 32440

System Information

• GPU: GTX 1070
• Driver/LLVM version: Nvidia 410.73
• Kernel version: 4.18
• Link to full system information report as Gist: https://gist.github.com/Leon422/15f1906b04e48ab3d03e6b946e008979
• Proton version: 3.16-4 beta

I confirm:

• [ ] that pressing the Play button in the Steam client is sufficient.
• [X] that runtime config options
  are necessary to run the game. (Disabling esync to fix an audio loop bug)
• [X] that no workarounds other than the mentioned ones are necessary.

Issues

• [X] I haven't experienced any issues.
• [X] There are no issues left open for this game.
• [X] Although I consider the gaming experience equal to Windows there are
  remaining issues:
  The audio loops incorrectly unless you disable esync. But once you do, it's perfect.

Note: I also tested the game on a laptop with a Nvidia 820M and it ran at a locked 60 FPS at 1600x900. Therefore, we can conclude that this game can run on a toaster, even with esync disabled.

[kisak-valve]

Looks like the game controller issue is something to consider a blocker to switching this issue report over to a whitelist request?

[Reonu]

Curious, my wired first-gen Xbox One gamepad worked perfectly. The game picked it up right away. It prompted me to configure it and the bindings showed the Xbox One button icons and everything. What's the issue exactly?

[Lucky-Lynx]

I found I had to change my Controller Settings in Steam (easiest in Big Picture Mode) to turn off "Configuration Support". I'm not in front of my home PC at the moment, but I'm pretty sure that fixed the issue for me on this game and a few others.

[Reonu]

Well yeah, I don't have "Xbox Controller configuration" enabled on Steam Input. I just plugged in the controller normally. Maybe that's why it works for me?

[codeman101]

I'm glad this issue is still open because I disagree that a whitelist request can be made if the game requires environment variable tweaks since you;d have to execute them from the terminal to launch steam every time you want to play that game.

[ritalat]

since you;d have to execute them from the terminal to launch steam every time you want to play that game.

You can set environment variables per game via the launch options.
PROTON_NO_ESYNC=1 %command% in this case.

[codeman101]

since you;d have to execute them from the terminal to launch steam every time you want to play that game.

You can set environment variables per game via the launch options.
PROTON_NO_ESYNC=1 %command% in this case.

Yeah I learned about that method after making that post. Although I wound up using the user_settings.py file after finally finding a youtube video that told me where it was. However using the method you're referring editing the option for the game within steam. Can that be used for multiple tweaks?

[AutoUpdatingBSoD]

I know I'm a bit late to this party, but....

I completely disagree with a whitelist as well. When I load up the game, It just shows some of the models (greyed out), and the esync patch does not work for fixing the sound bug.

Edit: By some of the models, I mean instead of the main menu, like it should show, the game just shows some of the models (staying still, right in front of the screen) and the screen flickers a bit. I've searched high and wide for a fix to this to no avail.

Edit 2: Got both fixed. A reboot was all I needed for the wierd models issue (thankfully), and as for the sound bug I'm still not sure how I fixed it.

[jp7677]

This game wont start anymore on my machine with 4.11. Both D9VK and Wine3D are crashing. Looking at the D9VK log it seems that the game tries to initialize some weird resolution, fails and falls back to 640x480 which fails in the end. The resolution I used with 4.2 and thus is persisted in the game settings is 3440x1440.

May be related to https://github.com/ValveSoftware/Proton/issues/1990#issuecomment-517904701 and https://github.com/ValveSoftware/Proton/issues/2932

LEGOStarWarsSaga_d3d9.log

[AutoUpdatingBSoD]

This game wont start anymore on my machine with 4.11. Both D9VK and Wine3D are crashing. ........

I know this is a stretch, but have you tried using either of the older Proton versions through the Game Settings in Steam (i.e. 3.16)....?

May sound silly if you've tried it, but I had to do something similar for Bloodstained: Curse of the Moon.

[jp7677]

@EdgyBama Thanks for your response. I haven't explicitly tested this, but I'm pretty sure this game will start again once I pin it to Proton 4.2. So this would be indeed a valid work-around.
That said I wanted to report that something weird goes on when using 4.11.

[AutoUpdatingBSoD]

@jp7677 I see. Apologies for the miscommunication on my end :+1: .

[jp7677]

The issue with the game not starting anymore has been fixed with Proton 4.11-2. Thanks a lot!

[bakkerthehacker]

I have yet to get this game to start at all.

Proton crashes with an unhandled page fault on read access. I have tested on proton 3.7-8, 3.16-9, 4.2-9 and 4.11-3, none work. It seems in every version, the crash is either in libsdl2 or JoystickAGenericImpl.

steam-32440-3.7-8.log
steam-32440-3.16-9.log
steam-32440-4.2-9.log
steam-32440-4.11-3.log

[xDShot]

Doesn't work

[Odzinic]

The game has been booting into a black screen for me recently. There is a slight white flicker then it goes back to a black screen and stays there. I've attempted launching it with Proton 4.2, 4.11 and 5.0 with no luck. The attached log is for Proton 5.0.

steam-32440.log

EDIT: With help from @qsniyg, the backtrace of what happened before the crash was found to be

Backtrace:
=>0 0x7e5c8e11 joystick_map_axis+0x11() in dinput8 (0x0032fb88)
  1 0x7e5d05aa poll_sdl_device_state+0x69() in dinput8 (0x0032fbd8)
  2 0x7e5c87b4 JoystickWGenericImpl_Poll+0x73() in dinput8 (0x0032fbf8)
  3 0x7e5c881c JoystickAGenericImpl_Poll+0x1b() in dinput8 (0x0032fc28)
  4 0x006d770e EntryPoint+0xffffffff() in legostarwarssaga (0x0318558c)

[qsniyg]

@bakkerthehacker Have you tried running protontricks 32440 dinput8?

Also, does the game run under normal wine? In @Odzinic's case (which is very similar to yours), the issue was only present under proton, as the proton branch uses SDL for gamepads (though I don't believe the issue is due to SDL, but rather due to proton's code).

[bakkerthehacker]

protontricks 32440 dinput8 lets the game launch!

[bakkerthehacker]

Controllers are not working (xbox 360 wired, dualshock 4, dualshock 4 with ds4drv --emulate-xpad) but at least its a start

[Odzinic]

Controllers are not working (xbox 360 wired, dualshock 4, dualshock 4 with ds4drv --emulate-xpad) but at least its a start

Hm same issue with me for my DS3. Other LEGO games are detecting it without a problem but this one can't. It did work before with the game. Tested with Steam controller as well and unable to get it detected as well. In both BPM and normal launching.

[Odzinic]

@qsniyg helped me fix my controller issue as well. They recommended that I copy over the native wine dinput dll files over to the Proton version that LEGO Star Wars is using. The commands they recommended were:

cp /usr/lib64/wine/dinput*.dll.so ~/.steam/steam/steamapps/common/Proton\ 5.0/dist/lib64/wine
cp /usr/lib64/wine/fakedlls/dinput*.dll ~/.steam/steam/steamapps/common/Proton\ 5.0/dist/lib64/wine/fakedlls
cp /usr/lib32/wine/dinput*.dll.so ~/.steam/steam/steamapps/common/Proton\ 5.0/dist/lib32/wine
cp /usr/lib32/wine/fakedlls/dinput*.dll ~/.steam/steam/steamapps/common/Proton\ 5.0/dist/lib32/wine/fakedlls

On Ubuntu I found that the files were located in /opt/wine-staging/lib and /opt/wine-staging/lib64. After copying all of those over, my controller worked right away. Had to remap the controls by using my keyboard and then pressing the relevant buttons on my controller but after doing that I was able to play without an issue.

Reddit comment of the fix

[E3FxGaming]

Using Proton 4.11-13 and the launch options PROTON_NO_ESYNC=1 %command% doesn't fix the looping audio problems for me.

Proton log file (just me going into the title screen where the theme music loops over and over again - the looping audio problem is present while playing the game too, but not entering the game beyond the title screen keeps the logfile small):

steam-32440.log

System Information

• GPU: GTX 1080 Ti
• Driver/LLVM version: nvidia 450.66
• Kernel version: 5.4.60-2
• Link to full system information report as Gist: https://gist.github.com/E3FxGaming/eba95835b6f897505caefba1d519acc0
• Proton version: 4.11-13

[mwkroening]

@E3FxGaming, you are using fsync. Try disabling both esync and fsync.

[E3FxGaming]

@E3FxGaming, you are using fsync. Try disabling both esync and fsync.

@mwkroening Thank you so much, this fixed my problem.