Ashley's Forum Posts

  • It is actually working correctly given the way it's currently designed: when the animation loops it goes back to the "Repeat to" frame, which is frame 0. This restarts the animation when playing forwards, but sticks it at the end when playing backwards.

    We're due a stable release soon and this is not a regression, so I won't fix this for the next build. However I'll leave the report open and figure out something for the next beta cycle (I guess a "set repeat-to frame" action would do it).

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Can't reproduce with Edge on Windows 10 build 10240. You can check your version by running "winver". I guess you are running an older preview with a bug that got fixed, so closing. (Providing screenshots would be useful in future).

  • As far as I can see the problem is specific to asm.js physics. If I set the .capx in this thread to use box2dweb physics, it works fine as a packaged app when tested from chrome://extensions. If anyone has any issues with the Chrome Web Store when not using asm.js physics, please file a separate bug report for that.

  • Closing as not a bug. The Anchor behavior keeps its relative position in the viewport, it does not snap it to the corner.

  • Can't reproduce - I exported Space Blaster as an Amazon packaged app, zipped the result, uploaded it and the Amazon developer section accepted it after clicking "Save". The launch path defaults to /index.html, which is one of the files C2 exports. Perhaps you accidentally zipped the folder instead of the files.

  • Closing as not a bug. Your project uses "Letterbox scale" fullscreen mode, so will scale the display to fit the browser. The browser is usually smaller than the full size of the monitor, so the displayed game will appear smaller than the C2 preview.

  • It works correctly in the Safari browser on iOS on an iPad. The iPhone displays it fullscreen with video controls, but that is how Safari handles video playback on the iPhone and there is nothing we can do to change it. The code C2 runs in the XDK is identical, so if the XDK does something different to Safari, that suggests the bug is in the XDK and not Construct 2. I think you should report this to Intel instead.

  • Can't reproduce in r211, besides, if clicking the top-left menu button crashes C2 then I'm sure we'd be hearing about it from loads of users, but so far it's only you. I think that suggests an issue specific to your system rather than with C2.

    The .capx you shared is completely empty so there's nothing to see changing when toggling layers. I tested it with the Space Blaster demo project and it was working fine.

  • It works in every browser except for Opera, so it must be an Opera bug. You should report it to the Opera developers instead.

  • Daedolon - the SID must be unique for every object. It is just a random number. It is used by the savegame and multiplayer systems to uniquely identify objects without relying on their name (which would break if you renamed them) - so those features will be broken if multiple objects share SIDs.

  • Closing as by design.

    Previously the 'loader layout' option (which your .capx has set to "Yes") was ignored in preview mode, and only had effect after exporting. The latest betas enable loader layouts in preview mode. A limitation of loader layouts is that you cannot create any objects from other layouts until the loading has finished (reached 100% progress) - otherwise it would have to load the entire project to display the loader layout, defeating the purpose of the loader layout! In 'Start of layout' on a loader layout, it is certain that nothing from other layouts will have loaded. Therefore the event will not be able to create the object. In other words, the bug is in your project, and it would previously have only shown up after export, but now it shows up in preview mode too (which is useful, it helps you catch the problem sooner).

  • Closing as not a bug. It is working correctly.

    Since one of the conditions in the OR block is true (the global variable check), the event runs. However it still picks all instances according to if they met the condition. Since no "Text" instances meet the condition "Is Variable1", the event runs with zero Text objects picked. Therefore despite the fact the event runs the "Set text" action has no effect. Note that if it did run, that would contradict the condition, allowing an action to run for an object that did not meet one of the event's conditions.

  • Closing, please follow the bug report guidelines. Note the Browser "Close" action is only allowed in certain circumstances; in general normal web pages do not have permission to close themselves.

  • Not really, it just uses OpenGL to render the layout view.

  • Closing, please follow the bug report guidelines (include a .capx, include the specific versions of NW.js affected, the C2 version, etc. etc...)