Various/Other Hovering?

Yes I would love some help with this also. I want in on the secret lol

 

Hi guys! I have played a lot of levels in this forum. But one thing always bugs me:Sometimes when B falls from a high spot,his legs disappear and start to act like an alien. This causes inconvenience in playing the level because when you tap around an open spot,he tries to float there but goes out of the dioramas because of probably too much speed. Has this ever happened to you guys? Why does it happen?

 

Always happens to me...:mad: You are right... it is a bug. However, I don't know why it happens...

Note: It happens to R too.

 

I think legless states happen to everybody, either on purpose or not. Even losing one leg will cause B to act strangely. Losing both legs is behind B's "hovering" state in Richard Fu's Spirits level. With his permission, I've used it many times (probably too many!) because it's so cool!

 

The hovering trick works always when the b bots head touches the ground or where he is standing.just like richarfu's spirits,but in a simple way I've tried to do it.
Step on the farthest metal block and tap on the cement block just when the lift is going down so that b bot can't reach the cement block on the first time.

 

I came across this thread only just now. The level card by @Mushfiq Zaman is quite astonishing, it is a very comprehensible demonstration of a special Mekorama effect. I like the card very much because is make me wonder and think. Thanks!

As some not too experienced player I see this in the video: The autopilot cannot finish since the distance to the autopilot target (topmost stone block) is greater than one block in height. The ground (iron block) is being moved (by the slider) downwards at apparantly the same speed B is going downwards. All the way down the autopilot still tries to step up to the topmost stone block; this might balance gravity in a way that B and the platform go down at the same speed (otherwise B would fall much faster than the slider could go down). It might be as well some simulated friction between B and the stone column that is slowing down B downward movement. The feet just do not find any ground to stand on and they float in the air and (often) they just go (periodically) through B's body. The feet just search desperately some ground. When the small iron platform then is being moved upwards again, the platform hits still floating B and pushes him upwards while he does (sometimes, sometimes not) some somersault kind of thing. On the way up his feet seem to find iron ground for few moments but this is obviously not possible to actually stand on these moving iron blocks while autopilot targeting the topmost stone block is active. I cannot see the cause and effect of what happens next. Is B's headfirst position enforcing the feet going inside the body? Or are the feet-inside the reason why B is turning into the headfirst position? Or are both effects just due to the irons pushing B up? Headfirst and feet-inside at the topmost position, which is the condition for the hovering that comes, seem to be always the case in this level if the autopilot is still active. In horizontal direction still the momentum is active B got from the autopilot initialization. While the platform is being moved up and down, this momentum is blocked temporarily by the stone column, but it is not destroyed. At topmost position B's momentum is no longer blocked, but since the feet are already "on ground" (inside body) the feet just cannot stand at the same time as well on the original autopilot target and with the momentum B is just overshooting the original target. Well, it also might be the fact that headfirst B is lifting up feet to the skies and that the feet therefore are too far away from the topmost stone block to step on; and stepping on that block with the nearer botic eye makes not much sense. During this overshooting B's height is not reduced (in a noticeable way), this gives the impression of hovering. But hovering lasts only until B is over the win block which seems to pull out one foot out of B's body (the topmost stone block could have done the same, but has not, indicating that the headfirst position is the more important condition than the feet inside condition). With one foot is touching the win block and letting B sometimes bounce even a little higher hovering is over and B follows some drop parabola. To me it seems that this level card uses some extremely delayed autopilot together with some sliding to prepare a condition (momentum, headfirst and/or feet inside body) that create some hovering-like state for some time. This hovering is bound to the motion (B hovers like an airplane flys, but not like a helicoptor standing in the air). Is it?
Another approach to this nice level is the question: what ends the autopiot routine? Tapping red X somewhere.

Well, the red X video indicates that headfirst position is not necessary. It's only the feet inside thing = the legless state mentioned above. The discussed "hovering" level card creates this legless state in an easily reproduceable way. How to produce a headfirst B that is not loosing legs? Would this legged headfirst B also hover? Probably there is no such B.
@Mushfiq Zaman I learned a lot on an entertaining Tuesday evening.
PS: I just checked out this Spirits level by @richardfu and saw that there is no autopilot utilized back than to produce the legless state but only mechanics. Legless state was archived via enforcing headfirst state. No legged headfirst B. But I see at this level that this kind of ghostly hovering is not necessarily bound to motion. With the right tap it is possible to stop the motion and let B stand in the air.

 

Hovering R

Spoiler: Video

 

Just noticed this other thread with a very nice level card on legless P hovering.