Zacros's Forum Posts

  • Hi guys

    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.

    Thanks!

    Zacros

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Hi

    Apologies if this is a feature that's not yet implemented rather than an actual bug. Happy to change this into a feature request indeed :)

    Cheers

    Link to .capx file (required!):

    dl.dropboxusercontent.com/u/14301736/UndoIssue.capx

    Steps to reproduce:

    1. Open project.

    2. Edit the only sprite on the layout (there is only one frame of animation)

    3. Click the 'Set origin and image points' button.

    4. Change the location of the origin point.

    5. Press Ctrl-Z.

    Observed result:

    Origin/image point change is not undone/reversed.

    Expected result:

    Origin/image point location change is undone to the prior location.

    Browsers affected:

    Chrome: N/A - Editor.

    Firefox: N/A - Editor.

    Internet Explorer: N/A - Editor.

    Operating system & service pack:

    Windows 7 x64 SP1.

    Construct 2 version:

    R152 64 bit.

  • I know this is a minor bug/variance, but thought I may as well raise it just in case.

    Link to .capx file (required!):

    N/A - Interface logic bug without any open projects.

    Steps to reproduce:

    1. Load Construct 2

    2. Click File, then Preferences.

    3. Click Colours tab.

    4. Select any theme other than 'Default', i.e. "Visual Studio 2005".

    5. Click 'OK', observe GUI theme changed successfully.

    6. Repeat step 2 and 3 to view selected theme.

    Observed result:

    Selected theme is 'Default', regardless of chosen theme.

    Expected result:

    Chosen theme should be selected by default.

    Browsers affected:

    N/A - No project open.

    Operating system & service pack:

    Windows 7 x64 SP1.

    Construct 2 version:

    R152 64 bit.