Ashley's Forum Posts

  • We sometimes make internal changes to the project file format, and we make sure it's backwards compatible, but it is not forwards compatible. This is why you can never guarantee a project will open in an older release and why it's not something that is officially supported. Some people have got in to the habit of working around that by modifying the project file directly, but as you've found, sometimes that just won't work, because it's not actually supported.

  • Project files are not actually backwards compatible with older Construct releases. If you manually edit the file to open in an older release it may or may not work. In this case it does not work.

  • I meant my super old ticket, which we re-opened last week. It is not related to any new changes, it is an old issue since we started with adaptives.

    This isn't anything to do with splash screens though is it? I'm not sure why you brought it up in the context of the new splash screen support?

  • Actually you can already raise the target to 32 (which is actually the default one by cordova now).

    Ah, I assumed 32 was for Android 13 beta, but you're right, it's for Android 12L apparently. I've updated the next beta to target API 32.

    ShowSplashScreenSpinner

    SplashMaintainAspectRatio

    Removing these is a bit tricky: ShowSplashScreenSpinner is still documented as affecting iOS, and SplashMaintainAspectRatio still applies for legacy Android builds. I've removed the latter from the latest builds though as it is indeed no longer a documented property.

    Also it would be handy if you added these lines to the config.xml

    Those tags are already the defaults, and I'd rather not re-specify the defaults, as the defaults can change and tracking the defaults manually adds to maintenance headaches in the long run.

    Also as mentioned in the bug tracker, the icon is not handled correctly at the moment, but there is an easy fix for it.

    I don't see a report for this, and it looked OK in my testing. Did you mean to file an issue?

    Also, would it be possible to format the config.xml file?

    I didn't realise it wasn't formatted! I always looked at it in an auto-formatting tool. I added formatting for the next beta.

    Also, any particular reason you still have a config.json?

    That's used by the build service.

  • - You still have to add a timeline controller and create an event to properly export an animation.

    It's simpler to set the 'Start on layout' property of the timeline.

    - When exporting your animation, the default settings for Duration and Framerate don't match with the settings you create for the project.

    I'm not sure Construct can easily guess the default duration if you have multiple timelines of different durations, and they can also start at different time offsets, which is why this is still a manual field.

    - The transparency tip is nice, but a checkbox to automatically make all layer backgrounds transparent would be better.

    That will break some cases, like using a non-transparent layer with opacity for a fade transition. Forcing all layer backgrounds transparent will remove the transition and break the animation. It's better to make the bottom layer transparent.

    Please contact supportwkk@construct.net for any questions regarding payments. For privacy reasons we cannot deal with these on a public forum.

  • In Construct 3 (since you posted in the C3 forum), extract all the files and run the WindowsIconUpdater.exe tool in the resulting files.

    C2 doesn't support that so you will have to manually update it using third-party tools.

  • I'm afraid it's impossible to help from just this information. Please file an issue following all the guidelines, as we need all the requested information to look in to it.

  • It sounds like you were actually talking about C2, but you posted in the C3 forum which works differently, so some of the replies you got were focused on that. Moved to C2 forum.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Construct Animate is not a huge addition to our workload. If it actually did double our workload, it would be totally infeasible, and we would not be doing it. Any time we make a big change lots of people like to predict the doom of our company, as has happened several times in the past, but here we still are.

    As I pointed out previously Construct Animate has been in research/development since last summer. Over the past year we have continued to add loads of updates to Construct 3, and I don't believe anybody over that period noticed that updates were any slower than usual.

    Please keep your posts in this thread civil, on-topic and within the Forum & Community guidelines, otherwise I will close this thread and ask that feedback be posted in individual separate threads.

  • You may need to enable "force own texture" on the layer. If you have a transparent layer rendering to its own surface, things like transparency-based compositing work properly. Otherwise if everything is rendering directly to an already-opaque surface, transparency-based compositing will not do anything interesting.

  • Collaboration is a technically very complicated thing, as it is easy for people working simultaneously to make conflicting changes. Something like Git is probably a necessary tool to manage collaboration.

    An alternative approach is to avoid multiple people working on the same Construct project. For example one person could be the game artist producing all the sprites and backgrounds, and another person could import that to Construct and build the project. Then you don't need to handle the possibility of conflicting changes in the same Construct project.

  • AFAICT occlusion culling is generally only applicable to complex 3D games. Being a primarily 2D engine I don't think it is really applicable to Construct. It just means stuff outside the viewport is not rendered. Unless you have an incredibly intensive game with tens of thousands of objects, it's probably not anything you have to think about at all.

    The same question was just posted in this thread which has answers, so closing this one so we don't have duplicate threads.

  • Loading r293.3 works fine for me. I don't know why there would be a problem loading it - it's loading the same version as you would have previously been using.

    We work hard to make sure changes don't break anything. By the time of a stable release most of the changes have also had several weeks of public testing in beta releases, but sometimes things slip through the net. I apologise for any inconvenience with changes in updates, but it's impossible to make any changes to software without some risk of breaking existing things; sometimes mistakes are made and not caught by beta testing. The best thing to do is to report any problems by filing an issue following all the guidelines. It's also very helpful if regular users can at least occasionally try their projects in the latest beta release, and let us know if anything isn't working, so we can make sure any accidental breakages are fixed before the stable release.

    I'd add we also have fixed loads of other bugs between r293.3 and r302, so the overall reliability of Construct has definitely improved, and will continue to improve. The longer you stick to an old release the more likely you are to end up stuck on some other issue that we already fixed, so it's best to regard that as a temporary measure and focus on getting your project working in the latest release.