Jump to content

Recommended Posts

Posted
24 minutes ago, MysticElodie said:

Looks like the meshes do have objSnow (or a variation) at all three levels, and nothing past the official plugins is overriding either snow shader on this profile.

image.thumb.png.a8d5e76c60ca21aa7c05f6fdfda81144.png  image.thumb.png.f05fe157cce24e231f51fd8d25489e2e.png

You should have the same problem with vanilla LOD meshes then?

Test with default INIs.

If that all works, upload the mentioned BTO files from the output.

Posted (edited)

Tested with the default Ultra INIs, no luck there. Disabling DynDOLOD's output files makes the snow appear as you'd expect from the vanilla LODs.

Noticed glancing again at the meshes that the LOD4 mountain's BSSubIndexTriShape has the name "objSnow-LargeRefobjSnowHD-LargeRef", which doesn't quite look right? But I'm not sure if that's anything.

meshes.zip

Edited by MysticElodie
Posted
30 minutes ago, MysticElodie said:

Tested with the default Ultra INIs, no luck there. Disabling DynDOLOD's output files makes the snow appear as you'd expect from the vanilla LODs.

Noticed glancing again at the meshes that the LOD4 mountain's BSSubIndexTriShape has the name "objSnow-LargeRefobjSnowHD-LargeRef", which doesn't quite look right? But I'm not sure if that's anything.

meshes.zip 2.87 MB · 0 downloads

That really doesn't look alright. Let me check the files.

Posted
1 hour ago, MysticElodie said:

Tested with the default Ultra INIs, no luck there. Disabling DynDOLOD's output files makes the snow appear as you'd expect from the vanilla LODs.

Noticed glancing again at the meshes that the LOD4 mountain's BSSubIndexTriShape has the name "objSnow-LargeRefobjSnowHD-LargeRef", which doesn't quite look right? But I'm not sure if that's anything.

meshes.zip 2.87 MB · 1 download

Fixed in Alpha-84.

If you backup and restore the content of the folder ..\DynDOLOD\Edit Scripts\Export\*.*, then you can just "Execute LODGen" for the worldspace(s) in expert mode to update the object LOD meshes only. https://dyndolod.info/Help/Expert-Mode

Posted

Hi, hope you're doing well. The texgenx64 works swimmingly for me but my dyndolod (newest version) refuses to run at all. This error persists no matter what I do,

Access violation at address 000000000191D60A in module 'DynDOLODx64.exe'. Read of address 0000000000000000
Error: Access violation at address 000000000191D60A in module 'DynDOLODx64.exe'. Read of address 0000000000000000.
User says "OK"
 

I tried turning off my anti-virus, and adding Dyndolod to the exceptions list, and running it and MO2 as admin but nothing seems to work ;(. Thanks for any help!

Posted
20 minutes ago, EvilBob773 said:

Hi, hope you're doing well. The texgenx64 works swimmingly for me but my dyndolod (newest version) refuses to run at all. This error persists no matter what I do,

Access violation at address 000000000191D60A in module 'DynDOLODx64.exe'. Read of address 0000000000000000
Error: Access violation at address 000000000191D60A in module 'DynDOLODx64.exe'. Read of address 0000000000000000.
User says "OK"
 

I tried turning off my anti-virus, and adding Dyndolod to the exceptions list, and running it and MO2 as admin but nothing seems to work ;(. Thanks for any help!

Read the first post which log and debug log and bugreport.txt if it exists to upload when making reports.

Posted
14 minutes ago, EvilBob773 said:

Hi, my mistake sorry :P.

The DynDOLOD_SSE_Debug_log - https://pastebin.com/BYAP9iWG
and the DynDOLOD_SSE_log - https://pastebin.com/pvMVyi2m

Thanks very much for any assistance :)

DynDOLOD_SSE_Debug_log.txt 340.87 kB · 0 downloads DynDOLOD_SSE_log.txt 333.86 kB · 0 downloads

Is there no bugreport.txt in the same folder as the executables?

No necessarily related but the game shouldn't be installed into special Windows folders like Program Files x86 to avoid issue with UAC, antivir etc.

Posted
14 minutes ago, EvilBob773 said:

No, I can only see two files in the logs folder.

Please carefully read what I wrote ("in the same folder as the executables", e.g. DynDOLODx64.exe) and what the first post says the path (..\DynDOLOD\bugreport.txt) is supposed to be for it.

Posted
19 minutes ago, sheson said:

Thanks. Did you unpack the Standalone into a new empty folder or where there old files from an earlier version?

Edit: Remove -PseudoESL from the command line options.

ooo yes that worked, thank you very much, hope everything goes swimmingly now :fingerscrossed:!

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

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