-
Notifications
You must be signed in to change notification settings - Fork 8
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
Lauhdutin keeps forgetting games + last banner is cut off #163
Comments
It doesn't fix the error messages and the issue with the last banner being cut off but there's a way to at least have it remember the games most of the time: Use the "hide" feature, not "remove"! |
I saw one of these errors this morning when I cold booted the PC but when I refreshed the skin it loaded all my steam games, leaving out anything I had hidden last night and my sorting settings had been retained as per the change made in the settings.json file. After rebooting the computer several times, including a full shutdown and turning off the PSU for 10 seconds or so has failed to reproduce the error again. I can only assume that it was temporary. Everything is continuing to work as expected now though. The appmanifest files link to the content folders - if you open libraryfolders.vdf (found in the steamapps folder at the default location) in notepad you will see a pair of numbers on each entry line. Assuming you have a Steam library in a non default location with things installed to it. My suggestion: Let us know how you get on, hopefully that'll quash the error for you. |
@Nathipha could you check if the file that gaves you the error exists? And if it exists, could you open it with notepad++ (or another editor) and check its contents? Just trying to understand if the issue is that the file is corrupted or that there is a reference to a file that doesn't exists. |
I updated Rainmeter to 4.5.2 and edited both "init.lua" files according to your changes @BanCrash (thanks again for that!), then restarted my PC and the skin's looking fine: All the banners are there, apart from the ones I'd hidden before I restarted the PC, and there's no error. I just noticed that I made a mistake in the first post: The 6-digit number isn't actually my steam id but a game id. Maybe your changes fixed that, I'm going to do a couple of random restarts in the next couple of days. The very last game is still cut off but that's probably a different bug then (must have been introduced with version 3) and since the skin is always also listing "Steamworks Common Restributables", I can just keep that one at the bottom of the list. |
Could you share a screenshot about that issue?? |
You don't need to worry about the app manifest files, they aren't something that was involved in these changes. The problem was a change in how Steam formats the data in the libraryFolders.vdf file causing the skin to be unable to recognise another install library location iirc from the other thread the fixes were implemented from. Odd, I don't have any cut off tiles, have you got the bar positioned in a manner that has the offending tile overhang the edge of the screen? The only issue I'm probably going to run into occasionally now is the rainmeter helpers app manifest one (only seen it once, this morning, since I mentioned it in my comment earlier on this thread) where the skin complains about failing to read it... but it doesn't matter with the recent changes to the init.lua file coz on skin refresh it disappears right away - IF it even appears in the first place, and games are once more displayed or hidden if i chose to hide them... and everything returns to behaving as it's supposed to. |
When I started my PC today I was greeted by the "Failed to read" error again. I checked and the file doesn't exist, even though the game ("Don't Starve") is installed on my PC. I had to "Detect Games" multiple times before all of the tiles finally showed up (including the one for "Don't Starve", even though the file still doesn't exist):
@BanCrash @humanspida |
I think your issue could be that skin is not being rewrite. Could you open settings -> Right click -> Rebuild main slots, and after that refresh your main skin if it doesn't happen automatically? About the other issue, I will check if we can somehow ignore a file if it doesn't exist. |
@BanCrash Btw, I just got the same error again (line 135) for the same file but this time everything was back to normal after a single "Detect games". |
Nevermind, your issue is somewhere else. Do you have enabled the option to hide the skin? If so, could you disable and check if that solves the issue? EDIT: About the other, I will check it when I have time |
@Nathipha could you try this to see if solve your line 135 issue? Go to Lauhdutin folder@Resources\lib\rainmeter_helpers.lua, go to line 125, press Intro to create a new line and then paste in the blank line this:
It should add three new lines automatically and should look like this: |
@Nathipha did you try the code of my previous comment? |
Short description of the issue
I'm using Lauhdutin to display 10 of my Steam games (Steam doesn't start with Win) and also 2 Windows shortcuts (in the "@Resources\Shortcuts" folder). About 90% of the time I start my PC, the Lauhdution sidebar is simply black and says "No games to show" at the very top. Sometimes there's also a "lua" error (see below) that's shown vertically centered in this black bar.
I then have to "Detect Games" but even if I don't get said "lua" error, it only loads of ALL the Steam games and I have to remove the ones I don't want again - it doesn't seem to remember which ones I already removed.
When this happens, the very last banner is also cut off (I can see less than a cm of it), even though it's still clickable.
Lauhdutin version
3.1.0 beta 4 (latest version)
Rainmeter version
4.3.1.3321 (64bit) (latest stable version)
Windows version
Win 10
Error messages
"xxxxxx" is a 6-digit number (probably the id of my Steam profile).
Steps to reproduce the issue
I don't know what's causing this problem. I used a very old version of Lauhdutin on my old Win 7 PC for years and everything was fine.
The text was updated successfully, but these errors were encountered: