DynDOLOD 3.00 Alpha 198

[sheson]

2 hours ago, ButchDiavolo said:

Thank you for your reply. Since you also didn't have this issue, I figured something in my set up was wrong. So I decided to reinstall the mods involved and DynDOLOD. I ran TexGen again and had no warnings!

Then I remembered that I had forgotten to change the ini's to what STEP advises and re-ran TexGen, which promptly brought the errors back... Figuring the issue concerns trees, opaque pixels/ transparency (=alpha right?) and STEP advising to set "TreeMSAlphaThreshold=144", I changed that back to the original 96 and it works again. Still no idea why just those two billboards were affected though. I then ran DynDOLOD and again no errors this time.

Thank you for pointing me in the right direction!

As I suggested, check the preview. Comparing them might show a difference, though it is possible the TreeMSAlphaThreshold setting is only really visible in the generated billboard. The billboards most likely have a high transparent to opaque pixel ratio and by changing the threshold it will be over the BillboardDiscardRatio. You could lower it to have the billboards still be generated and then check the result.

The settings of modding guides typically apply to the specific mods and setup of the guide. It would be a good idea to learn what settings do before changing them for custom load orders.

[SkyKatarsis]

В 26.10.2023 в 11:22, Шесон сказал:

Завершите или не устанавливайте мусорное ПО от AMD, как описано на https://dyndolod.info/FAQ#Long-running-time-or-output-several-GB-in-file-size . странице
Известно, что мусорное ПО, установленное вместе с графическими драйверами, увеличивает время работы. Выполняйте чистую установку только последней рекомендованной или официальной версии драйвера. Не устанавливайте поставку ненужного ПО вместе с драйверами и не прекращайте ее работу перед запуском инструментов.

Рассмотрите возможность установки .NET Runtime 7, как описано на   https://dyndolod.info/Downloads#Additional-Requirements . странице

Thanks for the answer.  But I don’t understand why lodes were generated before, but now they are not.  Runtime 7 is installed.  I'm not a native speaker and didn't quite understand about junk software.  Please clarify.  I killed a few days, but I couldn’t make lods like before.  Once, by some miracle, the logs were still generated and quickly, but I forgot about the ini I needed in Markarth, so that the suburb could be seen from the patio of my house.  From that moment on, several days of unsuccessful attempts and wasted time. The generation lods simply freezes and does not move for a large number of hours.

[sheson]

11 hours ago, SkyKatarsis said:

Thanks for the answer.  But I don’t understand why lodes were generated before, but now they are not.  Runtime 7 is installed.  I'm not a native speaker and didn't quite understand about junk software.  Please clarify.  I killed a few days, but I couldn’t make lods like before.  Once, by some miracle, the logs were still generated and quickly, but I forgot about the ini I needed in Markarth, so that the suburb could be seen from the patio of my house.  From that moment on, several days of unsuccessful attempts and wasted time. The generation lods simply freezes and does not move for a large number of hours.

https://dyndolod.info/FAQ#Long-running-time-or-output-several-GB-in-file-sizehttps://dyndolod.info/FAQ#Long-running-time-or-output-several-GB-in-file-size
Crapware installed with graphics drivers is known to prolong running times. Do a clean install of the latest recommended or official driver only. Do not install crapware shipping with the drivers or terminate it before running the tools.

Make a driver only installation or terminate all programs that were installed with the graphics driver. https://imgur.com/14VpsWk

[SkyKatarsis]

27 минут назад, Шесон сказал:

https:// dyndolod .info/FAQ#Long-running-time-or-output-several-GB-in-file-sizehttps:// dyndolod .info/FAQ#Long-running-time-or-output-several-GB-in-file-size
Известно, что мусорное ПО, установленное вместе с графическими драйверами, увеличивает время работы. Выполняйте чистую установку только последней рекомендованной или официальной версии драйвера. Не устанавливайте поставку ненужного ПО вместе с драйверами и не прекращайте ее работу перед запуском инструментов.

Выполните установку только драйвера или закройте все программы, которые были установлены с графическим драйвером. https://imgur.com/14VpsWk

I read this, but I don’t understand what exactly it means.  And it is not clear why earlier with the same software it was generated quickly, but now it is not.  In 8 hours a miracle happened, the lod was generated, but I got an error im Whiterun:

https://ibb.co/hX5BRmH

Could this error have been affected by the setting in DynDOLOD_SSE_childworld_WhiterunDragonsreachWorld ScanChild=1 ?

 

Also, Windhelm always generates the wrong lode:

https://ibb.co/9Zm0Y1d

https://ibb.co/xF0cCJY

 

I really appreciate your help and creating the much needed DynDOLOD.

[sheson]

1 hour ago, SkyKatarsis said:

I read this, but I don’t understand what exactly it means.  And it is not clear why earlier with the same software it was generated quickly, but now it is not.  In 8 hours a miracle happened, the lod was generated, but I got an error im Whiterun:

https://ibb.co/hX5BRmH

Could this error have been affected by the setting in DynDOLOD_SSE_childworld_WhiterunDragonsreachWorld ScanChild=1 ?

 

Also, Windhelm always generates the wrong lode:

https://ibb.co/9Zm0Y1d

https://ibb.co/xF0cCJY

 

I really appreciate your help and creating the much needed DynDOLOD.

If the tools experience a long running time, then the first thing to do, is to do a clean install of the graphics driver only. Alternatively terminate all the crapware that is shown in the screenshot via task manager so they are not running when using the tools.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to make useful in game screenshots with more informative console and textual explanations of what is being shown. The screenshot of Whiterun is pretty much self explanatory, however the screenshots from Windhelm are not. Also compare Windhelm to vanilla. The only way for it to have a good representation in Tamriel is to use Open/Exterior Cities.

Do not set ScanChild=1 in DynDOLOD_SSE_childworld_WhiterunDragonsreachWorld.ini
Do not set ScanChild=0 in DynDOLOD_SSE_childworld_WhiterunWorld.ini
Only one child worldspace in an overlapping area should be scanned and it needs to be WhiterunWorld in this case, so it works with the mesh mask/reference rules.

[SkyKatarsis]

Thanks for the answer, but in Windhelm the console was unable to capture these places, so it was not possible to take such a screenshot with it.

[sheson]

1 hour ago, SkyKatarsis said:

Thanks for the answer, but in Windhelm the console was unable to capture these places, so it was not possible to take such a screenshot with it.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts.

https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots
A screenshot alone does not substitute describing the issue with text. 
If making screenshots of the LOD area, also make screenshots of the close-up object or full model for comparison.
Note that tree LOD or object LOD does not have a form ID. To determine if something is LOD, toggle LOD on/off with tll in console. In that case, also walk close to an object, so its reference with the full model is loaded in order to get its form ID and provide that screenshot of the full model in addition to the screenshot of the LOD.

[SkyKatarsis]

21 час назад, Шесон сказал:

Прочтите первое сообщение и/или https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs . сообщений записывают в журнал и журнал отладки для , которые DynDOLOD загрузки при создании

https:// dyndolod .info/Official- DynDOLOD -Support-Forum#In-Game-Screenshots
Снимок экрана сам по себе не заменяет текстовое описание проблемы.
Если вы делаете скриншоты области LOD, сделайте также скриншоты объекта крупным планом или полной модели для сравнения.
Обратите внимание, что уровень детализации дерева или объекта не имеет идентификатора формы. Чтобы определить, является ли что-то LOD, включите/выключите LOD с помощью tll в консоли. В этом случае также подойдите близко к объекту, чтобы загрузить его ссылку с полной моделью, чтобы получить идентификатор формы и предоставить этот снимок экрана полной модели в дополнение к снимку экрана LOD.

https://drive.google.com/file/d/1NcxpfjuWJg3GgUj8lxUdAUPuK7NLZN64/view?usp=sharing - my reports

The last 3 generations did not work, twice DynDOLOD closed spontaneously in the middle of the process without notifications.
 
 Once again I was stuck for several hours on the ..._glow.dds recording, without moving (such freezing can extend up to 1.5 days).

https://ibb.co/jvPG9rD
 
From the miraculously obtained last generation of lods, a bug arose with the tree, its lods turned black, previously they were generated absolutely correctly.  There is no way to take a useful screenshot of the lods of this tree.

https://ibb.co/M735k47

I looked at Windhelm without lods, in vanilla it has a similar terrible look.  I use the flight function in the game, so I can see all these things right away.  Open cities are not an option for me, because...  there are no patches for my number of mods (~1800).

Previously, DynDOLOD worked without such problems.  And even now DynDOLOD can miraculously generate everything as before in a little over an hour or in 8 hours, depending on your luck, but in 95% it just freezes for up to 1.5 days no results or closes spontaneously.  In general, I really need your help, because the situation is very difficult for my nerve cells Sorry for my bad English.

Thank you in advance.

[sheson]

30 minutes ago, SkyKatarsis said:

https://drive.google.com/file/d/1NcxpfjuWJg3GgUj8lxUdAUPuK7NLZN64/view?usp=sharing - my reports

The last 3 generations did not work, twice DynDOLOD closed spontaneously in the middle of the process without notifications.
 
 Once again I was stuck for several hours on the ..._glow.dds recording, without moving (such freezing can extend up to 1.5 days).

https://ibb.co/jvPG9rD
 
From the miraculously obtained last generation of lods, a bug arose with the tree, its lods turned black, previously they were generated absolutely correctly.  There is no way to take a useful screenshot of the lods of this tree.

https://ibb.co/M735k47

I looked at Windhelm without lods, in vanilla it has a similar terrible look.  I use the flight function in the game, so I can see all these things right away.  Open cities are not an option for me, because...  there are no patches for my number of mods (~1800).

Previously, DynDOLOD worked without such problems.  And even now DynDOLOD can miraculously generate everything as before in a little over an hour or in 8 hours, depending on your luck, but in 95% it just freezes for up to 1.5 days no results or closes spontaneously.  In general, I really need your help, because the situation is very difficult for my nerve cells Sorry for my bad English.

Thank you in advance.

Either really make a clean driver only installation or terminate all the crapware in task manager. https://imgur.com/14VpsWk
https://dyndolod.info/FAQ#TexGen-DynDOLOD-stuck-while-creating-textures

Black textures are typically either running out of VRAM in the game or there might have been errors when textures and/or LOD was generated. No TexGen/DynDOLOD logs and debug logs were provided for the "successful" generation.

[SkyKatarsis]

3 часа назад, Шесон сказал:

Либо действительно сделайте чистую установку драйверов, либо удалите весь мусор в диспетчере задач. https://imgur.com/14VpsWk
https:// dyndolod .info/FAQ#TexGen- DynDOLOD -stuck-while-creating-textures

Черным текстурам обычно либо не хватает видеопамяти в игре, либо могли возникнуть ошибки при создании текстур и/или уровня детализации. не было предоставлено журналов TexGen/ DynDOLOD Для «успешной» генерации и журналов отладки.

Thanks for the quick response.  I completed the processes you specified, performed a clean reinstall, reinstalled the video card driver, but DynDOLOD stopped generating at all, it closes in the middle of the process.  The folder DynDOLOD_Output contains created meshes and textures, but ESM, ESP and occlusions are not created.

date/time          : 2023-11-04, 02:35:50, 509ms
command line       : "D:\Modding\DynDOLOD 3.00-68518-Alpha-155\DynDOLODx64.exe" -sse
executable         : DynDOLODx64.exe
exec. date/time    : 2023-10-11 04:00
version            : 3.0.0.155
compiled with      : Delphi 11
madExcept version  : 5.1.2
callstack crc      : $07fa6911, $b095d5a8, $398ad257
exception number   : 1
exception class    : Exception
exception message  : OpenGL: недопустимая операция (operation is not allowed) for 0AE877F9 while processing 0AE877F9 (4).

I don't know how to fix this What am I doing wrong?

[sheson]

46 minutes ago, SkyKatarsis said:

Thanks for the quick response.  I completed the processes you specified, performed a clean reinstall, reinstalled the video card driver, but DynDOLOD stopped generating at all, it closes in the middle of the process.  The folder DynDOLOD_Output contains created meshes and textures, but ESM, ESP and occlusions are not created.

date/time          : 2023-11-04, 02:35:50, 509ms
command line       : "D:\Modding\DynDOLOD 3.00-68518-Alpha-155\DynDOLODx64.exe" -sse
executable         : DynDOLODx64.exe
exec. date/time    : 2023-10-11 04:00
version            : 3.0.0.155
compiled with      : Delphi 11
madExcept version  : 5.1.2
callstack crc      : $07fa6911, $b095d5a8, $398ad257
exception number   : 1
exception class    : Exception
exception message  : OpenGL: недопустимая операция (operation is not allowed) for 0AE877F9 while processing 0AE877F9 (4).

I don't know how to fix this What am I doing wrong?

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log, debug log and enitre bugreport.txt (if it exists) to upload.

[SkyKatarsis]

3 hours ago, sheson said:

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log, debug log and enitre bugreport.txt (if it exists) to upload.

https://drive.google.com/file/d/1Um-rdmMZ24yNKETYl0xDxFHpC_LY8mtl/view?usp=sharing

I already sent reports today, I am providing updated ones again. Thanks.

[sheson]

55 minutes ago, SkyKatarsis said:

https://drive.google.com/file/d/1Um-rdmMZ24yNKETYl0xDxFHpC_LY8mtl/view?usp=sharing

I already sent reports today, I am providing updated ones again. Thanks.

Those seem to be the same log, debug log and bugreport.txt uploaded earlier today which show that crapware is installed and active.

Assuming you now have a clean driver only install or terminated the crapware:
Delete the log folder. Delete bugreport.txt. Run DynDOLODx64.

If there is an error, upload the new log, debug log and bugreport.txt 
If the tool seems to be stuck, read https://dyndolod.info/FAQ#TexGen-DynDOLOD-stuck-while-creating-textures

[SkyKatarsis]

No, I have attached all the updated files.  This is probably because all attempts to generate logs were unsuccessful and none were completed; DynDOLOD simply closed spontaneously 4 times.

[sheson]

1 hour ago, SkyKatarsis said:

No, I have attached all the updated files.  This is probably because all attempts to generate logs were unsuccessful and none were completed; DynDOLOD simply closed spontaneously 4 times.

Assuming you now have a clean driver only install or terminated the crapware:
Delete the log folder. Delete bugreport.txt. Run DynDOLODx64.

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs
The log and debug log are saved when the program shuts down. Do not interrupt the shut down process so it can write the log files. If there are no logs or debug logs because the tool is being terminated prematurely, check the Windows Event log for related messages. Add RealTimeLog=1 under [TexGen] or [DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\[TexGen|DynDOLOD]_[GAME MODE].INI respectively. Then execute the tool again to generate a debug log in the Logs folder in real time and upload that.