The irritating collision background BUG's ising to close to background will be adsorb to the top or direction and can't change!
The irritating collision background BUG's ising to close to background will be adsorb to the top or direction and can't change!
I can see the bug on the left (the tanks stays pointing to the right while going down), but I cant see what wrong on the right of the example. Can you tell me?
?????
The left right UP DN all would BUG I am also similar, Be just an example just
>_< bug bug bug
I am sorry, your translator is awful, we can't understand you.
After examining the example the problem on the left is to do with the starting position of the active and the wall. This may not be a bug. However if the F2 key is pressed you will notice that the tank can start in 4 different directions.
If the down arrow is pressed for the first time the active doesn't move in the right direction.
If the active is moved away from the wall the object will behave correctly from the start.
This may appear as a bug with mmf2 but this is more a bug with your initial setup and coding. You have coded the tank to stop when it collides with the wall. Since the tank is inside the wall, the algorithm can't deal with the object half surrounded by a background on startup. MMF2 movement algorithms have some smarts to un-stick objects from backgrounds if they are reversed. Since there is no initial direction for the collision the reverse direction cannot be determined by the algorithm. This algorithm has been incorporated into the movement engine because some object can move very quickly skipping pixels, thus ending up in the background.
You have two option
1.Is not to start an object overlapping a background.
2.Is to code for the situation where the object is overlapping the background to unstick it. There are a number of options to program this including hidden sensors to detect a way out from the overlap. This of course needs extra programming.
On the right the tank is supposed to collide with an active (which is not a background) and stop I assume. The reason it isn't is because there is no collision event set up between the two and then the action to stop the tank. Your conditions as setup in the even editor would work if the object was a background.
BUG I have already solved this BUG to put to be provided for everyone to make reference to once up the example with the another way, who have more simple method don't hope to put to come up
Posting Permissions
