ordering objects - is there a list of the current order?

[Jarred]

This one has me puzzled. I have a load of graphics in a frame and want to make sure the ordering is correct for what can be seen in front of and behind another. Is there a simple list generated by CTF that shows the ordering or do I have to set this up in every frame and constantly manage what goes where?

I was hoping layers would take care of this but read differing layers could interfere with objects interacting together. I also thought I could order by a fixed value I assign each object but all I see if order by X value, Y value, or 'move to layer'.

[schrodinger]

Hello Jarred,
the layer object usually serves enough for correct ordering,
but I don't think there's a straight way to get a list out of it.

However, this should be unneeded,
because the "sort" command already sorts all objects basing on the value you choose (was it x,y coords. or an alterable value).

I also thought I could order by a fixed value I assign each object but all I see if order by X value, Y value, or 'move to layer'.

Yes, you can do the order by a "value you assign" with the layer object and "sort --> by alt. value" of your choice.

[Jarred]

Ah, the layer object sounds like what I want. Thanks!

[schrodinger]

I didn't undertand if you were already using that or not,
so I didn't specify more clearly to get that object...
but now that I know... go take the layer object asap !!
It's cross-platform, super easy and super useful!

You'll just need to setup a single action:
always ---> sort by (parameter) (decreasing/increasing)

if all your objects are far (top screen) to near (bottom screen)
as in many game setups,
all you'll need is "sort by Y position decreasing"

Layer object rules

[mobichan]

Objects generally are sorted based on their creation order. This is the same with objects you have already created in the editor (using "Create at Start of Frame" checked in the object's properties). So you can get a good sense of the z order based on this. It is also why it is a good practice to create your objects at runtime, so you are sure of the order.

[Jarred]

I didn't undertand if you were already using that or not,
so I didn't specify more clearly to get that object...
but now that I know... go take the layer object asap !!
It's cross-platform, super easy and super useful!

You'll just need to setup a single action:
always ---> sort by (parameter) (decreasing/increasing)

if all your objects are far (top screen) to near (bottom screen)
as in many game setups,
all you'll need is "sort by Y position decreasing"

Layer object rules

I'm definitely using this wrong. As a test I created 'Alterable Value Z' for a few objects and set the Always --> Layer Object --> Increasing sort by alterable value (and again with the decreasing to see what would happen) but the orders don't seem to be changing. Also, am I forced to use the 'Alterable Value A' nomenclature instead of something like 'custom-order'?

[mobichan]

You need to set the Alt Value to a number (0 being the lowest). Then it will sort 0 in front (or back, you should test this) and the higher numbered Alt Vals will be sorted accordingly. You can change the name of the Alt Value by double clicking it in the object's properties.

You should try the Sort by Decreasing Y action as well. That will just use the Y position of the object's hotspot and sort higher position values in front. Sort by Increasing Y does the opposite.

Here is a sample:
sorting.mfa

[Jarred]

Wow, this is awful. On a whim I set the layer object to sort by value 'F' since it's not at the arse end of the assignment world, and added variables to my objects up to 'Alterable Variable F'. The layer object forces you to use the alterable value positioning instead of calling by name?! I already have a bunch of objects created and this would force me to move all the variables I have set at position 1 to keep this easy. I'm guessing I don't have a choice...

I can't use the order by Y in my case which is why I was looking for a value based system. I just wish the Layer Object didn't hard code to position and let you sort by user defined names.

[Jarred]

Actually, more time than i want to devote. Think I'll try assigning Alterable Value Z to all objects at frame start instead of pre-defining on each object.

[schrodinger]

Hey Jarred,
you'll definitely better use alt.value Z (I always use that too... it also resembles "Z index" )
because it's likely you won't reuse that in all your objects.

You can't rename that, because each object may have its own proper value names,
so the layer object wouldn't know which name to address between the many.

I don't get the problems you are experiencing,
what's exactly going wrong?

As a basic guide:

-set your alterable values Z before sorting
-refresh your alterable values Z on a "always" basis if you plan to move objects order

if more than one layer:
-make sure all objects to be sorted are in same layer (or create stack of objects to be sorted per-layer)
-make sure you address the correct layer before using the sort-command (always -> set current layer to "XXX", sort by "YYYYYY")