All of setting gone wierd.

Re2947 commented

2023-03-25 10:00:59 -04:00

(Migrated from github.com)

This my first time using Rainmeter and I don't know how to fix it. When I start the program and use this skin, some of setting layout will show like my screenshot.

Re2947 commented

2023-03-25 10:08:46 -04:00

(Migrated from github.com)

https://imgur.com/tNGrD5M

Xenon257R commented

2023-03-25 11:24:32 -04:00

(Migrated from github.com)

From a cursory glance, it looks like everything Lua related seems to be malfunctioning - more accurately, they are not functioning at all.

According to Rainmeter's Lua Scripting page:

Rainmeter has the ability to load and execute scripts in Lua, a functional programming language. Rainmeter includes the Lua 5.1 standard libraries, which encompass a variety of powerful features.

My first guess is that this issue is solely rooted in your personal device missing the Lua libraries that should have come packaged with your Rainmeter install. For starters, I would suggest you try the following steps:

(Re)install the latest version of Rainmeter (4.5.17).
ONLY IF the above doesn't work, install Lua manually from their official website here.
- Manually installing Lua and getting it to work can be EXTREMELY difficult; if you find yourself overwhelmed doing this, you can hold off on this step to see if we can find a more user-friendly solution. If you did end up holding off, please specify so that I am aware you do not have a manual installation while resolving this issue.

If neither of the above steps work, please share a screenshot of your Log page here. You can reach that page by opening the Rainmeter Client and clicking Open Log located at the bottom left area. It should look something like below:

To provide the most useful log, first CLEAR the log, uncheck the NOTICE option at the bottom left (keep everything else checked), then REFRESH Rainmeter from the main client page. This will make it so only the error logs are shown, and only for the skins you have active at the moment.

If the log output is extremely long, the most likely to be helpful tidbits will be the ones at the bottom of the list (after your REFRESH). It would be handy to have the full log, but if you can only spare a single screenshot, scroll to the bottom and provide the screenshot from there.

From a cursory glance, it looks like everything ***Lua*** related seems to be malfunctioning - more accurately, they are not functioning at all. According to _Rainmeter_'s [Lua Scripting page](https://docs.rainmeter.net/manual/lua-scripting/): > Rainmeter has the ability to load and execute scripts in Lua, a [functional programming language](https://en.wikipedia.org/wiki/Lua_(programming_language)). Rainmeter includes the [Lua 5.1 standard libraries](https://www.lua.org/manual/5.1/manual.html#5), which encompass a variety of powerful features. My first guess is that this issue is solely rooted in your personal device missing the **Lua libraries** that should have come packaged with your _Rainmeter_ install. For starters, I would suggest you try the following steps: 1) (Re)install the latest version of _Rainmeter_ ([4.5.17](https://www.rainmeter.net/)). 2) ONLY IF the above doesn't work, install Lua manually from their official website [here](https://www.lua.org/download.html). - Manually installing Lua and getting it to work can be EXTREMELY difficult; if you find yourself overwhelmed doing this, you can hold off on this step to see if we can find a more user-friendly solution. If you did end up holding off, please specify so that I am aware you do not have a manual installation while resolving this issue. If neither of the above steps work, please share a screenshot of your Log page here. You can reach that page by opening the _Rainmeter_ Client and clicking **Open Log** located at the bottom left area. It should look something like below: ![image](https://user-images.githubusercontent.com/65873135/227725168-165d545b-b249-45dc-9793-b798ab4b64e1.png) To provide the most useful log, first **CLEAR** the log, uncheck the **NOTICE** option at the bottom left (keep everything else checked), then **REFRESH** _Rainmeter_ from the main client page. This will make it so only the error logs are shown, and only for the skins you have active at the moment. If the log output is extremely long, the most likely to be helpful tidbits will be the ones at the bottom of the list (after your **REFRESH**). It would be handy to have the full log, but if you can only spare a single screenshot, scroll to the bottom and provide the screenshot from there.

Xenon257R commented

2023-03-25 11:31:10 -04:00

(Migrated from github.com)

Also if you could clarify if the comment below on the Steam Guide is also by you; there isn't a way to directly reply to a user in Steam Workshop comments, so if this is indeed you I can forego leaving a disjointed comment there, and your reply in turn as well.

Also if you could clarify if the comment below on the Steam Guide is also by you; there isn't a way to directly reply to a user in Steam Workshop comments, so if this is indeed you I can forego leaving a disjointed comment there, and your reply in turn as well. ![image](https://user-images.githubusercontent.com/65873135/227726799-e7ef9576-cb71-48b0-ba48-8c1170996d6d.png)

Re2947 commented

2023-03-25 12:07:11 -04:00

(Migrated from github.com)

This log is after I install Lua and still get error like this.

This log is after I install Lua and still get error like this. ![สกรีนช็อต 2023-03-25 225805](https://user-images.githubusercontent.com/115440691/227728441-3b1b9c5a-2c8e-47b7-880b-5209e1fb691a.png) ![สกรีนช็อต 2023-03-25 225959](https://user-images.githubusercontent.com/115440691/227728447-e44ee372-a92c-4bca-a3b0-a6989a238116.png)

Xenon257R commented

2023-03-25 13:22:56 -04:00

(Migrated from github.com)

It appears the json files are now acting up - Lua appears to be running perfectly fine now as it is responsible for spitting out the error messages in the first place. That's good - but we still can't rule out Lua as a problem. I'm pretty sure later versions of Lua are backwards compatible with the 5.1 documentation Rainmeter follows, but we'll put that possibility in the backburner for now.

Next, can you check the contents of your BlueArchive\@Resources\json directory? There should be several json files in that folder - if they are indeed there, can you share the contents of any one of them?

For example, my steamevent.json looks like the following:

{
    "group": "Steam",
    "struct": [
        {
            "label": "name",
            "type": "string"
        },
        {
            "label": "id",
            "type": "number"
        },
        {
            "label": "enable",
            "type": "boolean"
        }
    ],
    "data": [
        {
            "id": 593110,
            "name": "Steam News",
            "enable": true
        }
    ],
    "tips": [
        "The Steam ID of a game is a numeric value that can be found in the game's Home Page URL. For example, Team Fortress 2's ID is [440].",
        "Steam's RSS feed follows the same georestrictions as the game. Double-check if the Steam game is available in your region before making an active entry for it."
    ]
}

If they look undamaged, we can rule out .json files being the problem, leaving only Lua as the culprit. It looks like either dofile() or the \lib\* scripts are failing, making a bad parse of the data. This may have been a byproduct of manually installing Lua, making it lack the necessary libraries the scripts want to use.

It appears the `json` files are now acting up - Lua appears to be running perfectly fine now as it is responsible for spitting out the error messages in the first place. That's good - but we still can't rule out Lua as a problem. I'm pretty sure later versions of Lua are backwards compatible with the 5.1 documentation Rainmeter follows, but we'll put that possibility in the backburner for now. Next, can you check the contents of your `BlueArchive\@Resources\json` directory? There should be several `json` files in that folder - if they are indeed there, can you share the contents of any one of them? For example, my `steamevent.json` looks like the following: ```json { "group": "Steam", "struct": [ { "label": "name", "type": "string" }, { "label": "id", "type": "number" }, { "label": "enable", "type": "boolean" } ], "data": [ { "id": 593110, "name": "Steam News", "enable": true } ], "tips": [ "The Steam ID of a game is a numeric value that can be found in the game's Home Page URL. For example, Team Fortress 2's ID is [440].", "Steam's RSS feed follows the same georestrictions as the game. Double-check if the Steam game is available in your region before making an active entry for it." ] } ``` If they look undamaged, we can rule out `.json` files being the problem, leaving only Lua as the culprit. It looks like either `dofile()` or the `\lib\*` scripts are failing, making a bad parse of the data. This may have been a byproduct of manually installing Lua, making it lack the necessary libraries the scripts want to use.

Xenon257R commented

2023-03-25 14:14:28 -04:00

(Migrated from github.com)

AH! I just caught a very crucial keyword in your Error Log: OneDrive.

NOTE BEFORE YOU PROCEED WITH THIS SOLUTION: This solution requires you moving around your folders. This procedure IS reversible - just remember the location of your old Skins directory that you can switch back to if this doesn't work.

There is an issue a user posted with a similar issue that points to another somewhat old thread in the Rainmeter forums about this issue. Reading the thread, they never talk about Lua scripts specifically, but if I had to wager a guess how cloud storage works, I think some of the Lua scripts only exist in your cloud and not locally (or at least, Rainmeter can't differentiate the two states) - so the scripts failing may actually be because of those "locally non-existent" files.

So, assuming what I said above is correct, here is a transcription from user balala in the referred thread of what you should do:

Choose for the skins a location outside of the OneDrive folder. Usually this is under the Documents folder, but this is not mandatory (however is recommended).
Right click the Rainmeter icon in the Notification Area. Click Edit settings. Rainmeter's settings opens in your default text editor.
Locate the [Rainmeter] section. Locate the SkinPath option of this section. Edit it to the previously chosen location (first step above).
Save and close the file.
Exit Rainmeter.
Move the old Skins folder (or its content, obviously) to the new location.
Restart Rainmeter.
If the skins don't load, load them one by one.

Let me know if you tried this out and it works!

AH! I just caught a very crucial keyword in your Error Log: **OneDrive**. NOTE BEFORE YOU PROCEED WITH THIS SOLUTION: This solution requires you moving around your folders. This procedure IS reversible - just remember the location of your old Skins directory that you can switch back to if this doesn't work. There is an [issue a user posted](https://forum.rainmeter.net/viewtopic.php?t=39589#p202569) with a similar issue that points to another [somewhat old thread](https://forum.rainmeter.net/viewtopic.php?t=31708&hilit=onedrive#p197758) in the _Rainmeter_ forums about this issue. Reading the thread, they never talk about Lua scripts specifically, but if I had to wager a guess how cloud storage works, I think some of the Lua scripts only exist in your cloud and not locally (or at least, _Rainmeter_ can't differentiate the two states) - so the scripts failing may actually be because of those "locally non-existent" files. So, assuming what I said above is correct, here is a transcription from user _balala_ in the referred thread of what you should do: - Choose for the skins a location outside of the OneDrive folder. Usually this is under the Documents folder, but this is not mandatory (however is recommended). - Right click the Rainmeter icon in the Notification Area. Click Edit settings. Rainmeter's settings opens in your default text editor. - Locate the [Rainmeter] section. Locate the SkinPath option of this section. Edit it to the previously chosen location (first step above). - Save and close the file. - Exit Rainmeter. - Move the old Skins folder (or its content, obviously) to the new location. - Restart Rainmeter. - If the skins don't load, load them one by one. Let me know if you tried this out and it works!

❤️ 1

Re2947 commented

2023-03-25 15:49:31 -04:00

(Migrated from github.com)

That works! Thanks a lot for helping.

👍 1

222K6032 commented

2025-03-11 07:46:27 -04:00

(Migrated from github.com)

I just had this problem too, and once I figured out that OneDrive was doing something wrong and changed the location of the folder, it started working as if the previous error was not true! I'm glad I found this article!

Rows
Columns

All of setting gone wierd. #5