Cooked asset no collision bug

Summary

I am having trouble with collision on on the cooked assets. On my island you are tiny and a house is your map. With all the cooked assets the collision was not designed to be used in this way. They are designed for normal sized players and the hitboxes are very rudimentary. For instance, a kitchen table with four legs hitbox is just a square and it is like this with everything. With the hitbox being just a square it means that even though there is a ton of empty space under the table the tiny players can not go under anything. So for my map to work I have had to turn on no collision on most assets and i have used over 600 individually placed cubes, sphere and cylinders to make custom collisions for assets in my map, and made them hidden in game.

While this has worked for many things on my map, it seems like its not possible fore most assets. My problem is instead of just being able to walk through an asset or with no collision on, it is super buggy and laggy when you pass through the object. So when i turned on no collision on the mini fridge and made it so it can be walked in, on and around the items in the fridge. You can step in the fridge, and then your screen goes crazy until you get out of the fridge.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

Spawn in the yacht mini fridge and turn no collision on. It will seem like it works if you immediately go on Fortnite and go through the fridge. Start the game on fortnite and then end the game. At that point the it will be forever buggy when you try to go through the item

Expected Result

when you spawn in yacht mini fridge and turn no collision on, the player should be able to pas through object as if it wasnt there

Observed Result

when player goes inside of the objects static mesh the players screen will go crazy

Platform(s)

pc

Island Code

0662-2522-1769

Video

Additional Notes

Its as if the item both has collision and doesnt at the same time and the game engine is confused.

Here is another video perhaps displaying the bugginess better