Ashley's Recent Forum Activity

  • I don't think a "in exponential, out elastic" tween can be automatically designed. Would it just paste exponential in for the first 50% and elastic for the second 50%? It might not line up, so it would jump in the middle.

  • Maybe as a quick work around, have the first timeline set to Start on Layout 1 by default?

    The problem is timelines aren't actually associated with a layout - they are essentially global and can be used on any layout, and so there also isn't really a good "default layout" to play them on, according to the current design. The default for the first timeline could be changed, but then the first timeline works differently to any timelines you add next. In my experience that just moves the stumbling block for beginners - the question just moves from "why doesn't my first timeline play?" to "why doesn't my second timeline play?". Even if you have to figure out how to play the first timeline, at least you've learned the principle and can apply that to any timeline, instead of relying on defaults you haven't found out about yet.

    I agree that it would be nice to have a smoother experience for first-time visitors, but I'm not sure how to best solve this without introducing a new inconsistency.

    Maybe have it use the framerate from the first timeline?

    We don't yet have a property named 'framerate' for timelines... do you mean what we currently call 'Steps per second'?

    Maybe an export option for making the bottom layer background transparent then?

    Well, what is the bottom layer? That is a surprisingly difficult question. What if the bottom layer has sub-layers? Maybe it's the last sub-layer? But that is drawn after the root bottom layer, and could well be transparent anyway. What about the root bottom layer? That could actually be transparent and only used for a compositing effect, and in fact a sub-layer has the opaque background. There could be multiple sub-layers with opaque backgrounds, some used for fade effects, and only one truly being the background.

    I don't think there is actually a good way to automatically identify "the background layer", so I don't think we can make a reliable setting for it, hence the advice in the dialog instead - presumably the project author knows!

    The original post was full of swear words; I've removed them. Even after that the post is full of abusive language towards the author of the template. This is completely unacceptable and regardless of the merit of any claims or criticism, it goes far beyond any reasonable or good-faith critique. The Forum & Community guidelines are written specifically to avoid this kind of post.

    The author of the post has been banned in the past and repeatedly warned about breaking the Forum & Community guidelines and it was previously made clear to them they were on absolutely their last chance. They have now been banned. Thread closed.

  • See collaborating on projects in the manual.

  • I thought Safari did support it.

    Either way, you can record a WebM video and convert it afterwards with a tool like ffmpeg or some of the free online services that can do video conversion.

  • 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.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • - 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 supportvsk@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.

Ashley's avatar

Ashley

Early Adopter

Member since 21 May, 2007

Twitter
Ashley has 1,428,280 followers

Connect with Ashley

Trophy Case

  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Forum Unicorn Made 10,000 posts in the forums
  • Forum Mega Brain Made 20,000 posts in the forums
  • x108
    Coach One of your tutorials has over 1,000 readers
  • x62
    Educator One of your tutorials has over 10,000 readers
  • x3
    Teacher One of your tutorials has over 100,000 readers
  • Sensei One of your tutorials has over 1,000,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • RTFM Read the fabulous manual
  • x36
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs