DynDOLOD 3.00 Alpha 196

[sheson]

8 hours ago, ikonomov said:

I've had issues before because of scaling in other programs, as everybody probably does on windows using anything other than 100%, but it's only really obvious when it's higher than say 150%, which I have on one computer connected to a 4k TV.  This is with the newest versions of xLODGen, DynDOLOD and TexGen.  If I'm not mistaken the previous version of DynDOLOD did not scale at all, possibly related to a newer MS visual studio C++ version used.  Maybe you can increase the text fields a little, to minimize the chances of it happening.  The screenshots were taken at 200% to make it more visible where it happens.

If the scaling causes issues in other programs it seems to me the OS is not doing it very well. Do you have a multi monitor setup with different resolutions?
You can always try to disable scaling on the Compatibility tab of a programs properties.

xEdit is compiled with Delphi.

[ikonomov]

Yep, scaling is just one more thing that the Win OS is not doing very well.  I'm not having a problem here, I'm using a single 27" 1440p monitor with 125% which is not causing issues for the vast majority of programs even if their scaling method is not 100% conforming to MS standards (whatever those may be).  The 4k monitor that I have on the other computer just made me aware about how bad scaling really is in Windows and made it easier for me to spot when it might cause issues beyond the 125% that I normally use.

Sadly Compatibility settings for high DPI haven't been working for some programs for a while now.  It used to be that if the OS detects that a program is not DPI aware it would simply scale its interface and everything would look blurry and upscaled but proportional to what it would look at 100%.  Then when you turned off scaling or gave application priority for scaling Windows would display it the same as it would be at 100%.  Not anymore, I'm not sure in what update they made the change, but now text is almost always upscaled according to the Windows DPI scaling regardless of compatibility settings for an individual program.  Programs that are not specifically designed to scale will either be blurry or text will be upscaled, sometimes not being able to fit inside its field.  At least that has been my experience with this after some testing and experimentation.

[sheson]

On 3/11/2021 at 2:38 PM, TheDude said:

Hm, also got the "FXGlow floating bulbs of light"-bug in Markarth, thats a first for me actually, didnt happen once with Dyndolod 2.xx...

https://imgur.com/a/h85x0WP

This will be fixed next version.

[IchWarte]

On 3/1/2021 at 2:29 PM, sheson said:

"LODGenx64.exe failed to generate object LOD for Tamriel" means that the output is incomplete, obviously.

Use the legal Steam version of the game.

Make sure there is enough space on the drive where DynDOLOD is installed and where the output folder is. Make sure the standalone archive is installed completely into an empty new folder.  Make sure the tools can write and read files.

well after a few days i found out that Enhance Ship of Solitude SSE is the reason, uninstall it made dyndolod work perfectly

[sheson]

2 hours ago, IchWarte said:

well after a few days i found out that Enhance Ship of Solitude SSE is the reason, uninstall it made dyndolod work perfectly

There error messages form the logs you posted tell a completely different story.

Unsurprisingly, LOD generation works fine with the mod. It is even requiring DynDOLOD for proper LODs.

[IchWarte]

16 hours ago, sheson said:

There error messages form the logs you posted tell a completely different story.

Unsurprisingly, LOD generation works fine with the mod. It is even requiring DynDOLOD for proper LODs.

i had no ideal seems like after rerun a few times, the bug report end up with only warship.nif unable to read beyond the end of the stream(i deleted the report when i fixed it by accident) repeatingly i noticed it and found out it was enhance ship so i deleted it ,now work like charm, daily skyrim i guess

[sheson]

6 minutes ago, IchWarte said:

i had no ideal seems like after rerun a few times, the bug report end up with only warship.nif unable to read beyond the end of the stream(i deleted the report when i fixed it by accident) repeatingly i noticed it and found out it was enhance ship so i deleted it ,now work like charm, daily skyrim i guess

Use the legal Steam version of the game. Make sure there is enough space on the drive where DynDOLOD is installed and where the output folder is. Make sure the standalone archive is installed completely into an empty new folder. Make sure the tools can write and read files.

There are obvious issues with files, the file system, antivir, UAC, crapware  etc. Fix the underlying issues to avoid such seemingly random problems.

[Maidenfan724]

Is it still possible to generate full model tree LOD? Ultra tree settings in the latest versions do not do this, and the ini file says not to change the settings that used to be required to generate them. I can't stand paper looking lod trees.

[sheson]

7 hours ago, Maidenfan724 said:

Is it still possible to generate full model tree LOD? Ultra tree settings in the latest versions do not do this, and the ini file says not to change the settings that used to be required to generate them. I can't stand paper looking lod trees.

Yes it is still possible, but it still isn't a solution, but for testing only. Instead create static and optimized tree LOD models. Also, generate HD billboards. They are better than normal ones.

The warning above the fallback setting to billboard/full model has always been in the INI.

[PRieST]

With alpha 31 the default TreeFullFallBack setting in the ini is: 'TreeFullFallBack=0'
Is this on purpose? (on version prior to alpha 31 it was always set to =1 if I remember correctly)

'Wizard' and 'Expert' modes are also both set to =1 by default, which I think shouldn't be?

And are these some of your debug options, this settings are also new:

[DynDOLOD]
;IgnoreLODModels=1
;CreateObjectLODAtlasMap=0
;CreateObjectLODAtlas=0
;DontMergeShapes=1
;RemoveUnseen=0
mipmaptests=-1
;DebugFormID=2048

 

Edited March 19, 2021 by PRieST

[SteveTownsend]

30 minutes ago, PRieST said:

With alpha 31 the default TreeFullFallBack setting in the ini is: 'TreeFullFallBack=0'
Is this on purpose? (on version prior to alpha 31 it was always set to =1 if I remember correctly)

'Wizard' and 'Expert' modes are also both set to =1 by default, which I think shouldn't be?

And are these some of your debug options, these are also new:

[DynDOLOD]
;IgnoreLODModels=1
;CreateObjectLODAtlasMap=0
;CreateObjectLODAtlas=0
;DontMergeShapes=1
;RemoveUnseen=0
mipmaptests=-1
;DebugFormID=2048

 

I've changed this locally in my .INI file to quiet the warning about overriding the default, I think you are right

[PRieST]

I installed the new resources (alpha 9), generated LOD via TexGen and wanted to create the LODs with DynDOLOD Alpha 31, but I ran into this error message:
'Item not found' - nothing more.

bugreport

DynDOLOD_SSE_log

FileUpload for DynDOLOD_SSE_Debug_log (too much text/too large filesize - 52 MB)

[sheson]

1 hour ago, PRieST said:

With alpha 31 the default TreeFullFallBack setting in the ini is: 'TreeFullFallBack=0'
Is this on purpose? (on version prior to alpha 31 it was always set to =1 if I remember correctly)

'Wizard' and 'Expert' modes are also both set to =1 by default, which I think shouldn't be?

And are these some of your debug options, this settings are also new:

[DynDOLOD]
;IgnoreLODModels=1
;CreateObjectLODAtlasMap=0
;CreateObjectLODAtlas=0
;DontMergeShapes=1
;RemoveUnseen=0
mipmaptests=-1
;DebugFormID=2048

 

Ups. Forgot to clean.

22 minutes ago, PRieST said:

I installed the new resources (alpha 9), generated LOD via TexGen and wanted to create the LODs with DynDOLOD Alpha 31, but I ran into this error message:
'Item not found' - nothing more.

bugreport

DynDOLOD_SSE_log

FileUpload for DynDOLOD_SSE_Debug_log (too much text/too large filesize - 52 MB)

Does it work with Grass=0?

[PRieST]

4 minutes ago, sheson said:

Does it work with Grass=0?

Yes.
Error on my end? The grass cache was generated freshly (and I did a run with it with alpha 30)

[sheson]

Just now, PRieST said:

Yes.
Error on my end? The grass cache was generated freshly (and I did a run with it with alpha 30)

Grass cache itself should not matter. This happens while building the texture atlas. I don't think I changed anything in regards to that.

is this just default verdant or did you do any changes to it (for example like updating object bounds to generate more grass billboards)?