I have read through the forums and searched this topic. I understand that Skyrim does not differential near grid from far grid but only uGrids from far grid, so dynamic LOD only applies outside of uGrids. Skyrim SE differentiates uGrids, near grid, and far grid
I still don't fully comprehend:
Quote
As a rule of thumb, check the box "Upgrade NearGrid Large Refs" in case the large reference system is not used - uLargeRefLODGridSize = uGridsToLoad - to make sure all references receive dynamic LOD as intended. The result would be LOD working the same as it did in Skyrim.
Vice versa, do not check the box "Upgrade NearGrid Large Refs" in case the large referene system is used - uLargeRefLODGridSize > uGridsToLoad >= 5. Upgrading large references that were intended for NearGrid means more resource usage in case the large reference system is used. References that are intended for NearGrid are typically smaller and it generally makes not much sense to show them beyond the large reference grid.
...
In the Skyrim version the NearGrid and FarGrid of the dynamic LOD system start right beyond the uGridsToLoad. In Skyrim Special Edition the FarGrid starts beyond the uLargeRefLODGridSize, while the NearGrid still starts beyond the uGridsToLoad.
This means that for a worldspace which has any large refrences, the dynamic LOD for a large reference is always assigned to FarGrid, while dynamic LOD for normal reference is always assigned to the NearGrid. Consequently this will overwrite mesh rules grid settings automatically on a per reference basis as needed. If the worldspace has no large references, the grid settings are used as intended.
For example, a mesh rule might define "Far LOD" or "Far Full" for a mesh in case it needs to be dynamic LOD. If the reference using this mesh is not a large reference, it will automatically assigned to the NearGrid.
Checking the box
Does this automatically set uLargeRefLODGridSize = uGridsToLoad in the background, because the settings GUI do not reflect this ... perhaps it is advice to consider doing so manually?
"Near Grid" = uLargeRefLODGridSize?
This claims "better visualizations" in the DynDOLOD GUI, can you elaborate?
A large ref object is flagged as such by the plugin, and it has LOD:
what happens inside uGrids and uLargeRefLODGridSize? Potential for z-fight only in the latter? Setting both to '5' resolves? At what cost to visualizations and/or performance?
What is the advantage of SSE uLargeRefLODGridSize (pretend the large ref bug doesn't exist and this works perfectly)
What is the disadvantage, given the LR bug in SE?
NOT checking the box
"in case the large referene system is used" - in SE the large reference system IS used, so this phrase confuses me.
Mesh rule assigning a large ref to near grid will be overriden and vice versa?
This setting is ideal if and only if all large refs are flagged properly by the 'winning' plugin? (otherwise, either fix each or "check the box"?
*For best quality it seems that "Upgrade NearGrid Large Refs" SHOULD be ticked and uLargeRefLODGridSize > uGridsToLoad >= 5 ... is this correct? Is the caveat that there may be some z-fighting for large refs improperly flagged?
*For best performance, it seems like "Upgrade NearGrid Large Refs" SHOULD NOT be ticked and uLargeRefLODGridSize > uGridsToLoad >= 5 STILL should be used. To avoid the LOD/full large ref conflic problem, then we can do uLargeRefLODGridSize = uGridsToLoad to fix the large ref issue at the cost of some performance ... is this correct?
Question
z929669
I have read through the forums and searched this topic. I understand that Skyrim does not differential near grid from far grid but only uGrids from far grid, so dynamic LOD only applies outside of uGrids. Skyrim SE differentiates uGrids, near grid, and far grid
I still don't fully comprehend:
Checking the box
NOT checking the box
*For best quality it seems that "Upgrade NearGrid Large Refs" SHOULD be ticked and uLargeRefLODGridSize > uGridsToLoad >= 5 ... is this correct? Is the caveat that there may be some z-fighting for large refs improperly flagged?
*For best performance, it seems like "Upgrade NearGrid Large Refs" SHOULD NOT be ticked and uLargeRefLODGridSize > uGridsToLoad >= 5 STILL should be used. To avoid the LOD/full large ref conflic problem, then we can do uLargeRefLODGridSize = uGridsToLoad to fix the large ref issue at the cost of some performance ... is this correct?
3 answers to this question
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now