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 r221

Scene graph and timeline updates; SDK updates; bug fixes

20 October, 2020 ()

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

This release brings some updates to using the scene graph feature in the editor, and some updates to the timeline bar as well. We have more work planned to keep improving the scene graph feature, so stay tuned for more usability improvements on that.

We've also further enhanced the SDK with the aim of making sure third-party tools can seamlessly import - and reimport - content like bone animations. This will require further work by third parties to support, but we're doing the work to make it possible for others to work with it.

Other than that there are some bug fixes and other minor improvements. We'll have another update for you soon!

Vous aimez cette parution ?

Faites-le nous savoir avec un pouce haut !

56
Exécuter r221

Nouveaux ajouts

21 favoris
Loading message in preview in case it takes a long time to start up

Changements

6 favoris
Timeline bar: hold Ctrl/Cmd while moving playhead to preview the timeline at that position
6 favoris
Timeline bar: selecting a keyframe now moves the playhead time to it and previews the timeline
6 favoris
'Set mesh point' action now allows -1 for texture position in relative mode

Corrections de bug

8 favoris
Possible corruption of folder project after making changes in the Animations Editor (regression in r220)
8 favoris
Scene Graph: layout view UI now is shown at a constant size regardless of zoom level
8 favoris
Scene Graph: clone hierarchy information when cloning using Ctrl/Cmd + dragging
6 favoris
Scene Graph: crash copying and pasting instances with scene graph information
4 favoris
workermain.js accidentally exported in two places

Mises à jour du SDK

4 favoris
Add IProject.GetProjectFileByName() and IProjectFile interface
4 favoris
Add IFamily.SetMembers()
4 favoris
Add IContainer.RemoveObjectType(), IContainer.IsActive()

Partager Construct 3 la parution r221 maintenant

  • 15 Comments

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

  • Was waiting for this thank you. Any ETA for the patch for Local File Folder on the stable channel.

  • They could make a desktop application because sometimes I run out of internet and I would like to continue making a game. Thank you

    • jav13r it should work offline for at least one week without internet, if you have problems you should report it on the forum

  • could you make construct 2 be in spanish thanks

  • The "Back" button does not work in the Browser plugin.

    Closes the game on click instead of executing the event

  • One idea for usability improvements would be to show the small icon (parent / child icon) on the right side in the event sheet (I think these are the actions) for better code readability. Like the Pin-Behavior have the Pin Icon ...

  • Will there be an update where we can post our created games on this certain website here for other people to view and like/dislike and comment on it; and to play together?

  • Awesome!

  • I guess that's a no on the mesh color filters.

  • hi Ashley, it's very encouraging that new features are coming to construct 3. But what about fixing bugs in existing features? I've been waiting for 28 days to fix a bug with layer rotation and Drawingcanvas, which really slows down my development plans.

    github.com/Scirra/Construct-3-bugs/issues/4240

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

      We're a small team with limited resources, and we deal with thousands of bug reports. Please be patient. 28 days is still not that long in terms of software development cycles.

  • "takes a long time to start up" <- mean the old worker mode bug? There seems no chrome setting/way to analyze worker loading.

    While developing new plugins, scirra keeps own internal idea list, is it bigger then aha.io one? While developing new features, there must a lot of possiblities which can be added. Or the barebone plugin is kept still there is enough public need for new features?