Expected "{" but found value (1, 5) Error

[listenhere]

Greetings. Game is question is SSE, 1.6.1179.0. While running TexGen I run into a curious error "Expected "{" but found value (1, 5)" which I could not find a solution for while googling. Error comes up after TexGen is done loading configuration files, persists if all the plugins are disabled. I use the Stock Game folder. While running it for the vanilla Skyrim folder everything is in order. I could not find this error nowhere else in the support section. SSELODGen works without any problem. 

Loadorder is here https://pastebin.com/fKFqS6W1

[z929669]

20 minutes ago, listenhere said:

Greetings. Game is question is SSE, 1.6.1179.0. While running TexGen I run into a curious error "Expected "{" but found value (1, 5)" which I could not find a solution for while googling. Error comes up after TexGen is done loading configuration files, persists if all the plugins are disabled. I use the Stock Game folder. While running it for the vanilla Skyrim folder everything is in order. I could not find this error nowhere else in the support section. SSELODGen works without any problem. 

Loadorder is here https://pastebin.com/fKFqS6W1

Sounds like you have a corrupt/outdated/modified configuration file. This could be caused by updating DynDOLOD by copying the new files over the old. Instead, remove and replace the existing DynDOLOD folder with the new folder from the updated DynDOLOD archive. If you want to preserve certain settings, use a program like WinMerge to compare and merge files manually (assuming you moved the original folder location instead of deleting it).

You will be asked for your logs as explained in the DynDOLOD 3 OP and forum guidelines presented to you before posting this topic, so you should post them here asap.

[listenhere]

Sorry for that, forgot to paste it. Here is the bugreport https://pastebin.com/ajCCZiD4

 

Installation was fresh too. No other files preexisting. I will try to reinstall it though. 

Edit: the error still persists after the fresh install outside any folders. 

Edited December 10, 2024 by listenhere
addendum

[sheson]

3 hours ago, listenhere said:

Sorry for that, forgot to paste it. Here is the bugreport https://pastebin.com/ajCCZiD4

 

Installation was fresh too. No other files preexisting. I will try to reinstall it though. 

Edit: the error still persists after the fresh install outside any folders. 

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen log and debug log to also upload when making posts.

The ParallaxGen_Diff.json created by ParallaxGen seems to have an issue. Use a tool to check if it validates. For example https://jsonlint.com/.
In case it validates, upload it. If it fails, check the ParallaxGen log for hints, rerun it, check with its developer.

[listenhere]

Yeah it absolutely was ParallaxGen. Thanks for the replies. 

[CBSkyrimModding]

If ParallaxGen is the problem, what's the solution? I'm having the same issue.

[sheson]

2 hours ago, CBSkyrimModding said:

If ParallaxGen is the problem, what's the solution? I'm having the same issue.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen log and debug log to also upload when making posts.

Check the ParallaxGen log for hints, rerun it, check with its developer.

[CBSkyrimModding]

Got it, thanks. It's amazing that you have the stamina to keep answering questions after all these years...

I should note that I'm currently attempting a workaround that I thought of after reading the ParallaxGen comments. The mod author thinks it shouldn't matter in what order PG, TexGen, DynDOLOD, etc. is run, so I've simply disabled my PG output while running TexGen and then re-enabled it before starting DynDOLOD. I'll post an update after I get in-game to see the results.

Edited December 13, 2024 by CBSkyrimModding

[sheson]

42 minutes ago, CBSkyrimModding said:

Got it, thanks. It's amazing that you have the stamina to keep answering questions after all these years...

I should note that I'm currently attempting a workaround that I thought of after reading the ParallaxGen comments. The mod author thinks it shouldn't matter in what order PG, TexGen, DynDOLOD, etc. is run, so I've simply disabled my PG output while running TexGen and then re-enabled it before starting DynDOLOD. I'll post an update after I get in-game to see the results.

An invalid json file indicates something bad happed. Ignoring errors by disabling something is not going to fix anything.

You must have read an outdated post. The simple fact that DynDOLOD reads the json from ParallaxGen is hint enough, that it matters.

https://dyndolod.info/Generation-Instructions#Prerequisites
In case ParallaxGen is used, run it before TexGen and DynDOLOD, as they will use information from its ParallaxGen_Diff.json file in the data folder to properly match certain LOD models. ParallaxGen output should overwrite the full models included in DynDOLOD Resources. Leave the default setting of ParallaxGen to ignore meshes in ..\LOD\.. folder. See Community-Shaders - PBR for more.

https://dyndolod.info/Mods/Community-Shaders#PBR
Run ParallaxGen before TexGen and DynDOLOD, as they will use the CRC32 information from its ParallaxGen_Diff.json file to match LOD models that use CRC32 of the original full model, like for 3D tree LOD models. For best results there should be no patched full models in the load when running ParallaxGen, so it can generate the CRC32 information for all original full models. Also keep the default setting of ignoring meshes in ..\LOD\.. folders. ParallaxGen output should overwrite the full models in DynDOLOD Resources.

ParallaxGen also generates a plugin, that should be active in the load order.

[hakasapl]

Yes dyndolod/texgen should be run after PG. It used to matter less before PG generated a plugin and the diff file.

As for the JSON issue. There is a bug that the JSON has `null` as its contents only if PG patched zero meshes. So that's likely what you are running into. So if you are running into this issue and you're expecting PG to do something, it isn't. So likely a misconfiguration in the PG GUI.

I made an issue here to fix the JSON issue for the case where PG patches nothing. https://github.com/hakasapl/ParallaxGen/issues/171