# UE 4.15.1 - Nativize blueprint collision bug - Spawning child of a blueprint loses collision settings **URL:** \ **Category:** World Creation\ **Tags:** collisions, child-actors, unreal-engine, Physics, Blueprint, question\ **Created:** [April 25, 2017, 8:49am UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850 "2017-04-25T08:49:29Z")\ **Posts on this page:** 18\ **Page:** 1
**Author:** ![Obihb](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/obihb/32/88719_2.png) [@Obihb](https://forums.unrealengine.com/u/Obihb)\ **Post date:** [April 25, 2017, 8:49am UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/1 "2017-04-25T08:49:29Z")
I have a setup where I spawn in actors as pickups for the player, they use collision sphere with physics to drop into the world and collide with the world. When I do a build using Nativization, this physics sphere seems to lose it’s collision settings and falls through the world.This only happen when spawning a child of the base blueprint I created. Spawning the base blueprint seems to work just fine. I found this bug report that may or may not be related to the same problem I’m having, so here’s the link for that just in case there’s overlap there. > **[\[BUG REPORT\] Nativize BP breaks C++ collider component](https://forums.unrealengine.com/questions/543660/nativize-bp-breaks-c-collider-component.html)** > > Hello, I have created a Blueprint Pawn in which I added a C++ scene component. In that scene component, I created a UCapsuleComponent. In the Blueprint for the pawn, I change the shape of the capsule component. I compiled for Android and validated... … Repro 1. Using an example project like the Blueprint 3rd Person Example… 2. Create new blueprint Actor. 3. Inside this new actor, add a collision sphere and enable physics and I also constrain rotation on all axis and set it to only collide with WorldStatic channel, ignore all other channels. 4. Now make a child blueprint of this new Actor blueprint. No changes inside the child, keep as is. 5. Inside the level blueprint on begin play, spawn in the child blueprint. 6. Finally build the project using Nativization for play test. When you play test notice the sphere drops through the floor, in stead of colliding with it. ---
**Author:** ![anonymous\_user\_e729f54e](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_e729f54e](https://forums.unrealengine.com/u/anonymous_user_e729f54e)\ **Post date:** [April 25, 2017, 2:07pm UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/2 "2017-04-25T14:07:33Z")
Hello , I was able to reproduce this issue on our end. I have written up a report and I have submitted it to the developers for further consideration. I have provided a link to the public tracker. Please feel free to use the link provided for future updates. Link: [Unreal Engine Issues and Bug Tracker (UE-44333)](https://issues.unrealengine.com/issue/UE-44333) Make it a great day ---
**Author:** ![Obihb](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/obihb/32/88719_2.png) [@Obihb](https://forums.unrealengine.com/u/Obihb)\ **Post date:** [April 26, 2017, 7:57am UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/3 "2017-04-26T07:57:21Z")
Thanks Rudy, much appreciated!. ---
**Author:** ![Obihb](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/obihb/32/88719_2.png) [@Obihb](https://forums.unrealengine.com/u/Obihb)\ **Post date:** [April 27, 2017, 12:59pm UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/4 "2017-04-27T12:59:19Z")
I just wanted to add some info here that I just discovered based on another blueprint I use in my project. so with this one, it’s basically for damage, when the enemy does damage to the player, I use a collision sphere to run an overlap event. In this case, it doesn’t lose collision all together, but it changes the channels it can collide with. Basically my enemies end up hitting both themselves and the player. I have some custom channels for both player and enemies for collision, for these occasions so only specific things can overlap of course. So I’m not sure exactly what’s going on there, how the engine assigns these channels, based on what, but it changes from my “Custom” settings to something else. The reason I mention this is because originally it looked like it loses all collision, but it seems rather to change which channels are affected. I’m sure you guys would see what’s going on there when you look at it, but I just wanted to add this just in case it makes a difference in finding the problem there. ---
**Author:** ![blobdole](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@blobdole](https://forums.unrealengine.com/u/blobdole)\ **Post date:** [June 20, 2017, 1:19am UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/5 "2017-06-20T01:19:27Z")
I can’t be 100% sure but I may be having the same issue with some of my collision presets. In editor or stand alone the collision works as I expect and nothing I am using has custom collision. Once I nativize my build a child actor of mine seems to ignore its collision presets and instead use the default collision of its object type. ---
**Author:** ![lotodore](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@lotodore](https://forums.unrealengine.com/u/lotodore)\ **Post date:** [July 2, 2017, 10:41pm UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/6 "2017-07-02T22:41:55Z")
I’m having the same issue and searched for the problem on my side for the whole day. It is really frustrating how painful it is to enable nativization because of all the problems you encounter. And I am having only a relatively small project. ---
**Author:** ![anonymous\_user\_dc1d66e9](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_dc1d66e9](https://forums.unrealengine.com/u/anonymous_user_dc1d66e9)\ **Post date:** [July 5, 2017, 12:37pm UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/7 "2017-07-05T12:37:14Z")
I encountered the same issue when nativizing our project in 4.16.1. I investigated a bit and it seems that collision presets are not set correctly for nativized blueprint components. If I ask GetCollisionProfileName for the affected component, it reports correct name, but GetCollisionResponseToChannel can return wrong results. Calling SetCollisionProfileName first with some dummy name and then again with the intended name will apply correct collision profile and the components will start to colliding and overlapping as they should. I wrapped this to a function to make a playable proof of concept nativized build for benchmarking, but it is in no way sustainable to add that everywhere where custom collision profiles are used. I attached picture of the fixup function. ![201878-fixcollisionpreset.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/e/8/7/e87e068a3f9a8cdb6d44b320ad7eb9fa614d5f5d.png) ---
**Author:** ![Flash7](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Flash7](https://forums.unrealengine.com/u/Flash7)\ **Post date:** [September 22, 2017, 4:48pm UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/8 "2017-09-22T16:48:06Z")
4.17.1 still has the same bug. ---
**Author:** ![CUERN1T0S](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@CUERN1T0S](https://forums.unrealengine.com/u/CUERN1T0S)\ **Post date:** [January 5, 2018, 9:53am UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/9 "2018-01-05T09:53:41Z")
4.18.2 still has the same bug. ---
**Author:** ![WeoMage](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@WeoMage](https://forums.unrealengine.com/u/WeoMage)\ **Post date:** [December 2, 2018, 12:23pm UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/10 "2018-12-02T12:23:19Z")
4.21 still has the same bug. ---
**Author:** ![Flash7](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Flash7](https://forums.unrealengine.com/u/Flash7)\ **Post date:** [December 2, 2018, 3:15pm UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/11 "2018-12-02T15:15:10Z")
it says: Target Fix 4.22 ---
**Author:** ![lotodore](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@lotodore](https://forums.unrealengine.com/u/lotodore)\ **Post date:** [December 9, 2018, 6:17pm UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/12 "2018-12-09T18:17:17Z")
Yes. But before that, it said target fix 4.21, and before that, 4.20… ---
**Author:** ![lotodore](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@lotodore](https://forums.unrealengine.com/u/lotodore)\ **Post date:** [February 13, 2019, 8:37pm UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/13 "2019-02-13T20:37:23Z")
Rudy, is there some developer comment available as to why this is not being fixed? It has been retargeted several times now, and currently has no target release at all. ---
**Author:** ![seanny](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@seanny](https://forums.unrealengine.com/u/seanny)\ **Post date:** [February 14, 2019, 1:24am UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/14 "2019-02-14T01:24:04Z")
I used the method discovered by @jh_hmq for a while, which fixed some things, but then I encountered a very stubborn issue where a couple actors refused to overlap in packaged+nativized Blueprint, even though their collision channels were reporting _correctly_ (via “Get collision response to channel” → “Print text” on runtime). Somehow, re-applying every collision channel solved this problem (“Get collision response” → “Set collision response”). Only god knows why this works. **tl;dr:** I now have this function attached to every collide-able actor’s BeginPlay event, which takes an array of “Primitive component object references” and applies this nonsense workaround to each. ![268554-collision-fixup.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/3/4/7/34739821c4137bcccd6c493a1dd605741cc7ecc1.png) ---
**Author:** ![JimFox](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/jimfox/32/1211739_2.png) [@JimFox](https://forums.unrealengine.com/u/JimFox)\ **Post date:** [May 27, 2019, 6:26pm UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/15 "2019-05-27T18:26:47Z")
Thank you seanny, it works! (づ｡◕‿‿◕｡)づ ---
**Author:** ![seanny](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@seanny](https://forums.unrealengine.com/u/seanny)\ **Post date:** [October 25, 2019, 4:06am UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/16 "2019-10-25T04:06:30Z")
I’ll append a new note because the issue is still happening in 4.23.1 and it seems to be getting worse. The way I’ve been solving inexplicable nativization-collision bugs lately is by spawning collision components at _Event Begin Play_ rather than setting them up prior to runtime. I wish Epic would just fix this. ---
**Author:** ![seanny](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@seanny](https://forums.unrealengine.com/u/seanny)\ **Post date:** [April 14, 2020, 11:17am UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/17 "2020-04-14T11:17:15Z")
I haven’t tested it, but issue #UE-44333 is marked as **“fixed”** for UE 4.25. ---
**Author:** ![anonymous\_user\_7a820c07](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous\_user\_7a820c07](https://forums.unrealengine.com/u/anonymous_user_7a820c07)\ **Post date:** [July 5, 2020, 11:19pm UTC](https://forums.unrealengine.com/t/ue-4-15-1-nativize-blueprint-collision-bug-spawning-child-of-a-blueprint-loses-collision-settings/391850/18 "2020-07-05T23:19:42Z")
It doesn’t seem to be resolved by the PR by epic (tested on 4.24.3)