Serious performance issue in editor

Hi there.

I have a project with 180 levels (different layouts) using 1 main event sheet.

Whenever I want to edit event sheet, add something or even if I just open it C2 will freeze for ~10 seconds making it unusable.

I have been trying few things even creating version of game with just 20 levels and everything works alright. Is any way to go around this limitation? Maybe creating 180 event sheets with only "include main event sheet" in them?

Have you tried unticking the Preference option in Misc called cache icons?

Have you tried unticking the Preference option in Misc called cache icons?

Done that, no change.

It seems issue appears only when I want to access main event sheet. Everything else is working lightning fast when I close that event sheet.

How many events?

It would make updating / amending much easier if your event sheet was split into relevant sheets - animation, collision, globals etc - and these jst included into main. That way, you cane alter just the section you want without having to trawl through reams of events.

Just a suggestion.

Its just ~80 events. Many of them are disabled anyways.

They are grouped nicely. This event sheet is just basic mechanics of the game - movement etc.

Nothing overblown imo.

I cant say this is biggest event sheet I used, its regular by my standards but first time I have this issue (also first time I have 180 levels in a game though).

Can you send your project to so I can profile it and see if there's something slow in the editor? It would be a great help if you could remove any third party plugins before doing so, and provide instructions on exactly what to do to see the problem.

BTW it might help to create a folder-based project, delete all the .uistate.xml files, and try loading again.

Hi Ashley, I will clean it up and will send you example today then.

Thanks for answer

Can you send your project to so I can profile it and see if there's something slow in the editor? It would be a great help if you could remove any third party plugins before doing so, and provide instructions on exactly what to do to see the problem.

BTW it might help to create a folder-based project, delete all the .uistate.xml files, and try loading again.

Email sent, I will be waiting for updates!

I have noticed this to.

I 'think' its when your using an event sheet which is included by lots of layouts, i'm guessing the layouts have to be stored in memory or something.

My work around with this is to take parts of the code from the main event sheet, and spread them into separate events sheets, and include them in the main event sheet.

So you only have to worry about lag when you want to include a new event sheet.

Best wishes,

Tom

I have noticed this to.

I 'think' its when your using an event sheet which is included by lots of layouts, i'm guessing the layouts have to be stored in memory or something.

My work around with this is to take parts of the code from the main event sheet, and spread them into separate events sheets, and include them in the main event sheet.

So you only have to worry about lag when you want to include a new event sheet.

Best wishes,

Tom

I have been able to do some quick fix also, but it is not working for me since it makes everything few times longer unfortunatelly.

I have moved all layouts to dummy event sheet and keep only few for testing with original sheet.

I am tracking performance of my laptop all the time and CPU used by C2 is not bigger than 1%, disc usage not bigger than 2-3%, ram usage around 5%, GPU not even close to lag, yet this is the numbers I see when slow down occurs. Very strange imo.

Have you tried unticking the Preference option in Misc called cache icons?

I've been having the same problem and this seems to have helped in my case.

It's very odd - the issue isn't reflected in the task manager at all and I split my projects into multiple event sheets to help avoid this, but I'd still be hitting some kind of limit.

-EDIT-

Spoke too soon. I've since switched event sheets and it's grinding to a halt again.

Ashley, any update on this? Not sure if you have got my email with .capx

I got it, but we get lots of reports/issues to investigate all the time, hopefully I'll be able to take a look in the next week or so.

Just for the information of others in this thread: I was sent a .capx that demonstrated the problem and I've got a fix for the next beta (r188). Hopefully that will resolve it!

Great news Ashley, I will be waiting for new beta then