fedca's Forum Posts

  • the system object has pre-loading actions

    This does not work well as you want 50% on the slider to somewhat be perceived as half as loud, this is why the exponential formula that has been posted multiple times works better.

  • Take a look at the persist behavior

    I don't understand how you can create a slider with the db range -infinity to 0, how can the user lower it to half as loud (-10db) if the slider also has to linearly go to -infinity as than -10 would be almost no change to the slider?

    So you need to remap the range in some way to get a usable slider.

    Using 10 ^ (decibel / 33) and 33 * log10(interval) gives me the range of 0-1 and feels like I can set volume in a intuitive manner.

    But maybe I am missing something.

  • you can use a local variable to which you add 2 every iteration.

    alternatively use loopindex*2 when checking

  • create the specific object and then in a sub-event pick last created familyObject

  • I am not a fan of the every tick condition even existing. Every event is evaluated every tick unless it's a trigger so adding or removing every tick literally does nothing.

    This sometimes tricks people that hear the advice "avoid running events every tick" to think that just not using that condition would improve performance.

  • "Add subfolder" should immediately focus the rename on the newly created folder. This would be better UX and would also be in line with creating a folder in the project bar or creating a new layer.

  • Seems like the index is tied to all children not only the children of that objectType. There also doesn't seem to be a way to know which one is which aside from trying each one.

  • Though if you have need for this a lot, it sounds a bit like a programming style issue, where instead of having the same events again for multiple objects you could use families or instance variables

  • Select the events and press r

  • set webGPU to no in the project setting to show webGL only effects

  • you can disable it with alt, which can be handy when you want to color pick into the selected instance. (there is also a "bug", which lets you keep that state, hold alt while going into the color picker, then it stays like that)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I have a suggestion that isn't directly connected to the Instance Bar, but made more obvious by it. I would assume most user will have the instance bar as a tab of another bar, i.e. like this:

    here the Instance bar is a tab you can switch to from the properties bar. The way the tabs are positioned has two downsides:

    • Redundancy with the header, leading to wasted vertical space.
    • They are positioned below, which goes against common conventions, making it less intuitive.

    My suggestion is this, here the tabs are positioned on top and replace the header:

  • For me it does ask if I want to close if there are any unsaved changes to the project.