The designated write target "*" is not enabled

[JaxonHellsing]

I recently generated a new Texgen Output file and replaced my old one, it was working fine before. But now when I try to run Texgen again it says it's not enabled/empty when it isn't. I don't even know what to do with this, or how to even solve it. I've never had this issue before. As I'm typing this, it's saying the same thing with Dyndolod if I try to change the stuff in my mod organizer executables, and I haven't even changed anything in that.

  On 4/13/2025 at 7:38 PM, JaxonHellsing said:

I recently generated a new Texgen Output file and replaced my old one, it was working fine before. But now when I try to run Texgen again it says it's not enabled/empty when it isn't. I don't even know what to do with this, or how to even solve it. I've never had this issue before. As I'm typing this, it's saying the same thing with Dyndolod if I try to change the stuff in my mod organizer executables, and I haven't even changed anything in that.

Expand  

Well, I removed and re-added them and it seems to have fixed it, but I'm unsure if it won't happen again

[z929669]

  On 4/13/2025 at 7:38 PM, JaxonHellsing said:

I recently generated a new Texgen Output file and replaced my old one, it was working fine before. But now when I try to run Texgen again it says it's not enabled/empty when it isn't. I don't even know what to do with this, or how to even solve it. I've never had this issue before. As I'm typing this, it's saying the same thing with Dyndolod if I try to change the stuff in my mod organizer executables, and I haven't even changed anything in that.

Well, I removed and re-added them and it seems to have fixed it, but I'm unsure if it won't happen again

Expand  

It's not at all clear what issue you are having. First, provide your logs as described in the parent forum.

You generated TexGen output evidently, so why are you trying to generate another? Are you running DynDOLOD after generating TexGen output?

Logs will provide the answers if you can't explain the problem more clearly.

[JaxonHellsing]

  On 4/13/2025 at 8:43 PM, z929669 said:

It's not at all clear what issue you are having. First, provide your logs as described in the parent forum.

You generated TexGen output evidently, so why are you trying to generate another? Are you running DynDOLOD after generating TexGen output?

Logs will provide the answers if you can't explain the problem more clearly.

Expand  

I don't know how to share logs, as in, it didn't really give me any for this issue this time. But I was generating it again because I wasn't thinking when I downloaded more mods. So I don't even know how to explain this bug, it was very weird. All I know is I generated a new texgen output, replaced the modlists base one, forgot I downloaded more mods, tried to run it and it thought I didn't have Dyndolod or Texgen output and also thought they were empty. What I did to fix this was removed the executables and re-added them to the executables list

[sheson]

  On 4/13/2025 at 8:58 PM, JaxonHellsing said:

I don't know how to share logs, as in, it didn't really give me any for this issue this time. But I was generating it again because I wasn't thinking when I downloaded more mods. So I don't even know how to explain this bug, it was very weird. All I know is I generated a new texgen output, replaced the modlists base one, forgot I downloaded more mods, tried to run it and it thought I didn't have Dyndolod or Texgen output and also thought they were empty. What I did to fix this was removed the executables and re-added them to the executables list

Expand  

The message was from MO2 and not TexGen.

You are not supposed to use the Create files in mod instead of overwrite option of MO2 with xLODGen, TexGen or DynDOLOD but always generate into a dedicated output folder outside of MO2, mods and game folders with the -o command line argument for xLODGen and the built-in output folder UI option of TexGen/DynDOLOD.