I'm trying to debug my layout to see why it's taking ages to load the preview from Construct 2 (R152 x64).
I've narrowed it down to the cache file creations. I have a single completely blank/new layout with no event sheet.
I do have about 40 sprites, each with a total of 72 different frames of animations.
None of these sprites are in use on any layout or event sheet, they just exist within the Construct 2 project.
When previewing the blank layout via Node-Webkit, it takes around 10-15 seconds before the loading percent reaches 100% and creates approx 8,500 files in the cache folder (C:\Users\Zacros\AppData\Local\TestProject\Cache).
This is only one level's worth of graphics and I'm planning on having plenty more, with even more characters/sprites.
When I export the project as a standlone Nodekit application, it takes less than a second to load up so I'm fairly relieved that the users won't experience this delay - however it's becoming very painful to debug/create further levels.
I'm resorting to having to create new project files for each new level/screen and then copying/pasting objects/events to the master project when I'm ready to release/test the final versions.
Does anyone have any suggestions to improve the preview speed at all? My AppData folder resides on an SSD, so little to no improvements are available from better hardware.