https://linen.dev logo
Join Discord
Powered by
# ceramic
  • b
    What are you misunderstanding precisely?
  • f
    i assumed that it was all added together cumulatively, like transforms
  • f
    so if i had an object with its and its parents depth, in order, 1, 2, and 0, it would be in front of an object at depth 1
  • b
    Sorry I don't understand which object has which depth in your example
  • f
    An abbreviated object hierarchy
    Copy code
    dialog:DialogSubscene (depth=8008)
  ui:PrexUIObject (depth=0)
    adv:DialogADV (depth=2)
      mainBox:NineSlice (depth=1)
  backImage:Quad (depth=1)
  • f
    I expected 
    mainBox
    to be in front of 
    backImage
    because 8008+0+2+1 > 8008+1
  • b
    Yes that should be the case
  • b
    Oh wait, no
  • b
    ui:PrexUIObject is below backImage:Quad (depth 0 < depth 1)
  • b
    So anything inside ui:PrexUIObject (like mainBox) will also be below backImage
  • b
    You can make objects share the same depth space using 
    depthRange = -1
  • b
    Let's say you indeed want mainbox in front of backImage without changing your hierarchy
  • b
    You can do it if you set 
    depthRange
    of 
    ui:PrexUIObject
    and 
    adv:DialogADV
    to 
    -1
  • f
    oooh
  • f
    i should make 
    ui.depthRange = -1
    then
  • f
    (but not adv, i think)
  • b
    And set depth of mainBox to a value higher than backImage
  • b
    Yes that works
  • f
    i want all of adv to be together and higher and higher than backImage
  • b
    Then your suggestion is correct and should do it
  • b
    my brain is probably farts but how similar is ceramic's rendering engine to flixel's
  • b
    or OpenFL's
  • o
    Not similar.
  • b
    It’s similar in the sense that in all cases (ceramic, flixel, openfl) it’s about providing a high level API to the end user and translate that into textured quads or triangles that are sent to and rendered by the gpu
  • b
    It is different in how it does this in the details however
  • b
    And obviously the high level API is different on each framework
  • b
    I don’t know the state of this in flixel or openfl, but Ceramic has optimisations that include: multi-texture batching, “free” additive blending (in the sense that using it doesn’t need more draw calls), built-in rendertexture support with automatic ordering of the render targets
  • b
    I guess some of this exists in a form or another with other frameworks as well. I recall flixel addressing the multi-texture thing by creating texture atlases on the fly but I might be wrong
  • f
    Now that I'm doing the dialog and save systems I'm really starting to get into the weeds with the scene system
  • f
    - How scene transitions are done - How to preload a scene before switching to it
1...181920...124Latest