In a mountainous landscape, I placed 3 PlayerStart assets in a row. The outer two have “bad size” but I cannot locate any collision. The middle one is fine, and when I play from that one on, I run into some boundary, clearly a collision but none is shown. Placing a PlayerStart asset over that boundary gives it “BadSize”.
Is is completely unclear to me why just that can bu used and the others have this “Bad size” tag. I doublechecked the collisions but none exists…
Try this:
Apply physics to a sphere and drop that sphere over the point that you expect there is a collision. Does the sphere react in any way?
Also, posting a video will greatly help us help you!
Hey there @WillemGr! I concur with Leo in that you could create another actor BP, a cube or sphere with collision, then print out what it collides with after you place it there. Alternatively you could just go into the details of the Player Start and force it to spawn the player regardless of collision, then test and see if the spawn itself works.
Does moving either of the other player starts where the central one is get rid of their warnings? They could also be overlapping each other’s locations as well in some cases.
1 Like
Ah! I didn’t even consider the collision PRINT.
I’m stealing your idea.
K, thanks. Bai.
I found the culprit, had this issue before but realized it later: A round object, default collision and that includes a collision along the tangent of the circle. Just ONE asset, though duplicated a number of times, ‘miles’ away from where I intended to put my PlayerStart asset. After I changed collision to “Complex as simple” for all these assets, I could place my PlayerStart where I wanted.
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.