Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It looks like what I want so long as I can have multiple canvases use the same layer.
The main reason I am doing this is so I can have the player still exist, but be outside the level data, that way I can show the player entering the new area and not have to reload any of the player data or have to bother with moving it out of the child nodes of the level first.
So far using the Z-axis seems to be the best idea. I can probably just replace these CanvasLayers now with Node2Ds with the Z-order stored in those parent nodes.
Any better ideas?