Generating precombine breaks collision in stairs mesh

[csbx]

Working on a new cell and having a hell of a time making precombine / vis work without breaking something.

 

Although I initially tried using rooms / portals, there were major problems with objects flickering in and out and npcs/corpses being rendered invisible.

 

Now that i've generated precombine mesh / vis, all of that is fixed; and it runs beautifully, but it has resulted in a pretty major bug: every staircase in my cell (and only the staircases) does not have collision--one falls through. This includes variants of stairs ie. not just one base form.

 

I've tried re-generating precombines, deleting the folder and regenerating again. but thus far I can't seem to figure out what the hell is going on.

 

Anyone with tips to guide me through the crucible of gremlins ?

Edited May 22, 2018 by csbx

[SKKmods]

Hey any luck on this ?

 

I have exactly the same problem after updating precombine geometry for existing external wilderness base cells. It's clipping straight through any steps and stairs. Navmesh untouched and still there. Remove the timestamps and updated \Meshes\PreCombined and it works again.

[MissingMeshTV]

Stairs seem to give problems sometimes, although I have yet to run into this...yet. Your best bet might be to just exclude the stairs from the generation process by setting them to initially disabled. Disabled items get excluded from the generation process.

 

I’d recommend putting the stairs (and anything else you want to exclude) onto their own layer. When you are ready to generate precoimbines/previs hide all other layers except the layer with your excluded items so the only things visible are those items.

 

Select them all and set them to initially disabled. You can do all of them at once using the Batch window. Hide the “exclusion” layer and re-enable your other layer(s). Generate precoimbines and previs. Reverse the hide/show process so that only your precombine exclusion layer shows. Select all, remove the Initially Disabled flag via Batch window. Renable all other layers and test things out. It goes without saying that you should save through each step of the process since ya know, it's the CK. :wink:

 

The reason I suggest using layers and showing/hiding them is to cut down the chance of accidentally nudging something you’ve just added to a precombine when re-enabling the items you excluded and breaking things.

 

I’ve tested this with stairs in the past and it seemed to work as advertised, but have yet to use it in an actual mod. I am planning on doing this for the mod I’m currently working on that has lots of stairs. But at the rate I’m progressing, it will be a couple of months before I’d be able to report any results.

 

EDIT: Out of curiosity, what stairs object were you both specifically having problems with? Just wondering if there is something specific to stairs from certain building kits.

Edited May 27, 2018 by RedRocketTV

[SKKmods]

thanks RR another layer solved the clipping stairs problem for:

 

WrhsPlatStairs01
WrhsPlatStairs02
WrhsMainSladder01

 

1. PlacedItemLayer = Stuff I have placed that can't be precombined.

 

2. WorkshopStackedItemParentKEYWORDLayer (thanks to Trosski for this) = scrappable base game stuff to break out of and not include in precombiend.

 

3. DisableForPrecombineLayer (thanks to RedRocket for this) = non scrappable stairs to not include in precombined.

[csbx]

Great (sort of !) to hear others have heard of this specific issue. Here are the stair meshes that are affected for me:

 

HitSmHall1WayStairsExSm01

HitFloorEdge02Stairs01

HitSmHall1WayStairs01

HitSmHall1WayStairsExSm02

I should add: it's every stair mesh type and every stair mesh instance in my mod.

Making a layer and excluding from the precombine is easy enough. Thanks for the tip !

One question. What does 'remove the timestamp' mean ? I'd updated it but am not clear about how this works.

[SKKmods]

If you mean "Remove the timestamps and updated \Meshes\PreCombined and it works again." that's me amateur hacking my ESP in xEdit so I can purge the generated precombine and vis when I forget to take a copy to demonstrate the regression.

 

As the individual new precombine NIFs have to be carved out of each cell info as well, I would not recommend it. Memo: just make a named copy of your esp between every button press :)