Closed frostworx closed 2 years ago
Vortex works fine with the installDotNet function, but MO2 doesn't. Looks like the dotnet installation is not 100% clean (has NETFXRepair.exe).
Nope, Vortex works 99%, but it can't extract downloaded mods. https://github.com/frostworx/steamtinkerlaunch/issues/306. Very likely this is a dotnet issue as well...
Just updated DotNet TL;DR: The only valid options I currently see
will use self rolled https://github.com/frostworx/steamtinkerlaunch-tweaks/releases/tag/Proton-6.17-STL-1 at least until this works with official proton
With Vortex and MO2 seemingly working fine with this solution, I'll close this issue.
The Vortex rewrite is pretty much feature complete. Maybe some more changes to the Mod Organizer 2 (https://github.com/frostworx/steamtinkerlaunch/issues/304) implementation (they share many functions now :)) and then I'll probably push the monster commit somewhere in the 1st third of October. Any fixable reported issue will make it into the end of October major release (when I find the time)
Short problem description in the DotNet wiki ~~While rewriting several Vortex functions a generic working installDotNet48 function was added to stl (not released yet)~~
A clean (as possible) solution for installing dotnet48 using proton is required.
This could be added at least to all supported 3rd party programs, which use an own Compatdata/Wineprefix like
DepressurizerNope, I do not even use this, chances are higher that it will be removed againbut might be also added as a generic install option for every Compatdata/Wineprefix of any game.Running custom user-installed programs depending on DotNet should be pretty simple then and also allow f.e. to use the UniversalUE4Unlocker gui or maybe also use Vortex and Mod-Organizer 2 directly in the game pfx without any restrictions.Nope, as this requires a specific proton/wine version - won't risk breaking game prefixes by mixing proton versions