Ashley's Forum Posts

  • It's not yet supported in the mobile editor.

  • By the way you're also using undocumented unsupported features in that code, so I can't offer any further help if it's not working.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It looks like you have a typo in the filename.

  • Users can submit tutorials. There are well over 1000 tutorials there.

  • How can Scirra get us intermediate/advanced user to shoulder the burden of improving documentation?

    Users can submit tutorials. There are well over 1000 tutorials there.

  • That's good to hear, but if the problem is not actually solved, it's hard to be confident it won't come back in future again...

  • You can right-click the old "On function" conditions and automatically convert them to built-in functions.

    • Post link icon

    It completely depends on what you're doing and what you're comparing it to.

    Running events has relatively high overhead compared to JS code, so if you have event-heavy code doing things like intensive calculations with lots of loops, the equivalent JS may be faster.

    On the other hand, some parts of the Construct engine are extremely well optimised, and have been carefully honed over the years with all our long experience of performance testing JS code. If you write your own scripts to do your own code instead of using the engine, it could well be significantly slower, unless you put in the same effort we have. One example off the top of my head is if you ignore Construct's collision engine and write your own custom one in script, it could well be significantly slower. Not only could it be slower in absolute terms (slower when doing the same work), but it could be slower in algorithmic terms (as in getting exponentially slower as your game gets bigger, whereas Construct's engine is highly scalable and can keep doing about the same amount of work no matter how much bigger the game gets).

    As ever performance benchmarks are the only way to know for sure.

  • It's not currently supported. It might be difficult to add a feature for it, too. There are several critical performance optimisations for picking through sub-events that impose strict rules on which objects can be picked. So in general script could not simply go ahead and pick instances in some arbitrary object - unless we de-optimised the entire event engine to allow it.

    Maybe the best solution would be to come up with some way of combining picking with JS callbacks, e.g. using "Pick by evaluate" calling a JS function.

  • Are you ticking "Remember this access code"?

  • Glad you like it!

  • Not yet - I think we just need to add some functions to look up layouts.

  • Oh, and let me know the issue number here. We've had various reports of similar sounding issues over the past few months and it's always been a mystery what's going on, so it will be interesting to see if Google can find an issue.

  • I'm not sure it's the right place, but filing an issue at crbug.com might at least be a good place to start. It's the bug tracker for Chrome, but it also covers the WebView. If you explain the problem with the WebView app not being able to update, they might be able to do something about it.

    I think the weirdest thing is if it worked with v71, then from what you've said it sounds like failed updates beyond that have actually reverted it to the factory v43. A failed update should have at least left it on v71!

  • That's weird, I've not heard of that happening before... I guess you'd need to contact Google to get to the bottom of what's going on there.

    You can switch the project back to the C2 runtime, which works with older browsers. However it has fewer features and reduced performance. You might need to remove some things from your project to switch back. See the manual entry on the C3 runtime for more details.