Ashley's Forum Posts

  • Have you tried CocoonJS or appMobi directCanvas? They both provide polyphonic audio.

  • Very interesting video, and quite inspirational for Construct 2 features. I wonder if I could code a "continous preview" feature - for example, if you're 5 minutes in to a level and a block is too high to jump over, then you could edit it to be lower in C2, press "continuous preview", then carry on right from where you are without having to start over!

  • It should work with horizontally moving platforms, but due to a bug it didn't work with vertically moving platforms. That should be fixed in the next build.

  • cklester - jwilburn's events are fine, you don't need to make a subevent for the loop to work correctly. In fact sometimes adding redundant subevents can reduce performance.

    R0J0hound's suggestion of using the 'Load JSON' action is by far the best. As a rule of thumb, never do processor-intensive startup routines like this - process it once, save it to JSON, then just load the pre-processed JSON on startup. Loading JSON is done by the browser's native code (usually C++), whereas C2 events are processed by Javascript with the added overhead of the event system, which is why it can be a lot slower for this type of thing.

  • Local storage should work in CocoonJS, at least in r99.

  • There are strict limitations on what kind of image can be used for a cursor.

    1: it cannot be bigger than 128x128

    2: it will not take in to account any properties (such as angle, opacity, being resized other than 1:1, any blend modes, etc etc). It will simply use what you see in the image editor as the cursor.

    3: it won't work in Internet Explorer at all

    4: it may not work on operating systems other than Windows

    Since your image is bigger than 128x128 it fails to load. Resize it down in the image editor to something smaller and it works, at least on Windows 7 with Chrome or Firefox.

  • We will make an announcement a few days in advance as well. Don't worry!

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • tulamide - it should be working on XP, we definitely want to keep supporting the OS. I think Awesomium have already fixed a crash on exit problem, so hopefully the r100 release won't have this issue.

  • jwjb - I'm afraid I'm at a complete loss as to how this could happen. It seems Construct 2 with administrator privileges is unable to delete a file from the Desktop folder (which it should have permission to access anyway).

    I can only suggest that you try to find a way to reliably reproduce the problem and send me the project and steps to reproduce so I can see if I can get it to happen my end.

  • Thanks, should both be fixed in next build.

  • Image locking should have been fixed in r98. Have you tried r99?

    onstruct 2 should no longer lock image files after importing them or using them in the editor. (Previously importing an external image file could make the external file uneditable until you closed Construct 2 or at least the image editor.)

  • Somehow your player object got a collision mask several times larger than the object, even though it ought to be bound to the object size. This caused the weird collision result. Can you remember anything you were doing editing the player object beforehand that may have caused it?

    Anyway I've added a fix for r100, so hopefully this will be fixed and won't happen again.

  • Thanks, I think this should be fixed in the next build, let me know if it works when r100 is out.

  • 0plus1 - we have no plans to drop PhoneGap support! When PhoneGap Build supports 2.0, I'll do some testing and see if I can fix anything that's broken. If anyone can supply minimal projects that do not work as expected in PG 2.0 please send them to me, they will be a massive help.

  • You are spawning objects in layer number 0 (confusingly, named "Layer 4"), which is the background layer, which is parallaxed so it won't line up with the layer the player is on (layer number 3, confusingly named "Layer 0"). I think this is not a bug and you have just got your layer names mixed up from their numbers. See the column of numbers to the right of the layers in the Layers Bar.