![]()
|
|
Issue #1: Arthmoor concluded that this isn't something we can deal with on our end [Issue #25315].
I have a feeling that the second issue may not be resolvable either if the only "solution" is disabling that flag. We usually choose not to address issues that require correcting something at the cost of messing something else up. Since I'm not all that knowledgeable about how LOD works, maybe Arthmoor or another project member can comment further. Judging from the change log it looks like the patch has already addressed one or more issues related to the water previously at this location. The developers obviously did a rather poor job with their design.
I have a feeling that the second issue may not be resolvable either if the only "solution" is disabling that flag. We usually choose not to address issues that require correcting something at the cost of messing something else up. Since I'm not all that knowledgeable about how LOD works, maybe Arthmoor or another project member can comment further. Judging from the change log it looks like the patch has already addressed one or more issues related to the water previously at this location. The developers obviously did a rather poor job with their design.
Comment #1 Nov 15, 2020 2:00 am
Edited by BlackPete on Nov 15, 2020 2:04 am
The solution Ablaze666 mentioned in your mod thread seems to have solved the issue while retaining the ability to see the water from a distance. So we've added 3 new water refs that do not have the IsFullLOD flag on them. The water physics now work properly in all 3 cells. They've been duplicated from the refs set up by the USSEP initially so that the positioning data is maintained and we don't reintroduce water gaps.
Showing Comments 1 - 2 of 2