Ashley's Forum Posts

  • The solution is for everyone on your team to update at the same time. That's all you need to do.

  • What you're describing is essentially the same as saving a project in r225, and then opening it in r218. That's never been supported. Of course you can't use mesh distortion in r218 - the feature does not exist in that release.

  • Updating Construct does not affect the use of GitHub or any other source control tools. I need to understand exactly what has happened to be able to comment further or provide any help.

    For example, if you're seeing conflicts on source control, updating Construct does not cause that. Those are actually caused by submitting contradictory changes. That's a different type of problem. Even if Construct completely changed the project file format, that in itself does not cause a conflict on source control. You just need to submit an update which makes the necessary changes, and make sure it doesn't conflict with anyone else's changes. But in this case, Construct has not changed the project file format at all. So even that is not a problem here.

  • Correct, there is an issue for those that are using C3 Desktop. And it's a big one.

    And what is the problem exactly? I still don't know what the specific problem is that you're talking about.

    FYI there were also stable releases in late April, June, August, September, and now November.

  • We work hard to ensure a very high degree of backwards compatibility. Updates should never break projects. In fact you can open up projects made years ago, even with Construct 2 in 2012, and open them fine in Construct 3. If anything breaks, please file an issue following all the guidelines. As far as I'm aware, such breakages are very rare, and are usually corrected quickly.

  • In your original post you stated there was "a huge issue" in "c3 Desktop", and asked that "that this will be eventually looked into". It sounded like you were saying there was a big problem in C3 and asking for help, so I tried to find out more.

    As far as I can tell, all that's happened has been a routine stable release exactly as we've been doing for years and years. I don't think there's anything more I can add.

  • It sounds to me like this isn't actually anything to do with Construct. Of course software updates happen all the time no matter what software you're using. When using source control, it's up to you to manage updates with your team so you stay in sync - that's not specific to Construct. Also, I'm not aware of any problematic changes we made to the file format, it should be virtually the same and not cause any unnecessary conflicts on source control. Also there were no breaking changes I'm aware of so I don't know why your custom plugins would have broken, but it's up to you to maintain those anyway. I don't think it's fair to come here and tell us we shouldn't be making routine improvements to Construct, as we've been doing for about 10 years now without these types of problems seeming to happen to anyone else.

  • Construct doesn't have a plugin named "Text box" - there's the "Text input" form control, which doesn't support BBcode, and the "Text" object, which does (and I presume you mean that).

    As ever it's all documented in the manual page for the Text object.

  • Thanks for the feedback! We've worked hard to make C3 even better, as well as maintaining a high degree of backwards compatibility.

  • gustavoChico - I'm afraid I'm still mystified as to what the actual problem in r225 is that you're talking about. It still supports everything you've mentioned, including folder-based projects for use with source control like GitHub.

    That feature is still there, and so you can update to r225 just fine.

  • Construct picks an arbitrary existing instance to copy the properties from.

    If you have two instances with different properties, and create a new instance at runtime, which should it pick to copy properties from? There's currently no way to tell Construct which one to use as a reference, so it guesses one. It could use either.

    The main idea behind this is that if all your instances use the same properties, new instances get the same properties like you'd expect. If your instances use different properties, you can use actions after creating the instance to set the properties that matter.

  • I don't understand what you mean. Construct doesn't have any direct integration with GitHub. I guess by that you mean the folder based projects? But those are still supported in r225 just as they are in r218. (You just have to be on the latest version of NW.js, and the editor prompts you to update if you're on an older version of NW.js.) There's also been no change at all to Steam support between r218 and r225. So there shouldn't be any material change between these two releases. I don't know what you're doing or seeing that's behind this apparent claim that Construct has removed or changed these features - it should all still be there.

    As I said, staying on old versions generally causes more problems than it solves. We fix dozens of bugs and make loads of improvements between stable releases. If you don't update, sooner or later you run in to difficult problems that we already solved. People already routinely file issues and contact support about issues we've already solved, and it turns out they kept using an old version of the software, and updating fixes it. It's certainly not a panacea for all software problems!

    • Post link icon

    Please don't cross-post the same post, it makes things confusing. You already posted this here, and I just replied here. To avoid duplication and mixed up discussion, closing this thread.

  • All our stable updates roll out to everyone. This is routine.

    Why do you need to use r218 specifically? That will probably cause more problems than it solves (such as running in to bugs we've already fixed). Updating shouldn't be a significant problem, especially since we work hard to preserve a very high degree of backwards compatibility across years of releases.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It's a mistake in your code. The clientX/clientY properties of input events are in a different co-ordinate system to the game. You need to use the layer cssPxToLayer method to convert between the co-ordinate systems.