Ashley's Forum Posts

  • If they are just building an app with a WKWebView, then it would be using an identical engine to PhoneGap Build/Cordova, so it's odd there would be any performance difference. If you're only testing in low battery mode, maybe they're going against Apple's advice and ignoring low battery mode's throttling and rendering at full performance anyway? Dropping to 30 FPS is a battery saving technique so may be the expected result in power saving mode. Alternatively perhaps they're doing something like rendering at a lower resolution by default.

  • Update April 20th 2018: the download links in the original post have been updated to a new download based on Chromium 66. Please download again to make sure you're using the latest version.

  • So far so good. I'll wait a little longer to be sure before closing this issue.

  • Can you verify if the issue is resolved in r257.3?

  • Can you verify if the issue is resolved in r257.3?

  • This is proving tricky to get right, but should have a .3 release out soon...

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • OK, looks like one more issue, should have another release out soon...

  • It looks like the browser is enabling antialiasing on the 2D canvas by default. This has a high performance cost, so we have it disabled in the WebGL renderer. Instead by default Construct crops images with a 1px transparent border around them, so you get the same kind of smooth edge effect without the high performance cost of antialiasing. (If you just bucket fill and don't crop then you won't have the 1px transparent border, which is what I think happened in your screenshot with the Sprite, so try just hitting the crop button on that.)

  • Generally JavaScript errors are bugs and should be filed in the Bugs forum following all the guidelines. In this case I think you've run in to an already reported issue with that beta release.

  • You're right, it's not documented anywhere yet. Here's a complete list. Remember you have to check "Enable BBcode" in the object properties.

    Text object

    [b]bold text[/b]

    [i]italic text[/i]

    [u]underline text[/u]

    [s]strikethrough text[/s]

    [h2]change font size (in pt)[/size]

    [font=Arial]change font face (including any webfont in project)[/font]

    [color=#ff0000]change text color[/color]

    [opacity=50]change text opacity[/opacity]

    [hide]invisible text (useful for flashing effects)[/hide]

    [background=#ff0000]change background color[/background]

    [offsetx=10]offset text on X axis (useful for animated effects)[/offsetx]

    [offsety=10]offset text on Y axis[/offsety]

    [stroke]stroke text[/stroke]

    [outline=#ff0000]outlined text[/outline]

    SpriteFont object

    [scalex=2]stretch wider[/scalex]

    [scaley=2]stretch taller[/scaley]

    [scale=2]stretch both axes[/scale]

    [color=#ff0000]change text color[/color]

    [opacity=50]change text opacity[/opacity]

    [hide]invisible text (useful for flashing effects)[/hide]

    [background=#ff0000]change background color[/background]

    [offsetx=10]offset text on X axis (useful for animated effects)[/offsetx]

    [offsety=10]offset text on Y axis[/offsety]

    Tags can also be nested, e.g. text which is both bold and italic, text which is offset on both X and Y axes, etc.

  • Given we market primarily to non-technical users, I think the appeal of a "do it yourself" plugin will be limited. This also has a high opportunity cost for us since we're a small team and deal with hundreds of bug reports and feature requests. So I think either we would have to go the full way and implement the hosting part ourselves (a ton of work + ongoing hosting expenses), or just leave it to third-party addons, which I think is the best approach right now.

  • Should be fixed in r257.2!

  • artbava can you see if the issue is fixed in r257.2?

  • Please test with the latest beta, this should be fixed. File a new issue if you still have trouble.

  • As far as I could tell, it looked identical to Chrome on Windows 10. For bug reports, the simpler is the better. Ideally there should be no interaction necessary, no unrelated objects/layouts/events, and no other issues mentioned. This will minimise the chance that your report is misunderstood.