Les versions Beta ne sont pas autant testées que les versions Stables

Les versions Beta ne sont pas autant testées que les versions Stables

Branche Beta

Construct 3 r391

Addon SDK v2; better video support; prompt on close & lots more

14 May, 2024 ()

Envoyez-moi un courriel lors de nouvelles parutions

Don't miss out on the latest and greatest new features in Construct 3

Créer un compte

Notes

In this week's beta release we're introducing support for the Addon SDK v2. Addon developers should check this forum thread to read more about what that involves.

This week's release includes a variety of updates, improvements and bug fixes. The Video plugin has been upgraded to support more video formats. Previously you could enter a WebM source or MP4 source, but without specifying a particular codec. Now you can enter a primary source and secondary source, and choose the format for each. The format options now include more modern video formats such as WebM AV1 and MP4 H.265. This means you can now specify an optimal but not universally supported format like WebM AV1 as the primary source, and an older but ubiquitously supported format like MP4 H.264 as the secondary source, and it will automatically play the best supported video depending on the platform.

Further a small new feature on the Browser plugin allows adding a prompt on close when attempting to close the browser tab or window, much like Construct itself uses when closing an unsaved project. To prevent abuse browsers do not allow customizing the message, but it usually says something like "Are you sure you want to leave this page? Any unsaved changes may be lost."

Other improvements include Sprite's 'Spawn' action now supporting templates, revised artwork for the 'Ghost shooter' example (now referred to as 'Spell caster'), some more scripting APIs, and as ever a batch of bug fixes. Happy testing!

Vous aimez cette parution ?

Faites-le nous savoir avec un pouce haut !

20
Exécuter r391

Nouveaux ajouts

8 favoris
Video: support for additional video codecs like H.265 and AV1
4 favoris
Mobile advert: add 'offset' parameter to 'Create banner advert' action
7 favoris
Browser: action to enable warning prompt on closing browser tab/window
8 favoris
Sprite: add 'template' parameter to 'Spawn' action
7 favoris
New example 'Sunset runner'

Changements

7 favoris
Replace 'Ghost shooter' examples/guided tour with 'Spell caster'
4 favoris
Video: replace properties with primary and secondary sources with dropdowns for format
5 favoris
Windows WebView2: update WebView2 SDK to v1.0.2420.47

Corrections de bug

6 favoris
SpriteFont: did not handle alpha of background color correctly
6 favoris
Windows WebView2: failed to run if project did not use any icons
5 favoris
Some effects did not render correctly with fog in 3D (regression r380)
5 favoris
Possible error destroying object with behaviors (regression r390)
4 favoris
Ease editor: ensure handles the same size regardless of zoom
5 favoris
Custom eases: certain edge cases of custom eases not producing the expected results
3 favoris
Templates & hierarchies: possible hang when used in combination that caused infinite recursion
5 favoris
Hierarchies: loading from JSON not restoring all the state of all the instances in a hierarchy
4 favoris
Tilemap bar: drawing tools getting stuck if the pointer is released while scrolling Layout View with spacebar
5 favoris
Tilemap bar: some combinations of mirror, flip and rotation not producing the expected results
4 favoris
Layers: possible runtime crash removing a layer
5 favoris
Timeline bar: crash duplicating a timeline with a color property track
5 favoris
Timeline bar: crash after deleting property property tracks then trying to move the corresponding instance in Layout View

Mises à jour du SDK

5 favoris
Support for addon SDK version 2

Scripting updates

5 favoris
Add IInstance.dt
4 favoris
Add IBehaviorType interface
5 favoris
Fix indents being added to template strings in scripts in event sheets

Partager Construct 3 la parution r391 maintenant

  • 28 Comments

  • Order by
Want to leave a comment? Login or Register an account!

  • Sooo... according to the forum thread about addon SDK 2.0, you plan to break every single addon ever made for Construct 3 and every single project ever made with C3 using at least 1 addon on purpose in approx 1 year ?

    What are you doing Scirra ?

      • [-] [+]
      • -8
      • Ashley's avatar
      • Ashley
      • Construct Team Founder
      • -8 points
      • (8 children)

      Addon developers need to update their addons to SDK v2 and they will continue working.

      • 2 months ago you promised you will support Addon SDK V1 documented features indefinitely in this thread. So it looks like the plan is to break this promise.

        construct.net/en/forum/construct-3/scripting-51/method-access-engine-181244

        The exception to all this is the documented, supported APIs. If you use those, we promise to support them indefinitely

        You can of course stick to the documented APIs and do anything you like, and we promise to support that indefinitely

        Load more comments (3 replies)

      • What makes the Addon SDK v2 so important that it's worth breaking all 3rd party plugins?

        If I understood correctly, v2 is mainly to prevent plugin developers from using undocumented APIs.

        In other words, you value your control more than the projects of your customers.

        Your engine is so slow on Android and iOS; you complain of lacking time to accommodate the most requested essential features, but still have time for this?

        Stop lying to us!

        Load more comments (3 replies)

  • breaking every project sounds like a bad idea.

    If you're calling it Construct 4, then it might be more acceptable.

  • Updating the SDK to version 2 will break a lot of plugins.

    I see you really want to make Construct3 a choice for teaching schoolchildren, but not real game developers.

      • [-] [+]
      • -2
      • Ashley's avatar
      • Ashley
      • Construct Team Founder
      • -2 points
      • (0 children)

      The SDK version 2 supports all documented APIs that were in the v1 SDK. It will only break addons if they ignored a warning in our SDK documentation saying not to use undocumented features. The SDK version 2 also uses an industry-standard design also used by all other software and tools in the industry.

  • I strongly suggest allowing us to stay on the current release version (r388.2), which is possible, but having export-related updates released to that version as well. (Maybe linking these updates to the export service)

    Updates like Targeted API from Google, Cordova updates, IOS, etc..

    This way, we can preserve our current projects exportable at anytime with up-to-date APIs, and you can go forward with SDK2 as you like. Sounds win-win for both to me.

  • The new Addon SDK 2 is a good idea, but the way legacy addons are being handled is just abysmal. People are working with projects that they have poured years into with addons that simply will not be updated anymore. There has to be a way to use "legacy" plugins in future construct versions. Especially as most addons just add additional objects that can simply be deleted in the editor without any issues, I don‘t see how there shouldn‘t be a safe way to continue supporting basically ALL addons that exist right now.

      • [-] [+]
      • -4
      • Ashley's avatar
      • Ashley
      • Construct Team Founder
      • -4 points
      • (3 children)

      At the moment, projects years in the making are already at risk of being permanently broken by Construct updates. This is happening and we are getting desperate customers contacting support and sadly there's little we can do to help them. This is the problem we want to solve, and this process is necessary to ensure that in the long run - years down the line - this no longer happens.

      • I see, but the majority of users have not experienced such issues. I have multiple old projects that I want and need to maintain and especially for mobile games (with new requirements coming up all the time) construct updates are necessary.

        Breaking all older projects to avoid breaking a few just isn’t the right move. The amount of customers complaining after this change goes through will be much bigger than now. There really has to be a way to make this change, at least, only affect newly created projects. Breaking all old ones in the future is simply no sensible solution, especially considering that the reasoning for this is to avoid breaking projects.

        Load more comments (2 replies)

  • Thank you for adding templates to the spawn action and the browser warning prompt action.

  • I already hate Custom Addons since i realized how stupid they are. Not in a good way, i mean they are really useful sometimes only when the developer itself care about for a brief moment or really need money from their plugin sales. until then they disappear and left the plugin unmaintained.

    My suggestion, use built-in feature construct has. it is very powerful enough to create online databases, purchases, and even custom patch and online updates.

  • does this mean can have a transparent alpha layer on a video now?

  • Ashley did you change something in DragDrop behavior?

    In Stable Relase all works fine Im clicking on Item (item spawn in mouse position) and im hold left mouse button item is really dragged. But in newest updates when i do this same my obiect are spawnet but not dragged: youtu.be/PNef1kbHUoU

  • Great update! Is there a way to use the exit prompt as an event trigger?