Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Steam Deck, Mono vs dotnet40, new Fling trainers #167

Open
sevenpastzeero opened this issue Sep 6, 2023 · 9 comments
Open

Steam Deck, Mono vs dotnet40, new Fling trainers #167

sevenpastzeero opened this issue Sep 6, 2023 · 9 comments

Comments

@sevenpastzeero
Copy link

Sorry if this is the wrong place to post, but it is related to NET framework, linux, and Mono.
Firstly, I am using Steam Deck. I recently started having issues with Fling trainers. The old ones worked on Steam proton/wine prefixes without any issue (Wine Mono Windows Support v7.4.1 is installed by default). But the recently released trainers does not work. After much research, it turns out I need to install dotnet40.
And after much work, I was able to install dotnet40 and get the trainers to start.
So I thought I wold post here, so maybe there would be a fix to make Mono support these new trainers.

Old trainers that work without any fixes. Mono 7.4.1 is installed by default:
https://flingtrainer.com/trainer/ace-combat-7-skies-unknown-trainer/
https://flingtrainer.com/trainer/elden-ring-trainer/

New trainers tested not working unless installing dotnet40:
https://flingtrainer.com/trainer/starfield-trainer/
https://flingtrainer.com/trainer/total-war-warhammer-iii-trainer/
https://flingtrainer.com/trainer/powerwash-simulator-trainer/

If I am at wrong here, then forgive me.
If you need any testing or logs, I can gladly provide them.

@madewokherd
Copy link
Owner

Thank you. This is the right place for this bug.

A log of the trainer running with WINE_MONO_TRACE=x WINEDEBUG=mscoree might shed some light on it. If it doesn't, it'll probably be a while before I can find time to investigate.

@sevenpastzeero
Copy link
Author

Ok, so here is 3 log files after starting 2 trainers added as a non steam games. Using Proton 7.
First on is Ace Combat 7 trainer that is working normally without any workarounds:
Ace_Combat_7_trainer_working_steam-14402251569569464320.log

Armored Core 6 trainer, not working:
Armored_core_6_trainer_notworking_steam-12961832436001406976.log

Armored Core 6 trainer working after force installing dotnet4 through cli using these commands (normal installation through winetricks gui fails)
WINEPREFIX=/home/deck/.steam/steam/steamapps/compatdata/{APPID}/pfx winetricks dotnet40 win7
WINEPREFIX=/home/deck/.steam/steam/steamapps/compatdata/{APPID}/pfx winetricks winecfg then switching to Windows 10
steam-12961832436001406976.log

steam-18104240248866209792.log

Hope this helps

@madewokherd
Copy link
Owner

I'm gonna say this shouldn't happen:

[0000000000000138:] EXCEPTION handling: System.InvalidOperationException: The calling thread must be STA, because many UI components require this.

Can you redo "Armored_core_6_trainer_notworking" with WINE_MONO_TRACE=E:System.InvalidOperationException? That should give a stack trace for this.

@sevenpastzeero
Copy link
Author

For some reason this command is not giving me a log file in the Home folder? Does it out put it somwhere else?

@madewokherd
Copy link
Owner

It shouldn't change where the log goes.

@sevenpastzeero
Copy link
Author

sevenpastzeero commented Sep 6, 2023

This one WINE_MONO_TRACE=x WINEDEBUG=mscoree immediatly gives a log file but the other one does not. I am adding it as a Launch Options in steam game properties.

Edit:
steam-10976871175115767808.log

@sevenpastzeero
Copy link
Author

I am not sure if this is correct but I also used this command WINE_MONO_TRACE=E:System.InvalidOperationException PROTON_LOG=1 %command% and got this output file
steam-10976871175115767808.log

@Xathros1
Copy link

Armored Core 6 trainer working after force installing dotnet4 through cli using these commands (normal installation through winetricks gui fails) WINEPREFIX=/home/deck/.steam/steam/steamapps/compatdata/{APPID}/pfx winetricks dotnet40 win7 WINEPREFIX=/home/deck/.steam/steam/steamapps/compatdata/{APPID}/pfx winetricks winecfg then switching to Windows 10 steam-12961832436001406976.log

I tried dotnet48, which works directly without changing to win7. dotnet40 didn't work for me.

@wyyadd
Copy link

wyyadd commented Nov 7, 2023

Hi, any updates to this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants