Official [Discussion] An option to ignore parent Sorting Groups

Hey! I accidentally stumbled upon this thread, because this is what I am looking for right now.
Unfortunately rendering at the root level would not help in my case. I would rather like to only ignore the direct parent sorting group.

Maybe an option to reference another sorting group which should akt as the new parent when Ignore Parent Sorting Group is enabled could help here. If nothing is referenced, it sorts on root level.

 

What is described by the OP is actually exactly what I need.

What does your hierarchy look like?

 

• How well does this solution fit your goals and objectives?
  100% fit
  
  
• In what situations would it work well?
  Especially good for those gameobjects whose parents change.
  Examples 1: are items that can be picked up and attached to the gameobject player.
  Examples 2: Special particle effects with sortingLayer on top like your Glow example..
  ..vv
  
  
• What difficulties do you see for your projects?
  Without this feature, I have to accept some defects in my game. The way to fix it is very time consuming or unsafe, so I voted for this feature.
  
  P/s: It would be Amazing if this feature is updated for 2019LST.

 

I appreciate the need for bypassing sorting groups internally in the hierarchy. The solution provided might be a good short term solution. I do worry about the sprite sorting becoming more difficult or confusing to work with in the longer term with multiple sorting groups and figuring out what bypasses what. This creates a kind of bidirectional communication structure on the component.

My initial thought would be to make sorting groups only affect sprite renderers set to a particular render layer. Then if needed multiple sorting groups could be added to handle each layer. So you may have multiple sorting groups at the parent level, but the component structure would remain unidirectional (only affects self/children transforms) and maybe a bit clearer? The downside to this of course is that currently layers in the 2D renderer add passes and overhead to the rendering. If that can be fixed or reduced I think layers are a clearer workflow to break up a group.

 

One more example, I have a gun and it's a child gameobject in the gameobject player, it has a ammo_shell particleSystem.
SortingGroup(Character) will cause the shells in the particle lying on the ground to be displayed on top of the player when player are below it. (2d sorting by Y position)

Also I have a suggestion that it would be easier to release a test by creating a BypassSortingGroup.cs script instead of creating an option on it.

 

Sorry for the total offtopic, but I wish someone told that to UGUI developers.

 

@rustum

Just wondering if this is coming out in 2022.1 alpha or beta?

 

Honestly, we desparately need 2D world space text. Having even the current 3D textmeshes within the sorting group of 2D sprites breaks batching, that's draw calls and set-pass calls, except fot the text.

Making a card game is a nightmare because text can never sort properly and run efficiently.

 

It would be nice to have some way to ignore sorting parent group. In my project, I'm spawning a simple sprite which transform needs to be the same as the parent but at the same time, the spawned sprite needs a different sorting layer.

Currently, I need to spawn this sprite somewhere else and then write a bit of code so it will follow a certain game object. With this feature, I would have a bit less work. Nice QoL.

 

@Leo-Yaik @Chris_Chu

Any idea when this feature will land and if it will be in 2022.1?