Jump to content

DynDOLOD 3.00 Alpha 169


sheson

Recommended Posts

15 hours ago, sheson said:

If you are following a third party guide, you need to ask qestions about it on its forum section.

https://dyndolod.info/Generation-Instructions
Finalize the load order as explained in the prerequisites above. Make sure all mods, plugins and patches (that affect affect trees, grasses or any textures) are enabled and their overwrite order is sorted. Ignore wrong 3rd party advice to temporarily disable plugins, mods, meshes or textures. Such advice is categorically wrong or outdated. In case of issues, solve the cause or use appropriate rules or settings for desired results. Disabling plugins, mods, meshes or textures is a troubleshooting step and not a fix. In case of problems or questions, use the official DynDOLOD support forum for qualified help and advice.

However:

https://dyndolod.info/Help/xLODGen#Requirements
Remove or disable the plugin after terrain LOD generation. No harm done if loaded in-game. Typically the player can not get close to these areas. There are no effects outside the far away added cells.

https://dyndolod.info/Mods/Waterfalls
Bright Waterfall Fix for ENB - do not install DynDOLOD Bright LOD Waterfall Fix

Thank you very much for all your help. It turns out the issue with DynDOLOD not recognizing my LODs and billboards was due to the fact that when I converted my TexGen_Output files with Texconv, the Texconv_Output files didn't include the associated .ini and .txt files. The solution was to copy everything in the TexGen_Output folder and paste it in the Texconv_Output folder WITHOUT replacing anything already there (just adding all of those missing .ini and .txt files to the converted .dds files). Everything works and is looking great.

Hope this info is useful to you and the people you help.

Link to comment
Share on other sites

Hi Sheson,

I ran Dyndolod a few more times here are two more bugreports that I encountered with the alpha 115. The problem is most likely with amd drivers, but want to give you some feedback I am using the driver only version of 23.2.1.

error: Assertion Failure

https://ufile.io/jdduc6g4

error: OpenGL invalid operation exception

https://ufile.io/jdduc6g4

Best,

LoooneyTunes

 

copied the wrong file here is the OpenGL exception

https://ufile.io/ub4rn1i8

Link to comment
Share on other sites

My DynDOLOD_Output file isnt getting recognized in Vortex's Lod Rules Esp,Esm, and Occlusion plugins do show up but when i launch the game Dyndolod dosent recognize my LOD generation and is unticked in the MCM which causes my LODS to Flicker. never had this issue before until i updated Dyndolod 3 to Alpha version 115
Link to comment
Share on other sites

2 hours ago, LoooneyTunes said:

Hi Sheson,

I ran Dyndolod a few more times here are two more bugreports that I encountered with the alpha 115. The problem is most likely with amd drivers, but want to give you some feedback I am using the driver only version of 23.2.1.

error: Assertion Failure

https://ufile.io/jdduc6g4

error: OpenGL invalid operation exception

https://ufile.io/jdduc6g4

Best,

LoooneyTunes

 

copied the wrong file here is the OpenGL exception

https://ufile.io/ub4rn1i8

These crashes seem to be all over the place. Check for CPU / main memory problems from overclocking, some kind of boost for example.

Link to comment
Share on other sites

5 hours ago, emtz9393 said:
My DynDOLOD_Output file isnt getting recognized in Vortex's Lod Rules Esp,Esm, and Occlusion plugins do show up but when i launch the game Dyndolod dosent recognize my LOD generation and is unticked in the MCM which causes my LODS to Flicker. never had this issue before until i updated Dyndolod 3 to Alpha version 115

Merged into the DynDOLOD Alpha 115 topic.

Please see the OP and post your logs as indicated there.

Link to comment
Share on other sites

17 minutes ago, star_death69 said:

Went through without an exception,

MaxTextureIndex=4
RenderThreads=2

Logs_20230222_1520.7z 603.73 kB · 1 download

Great.

Make the INI default (from Alpha-115) and use this test version https://mega.nz/file/hUBFGD5C#UKoDN3CpIPDrmojYmp8zqn8WLu9VmsFs9FPF4EuFQMg

if it also runs through, it should be fixed for good.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.