Ashley's Forum Posts

  • As far as I can tell, everything is working correctly. The project is a bit obfuscated though which makes it harder to understand. You could do the same with much simpler events.

    Click on the right green box (trigger2) first. Notice the change of the two blue circles to frame 1. This trigger also tries to display the name of the sprite via Browser console. However, the console only displays the first Sprite's name.

    All three sprites meet the "trigger = trigger2" condition, so the event runs with them all picked. You log the name, and C2 arbitrarily picks the first one. Then you test which are to the right of X=50, two of them are, so those two change frame. Everything has worked correctly.

    [quote:2wchklem]This time click on the left blue box (trigger1). Nothing happens. What trigger1 is trying to do is use System actions to and expressions to query the Sprite.X, and set the animation frame based on it. But this isn't happening.

    Again, all three sprites meet the "trigger = trigger1" condition, so the event runs with them all picked. You log the name and the same thing happens as before, it just chooses the first one. Then in a sub-event you evaluate "Sprite.X > 100". Since Sprite.X must evaluate to a single number, C2 again arbitrarily picks the first one, which has an X of 50. Therefore it evalutes "50 > 100" and returns 0 for false. The next condition tests if the result was 1, which it isn't, so the event doesn't run.

    None of this has anything to do with "Trigger once". I think you're just confused about what that condition does. A more accurate name for it might be "did this event not run last tick". That is pretty much all it does.

  • The preview settings categorically do not affect the export and certainly do not include any IP address settings. You should be able to verify this by comparing the exported files are identical after exporting with different preview settings.

    This is probably a different problem, but we can't do anything about it unless you provide a .capx that reproduces the problem as per the bug report guidelines.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I can't reproduce any problem on an iPad Air 2 running Chrome for iOS 57. The error message looks like a crash in Chrome itself too. Maybe it's an addon you have installed?

  • It's almost impossible to debug projects like the one you provided. Can you make a minimal .capx as per the bug report guidelines?

    Also does it only happen in cocoon.io's build service? If so you should probably report it to them, since it would probably not be a C2 bug.

  • It's not to do with NW.js or downloading, turns out the canvas recording feature was broken if you exported with minification. Should be fixed in the next build!

  • It enables Point sampling, pixel rounding, and letterbox integer scale. This guarantees pixel-perfect display in any circumstances.

  • We already do everything that article says. It's also quite out of date now, new features have been added since 2014. But none of that solves the problem that JS can't cause a paste. You can already paste, by the way, you just have to use the system shortcut (e.g. Ctrl+V on Windows) or the browser menu which has cut, copy and paste options - it's just we can't add a corresponding menu option for that, and the shortcut doesn't work on mobile.

    The desktop build will be able to show a menu option for pasting. Otherwise I think it would be better to work around it by having a fake in-app clipboard that doesn't really paste from the clipboard, just the last thing you copied in the same instance of C3. This will have some quirks like not being able to copy-paste between two separate instances of C3, but at least you'll be able to use copy-paste from the menu.

    Overall it's pretty minor I think, you can still paste, it's just about whether or not we can display a menu option for it.

  • But anyone can deliver any crappy game and charge for cookie coins.

    Not really, if you intend to make actual money from gambling games - it's an incredibly tightly regulated industry, which is probably imposing enough to keep out any indie devs or even small companies. This particular aspect is aimed at large gambling corporations.

  • The scale, rotate and actual rendering work done by the shader is all done on the GPU so that aspect ought to be identical across all browsers (and even native engines).

    However rendering shader effects does involve quite a lot of complex rendering calls, so there is a significant CPU aspect to that, and that's what looks like has significantly improved in the latest Edge. I'd suggest focusing any measurements on the CPU side.

  • The expression returns the correct path - e.g. "/home/username/Desktop/". This is a valid path for the file system. The problem is if you make a request to this treating it as a URL - such as you do to issue an AJAX request and load an image - then it's routed through the browser URL resolution. This is not the same as a file path. It expects URLs of the form "https://www.scirra.com", but you pass it something like "/home/username/Desktop/test.txt". This looks like a relative URL (e.g. fetching "/folder/file.txt") so the request happens to be made relative to the current URL, which happens to be something based on chrome-extension:// for NW.js apps. The problem probably only does not happen on Windows because the different file path style with a drive letter unambiguously identifies a local path. You can force it to treat a path as a local URL by prefixing "file://". So your example actually starts working if you add "file://" before the request URLs. That's a nice easy workaround for the time being!

    So far everything is actually working correctly. The real problem is confusion between file paths and URLs. We can't change AppFolder because adding "file://" is incorrect for actions that directly manipulate local files. But then you can't directly use AppFolder in a URL expression without prefixing "file://".

    So I think the best solution is a new expression AppFolderURL, which has the "file://" part automatically included. Then you can use AppFolder for local file stuff, and AppFolderURL for anything treated as a URL. This will be added in the next build, but you don't need to wait, just add "file://" for now and it works.

  • In Edge 15 with the Creator's Update, Edge performs approximately the same as Firefox on my machine. I can get 60 FPS on all three browsers, but the CPU usages are approximately 20% in Chrome, 40% in Edge and 45% in Firefox. So it looks like Edge 15 has been optimised and is now slightly better than Firefox. Can you confirm?

  • Link doesn't work, closing.

  • Please see the bug report guidelines so we can actually help you. Closing.

  • Closing as not a C2 bug, please check your third-party addons.

  • Closing as not a C2 bug, it's a limit in the APIs, sorry.