Sliced Sprite issues with atlas reference swap

[schellenberghq]

In my project the expected behavior is correct on Simple Sprites.
The expected behavior when switching between low/hi def atlas is that a) the sprite uses the same real estate, b) the sprite looks low/hi quality.

The issue is with sliced sprites. In the provided images, I have 2 button sprites. One exported at 160dpi, and the other at 320dpi. The result is smaller pixel size, thus less memory and texture space.

I have ensured that both sprites have the same slicing.

The 320dpi button looks perfect. However the 160dpi sprite takes up more real estate than expected and becomes deformed. Rather than the expected behavior of looking lower quality.

Is this the expected behavior for sliced sprites?

I have considered Not using a sliced sprite, which would indeed fix the issue, but there are many areas in the project in which a sliced sprite would be much more efficient over full size exports.

Thoughts/recommendations?

Thanks!

EDIT: I just realized that you may not be able to fully see the size differences with the provided button screenshots because you can't see the full context of the scene. Unfortunately due to the projects NDA, I may run into problems revealing more.

[motionsmith]

This can be done, I do it in my app.

In your atlas settings for your HD atlas, make sure "pixel size" is set to "0.5". This is all it takes for me. I'm using a "fixed size" UIRoot.

[schellenberghq]

Ah excellent. I actually had to do "1" for my 320dpi atlas, and "1.5" for my 160dpi atlas.