Ashley's Forum Posts

  • If you're making linear comparisons, you shouldn't be, because they don't respect the cyclical nature of angles. You should stick to the angle-specific conditions like 'Is within angle'.

  • - if you're using a non-fullscreen mode that should be fair, yes. Also exporting can actually help it run faster - the export-time optimisations can help and some preview-mode bug checks are removed. Obviously that's a bit more hassle, but if you want it to be totally fair, export as a HTML5 website and run it from a web page (e.g. Dropbox)! (That also makes it easy for others to run your tests)

    I think Classic would beat C2 in several tests, but hopefully not by as much as you might think, and I reckon C2 would beat CC on some other tests as well. I'd be curious to see your results with WebGL support.

  • It shouldn't be important. 270 is the same angle as -90.

  • For C2 to have a fair chance you really have to test with WebGL available and pixel rounding off. Without WebGL you'll see a big hit from the browser engine overhead. I know not all systems support WebGL, but it's increasing all the time and represents the best possible performance with C2, which is probably what you really want to test. Also with pixel rounding on you make C2 do extra work on each draw call to round the position where in Classic the option was effectively off (it was not supported) so it wouldn't be doing that work for each object.

    It's also vitally important to use exactly the same window size at runtime for the test to be fair. If you run a CC test in an 800x600 window, you must also ensure the viewport in the browser window is also 800x600 when testing C2 - otherwise the amount of work for the GPU is different and will skew the test. It's not enough to just set the window size property.

    We have in the past found one case where C2 outperforms Classic with WebGL rendering on some systems: https://www.scirra.com/blog/102/html5-games-faster-than-native

    C2 also has some algorithmic improvements over Classic in some cases:

    • in C2 pathfinding is asynchronous (runs in a separate thread via a web worker) whereas in CC it was synchronous and run in the main thread. This meant even with native code long pathfinding searches would make the game jank, whereas this does not happen in C2.
    • C2 recently got the collision cells optimisation, making very large layout collision-test intensive games far faster. CC never did this optimisation and brute forced everything all the time, so C2 probably actually scales better for large games.
    • some areas of the event engine and rendering engine do less work via a lazy loading scheme whereas Classic brute forced things again.

    C2 is also considerably more stable, including at runtime - Classic had some weird crashes and glitches due to the gone-too-far optimisations we implemented.

  • The supported languages depends on the browser and OS. You can get a list of the available voices like the built-in example shows for speech synthesis, and you can enter which language to use for speech recognition too. Node-webkit and Crosswalk are both based on Chrome so it should work there too. I don't think any other platforms support it yet.

  • It appears to work in r160.2. Please only submit bugs in the latest version of Construct 2. Also, the project is corrupt - it prompts about missing files when opening. That may be the cause of the problem you're seeing. Closing.

  • I'm afraid it's hard to help, because it sounds like some router or firewall specific configuration is blocking access to the host computer from other devices on your LAN. It all depends on your particular setup.

  • True Valhalla - our last blog post on future plans was in November: https://www.scirra.com/blog/129/ideas-for-construct-2s-future

  • Closing as won't fix: the text object needs to be drawn before the size is available, so it cannot be retrieved immediately like you do in your project. Add 'Wait 0.1 seconds' and it works.

  • I can reproduce, but there are hundreds of events and objects, so it's very difficult to prove it's a bug in Construct 2 and not some logic in your project that changes layer or object effects depending on the layer the Ash object is on. As per the guidelines please provide a minimal project using the fewest objects and events possible to prove it's a problem with Construct 2.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Double-check you set up the firewall correctly, and possibly also have a look at Troubleshooting Construct 2's preview server.

  • Like with most new web platform features, the supported browsers will change over time. As generally happens new features land in Firefox and Chrome first, and then other browsers catch up.

    HTML5test.com and caniuse.com are good places to check support, although they list different sets of features. Only HTML5test seems to have speech recognition and synthesis, and there are lists of supported browsers here:

    http://html5test.com/compare/feature/audio-speechrecognition.html

    http://html5test.com/compare/feature/audio-speechsynthesis.html

    We also have ScirraMark which is a good way to quickly check a specific browser for C2-related HTML5 features.

    Don't forget if Chrome supports a feature, that means node-webkit and Crosswalk will also support it, and if Firefox supports a feature, Firefox OS will likely also support it (although it's on a slower release cycle).

  • Does disabling WebGL in project properties fix it? It's new to IE11.

    Intel GMA have notoriously buggy drivers. Check for an update or report the issue to Microsoft.

  • MaorKeshet - you can look it up yourself on Google, but the amount reserved by the OS will be a significant proportion of it. It's hard to tell exactly.

  • Notepad++ does the trick for me. It has word autocompletion which is pretty good by itself - IDEs with proper autocomplete like Visual Studio still have a hard time inferring which objects you're using because it's an untyped language.