DynDOLOD 3.00 Alpha 182

[NBBEAST]

I downloaded a retexture mod for moonpath to elsweyr and I'm greeted by this message when trying to run texgen :

[Window Title]
TexGen

[Main Instruction]
Error: OpenGL: invalid enumerant.

[Exit TexGen]

[Footer]
Online Manual | Support Forum | Copy message to clipboard. 

Edited April 30, 2022 by NBBEAST

[sheson]

29 minutes ago, DarthVitrial said:

Instant failure, should I not be using the dyndolod exe from here: https://stepmodifications.org/forum/topic/16796-dyndolod-3-alpha-88/page/284/?tab=comments#comment-259338?

bugreport.txt 425.01 kB · 0 downloads Logs.7z 1.19 MB · 0 downloads

This range error has nothing to do with the LODGen I uploaded.

Try again, see if it happens again. It is probably a rare race condition I will fix for next Alpha.

Use expert mode. Execute LODGen.
 

[NBBEAST]

Plus if I want ultra trees, I know I need to enable hd trees within texgen, but do I disable regular tree lod as well and thus only have hd trees enabled or should I have both enabled for ultra trees? Thanks. 

[sheson]

26 minutes ago, NBBEAST said:

I downloaded a retexture mod for moonpath to elsweyr and I'm greeted by this message when trying to run texgen :

[Window Title]
TexGen

[Main Instruction]
Error: OpenGL: invalid enumerant.

[Exit TexGen]

[Footer]
Online Manual | Support Forum | Copy message to clipboard. 

Read the first post which log, debug log and bugreport.txt to upload when making posts.

Using search as explained in the first finds this https://stepmodifications.org/forum/topic/16796-dyndolod-3-alpha-88/?do=findComment&comment=255045

[DarthVitrial]

29 minutes ago, sheson said:

This range error has nothing to do with the LODGen I uploaded.

Try again, see if it happens again. It is probably a rare race condition I will fix for next Alpha.

Use expert mode. Execute LODGen.
 

Rare race condition aside it worked perfectly, generated seasons and everything. Looks like converting to .net 6 did it.

[NBBEAST]

32 minutes ago, sheson said:

Read the first post which log, debug log and bugreport.txt to upload when making posts.

Using search as explained in the first finds this 

 

Sorry it slipped my mind. Here they are. Its not the same issue as that other person, as my integrated GPU is enabled and updated to latest driver, same with my GPU. Plus if I want ultra trees, I know I need to enable hd trees within texgen, but do I disable regular tree lod as well and thus only have hd trees enabled or should I have both enabled for ultra trees? Thanks.

TexGen_SSE_log.txt TexGen_SSE_Debug_log.txt

[NBBEAST]

I restarted my laptop and I don't get the error anymore when running texgen. 

Edited April 30, 2022 by NBBEAST

[adrianb]

alpha 88 seems to work fine again,  i dont know if it was the beta update or me removing the following mods:-

jk's all in one and all the patches

cfto and the patches

oh god more bees

skybirds

 

hope us on the beta windows 11 haven't caused you too much unnecessary work.

 

[DarthVitrial]

it might just be placebo, but I think the .net 6 version runs faster too.

[sheson]

6 hours ago, NBBEAST said:

I restarted my laptop and I don't get the error anymore when running texgen. 

The restart fixed that the system reported just "OpenGL version: 1.1.0", which is typically what the Windows fallback graphics driver reports. 

You could search the new debug log now for "OpenGL version" for the current version reported to see the difference.

[sheson]

7 hours ago, adrianb said:

alpha 88 seems to work fine again,  i dont know if it was the beta update or me removing the following mods:-

jk's all in one and all the patches

cfto and the patches

oh god more bees

skybirds

 

hope us on the beta windows 11 haven't caused you too much unnecessary work.

Local variables becoming undefined exceptions in LODGen are definitely not caused by mods.

It did cost quite some time/work, maybe more than I'd liked - including installing Windows 11 in a VM and then installing the insider preview, but I would not call it unnecessary. 

[sheson]

5 hours ago, DarthVitrial said:

it might just be placebo, but I think the .net 6 version runs faster too.

That's most likely because of different threadsplit defaults. Though long running generations with 3D tree LOD or grass LOD could be a couple minutes faster because of micro optimizations.

[Zahkrii]

23 hours ago, sheson said:

@DarthVitrial @adrianb @Zahkrii

It seems you have these problems because of Windows Insider Preview (Dev/Beta) 22593. It also updates .Net Framework 4.8 to a new build.

I see, I should have mentioned earlier that I was using the Insider Build. Thanks for painstakingly finding a reason for our problems lmao. Unfortunately for me it seems very difficult to revert to a non-insider preview build of windows. Guess I'll have to wait until it updates to a version that lets DynDOLOD work. But it seems strange how these builds f*cks processes like this entirely.

[sheson]

5 hours ago, Zahkrii said:

I see, I should have mentioned earlier that I was using the Insider Build. Thanks for painstakingly finding a reason for our problems lmao. Unfortunately for me it seems very difficult to revert to a non-insider preview build of windows. Guess I'll have to wait until it updates to a version that lets DynDOLOD work. But it seems strange how these builds f*cks processes like this entirely.

See this post https://stepmodifications.org/forum/topic/16796-dyndolod-3-alpha-88/?do=findComment&comment=259371

It worked for the other users.

[adrianb]

thanks, the new version works fine on windows 11 , seem a lot faster too