The issue is on larger projects, the C2 editor becomes increasingly slower and the performance lacks. I have attached a sample capx to try and replicate this issue. On a new project, adding an action takes a fraction of a second. Fast enough, you do not notice. On a larger project, it can take easily 1-5 seconds, slowing down your productivity and making C2 near unusable long term.
I have noticed on computers, the extended use of these poor performance projects can also lead to poorer performance over extended use leading to a computer restart required. Although this could be two separate issues that are just correlated.
Attach a Capx
chadorireborn has created a better example here in this thread:
Description of Capx
Fast.capx: a simple project to show the initial speed of the editor. Simply edit the action in the CAPX and you will notice the dialog pops in a fraction of a second (a quick blink).
Slow.capx: a larger project to demonstrate the slowness. Do the same as the first CAPX, simply go and edit an action already there. The window will take 1-5 seconds depending on the computer you use.
Steps to Reproduce Bug
- Open both CAPX
- Edit existing action in both CAPX
- Repeat several times, noting the time it takes for the dialog to pop
Action dialog takes extremely long to open. Other performance issues exist, but this is the main concern. Adding actions, editing actions, copying variables, reusing variables, adding objects, cloning objects, moving objects into subfolders, it all goes unbearably slow once the project gets to this level.
Dialogs are reponsive and fast.
Operating System and Service Pack
I have tried this on the latest Windows 10 version, on multiple computers. The same issue exists, the only difference is how slow the dialog pops open.
Construct 2 Version ID
- Capx vs Project folder - no difference
- HDD vs SDD - no difference
- Disabling object icons - no difference
Edit (Jan 5th, 2017): Still no resolution. Updated workaround section.
chadorireborn has created an even better CAPX to show the performance degrades terribly on larger projects: https://www.scirra.com/forum/poor-c2-editor-performance-on-larger-projects_p1156416?#p1156416
jan 6th: updated user count that are reporting this issue
jan 8th, 2018: updated user count
jan 11th, 2018: updated user count
jan 15th, 2018: haZba has created another demo CAPX here: https://www.scirra.com/forum/poor-c2-editor-performance-on-larger-projects_p1157777?#p1157777
Jan 20th, 2018: A few test ran, numbers, evidence, tear-down of a project, and so forth. Estimation of 20 hours lost to the bug in best case scenario, 2 hours on smaller projects. See it here: https://www.scirra.com/forum/poor-c2-editor-performance-on-larger-projects_p1158480?#p1158480
Jan 22nd, 2018: A beta release, r251 has been made available which addresses some performance issues when adding/editing actions. Results look good from my own testings and users are reporting big differences.
Some other facts found/reported:
The issue is not due to NVIDIA graphics cards (as shown by using Virtual Machines, and non-nvidia onboard graphics).
C2 has very inconsistent behavior when the issue occurs (freezing at times, inconsistent load times)
it is not a recent W10 issue or driver update, as shown in digitalsoapbox post here:
(jan 15th, 2018) I have received a report that this bug exist on the original Windows 10 Build, meaning a windows update did not cause this.
- Rebooting the computer regains *some* performance, but dialogs still take abnormally slow time to pop
- The issue does not appear to exists in C3, but it is not a good workaround due to: " I had to delete my incompatible plugins.
Because of the fact that C3 isn't cross compatible with C2, it's only a one way conversion. I would say this is an impractical solution for
C3 isn't fully equipped with essential 3rd party extensions yet. It's way too soon to permanently move especially with the limited SDK of C3."
Current count of people that have reported this issue (as of Jan 12th, 2018): 14
Note: This is a count of individual users and not machines. The count of machines is MUCH higher. At the moment, roughly 95% of windows 10 users asked, are hit with this issue.
Please post here if you have this issue.