https://linen.dev logo
Join Discord
Powered by
# ceramic
  • a
    if they're in multiple scenes load in app i guess
  • a
    no need to reload it in every scene
  • b
    @faint-toothbrush-51643 yes, and you can still make those assets accessible within the scene's 
    assets
    object by setting 
    assets.parent = app.assets;
    in your scenes
  • b
  • f
    oh i've just been accessing app.assets directly
  • f
    i know i can access app.assets, i was just asking if that's optimal for this case
  • a
    as a blanket "yeah" it seems so, unless you have any particular reason you don't want it preloaded early for each scene then go for it
  • a
    but this is one of those things that is context dependent
  • b
    Sure if you have some assets that you use on several scenes, better to have them loaded before. Using app.assets for that is valid
  • f
    oookay i've finally implemented that and it isn't working
  • f
    aaand i worked around it
  • f
    it seems that at least in new Project(), if you try to load a non-standard asset type, it doesn't work
    Copy code
    hx
    app.assets.add(Spines.HUMAN);//error
    app.assets.addSpine("human");//works
  • f
    nevermind, that actually apparently doesn't load it at all
  • f
    when i do that, i get
    Copy code
    Load spine human C:\Haxe\ceramic\plugins\spine\runtime\src\ceramic\SpineAsset.hx:70
Failed to retrieve json path for spine: human C:\Haxe\ceramic\plugins\spine\runtime\src\ceramic\SpineAsset.hx:94
Failed to load asset human (SpineAsset(human human)) C:\Haxe\ceramic\runtime\src\ceramic\App.hx:865
  • f
    okay i've actually made a functional workaround this time
  • b
    Difficult to say what’s going wrong without having the whole context anyway
  • b
    Soon™️
  • g
  • g
    comedy ™️
  • I'm going thru entities and components. One thing that i noticed, I find it weird you didn't provide a factory approach to the component systems, as they must be created only for 1 Entity. And the entity literally disposes the component instance (on your behalf) if you assign another one under the same name... as i migrate this to Flutter, it threw an exception right away on the "event", for obvious reasons 😛 when disposing the same component. I think i might go with an implementation based on "generics" or Types... on my end like: `entity.addComponent<Type>();`
    m
    I'm going thru entities and components. One thing that i noticed, I find it weird you didn't provide a factory approach to the component systems, as they must be created only for 1 Entity. And the entity literally disposes the component instance (on your behalf) if you assign another one under the same name... as i migrate this to Flutter, it threw an exception right away on the "event", for obvious reasons 😛 when disposing the same component. I think i might go with an implementation based on "generics" or Types... on my end like: 
    entity.addComponent<Type>();
  • Idk how to call it
    m
    Idk how to call it
  • Resolve instance initialization at runtime? Like component metadata does?
    m
    Resolve instance initialization at runtime? Like component metadata does?
  • Did you read this: https://ceramic-engine.com/guides/components/?
    b
  • Yep
    m
    Yep
  • I know both systems are there
    m
    I know both systems are there
  • var entity = new MyEntity() var component = MyComponent() entity.component( ‘a’, component ) entity.component( ‘a’, component )
    m
    var entity = new MyEntity() var component = MyComponent() entity.component( ‘a’, component ) entity.component( ‘a’, component )
  • component disposed
    m
    component disposed
  • Why would i instantiate a component by itself when only is meant exists inside an entity?
    m
    Why would i instantiate a component by itself when only is meant exists inside an entity?
  • Thats was my point
    m
    Thats was my point
  • `Component` is only an interface
    b
    Component
    is only an interface
1...101102103...124Latest