chrysopoeia

I'm experiencing the same error that mom_san seems to have had, though I am using Linux and wouldn't be surprised if it is a result of that. This recurs each time. All DynDOLOD files are up to date, I have never had old versions of these files (I set up my OS and NGVO after the last updates), and I tried reinstalling both by nxm_handler and manually. I have verified that the nif in question appears correctly in the MO2 virtual data folder. I tried shortening the file path on my OS (not the unchangeable virtual path displayed here, that is), and this got past this initial error but returned many missing meshes/textures after launching generation, and then reverted to the error displayed here after that one aborted run. I have since reverted the file path back to the original, under the assumption that it did not fix anything. No other possible errors pointed to by the troubleshooting guide seem to apply. Debug log: https://paste.ee/p/cMdVHQJ8 Log: https://paste.ee/p/h9gYrrE3

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

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

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.

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.

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.