Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The UI Language setting was not working

See original GitHub issue

Describe the bug The UI Language setting was not working.

To Reproduce Steps to reproduce the behavior: I changed the UI language pack in the Setting tab of DS4Windows. I found the <UseLang>ja</UseLang> part was changed in the Profiles.xml. But after I restart DS4Windows, the UI language still English.

Expected behavior A clear and concise description of what you expected to happen.

Screenshots and Logs

2022-10-15 19:37:11.0553|INFO|DS4Windows version 3.1.7
2022-10-15 19:37:11.0611|INFO|DS4Windows exe file: DS4Windows.exe
2022-10-15 19:37:11.0611|INFO|DS4Windows Assembly Architecture: x64
2022-10-15 19:37:11.0611|INFO|OS Version: Microsoft Windows NT 10.0.19044.0
2022-10-15 19:37:11.0611|INFO|OS Product Name: Windows 10 IoT Enterprise LTSC 2021
2022-10-15 19:37:11.0611|INFO|OS Release ID: 2009
2022-10-15 19:37:11.0611|INFO|System Architecture: x64
2022-10-15 19:37:11.0611|INFO|Logger created
2022-10-15 19:37:12.6764|INFO|Running as User
2022-10-15 19:37:12.6764|INFO|HidHide control device found
2022-10-15 19:37:13.7013|INFO|Starting...
2022-10-15 19:37:13.7013|INFO|Using output KB+M handler: FakerInput 0.1.0.0
2022-10-15 19:37:13.7013|INFO|Connection to ViGEmBus 1.21.442.0 established
2022-10-15 19:37:13.7013|INFO|Searching for controllers...
2022-10-15 19:37:13.7013|INFO|Using Exclusive Mode
2022-10-15 19:37:15.0283|INFO|Found Controller: 00:1F:E2:XX:XX:XX (USB) (DS4 v.2).
2022-10-15 19:37:15.1827|INFO|Plugging in virtual DS4 Controller in output slot #1
2022-10-15 19:37:15.1827|INFO|Associated input controller #1 (DS4 v.2) to virtual DS4 Controller in output slot #1
2022-10-15 19:37:15.2227|INFO|Controller 1 is using Profile "Default". Battery level is 100%
2022-10-15 19:37:23.4192|INFO|Request App Shutdown
2022-10-15 19:37:23.4192|INFO|Stopping Virtual Output Controllers
2022-10-15 19:37:23.4192|INFO|Closing connection to ViGEmBus
2022-10-15 19:37:23.4855|INFO|Disassociated virtual DS4 Controller in output slot #1 from input controller #1 (DS4 v.2)
2022-10-15 19:37:23.4855|INFO|Unplugging virtual DS4 Controller from output slot #1
2022-10-15 19:37:23.4855|INFO|Stopping DS4 Input Controllers
2022-10-15 19:37:23.4855|INFO|Stopped DS4Windows

2022-10-15 19:37:28.4716|INFO|DS4Windows version 3.1.7
2022-10-15 19:37:28.4716|INFO|DS4Windows exe file: DS4Windows.exe
2022-10-15 19:37:28.4716|INFO|DS4Windows Assembly Architecture: x64
2022-10-15 19:37:28.4716|INFO|OS Version: Microsoft Windows NT 10.0.19044.0
2022-10-15 19:37:28.4716|INFO|OS Product Name: Windows 10 IoT Enterprise LTSC 2021
2022-10-15 19:37:28.4716|INFO|OS Release ID: 2009
2022-10-15 19:37:28.4716|INFO|System Architecture: x64
2022-10-15 19:37:28.4716|INFO|Logger created
2022-10-15 19:37:30.1401|INFO|Running as User
2022-10-15 19:37:30.1401|INFO|HidHide control device found
2022-10-15 19:37:31.1706|INFO|Starting...
2022-10-15 19:37:31.1706|INFO|Using output KB+M handler: FakerInput 0.1.0.0
2022-10-15 19:37:31.1706|INFO|Connection to ViGEmBus 1.21.442.0 established
2022-10-15 19:37:31.1706|INFO|Searching for controllers...
2022-10-15 19:37:31.1706|INFO|Using Exclusive Mode
2022-10-15 19:37:32.4097|INFO|Found Controller: 00:1F:E2:XX:XX:XX (USB) (DS4 v.2).
2022-10-15 19:37:32.5465|INFO|Plugging in virtual DS4 Controller in output slot #1
2022-10-15 19:37:32.5465|INFO|Associated input controller #1 (DS4 v.2) to virtual DS4 Controller in output slot #1
2022-10-15 19:37:32.5774|INFO|Controller 1 is using Profile "Default". Battery level is 100%
2022-10-15 19:37:51.0610|INFO|Request App Shutdown
2022-10-15 19:37:51.0610|INFO|Stopping Virtual Output Controllers
2022-10-15 19:37:51.0610|INFO|Closing connection to ViGEmBus
2022-10-15 19:37:51.1252|INFO|Disassociated virtual DS4 Controller in output slot #1 from input controller #1 (DS4 v.2)
2022-10-15 19:37:51.1252|INFO|Unplugging virtual DS4 Controller from output slot #1
2022-10-15 19:37:51.1252|INFO|Stopping DS4 Input Controllers
2022-10-15 19:37:51.1252|INFO|Stopped DS4Windows

Desktop (please complete the following information):

Controller Make and Model: Sony DS4 v.2 (CUH-ZCT2U)
OS: Windows 10 LTSC Build 19044.1299
DS4Windows Version 3.1.7

Issue Analytics

State:
Created a year ago
Comments:6 (2 by maintainers)

Top GitHub Comments

2reactions

Ryochan7commented, Nov 10, 2022

Seems to be fixed with commit f2fa15ce5b7facacf99deab22259cd3b252a9820. Had to the AppDomain.CurrentDomain.AssemblyResolve hook like was suggested to pass pre-loaded assemblies so the .NET Runtime would utilize them. Found out later leaving the hook in place causes app slowdown so I had to remove the hook after the main window was loaded. Seems to work with components created later on.

0reactions

Ryochan7commented, Nov 10, 2022

Just found out Microsoft intentionally removed support for specifying additional probing paths for assemblies with .NET 6. Didn’t even notice the issue since Visual Studio pumps out the standard locale subfolders (contained in the main app folder) and I failed to look into it outside of the dev environment. Looks like the feature has actually been broken since version 3.1.0.

Thanks Microsoft yet again.

https://github.com/dotnet/runtime/issues/73710#issuecomment-1222651405 https://github.com/dotnet/sdk/issues/10366#issuecomment-990896208