fedca's Recent Forum Activity

  • Currently there are some issues with the official 3D model that keep me and other users from updating to it from the sdk v1 addon to it. I'm writing this here in hopes it can be prioritized.

    SCALING: most of the times developers author their 3d models to scale in their software. Meaning different models all have the correct relative scale, correct texel size etc. This is generally important but critical for modular kits (e.g. wall pieces that snap together). Currently Construct uses scale base on the bounding box, which doesn't work with this common workflow, the expected behavior is that a model at scale 1,1,1 it will match all other models at scale 1,1,1 the way they match in the 3d software they were made in.

    ANIMATION BLENDING: blending between animations is very important to make animations look good, animation transitions look janky without it.

  • brainjulius Construct 3 has the LTS branch for this! https://www.construct.net/en/make-games/releases/lts

  • It moved to the position property, instead of x and y it now has x,y and z.

  • I mean if we could plan perfectly and never make mistakes we wouldn't need most things.

  • yea it can get complex, though a layer can not be a template/replica and global layer at the same time imo.

  • yea, that wasn't the best suggestion. The template layer should be the layer you set "semi-global" on, similar to global layer, with a context menu option "open original template layer layout"

  • Imo the most robust and flexible way would be fairly similar to how objectType templates work: you can set something as a template layer and you can set another layer as a replica of it (could just be that any aditional layer with the same name is a replica), then on that replica you can disable copying of specific properties, effects and for a more completete case we could even choose if sub-layers and content should be copied (in that case it could supersede global layers).

    The initial implementation could forgo that disabling of replication functionallity, so the replica layer would basically behave like a global layers without copying what's on the layer itself.

  • Nice work on this!

    Would it be possible to add a gamepad scripting interface, so it works independent of what's used internally?

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • Folder structure and c3proj sometimes desync with collaborative work when merging different branches, which leads to annoying merge conflicts that need to be resolved manually.

    But with flat folder structure removed, it may not be nescessary to store the folder structure in c3proj anymore. This could streamline version control greatly.

    I put this here for discussion, but I can also write a suggestion later.

  • The problem is that the layers content needs to be different, it cannot be shared:

    i.e. on level 1 there are mountains on the background layer and on level 2 there are clouds.

    But you still want a shared layer setup that is consisten across levels, like [postProcessing, foreground1, foreground 2, world, player, enemies, background1, background 2]. Now after creating 100 levels and noticing you need to make some change to that layer set-up you need to repeat it 100 times.

  • I have done this a bunch on accident too! Idk how to make it clearer, maybe using {my} (behavior name and icon) but this isn't used in conditions only in actions typically.

fedca's avatar

fedca

Online Now

Member since 6 Jul, 2017
Last online 12 Aug, 2026

Twitter
fedca has 88 followers

Connect with fedca