Hi,

I am working on a Pinball game, where the ball is moving the most time only on the z and x axis.

The problem is if one of the triggerarms tries to push up the ball, the ball is pushed out of it 2D movement and drops out of the pinball game.

Does anyone knows how to "turn off" the physicsmovent for one axis (like the y).

I had one idea how I could maybe solve my problem, but I am not happy with that idea: Invisible Block/Walls which keep the ball in the flipper area.

hmm aber dass wäre das einfachste. du könntest aber auch noch versuchen, die y position am anfang zu speichern und das objekt dann per while-schleife immer an die gespeicherte y position hinzuschieben.

Thank you for the ideas!

I tried the cage, and it works very well. The problem is, the collisions with the invisible walls.

-There are collisions where is nothing. If I want to make sparks and sounds when the ball collides with walls (for example), there will be sparks and noises by the collisions with the invisible wall. That´s very strange.
-The other thing is the ball is rotating very funny.
-The next thing is the ball is slower and slower the more often it collides with the invisible balls. That means one time you hit the ball and it flies higher and higher. And the next time it doesn´t flies that high, and the player has no idea why.

Boah, da hört mein Englisch auf. Y soll immer 0 sein, da brauch man nicht viel zu Speichern. Physikobjekte verschieben ist so eine Sache. Denn es ist genauso schwierig wie in der Realität ein Objekt of eine Linie zu schieben, also ziemlich unmöglich, besonders wenn es durch die Gegend gedrückt und geschleudert wird. Ich sag nur Trägheit, Masse und Reibung... :/

Das Problem mit der Invisible wall war nur ein Beispiel. Ich ahne, dass für den Zweck für den das PhysicPinballspiel gemacht wird, es mit der unsichtbaren Kollision noch viel größere Probleme geben wird. Bin mir aber noch nicht sicher.

By the way, are EVENTS activated by physic movents, or only by c_move/ent_move?

Yes, you need invisible walls to keep the ball on the playing field. There are a couple of options for preventing sparks and sound effects from collsions with the invisible blocks. For a start, you make them entities, that way you be able to check if they were collided with (the collsion system uses its own collision system, which is a bit inconvenient). If you are more ambitious, you can base your sound effects and sparks on the force of the collision, which I think you will need to calculate youself as event_friction doesn't tell you.

good idea, thank you!