HGL
afraid-scarlet
F1 Manager 2024 not starting
36 Replies
passive-yellow•4mo ago
try using proton-ge and umu instead of proton hotfix
also, make sure the EOS overlay is enabled, is required for the authentication
afraid-scarletOP•4mo ago
Installed EOS overlay, restarted Heroic, tried Proton-GE-latest and Proton-GE-Proton9-20 still no dice. log https://0x0.st/8NJc.log

wise-white•4mo ago
did you enable eos overlay for the game? (three dot menu from the game screen)
afraid-scarletOP•4mo ago
There is Disable EOS Overlay
wise-white•4mo ago
you can add the environment variable
WINEDEBUG=+fixme
rerun and repost logsafraid-scarletOP•4mo ago
wise-white•4mo ago
these logs dont show that you set the environment variable
afraid-scarletOP•4mo ago
hmm.. i did "export WINEDEBUG=+fixme"
my bad https://0x0.st/8NJQ.log
wise-white•4mo ago
doesnt look like you enabled umu?
Wine-GE is rather old now (last release is almost a year ago) and thus might not work correctly. Please follow these instructions on using GE-Proton with umu instead:
1. Head to the Wine Manager in Heroic, click the "Proton-GE" tab, and install "Proton-GE-Latest"
2. Enable umu in "Settings" (Heroic sidebar) -> "Advanced" -> "Use UMU as Proton runtime"
Note: For a visual guide, see attached image
3. Head to the settings for your game(s) (icon on game card in library). In the "Wine Version" dropdown, select "Proton - Proton-GE-latest"
4. Rename your Wineprefix (path is shown in game settings), e.g. from
current-name
to current-name_bak
. To clarify: Rename the actual folder on your hard drive, do not change the option in the game settings.
Note: This will make game-specific configuration data (e.g. in-game settings or save files) unavailable. If this is an issue, let us know & we'll help you restore them.
afraid-scarletOP•4mo ago
https://0x0.st/8NJg.log
i didnt rename anything yet
after renaming F1 Manager 2024 folder on prefixes https://0x0.st/8NJ0.log
passive-yellow•4mo ago
this doesn't look right:
I wonder if it's a nixos issue
@aidalgol I think you are involved in that project? maybe I misunderstood
crude-lavender•4mo ago
Yes, and I don't know why this happens for some users. I haven't been able to get enough information to get anywhere with this.
wise-white•4mo ago
nixos does something and it reports funny to heroic but i think its generally a red herring?
crude-lavender•4mo ago
I used to have my driver show up like that, but games still worked, and now it shows up properly (and games still behave).
I haven't had time to set up a Heroic dev environment and do some debugging to figure out how it tries to evaluate the GPUs.
sunny-green•4mo ago
seems like nix packaging issue indeed
even legendary seems out of place as it doesn't activate the ownership token flow
idk where is the package hosted and how its bundled
but something is not yes
crude-lavender•4mo ago
0x0.st returning a server stacktrace for every request now.
It's using the nixpkgs package, which is built from the latest release on the legendary github repo.
sunny-green•4mo ago
you sure that build is also included with Heroic?
idk how nix packages really work
but don't you need to rebuild or something when one dependency changes?
crude-lavender•4mo ago
basically, yes.
sunny-green•4mo ago
because from the look of it the user here doesn't have legendary that's capable of differentiating
TRUE
from true
sunny-green•4mo ago
which is provided by this patch https://github.com/derrod/legendary/commit/f1f5cc07f6e14663cf6d040fc01d2019f4a35173
GitHub
[core] Normalise OwnershipToken value to lowercase · derrod/legenda...
Apparently this can be uppercase or lowercase, thanks Epic!
crude-lavender•4mo ago
The latest release is from December 2023, and that's dated August 2024, so it won't be in nixpkgs. Sounds like we should include that patch.
On my system, I'm getting this error in the Chromium Dev Tools console when I go to the Global Settings page.
- https://github.com/NixOS/nixpkgs/blob/master/pkgs/games/legendary-gl/default.nix
- https://github.com/NixOS/nixpkgs/blob/master/pkgs/games/heroic/default.nix
The nixpkgs code for legendary and heroic ^
sunny-green•4mo ago
also Heroic has its own fork of legendary now, even though it doesn't have that many differences it includes some patches that are there eariler than upstream
like EULA compatibility that we'll want to adapt eventually in the launcher
crude-lavender•4mo ago
Ah, we should probably package that one, then.
sunny-green•4mo ago
or even something as simple as allowing some Ubisoft games to be installed
it would be preferable, this is the build we ship starting 2.15.0 I believe
crude-lavender•4mo ago
Because compiled binaries of the helper programs are committed to the Heroic repo, I've just had to make a best guess which version of each to reference in the Heroic package.
sunny-green•4mo ago
nowadays we are pulling them from github's releases during the build
check
meta/downloadHelperBinaries.ts
crude-lavender•4mo ago
Where does the legendary fork live?
sunny-green•4mo ago
under Heroic's org on GitHub
sunny-green•4mo ago
GitHub
GitHub - Heroic-Games-Launcher/legendary: Legendary - A free and op...
Legendary - A free and open-source replacement for the Epic Games Launcher - Heroic-Games-Launcher/legendary
crude-lavender•4mo ago
I'll work on fixing up the packaging over this week.
wee-brown•4mo ago
i'm having the same issue now, did anything get fixed?
crude-lavender•4mo ago
On NixOS?
wee-brown•3mo ago
i'm just wondering if the game is playable now because i have the same issue
sunny-green•3mo ago
are you on NixOS?
wee-brown•3mo ago
ah, no, sorry (i don't think so) i'm on steamdeck. my apologies if it makes this thread not applicable - i just noticed they had the same problem as me.
i posted a separate thread on 3/3 specifically to my issue w/logs