# Collider has to have 'CollisionEnabled' set to 'Query and Physics' warning - possible bug? **URL:** \ **Category:** World Creation\ **Tags:** bug, collider, unreal-engine, Physics, Collision, Blueprint, question\ **Created:** [March 2, 2017, 9:39pm UTC](https://forums.unrealengine.com/t/collider-has-to-have-collisionenabled-set-to-query-and-physics-warning-possible-bug/386775 "2017-03-02T21:39:39Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![jamiewhitephd](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@jamiewhitephd](https://forums.unrealengine.com/u/jamiewhitephd)\ **Post date:** [March 2, 2017, 9:39pm UTC](https://forums.unrealengine.com/t/collider-has-to-have-collisionenabled-set-to-query-and-physics-warning-possible-bug/386775/1 "2017-03-02T21:39:39Z")
Every so often in my project, I have a warning that tells me to ensure that my Blueprint’s sphere collider collision setting is set to either ‘Query and Physics’ or ‘Physics Only’. However, the problem I have, as illustrated in the screenshots, is that my collider is set to use the physics settings suggested by the warning, but yet I am still presented with this pop up when I stop playing the game. Is it possible that this is a bug? ![128513-capture.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/2/4/a24c8dd59220ad6b44f49f119efc9616e32afc85.png) ![128514-capture2.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/6/3/f/63f0a99caa2efb3d344af5c6f0746232bc59e220.png) ---
**Author:** ![TJ\_V](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/tj_v/32/1008648_2.png) [@TJ\_V](https://forums.unrealengine.com/u/TJ_V)\ **Post date:** [March 8, 2017, 9:00pm UTC](https://forums.unrealengine.com/t/collider-has-to-have-collisionenabled-set-to-query-and-physics-warning-possible-bug/386775/2 "2017-03-08T21:00:31Z")
Hi jamiewhitephd, In my tests I could only get this warning if I was attempting to add an impulse to a component that wasn’t simulating physics. What blueprint contains the add impulse setup? Could you provide some more screenshots and/or a small test project? ---
**Author:** ![jamiewhitephd](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@jamiewhitephd](https://forums.unrealengine.com/u/jamiewhitephd)\ **Post date:** [March 8, 2017, 9:04pm UTC](https://forums.unrealengine.com/t/collider-has-to-have-collisionenabled-set-to-query-and-physics-warning-possible-bug/386775/3 "2017-03-08T21:04:11Z")
Hi TJ, I’m not adding any impulse. In this case, the collectibles are spawned when a prop object is destroyed - they are spawned a little bit off of the floor so they can “pop up”, kind of like a typical 3D platformer collectible effect. ---
**Author:** ![TJ\_V](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/tj_v/32/1008648_2.png) [@TJ\_V](https://forums.unrealengine.com/u/TJ_V)\ **Post date:** [March 9, 2017, 9:15pm UTC](https://forums.unrealengine.com/t/collider-has-to-have-collisionenabled-set-to-query-and-physics-warning-possible-bug/386775/4 "2017-03-09T21:15:54Z")
I’m still unable to get this warning with just a collectible that has a similar setup that you pictured above. Would you mind creating a small test project with the issue and uploading it here? ---
**Author:** ![TJ\_V](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/tj_v/32/1008648_2.png) [@TJ\_V](https://forums.unrealengine.com/u/TJ_V)\ **Post date:** [March 14, 2017, 12:49pm UTC](https://forums.unrealengine.com/t/collider-has-to-have-collisionenabled-set-to-query-and-physics-warning-possible-bug/386775/5 "2017-03-14T12:49:13Z")
Posted this 4 days ago but it was deleted when moving it to an answer. > I’m still unable to get this warning with just a collectible that has a similar setup that you pictured above. Would you mind creating a small test project with the issue and uploading it here? We haven’t heard back from you in a few days, so we are marking this post as resolved for tracking purposes. If you’re still experiencing this issue, please feel free to post back here with additional information to reopen the post. Cheers, TJ ---
**Author:** ![jamiewhitephd](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@jamiewhitephd](https://forums.unrealengine.com/u/jamiewhitephd)\ **Post date:** [November 11, 2017, 2:42pm UTC](https://forums.unrealengine.com/t/collider-has-to-have-collisionenabled-set-to-query-and-physics-warning-possible-bug/386775/6 "2017-11-11T14:42:56Z")
Hi there, After further experimentation I still cannot remove this warning. Could I have this question re-opened, please? My issue is still the same as outlined in the question - this error appears in the output log: "PIE: Warning: PICKUP\_LOOT\_C\_1.SPHERE\_COLLIDER has to have ‘CollisionEnabled’ set to ‘Query and Physics’ or ‘Physics only’ if you’d like to AddImpulse. " In my loot blueprint, there is only a collider (root) and a particle system. The root collider is set, despite the warning, to “Collision Enabled” and simulates physics. Yet, why does the warning still appear? In my code, I have this in the BeginPlay function: ``` if (_spawnVelocity != FVector::ZeroVector) _collectCollider->SetPhysicsLinearVelocity(_spawnVelocity * (FMath::FRand() + _spawnVelocityPower)); ``` ![219822-capture.png](https://d3kjluh73b9h9o.cloudfront.net/original/4X/4/6/3/463edcb3e9d6b7fcb9b9639f6b926986d1883603.png) The loot is spawned when a prop is destroyed. ---
**Author:** ![TJ\_V](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/tj_v/32/1008648_2.png) [@TJ\_V](https://forums.unrealengine.com/u/TJ_V)\ **Post date:** [November 15, 2017, 1:41pm UTC](https://forums.unrealengine.com/t/collider-has-to-have-collisionenabled-set-to-query-and-physics-warning-possible-bug/386775/7 "2017-11-15T13:41:09Z")
Hi Jamie, What version of the engine are you experiencing this in? ---
**Author:** ![jamiewhitephd](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@jamiewhitephd](https://forums.unrealengine.com/u/jamiewhitephd)\ **Post date:** [November 21, 2017, 8:49pm UTC](https://forums.unrealengine.com/t/collider-has-to-have-collisionenabled-set-to-query-and-physics-warning-possible-bug/386775/8 "2017-11-21T20:49:32Z")
I’m using 4.17.2. ---
**Author:** ![jamiewhitephd](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@jamiewhitephd](https://forums.unrealengine.com/u/jamiewhitephd)\ **Post date:** [November 21, 2017, 8:57pm UTC](https://forums.unrealengine.com/t/collider-has-to-have-collisionenabled-set-to-query-and-physics-warning-possible-bug/386775/9 "2017-11-21T20:57:40Z")
After a process of elimination I finally found out my problem. What happens is that the pickup gets created upon the prop being destroyed. However, in the event the player is standing very close by when this happens, the engine detected an immediate collision (i’m guessing within the same frame) as the loot piece is spawned. In my pickup class, I set the collder to disable itself so it may float for a second before disappearing. The problem was that after disabling the collision at the same time as it was being created, the initial upwards force I was adding to the actor when its created (to simulate a flurry of loot shooting upwards) was technically invalid, hence the error. This is because at the time of object’s creation, the physcis is, technically, turned off. I hope this makes sense. It seemed a bit hacky, but in the end I left the collision enabled after collection but added a boolean that, when true (i.e. collected), stops any further pickup events.