Robert the bugfixer and the SREX team are making their own fix for the intersecting occlusion planes. This fix might be obsolete soon. Only download if you encounter crashes when opening the map in and around Whiterun.
For me, I isolated this crash to JK's Whiterun Outskirts. Disabling it fixed the crashing. I tested this with both open cities and SREX. For me, adding or removing JK's AiO, Dawn of Skyrim, Capital Whiterun Expansion, Fortified Whiterun, or Whiterun Has Walls had no effect whatsoever.
I have a patch I made for myself for Open Cities + JK + DoS + CWE, to be used alongside JK's Whiterun Outskirt, I can link it if anyone needs that.
I get a ctd when I open the map, however I don't have SR Exterior Cities Series at all, so can't use this, is there one that would fix it without SR Exterior Cities Series? Also I tried to install SR Exterior Cities Series so I could play, however when I enable the patch hub, I can't even play, it ctd before I see the menu, anyone have any ideas?
I just wanted to thank you for the post you made about the too many occlusion planes leading to a crash; I don't use exterior cities but Capital Whiterun has always crashed on opening the map. So I went in and removed a small amount of panels out (still use occlusion from Dyndolod though) and tested with and without this patch a number of times and can honestly say that has 100% fixed my crashing. I can't explain why, but it really did help me so much. Really appreciate the post and is a major help. Cheers
Glad it helps. Now help spreading the knowledge about that issue. Maybe some day we will understand why different people with different hardware can handle different occlusion plane situations.
Strange issue. It reminds me of the strange problem I am currently facing. When I try to add capital windhelm to my load order, no matter how many patches are added or no patches are added. I couldn't start a new save, so I had to remove it. Moreover, the crash logs display irrelevant information.
Capitol Whiterun shouldn't have that effect. Certainly a major conflict in your load order that cannot be diagnosed without doing a process of elimination style troubleshooting. Certain patches for mods being out of date will cause crashing problems too. AI Overhaul being one, EmberXD, another.
If still ctd'ing, disable other plugins that affect the cells CR does in small blocks of 10 plugins until the new game successfully starts.
Add back all the rest, in again small blocks of like 10 until you encounter the problem again. Leaving out the one that of course is known to have prevented your new game from starting.
Then enable one by one the patches for CR. I'll bet big one will deffo crash it.
While I've not used it for ages, never had the problem you're describing unless an out of date patch was in play.
I get stuck in CTD when I open a map in an open city, and the internal space in an open city won't have CTD. I don't know how to fix this bug either. OCS - RedBag Solitude - LOTD - BPT
Occlusion planes and cubes temporarily disable the rendering of certain meshes and textures. Effectively turning them off as long as the plane or cube is between you (the camera) and the object. Also does not affect all LOD's, grass, nor terrain. This is an ancient method, camera based occlusion found in more modern engines is far more effective. Modern games even when oldrim was released 12 years ago...
Short & sweet; occlusion reduces memory, gpu, and cpu load by turning things off behind them enhancing performance overall.
Yellow cube seen is a navcut (this is the default color, which can be changed by the modder in CK, but the primitive type itself can be edited leaving a question sometimes. Although here is definitely a navcut). This prevents AI from seeing the navigation pathing under the navcut, hence the name, causing npc AI to go around it. It's a shortcut rather than editing the navigation mesh directly. Not entirely effective if the game engine is stressed where it can take a back seat because it ranks lower in priority, and be ignored as such by the engine, while a navmesh cannot. So navmesh edits are the superior method. Unless you value the immersion breaking npc faceplanting a tree or wall all day long.
24 comments
This fix might be obsolete soon.
Only download if you encounter crashes when opening the map in and around Whiterun.
For me, I isolated this crash to JK's Whiterun Outskirts. Disabling it fixed the crashing. I tested this with both open cities and SREX.
For me, adding or removing JK's AiO, Dawn of Skyrim, Capital Whiterun Expansion, Fortified Whiterun, or Whiterun Has Walls had no effect whatsoever.
I have a patch I made for myself for Open Cities + JK + DoS + CWE, to be used alongside JK's Whiterun Outskirt, I can link it if anyone needs that.
Anyways, with SREX 2.0, this patch of mine is obsolete :)
Now help spreading the knowledge about that issue.
Maybe some day we will understand why different people with different hardware can handle different occlusion plane situations.
While I've not used it for ages, never had the problem you're describing unless an out of date patch was in play.
And yellow box？
What role does this type of BOX play in CK?
Short & sweet; occlusion reduces memory, gpu, and cpu load by turning things off behind them enhancing performance overall.
Yellow cube seen is a navcut (this is the default color, which can be changed by the modder in CK, but the primitive type itself can be edited leaving a question sometimes. Although here is definitely a navcut). This prevents AI from seeing the navigation pathing under the navcut, hence the name, causing npc AI to go around it. It's a shortcut rather than editing the navigation mesh directly. Not entirely effective if the game engine is stressed where it can take a back seat because it ranks lower in priority, and be ignored as such by the engine, while a navmesh cannot. So navmesh edits are the superior method. Unless you value the immersion breaking npc faceplanting a tree or wall all day long.