I've tried to read as much as possible about "lod unloading bugs" and I don't think my problem fits into the categories I've found, so far. I don't have a problem with large reference lod MESHES not unloading (that I've noticed). I don't have a problem with lingering lod meshes, such as roads, snow, etc. I do think all MESHES are loading correctly.
What I see is that textures applied to terrain, and only terrain, often look blurry, like terrain lod, until even after I enter the cell. I can stand over terrain with those blurry textures, and when it happens, if I don't move, those textures are never replaced by the correct, full resolution terrain textures. If I keep walking/running, there's a point where, suddenly, the full res textures "kick in" and everything around me looks correct. I have no idea why this happens with this particular build I'm working on. I'm pretty sure I didn't have this problem on previous builds - at least, not in such a conspicuous way.
It's not a DynDOLOD problem, happens with both DynDOLOD active, or inactive, tested on new games every time. Could be something I did wrong in xLODGen?
This is a random problem. Doesn't happen continuously, but very frequently. I'd risk stating that every other cell, or every third cell shows this problem.
Question
godescalcus
I've tried to read as much as possible about "lod unloading bugs" and I don't think my problem fits into the categories I've found, so far. I don't have a problem with large reference lod MESHES not unloading (that I've noticed). I don't have a problem with lingering lod meshes, such as roads, snow, etc. I do think all MESHES are loading correctly.
What I see is that textures applied to terrain, and only terrain, often look blurry, like terrain lod, until even after I enter the cell. I can stand over terrain with those blurry textures, and when it happens, if I don't move, those textures are never replaced by the correct, full resolution terrain textures. If I keep walking/running, there's a point where, suddenly, the full res textures "kick in" and everything around me looks correct. I have no idea why this happens with this particular build I'm working on. I'm pretty sure I didn't have this problem on previous builds - at least, not in such a conspicuous way.
It's not a DynDOLOD problem, happens with both DynDOLOD active, or inactive, tested on new games every time. Could be something I did wrong in xLODGen?
This is a random problem. Doesn't happen continuously, but very frequently. I'd risk stating that every other cell, or every third cell shows this problem.
Edited by godescalcus10 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