Why does ResolutionPolicy::SHOW_ALL move the layer up ?

[rahuliyers]

With FIXED_WIDTH policy:

With SHOW_ALL policy:

Code:

    _gameObjectsLayer = Node::create();
    this->addChild(_gameObjectsLayer);
    
    auto visibleSize = _director->getVisibleSize();
    auto origin      = _director->getVisibleOrigin();
    auto safeArea    = _director->getSafeAreaRect();
    auto safeOrigin  = safeArea.origin;
    
    auto sprite = Sprite::createWithSpriteFrameName(spriteName);
    auto size = sprite->getContentSize();
    auto pos = Vec2(visibleSize.width / 2 + origin.x,origin.y);
    sprite->setPosition(pos);
    _gameObjectsLayer->addChild(sprite);

The simulator is iPhone 15. The design resolution size is 2048 x 1536. Orientation is Portrait.

There are a couple of things I don't understand:

1. In SHOW_ALL, why is the image moved up so high on the screen ? it doesn't make sense to me.
2. Why is the bottom of the white tile cut off? If I move it up 1/2 the height of its content size by changing the code to:

auto pos = Vec2(visibleSize.width / 2 + origin.x,size.height/2 + origin.y);

Then the simulator looks like this:

So it seems strange to me the way the scene is rendered on screen in SHOW_ALL. I understand how the resolution policy used to work in cocos2d-x because I published multiple apps to iOS and android. But here it seems weird. I understand that sometimes one can have bars above and below depending on the aspect ration. But in this case, the entire scene seems to have been moved up, and the top of the scene is cut off.

Can someone please explain to me so I understand if I am doing something wrong ? Thanks.

[rh101]

I edited your post just to fix the formatting, since it wasn't rendering the bottom image and text properly.

Are you able to upload a minimal test project with the exact code you're using to show the examples from your post?

[aismann]

@rahuliyers
Maybe the reason is:
_gameObjectsLayer has no => setPosition(pos);
The default values can be wrong.

Another point:
_gameObjectsLayer = Node::create();

It should be an "ax::Layer" object?
Why not using the 'correct' one:
_gameObjectsLayer = Layer::create();

[rahuliyers]

@rahuliyers

Maybe the reason is:

_gameObjectsLayer has no => setPosition(pos);

The default values can be wrong.

Another point:

_gameObjectsLayer = Node::create();

It should be an "ax::Layer" object?

Why not using the 'correct' one:

_gameObjectsLayer = Layer::create();

Thats just a name - i intended to use a node only.

Whether i use the node or not makes no difference to the outcome - if i attached it directly to "this" in the game scene the outcome is the same.

[rh101]

The choice of node is unlikely to have anything to do with the issue you're seeing regarding the scene being shifted upwards or the clipping at the bottom.

Once again, please upload a minimal project that reproduces the issue, either on here, or a link to a project on your github account.