Custom collision box problem

[ZuTheSkunk]

I have a little problem with a custom shaped collision box (based on the other vanilla collision box) - it remains visible in-game, even though it shouldn't. Anyone knows how can I fix it?

http://www.filefactory.com/file/b52fh0e/n/PortalCollision.zip

[_echo]

Might i suggest a different file host? The one you use is add laced and its annoying. plus the 30 second wait for downloading is total BS for any host to pull.

Edit: Try this

http://www.mediafire.com/?amkxcdxgu858d1c

[Artisanix]

Collision can't be visible in game until you use a special console command to show it. What you see in the game in place of your nif is not the collision but editor marker - your nif has editor marker node present but it has no proper flag set to make it behave correctly in game - to use editor markers you need to enable bit 5 in BSXFlag block's properties.

[ZuTheSkunk]

What you see in the game in place of your nif is not the collision but editor marker

Yes, I meant editor marker when talking about collision box.

your nif has editor marker node present but it has no proper flag set to make it behave correctly in game - to use editor markers you need to enable bit 5 in BSXFlag block's properties.

I'm not sure where I'm supposed to enable "bit 5" - at first I thought that I need to just change the number in the "BSX" node to 5, but I've checked two vanilla editor markers and none of them has this number in there. Could you explain, please?

Note that I've managed to get it working by just replacing the original nodes in vanilla version with modified nodes of NiTriStrips and bhkRigidBody (I've saved it under other name, obviously), but I still would like to know what exactly my version lacked - I noticed that the vanilla mesh had NiTriStrips under another NiNode, but doing copy/paste to bring it to my version and then replacing NiTriStrips did not worked (even though the order looked practically the same like in the vanilla one, which was the NDCloudCollision.nif from KotN).

Edited January 28, 2011 by ZuTheSkunk

[WindmillTilter]

You need to add 32 to current value in your BSX flags. So for this NIF set it too 34. Haven't tested it ingame but that should sort it for you. Not sure about the OL_TRANSPARENT layer setting, based on your settings it looks like OL_STATIC would work fine.

WT

[Artisanix]

I'm not sure where I'm supposed to enable "bit 5" - at first I thought that I need to just change the number in the "BSX" node to 5, but I've checked two vanilla editor markers and none of them has this number in there. Could you explain, please?

Select BSXFlags block and check its integer data value in block details window - just click the flag there and in the small window that will appear select Bit 5...

Not sure about the OL_TRANSPARENT layer setting, based on your settings it looks like OL_STATIC would work fine.

Layer settings have nothing to do with collision behavior or its visibility in game. These just only change the color of collision's wireframe, and nothing else.

[ZuTheSkunk]

Okay then, I've just checked it in the mesh and I think I finally understood how it works. Great thanks for both of you.