Recurring - CommunityShaders.json is generated blank, thus most shaders are not compiled

[matm-git]

Linked issue: 536 Issue identified in CS version: 2024-09-17 VR Screen Space Reflections - RC and all following builds up to 2024-10-10 Skyrim version used: SkyrimVR Reporting users: jepster Reproducable: Yes, every start of the game Initial analysis:

1. I activate the latest CS version in MO2. I deactivate the previous shadercache and CS.json which are in a separate mod. I deactivate previous CS version and shadercache with jsons. I double check, there is no CS.json or CSUser.json left.
2. I start SkyrimVR via MO2, some shadercache is created but it goes much faster (like 4 times faster) than normal.
   • When later I look at info.ini in the shadercache I find the following entry: https://pastebin.com/Tv1G4vhS
   • CS.log looks like this: https://pastebin.com/FcqvwCYK
3. Sometimes the game starts, but sometimes it also freezes. If the game starts and I open CS.menu I can see that no features are shown in the CS menu. If I load a savegame the game looks very broken with grass floating. This was sometimes reported by other users.
4. In previous versions I have been able to click on 'load config' in the CS menu. This created a new valid CS.json in the background. With the latest build this is not possible. If clicking on 'load config' the game crashes with this errorlog: https://pastebin.com/EdJdMZPn
5. Afterwards MO2 reports an error for Community Shaders (which has also been reported by some other users): https://imgur.com/a/8liP32k

Workaround: The workaround for this is to obtain a valid CS.json and place it in overwrite or a mod \SKSE\Plugins. With the next game start the shadercache is created correctly and everything is fine.

[alandtse]

I feel like this is a mo2 issue. We are trying to save a new one. Mo2 is blocking us.

[alandtse]

At most we can force an exit or disable CS when we detect this state.

[matm-git]

Yes, sounds very likely to be related to MO2. I am not worried about us beta testers. We can organise ourselves for workarounds. But I am not sure how many users would be experiencing this with a Nexus release. Might be an temp. option to ship with a pregenerated config, even though it is no fun packaging manually :-( Up to the team ofc

[alandtse]

I appreciate the report, just posting the reality. I don't use MO2 so may have to rely on someone who does to figure this out.

I'll post an example of a working log later for reference, but essentially the "save" command is being blocked by MO2. This may mean we need a more apparent error when saves fail.