This is actually correct behavior and not a bug after discussing with some colleagues. Tick is called for every frame where as Event Begin Play will start once the level has loaded.
This is confusing, maybe I didn’t explain this very good. Is it expected behavior that if you spawn an actor and set his location in some other actor’s beginplay function that you can then never ever apply physics to that object in any tick function?
I’m aware of the difference in calls to tick vs begin play, the only thing happening in begin play is the object being spawned and his location being set. After that, applying forces in tick functions is essentially a NOOP. The end result of what I’m describing is that objects spawned like this never respond to physics forces that are applied to them (regardless of where you apply those forces i.e. in tick or an input event).
oh, okay. I didn’t get that from the initial post. That may be my fault as well. I understood it as you were wanting to have physics start when the tick does, but it was not since the level hadn’t loaded with the event begin play.
I’m not a programmer so I’ll try and repro this in BP first before I bug the programmer on our team.
After trying to make a sample project to illustrate this, I can’t get it to repro either. The issue is obviously more complex than spawning and adding forces but I don’t know to what degree. I guess we’ll mark this as answered until I can provide a reliable reproduction case. Sorry for wasting your time here