Error reading grass [worldspace] [x,y] Unknown grass data file format

[Nemo92]

I have currently problems with generating grass lods with DynDOLOD.

When i click on Start this error message pop up:

[02:15] [DoObjectLOD] <Notice: [Tamriel] Gathering grass data for object LOD>
[03:11] Error reading grass Tamriel [-1,-3] <Unknown grass data file format>

When i fixed a worldspace another error with another cooridinate pops up afterwards.

The only grass mod i use is Verdant.

Is there a way to solve this problem?

The log.txt is in the attachment.

DynDOLOD_SSE_log.txt

[sheson]

3 hours ago, PumpkinHat said:

I finally fixed it by rebooting my computer and disabling my bashed patch. I'm not sure which one fixed it but I would guess the bashed patch was the problem since it says in the console to disable it if you have problems I just didn't think the problems I was having, DynDOLOD just getting stuck, were caused by the bashed patch. If anyone else encounters this issue make sure to disable the bashed patch before you generate.

https://dyndolod.info/Generation-Instructions
Disabling plugins, mods, meshes or textures is a troubleshooting step and not a fix

If the bashed patch plugin causes issues it means is outdated or otherwise broken (like really old versions did that years ago) and should be removed, generated from scratch and the activated again before generating LOD.

It is unfortunate that you did not upload logs or a realtime log that shows the actual issue as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

[PumpkinHat]

On 2/2/2025 at 12:04 PM, sheson said:

https://dyndolod.info/Generation-Instructions
Disabling plugins, mods, meshes or textures is a troubleshooting step and not a fix

If the bashed patch plugin causes issues it means is outdated or otherwise broken (like really old versions did that years ago) and should be removed, generated from scratch and the activated again before generating LOD.

It is unfortunate that you did not upload logs or a realtime log that shows the actual issue as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

Hey sorry, I didn't see in the instructions that you could enable real time logging, it's made it much easier to see what is going on especially if the UI freezes by just tailing the log file. I really appreciate the patience you have with stupid people like me who don't read the entire documentation. Anyways, here is the realtime log from a DynDOLOD run that froze up when generating atlas for PalePass worldspace from LotD:

https://ufile.io/fg14y8h9

It spit out a bunch of errors about missing textures and the UI and debug logs just stopped without the program exiting. The weird thing is, the very next run I did was fine and didn't even spit out those errors even though I'm pretty sure I didn't change anything between the runs. I think at least some of the times I though it was not working I exited prematurely because either the UI was frozen or it was stuck at the same spot for a very long time, but real time logging makes it much easier to tell if work is still being done. I'm not as worried about it anymore now that I can monitor the progress more reliably, but I thought I'd still provide the log just in case this is a bug and not just me being dumb.