Executing LODGen.exe returned error code C0000135

[Torwak]

Following the Dyndolod generation instructions, I get the following error in a popup window: Executing LODGen.exe returned error code C0000135

xLODGen worked fine. As well as the included TexGen from Dyndolod.

DynDOLOD_SSE_Debug_log.txt

LODGen_SSE_Test_log.txt

It is worth mentioning that I am running MO2 with wine on Linux. I'm kind of bothered by dyndolod not working, when everything else skyrim modding has worked as well as on windows. Any chance of getting some pointers on what might be causing my issue?

[sheson]

14 minutes ago, m4DnZ said:

Following the Dyndolod generation instructions, I get the following error in a popup window: Executing LODGen.exe returned error code C0000135

xLODGen worked fine. As well as the included TexGen from Dyndolod.

DynDOLOD_SSE_Debug_log.txt

LODGen_SSE_Test_log.txt

It is worth mentioning that I am running MO2 with wine on Linux. I'm kind of bothered by dyndolod not working, when everything else skyrim modding has worked as well as on windows. Any chance of getting some pointers on what might be causing my issue?

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

Always use the x64 version as explained by the installation instructions.

I believe the "OS" is missing the x86 version of either  .NET and .Net Framework

[Torwak]

Here back to report that I fixed my issue by installing mo2 with the modorganizer2-linux-installer instead of using steamtinkerlaunch, which I used in the non-working setup. I used the Modding Skyrim SE on Linux - A Headache Minimization Guide, and adapted it to my setup.

I installed "dotnet-runtime" natively on linux via package manager. Because I use Arch (btw), the extra repository provided version 7.0.11.sdk111-1. I also installed the Visual Studio 2015-2022 redistributables into my user's wine prefix ~/.wine by running the installer, not winetricks.

Now dyndolod runs ok, except for the middle part of the window being "blank" in expert mode. I think there is supposed to be a list of rules/items there. You can barely work around this by clicking the on the items to see a quick flash of the name of the list item.

I'm not sure my original issue was because of steamtinkerlaunch, could've been that I messed up my game prefix at some point.

[sheson]

1 hour ago, m4DnZ said:

Here back to report that I fixed my issue by installing mo2 with the modorganizer2-linux-installer instead of using steamtinkerlaunch, which I used in the non-working setup. I used the Modding Skyrim SE on Linux - A Headache Minimization Guide, and adapted it to my setup.

I installed "dotnet-runtime" natively on linux via package manager. Because I use Arch (btw), the extra repository provided version 7.0.11.sdk111-1. I also installed the Visual Studio 2015-2022 redistributables into my user's wine prefix ~/.wine by running the installer, not winetricks.

Now dyndolod runs ok, except for the middle part of the window being "blank" in expert mode. I think there is supposed to be a list of rules/items there. You can barely work around this by clicking the on the items to see a quick flash of the name of the list item.

I'm not sure my original issue was because of steamtinkerlaunch, could've been that I messed up my game prefix at some point.

Latest version still displays fine in a Ubuntu test setup I did a while ago. I can't really help with such problems.

[Torwak]

I understand, linux isn't officially supported. Thank's for the replies anyways, they helped me get this far. By the way, is Dyndolod supposed to run for over 16h? I used medium preset and use LOD level 32 according to A Clear Map of Skyrim and Other Worlds. I have a few big mods that change the landscape & trees too:

• Nature of the Wild Lands - forest and trees improvement mod
• Enhanced Landscapes
• Folkvangr - Grass and Landscape Overhaul

I have a Ryzen 7 2700x CPU. It has now been over 16h since I started the generation.

Edited October 2, 2023 by m4DnZ
Forgot to add that I'm in the middle of lod generation

[sheson]

37 minutes ago, m4DnZ said:

I understand, linux isn't officially supported. Thank's for the replies anyways, they helped me get this far. By the way, is Dyndolod supposed to run for over 16h? I used medium preset and use LOD level 32 according to A Clear Map of Skyrim and Other Worlds. I have a few big mods that change the landscape & trees too:

• Nature of the Wild Lands - forest and trees improvement mod
• Enhanced Landscapes
• Folkvangr - Grass and Landscape Overhaul

I have a Ryzen 7 2700x CPU. It has now been over 16h since I started the generation.

It takes about 5-10 minutes for the vanilla game.

https://dyndolod.info/FAQ#Long-running-time-or-output-several-GB-in-file-size

 

[chrysopoeia]

Having gotten all other tools to function in making a custom list based on NGVO, including TexGen, I've found myself unable to make DynDOLOD function at all on Linux.

When initializing LODGenx64.exe prior to the expert menu appearing, DynDOLOD returns the error C0000135, which I understand to indicate that .NET is missing or the wrong version.

I have tried installing both the 4.81 framework and 6.0 runtime. I have done this via the winetricks GUI for my default wine prefix, via the protontricks GUI for my specific MO2 prefix, and by using Microsoft's installers for both options on both of those prefixes. The installers ran to completion, though 4.81 framework required me to try again with the offline installer, since the web version couldn't download some files. As far as I can tell, both .NET versions are fully installed in both prefixes. I've tried running DynDOLOD via MO2 both through Steam and through Wine, though this doesn't affect the outcome at all, it seems. I have been able to install dependencies for other tools such as Synthesis to success, though not .NET iirc.

Despite trying all of these steps, I still get the C0000135 error. Am I setting up .NET wrong, or is there something I can do to get DynDOLOD to recognize it? Could some other thing be causing this error?

DynDOLOD_SSE_log.txt: https://paste.ee/p/DUnGw64A
No LODGen log was produced, as it wasn't able to run.

[sheson]

29 minutes ago, chrysopoeia said:

Having gotten all other tools to function in making a custom list based on NGVO, including TexGen, I've found myself unable to make DynDOLOD function at all on Linux.

When initializing LODGenx64.exe prior to the expert menu appearing, DynDOLOD returns the error C0000135, which I understand to indicate that .NET is missing or the wrong version.

I have tried installing both the 4.81 framework and 6.0 runtime. I have done this via the winetricks GUI for my default wine prefix, via the protontricks GUI for my specific MO2 prefix, and by using Microsoft's installers for both options on both of those prefixes. The installers ran to completion, though 4.81 framework required me to try again with the offline installer, since the web version couldn't download some files. As far as I can tell, both .NET versions are fully installed in both prefixes. I've tried running DynDOLOD via MO2 both through Steam and through Wine, though this doesn't affect the outcome at all, it seems. I have been able to install dependencies for other tools such as Synthesis to success, though not .NET iirc.

Despite trying all of these steps, I still get the C0000135 error. Am I setting up .NET wrong, or is there something I can do to get DynDOLOD to recognize it? Could some other thing be causing this error?

DynDOLOD_SSE_log.txt: https://paste.ee/p/DUnGw64A
No LODGen log was produced, as it wasn't able to run.

Moved to the appropriate thread for the message. See posts above. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search

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

DynDOLOD seems to function fine. It is the command line tool LODGen that doers not work because a requirement for it is not working.
Terrain LOD meshes generated fine with xLODGen in the same prefix?

Neither .NET6 nor NET Framework 4.8 x64 versions seem to be properly installed in the prefix in which LODGenx64.exe is started.
AFAIK the framework 4.8 version of LODGen also works with mono.

[chrysopoeia]

12 minutes ago, sheson said:

Moved to the appropriate thread for the message. See posts above. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search

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

DynDOLOD seems to function fine. It is the command line tool LODGen that doers not work because a requirement for it is not working.
Terrain LOD meshes generated fine with xLODGen in the same prefix?

Neither .NET6 nor NET Framework 4.8 x64 versions seem to be properly installed in the prefix in which LODGenx64.exe is started.
AFAIK the framework 4.8 version of LODGen also works with mono.

My mistake, here is a debug log: https://paste.ee/p/AeDPkZwi

xLODGen worked/works as intended.

I've tried installing mono, to no effect. I suppose the issue is with the install then, though I can't figure out how so or what to do.

[chrysopoeia]

Putting this in a separate post. As my previous hasn't yet been approved, so I cannot edit or delete it:

I nuked my Steam prefix for MO2, and re-ran SulfurNitride's NaK. This, I presume, properly installed .NET as required. It is possible that I may have messed up my prefix in the interim, after having originally set it up using that app.

That said, I have a new error for LODGenx64.exe, C0000005. This now happens every time. I will look for the proper thread to continue this discussion and post my logs.

[chrysopoeia]

Log: https://paste.ee/p/QQfrnWVg

Debug log: https://paste.ee/p/ntejwHT4

When launching DynDOLOD via MO2 via Proton on Linux, it returns the error code C0000005 for LODGenx64.exe after loading all plugins. I don't think this is analogous to other reports of this code, which regard Texconv or are mid-generation. I have run DynDOLOD successfully on Windows on the same hardware, so I presume this is a Linux or dependency issue, rather than hardware-related.

Edit: Never mind, I found a solution, also resolving a C0000135 error I had due to a failed solution to this error.
1) I purged my Steam prefix for MO2.
2) I used ProtonUp to install Cachy Proton (despite not using CachyOS), then setting that as the compatibility tool for MO2 in Steam.
3) I ran this command, as suggested by SulfurNitride, who hadn't realized it didn't work for other Proton versions: protontricks appid -q fontsmooth=rgb xact xact_x64 vcrun2022 dotnet6 dotnet7 dotnet8 dotnet9 d3dcompiler_47 d3dx11_43 d3dcompiler_43 dotnet48

Edited June 12 by chrysopoeia
More specific title

[chrysopoeia]

50 minutes ago, chrysopoeia said:

Putting this in a separate post. As my previous hasn't yet been approved, so I cannot edit or delete it:

I nuked my Steam prefix for MO2, and re-ran SulfurNitride's NaK. This, I presume, properly installed .NET as required. It is possible that I may have messed up my prefix in the interim, after having originally set it up using that app.

That said, I have a new error for LODGenx64.exe, C0000005. This now happens every time. I will look for the proper thread to continue this discussion and post my logs.

I'm sorry, I don't know how to edit a post. That said, I found an actual solution that fixes both errors.

1) I purged my Steam prefix for MO2.
2) I used ProtonUp to install Cachy Proton (despite not using CachyOS), then setting that as the compatibility tool for MO2 in Steam.
3) I ran this command, as suggested by SulfurNitride, who hadn't realized it didn't work for other Proton versions: protontricks appid -q fontsmooth=rgb xact xact_x64 vcrun2022 dotnet6 dotnet7 dotnet8 dotnet9 d3dcompiler_47 d3dx11_43 d3dcompiler_43 dotnet48

[sheson]

The relevant libraries that need to be properly installed are dotnet48 for LODGenx64.exe, dotnet6 or dotnetdesktop6 for the alternative LODGenx64Win.exe, vcrun2022 for Texconv and DynDOLOD DLL NG.

https://dyndolod.info/Downloads

If LODGenx64.exe included in latest xLODGen works, so should be the LODGenx64.exe included in latest DynDOLOD.