Ashley's Forum Posts

  • You need to complain to the site owners where it is hosted. App stores like the Apple app store and Chrome web store should have official ways to complain if you look around. You'll need to provide evidence you own the copyright and the location you originally published it, and then if you've made a good case they should take it down within a couple of weeks.

  • So how much is there to his claim that Apple won't approve apps that use the C3 runtime with IAPs?

    As far as we are aware IAP works in the C3 runtime and Apple accept the apps. If there are any issues you can file an issue following all the guidelines. I'm not aware of any such issues at this time. Remember that official materials on our site, such as the manual, are the best place to go for accurate information. Unofficial sources may be inaccurate.

  • It doesn't make sense to put a trigger in a function. Triggers only run when some outside event happens, like a mouse click. Functions only run when you use a 'call function' action. There is no overlap between these. Since it's invalid, the editor disallows it.

    I think you need to just rearrange the events so you call the function in the triggered event.

    Perhaps you are confusing functions with libraries - they're two different cases. A function is a single re-usable piece of logic, and a library is a collection of functions and other pieces of logic. Right now Construct doesn't have a good equivalent for libraries, but functions work analogously to how they do in programming languages.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
    • Post link icon

    Please contact supporttqp@scirra.com for help with payments. For security reasons we cannot deal with this on a public forum.

  • Ashley I thought the whole point of new "Load images" actions in C3 was to avoid that.

    No. "Load images" loads images that are currently unloaded. Placing an object in a layout tells Construct "this layout uses this object's images". Those are two different things.

    Is it technically possible to add an option to store images in memory permanently?

    Yes, place it on every layout.

  • Is there any way to preload images and keep them in memory even after switching to another layout?

    Yes - place them on the layout, as described.

    • Post link icon

    Sorry, in this case that type of report does not provide anything particularly useful.

  • It doesn't matter. This is the wrong approach for performance. Do whatever suits you best, and then optimise later based on actual performance measurements. Anything else is basically a waste of time.

  • iOS 12 removed the feature for security reasons. It's back in iOS 13 behind a permission prompt.

    • Post link icon

    I don't think so, it probably also redraws the OpenGL view on a click as well. This isn't really a useful direction to take the conversation though. The things I outlined in my first reply are the key things to make progress on this.

  • Projects use the same runtime code regardless of how you imported the project. So there is no technical reason for there to be any difference with imported C2 projects vs. other projects. If you encounter bugs as usual please report them following all the guidelines and we can investigate.

    • Post link icon

    Well, you can't really rule it out - driver bugs can be non-deterministic, and could involve memory corruption that depend on random unrelated details of the app. And nothing else significant other than redrawing an OpenGL view happens when you zoom the layout view.

    • Post link icon

    I've been thinking for the past few minutes but I can't think of any reason zooming in would cause C2 to close.

    Well, zooming will redraw the Layout View, which is rendered with OpenGL. That suggests it might be a GPU driver bug...

  • I tested your project on a Pixel 3 and got the following results:

    C2: first switch ~232ms, later switches ~100ms

    C3: first switch ~170ms, later switches ~100ms

    So according to this, the C3 runtime is faster in this case. I don't know why other devices would be different, maybe specific hardware is better or worse in different cases.

    Besides, C3 has a new feature that helps you hide this from the user - there's a built in memory management action "Load layout images", so you can load the next layout's images in the background while the current layout continues to run, and then switching layout will be instant. This feature is not available in C2. If I use "Load Layout 2 images in to memory" on start of layout in Layout 1, then it can switch layouts in around 5ms, which is far faster than you can ever achieve in C2.

    So as far as I can tell C3 is both faster at loading layouts and it has a feature to help guarantee that layout switching will be instant, which works here.

  • So it dosent matter how many family members there are?

    If by "family member" you mean "object type added to the family", then no. Families work in terms of instances, not object type members.