Closed matm-git closed 1 month ago
I think MO2 is fucking something up. This is what it should do when it detects no config file. For some reason, it's detecting something to open and it's blank.
[2024-09-20 01:47:45.561] [info] [50376] [XSEPlugin.cpp:53] Loaded CommunityShaders 0-8-7-0
[2024-09-20 01:47:45.564] [info] [50376] [State.cpp:138] Unable to open user config file (Data\SKSE\Plugins\CommunityShadersUSER.json); trying default (Data\SKSE\Plugins\CommunityShaders.json)
[2024-09-20 01:47:45.564] [info] [50376] [State.cpp:143] No default config (Data\SKSE\Plugins\CommunityShaders.json), generating new one
[2024-09-20 01:47:45.565] [info] [50376] [State.cpp:265] Saving settings to Data\SKSE\Plugins\CommunityShaders.json
[2024-09-20 01:47:45.572] [info] [50376] [State.cpp:153] Loading config file (Data\SKSE\Plugins\CommunityShaders.json)
I guess we could have a try to catch it.
Don't reopen issues with old data. Have them create a new one and cross reference. This build is no longer in use so just clutters up the response.
Ok, I create #624 . Please feel free to close this then
Issue identified in CS version: 2024-09-17 VR Screen Space Reflections - RC Skyrim version used: SkyrimVR Reporting users: jepster and hostile80 Reproducable: Yes, every start of the game Initial analysis: This does not seem to impact all users. For Patka the config file was created successfully. The following log entry is generated in CommunityShaders.log [2024-09-17 19:19:51.766] [info] [9064] [XSEPlugin.cpp:53] Loaded CommunityShaders 0-8-7-0 [2024-09-17 19:19:51.771] [info] [9064] [State.cpp:135] Unable to open user config file (Data\SKSE\Plugins\CommunityShadersUSER.json); trying default (Data\SKSE\Plugins\CommunityShaders.json) [2024-09-17 19:19:51.771] [info] [9064] [State.cpp:150] Loading config file (Data\SKSE\Plugins\CommunityShaders.json) [2024-09-17 19:19:51.771] [error] [9064] [State.cpp:156] Error parsing json config file (Data\SKSE\Plugins\CommunityShaders.json) : [json.exception.parse_error.101] parse error at line 1, column 1: attempting to parse an empty input; check that your input string or stream contains the expected JSON Workaround: Users were able to resolve this by using Patka's config file and placing them in the correct location in overwrite