View a comprehensive history of all the performance optimisations in Construct 3 since the first release.
Optimise object grouping on spritesheets according to their usage across layouts, which should reduce memory usage
Avoid placing both very large and very small images on the same spritesheet, avoiding the case where loading a small image ends up loading a large unused image
Optimise time spent building spritesheets for extreme cases (e.g. thousands of frames in one sprite)
C3 runtime: improve performance when rendering lots of similar objects
Adjust spritesheeting algorithm so animated objects are more likely to be moved to their own spritesheet, helping to reduce memory usage
C3 runtime: optimise bounding box calculations for rotated objects
Support for asynchronous WebGL shader compilation, helping games using lots of effects start up faster
Reduce the memory overhead of the editor and C3 runtime, especially on systems with many CPU cores
Improve performance of C3 debugger inspector
C3 runtime: even faster Pathfinding, particularly with small cell sizes.
C3 runtime: optimise creating and destroying large numbers of instances with behaviors
Cloud save: now loads folders individually instead of the whole tree. Should improve load times for users with large numbers of files.
C3 runtime: constant event variables now directly insert their value to compiled expressions instead of calling a getter function
C3 runtime: small optimisation for running some object actions
C3 runtime: optimise system/single-global conditions and actions
C3 runtime: fix performance regression in destroying instances
C3 runtime: new expression compiler to accelerate expression evaluation (+20-50% performance for intensive projects)
Reduce the number of network requests when loading Google Drive file list
Small GPU performance improvement to effects rendering in editor
Improve the responsiveness of Cloud Save by caching cloud meta data for the length of the session (can be disabled in settings)