Bot Paths Wedge Climbing

super. A very interesting idea! Perhaps it is. The principle is the same - "Bots do not see blocks". Everything is possible as you say - physics beyond the level, this is the same effect that a star causes .

 

@Labyrenight @MekaSage
FRIENDS!!! I REALIZED! I UNDERSTOOD THE STAR PHENOMENON!
In mekorama, each block has its own physics. The star is a unique block - it can pass through other blocks! There is a superposition of two blocks - this is a paradox. Each of these blocks is responsible for its own physics! Any block fills the space of the pixel in which it is located . The star has unique physics - the star is air! For a bot, this is a void - through which it freely passes.
When two blocks are superimposed, the question arises - "WHICH BLOCK DETERMINES THE LAWS OF PHYSICS IN A GIVEN PIXEL? !!". There are two blocks in a pixel at the same time. One of these blocks should dominate. The law of physics of a star (air) - dominates all blocks that (potentially) can move or leave the space of a given pixel. Conversely, static level blocks dominate the star.
That is, when there are two blocks at the same time in the space of one pixel, only one of these blocks can determine the physics that operates in this pixel. You need to understand which of the blocks dominates.

BUT!! It matters only for how the BOT itself perceives this pixel !!! Because in reality, the block over which the star dominates - WILL NOT disappear ANYWHERE! Therefore, it turns out that the bot perceives the pixel as a void, but stumbles upon a real block.

 

An interesting conversation but I feel terminology/units of measure are a little confusing.
Pixels, in my definition, are a unit of graphical resolution. My laptop for instance is capable of a resolution of 1920 x 1020 pixels. Mekorama blocks are composed of many pixels, the ratio I do not know. The more pixels the greater the possible resolution of the block on screen.
Mekorama is based on a matrix of 16x16x16 'cells', my definition. These cells I have always assumed are empty, but in @Labyrenight theory they actually contain a collection of pixels which would normally graphically display a star but, in reality, are invisible? In @Denis Nazin theory a block can occupy this 'cell' and coexist with the 'invisible' star block?
In another life, coding games in Z80 assembler, I could detect a collision between individual pixels OR a group of pixels. On the surface Mekorama detects an interaction between groups/blocks. However with non cuboid blocks, stair, wedge, curved etc, it seems to operate at pixel level, allowing, for instance, two triangular blocks to coexist in the same space.

@Denis Nazin Nothing I have rambled about is substantially different to what you have written other than a block occupying a cell rather than a pixel. I swore I would not let myself get involved in the murky/shady world of Mekorama tricks/bugs/features but old MS Dossers/Z80 Nerds seem to refuse to die.

 

@MekoMole @Labyrenight @MekaSage
Friends, I'm sorry, I used the wrong term. @MekoMole said correctly: instead of the word "pixel", put the word "cells". And then the meaning of my text will become more correct.

 

That's a cool effect!

 

That makes sense. But I wonder why it matters which direction the star approaches the cell? Is it the case that B "sees" the cells in a certain order, so if the star is seen first it determines the physics, but if the other block is seen first then it determines the physics?

 

@MekoMole - Mekorama's credits mention it was built using the Bullet physics engine. The documentation is here:
https://pybullet.org/wordpress/index.php/forum-2/

It's mostly beyond me (I've only dabbled in programming) but maybe it would make sense to you. I suspect it accounts for how elements can exist in the same cell.

 

Yes Yes!! I absolutely agree! I now understand why B goes to the block - because it sees a star (air, emptiness). But why does this act differently from different sides of B - this is really UNCLEARED !! ?? !!
I remembered another demonstration of "block overlay" - this also proves my theory. And confirms what you're talking about

"Left" phantom blocks dominate the fence,
BUT! The fence dominate the "right" phantom blocks. This is exactly the same block overlap as with the star. The physics of one of the blocks must dominate within one cell!

The most important question: "Which of the blocks dominates and why ?!"

 

@MekaSage @Labyrenight
Friends! I'm sorry - I was wrong. This card has been moved to the discussion - "star Pass"

 

My friend! I am sorry! I am completely confused about forums and discussions. I thought it was "star Pass". There are a lot of discussions, I'm completely confused where what! Sorry.
Many topics overlap, so it is difficult to keep track of where and what discussion. It seems to me that this is not so important. The most important thing is that we are trying to reveal the secrets of the physics of mekorama. In my opinion this is the main thing. But I respect your opinion - I moved the map to another discussion. I'm really confused - sorry!

 

I wanted to continue the conversation on this topic. But now I do not understand where to write ???? This is where this conversation started - and other players are involved. But on the subject, he is more suited to the "star Pass". What to do?? Where should I write ??

 

I would like to answer you an important thing !! (Since you asked the question here - I'll answer here)
You are absolutely correct about the initial position of the slider !! I specifically demonstrated this on my map. I built from different angles - to show that this also affects. But one does not exclude the other. ..apparently you misunderstood me. I wrote what is happening inside the cell. There can be only one physical law within one cell (for how this cell perceives B). Therefore, when the blocks are overlapping - "B" cannot see two blocks at once inside the cell! ..b sees one thing! Either a block, or a star, or a fence .... And I called this dominance. Don't get attached to a term - it doesn't matter at all. It's important to understand what's going on. And what word to call it - it makes no difference to me. The main thing is to understand the meaning!
And you are absolutely right. ..which block sees B in one cell depends on how the sliders are located, how B is located, and so on ...
One does not exclude the other. The initial filling of the blocks at the level is important. And just as important is how these blocks interact with each other within the same cell. ..therefore, there is one and the other!

 

Thanks for this very interesting link @MekaSage. My coding skills are ancient and only part remembered I'm afraid but I have had a brief look at the Bullet engine. Wow! I did notice on one of the Power Point presentations, under Collisions, one shape nesting inside another after collision. How this affects the properties of the Objects I don't know. Do nested Objects create a new Object with new properties? A cell is presumably an Object in it's own right and it's properties therefore must change when it hosts one or more blocks (Objects).
This is perhaps pertinent to the discussion but I must emphasise my coding knowledge pre-dates Object Orientation.
Afraid I'm struggling with this conversation but will go back to the start and read again to try to get my brain around it. That said it is fascinating stuff.

 

@Labyrenight - I can't remember if you've used this technique before, so apologies if this is a repeat.
A mechanism that I first saw in @Fendi's Slips Trips can be used to initiate a wedge climb. It's inconsistent, though. L usually captures the lower star but won't always capture the upper star.

 

Wow, that's great! I noticed the bot stops at the top, turns round, then carries on to the star.