If an object did not have an angle property, you could use behaviors to circumvent that and rotate it anyway, which then caused bugs as rotation wasn't meant to be supported. This change ensures behaviors can't cause unintended rotation.
See this thread for details if you have issues with the Kaspersky browser extension: https://www.construct.net/en/forum/construct-3/general-discussion-7/issues-loading-construct-150535
Construct works on Mac in Chrome, Firefox and Safari.
Try using addEventListener("instancecreate") or addEventListener("instancedestroy") on an object class or the runtime. That's the standard way events are used, so if you ever see an event mentioned, that's what you do.
Please see this post: construct.net/en/forum/construct-3/general-discussion-7/local-file-folder-saves-chrome-147071/page-4
Please file any issues to our tracker following all the guidelines: https://github.com/Scirra/Construct-3-bugs
Issues not filed there won't be investigated, and note we need all the requested information to be able to investigate.
I just tried it and it worked fine. Please do file an issue, because we usually need much more information than this to solve problems, and it also avoids the problem being lost and forgotten.
I can't answer questions like this, it just seems too vague. What exactly is this hypothetical project doing? As before, you can get a precise answer by making a project, and measuring it.
If it doesn't need to, it doesn't. Sprites don't need their own copies of the collision polygons, so they don't make copies. Instances that don't use instance variables don't need to allocate anything for them, so they don't. This is basic software design stuff, if it did that it would be senselessly inefficient.
I'm not quite sure what you mean. But if you are wondering what the performance or memory usage impact of something is, measure it. That's the only real answer.
It's working fine here. If you think there's a problem please file an issue following all the guidelines, it's generally impossible to help without all that information.
Please note only problems reported to the issue tracker following all the guidelines. However this looks like a problem that was already reported and fixed: github.com/Scirra/Construct-3-bugs/issues/3809
Please file an issue following all the guidelines if you think something is wrong, there's very little that can be said otherwise.
There hasn't been any change regarding this.
The Audio object is still there in this release, but note it disappears from the list once you've already added it to your project.
Member since 21 May, 2007
The official blog for all things Construct and Scirra run by our employees!
Wider technology issues from Ashley's perspective.