Ashley's Forum Posts

  • blob: URLs only last for the duration the browser window is open. That is irrelevant to this process though, because you immediately load it in to a Binary Data object and send it to the server.

  • Moved to C3 forums.

    You should avoid converting to base64 if you can - it's slower and uses more bandwidth than the binary (blob) equivalent. Any good server should be able to handle binary data directly.

    So the approach I'd recommend is:

    1. Take a canvas snapshot (either runtime or Drawing Canvas)
    2. Use AJAX to load the snapshot URL in to Binary Data
    3. Post the Binary Data to the server

    If you really can't figure out how to load binary on the server and are willing to use a less efficient approach, the Binary Data object can also convert to base64.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Unfortunately iframes on iOS just don't properly support scrolling. We looked in to this in issue 2435 but couldn't figure out a decent workaround. I think the only solution is for Apple to implement proper iframe support on iOS.

  • Nobody's reached out to us, and I don't think they will. Some good points have been raised already: it looks like it's aimed at AAA games, particularly the kind of games that are a 50GB+ download and require a $2000 PC to play. With Stadia you can still get to play such games on a cheap low-end device, and without having to wait for a colossal download. Construct 3 already excels at making lightweight, high-performance HTML5 games, which still load fast and run well even on cheap low-end devices. So it's already great for that kind of casual gaming. Putting that behind a cloud game streaming service would likely actually make it a lot worse, as Keyo pointed out:

    Why in the world would they allow the streaming of a Construct game if the streaming would easily surpass the game download size itself in seconds?

  • Make sure you install the app while the URL is editor.construct.net. It works a lot like a bookmark. If you install a specific version URL like editor.construct.net/r136, it will always load only that version, just like if you visit that URL directly.

  • Perhaps the idea board should reflect these numbers you're quoting? I don't see them there. I can only look at the numbers on left side.

    They are right there, on the left side, already.

  • Oh about that "ideas" board, that makes me a bit concerned. Looks like there are many hundreds of suggestions and only 4 being considered and 2 developed. So, all those hundreds of ideas are terrible? What is your idea evaluation process?

    Please, please read the full suggestions guidelines here. This is exactly the kind of feedback we want to avoid - if we get too much scepticism like that, we can always just take it down and stop having votes...

    And as Kyatric pointed out, we've already developed and released nearly 100 user suggested ideas from that site.

  • 95%

    Do you have a citation for that? If you're making up numbers, it doesn't make for a strong case for features.

  • No. If you don't use events or behaviors that check for collisions, the engine doesn't check for collisions, and so there are no checks to disable.

  • There are lots of subtleties in UI design. I don't think expand/collapse icons count as push buttons (like an OK button on a dialog), and if you're reading UI guidelines relating to "buttons", it may mean "push buttons", and not cover other cases.

  • If you have to ask, don't buy it and just use the free signalling server we host for you. If you're asking these questions, it's unlikely that hosting it yourself will do anything better than our host.

  • They're designed to work the same way as the expand/collapse icons in Windows. I assumed Microsoft's design was a standard or widely understood one.

  • A common issue is that because tiled backgrounds repeat the image and can be displayed at fractional positions, sometimes the bottom part of the image wraps around and appears faintly along the top of the object. Adding 1px of transparency at the bottom of the image usually fixes this.

  • It looks like Safari does not provide the information. According to this it's unlimited in desktop Safari.

  • The first thing to check for is if there are any errors in the browser console.