https://linen.dev logo
Join Discord
Powered by
# ceramic
  • a
    yeah, i've never really used event based systems so as soon as you started hinting at that I was like "I may be missing some info here" 😆
  • a
    almost the main set of components are done for the haxeui backend
  • a
    I have like 1 or 2 more very persistent bugs/issues and i'd say it is usable
  • a
    it'll go up without the canvas component but, that will be the only thing i want to leave
  • a
    the main bug i need to fix there is the tree view hover
  • a
    which is mouse event related but just trying to figure out what will work properly with each backend is the nuance
  • b
    Meanwhile, I'm seeing my first texture in Ceramic extracted from an aseprite file yay
  • s
    Epic win!
  • b
    This atlas was created at runtime from an 
    .aseprite
    file
  • b
    (still need to detect duplicates)
  • b
    Alright alright, duplicates are detected and removed, and when loading multiple aseprite/ase files, everything is packed within the same texture atlas on the fly, so that it's optimal for performances and memory usage
  • f
    Are you able to manipulate the layers of the aseprite sprite at runtime? Like tinting one layer?
  • b
    I mean, I could change one layer setting/tint when loading at runtime, but only at load time, as after all the layers are flatten into one frame and put in the atlas
  • b
    Actually, there are still duplicate regions in the generated atlas above. There are 3 identical arrows. This is because the original arrow images are at different positions to make the animation. But when trimming white spaces around, the remaining area is identical. I'll handle that case too (which is not even handled by aseprite when exporting from it)
  • b
    (basically that will mean: animating frames by moving pixels won't cost more pixels in the atlas anymore)
  • m
    cool u have sub textures region/frame rect in ceramic?
  • m
    separated
  • b
    yes, there is a 
    TextureAtlas
    object
  • b
    And right now, I am setting up an utility to generate atlas at runtime (because I need it for aseprite parsing)
  • m
    separated
  • b
    What do you mean?
  • m
    I lost context ha
  • m
    Nvm i meant texture region vs frame rect for rendering with offsets like the arrow example
  • m
    @billowy-waiter-28954 ceramic is based on lost or linked lists for the rendering tree pipeline?
  • b
    Mmmh I guess no? Ceramic simply orders visuals and the renderer walks through the visuals array to render them
  • b
    Nothing very fancy except some batching tricks
  • m
    Example
  • m
    Batching based on … alpha, blendmode texture?
  • m
    How do u work around the painters algorithm?
  • b
    No there is nothing specific about alpha & opaque. Everything is rendered back to front sorted by depth (but also texture, blendmode if not normal or additive, and render target) regardless of it being opaque or transparent. Depth buffer is enabled though, so I guess the GPU is still helping a bit
1...979899...124Latest