Ashley's Forum Posts

  • If Crosswalk crashes, you probably want to report it to Intel. (Nothing in the C2 engine should ever be able to crash the browser that runs it.)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • This normally is actually a server problem: either misconfigured MIME types or you just forgot to upload a file and it returns 404 not found. The browser console (Ctrl+Shift+J or F12) usually has more info.

  • "WorldOverview" is not a valid XML document. The action you are using expects an XML document starting with the usual "<?xml ...". You can pass any variable that is a valid XML document. You might need to AJAX request a project file first.

  • I doubt a web font has anything to do with it. The editor has no special treatment of web fonts: they are handled entirely by the runtime, or if you import it as a project file, it's treated as an ordinary binary file with unknown contents. So that explanation doesn't make any sense to me, and I'd suspect it's something intermittent that you attributed to your last change.

    As ever if you can reproduce anything or share any related projects then post them to the bugs forum. Also if you have extremely large projects, try turning off icon caching in Preferences.

  • I'm not sure many people have tried what you are suggesting, so I'd recommend running some tests with C2 using lots of video in various browsers and see how it fares.

  • Did you test on IE11? I can't see that you've addressed that point yet, and IE11 has typically had the best v-syncing performance. It's critical to report on this kind of information to identify browser-specific issues.

  • It's hard to provide many useful "general purpose" functions without incurring a serious performance penalty, or having to make some significant changes to how the engine predicts which SOLs are going to be modified.

  • It happens because in preview mode it tries to identify functions that are mis-typed and log to the browser error console if so. In this case it incorrectly identifies the function call as not having triggered any "On function" event (apparently due to the second false condition that prevents the event running) and so incorrectly logs to the browser console that it's a possible mistake. Since it ends up logging several hundred messages a second it burns a lot of CPU.

    Post this to the bugs forum and I'll take a look some time for the next beta.

  • You should avoid this kind of thing for performance reasons. Since you have code that runs for each unique type in the project, you will have a slowdown proportional to the size of the project, and we've had bugs reported (and fixed them) based on accidentally having code like that which slows down large projects.

    Also in the event engine you are not actually allowed to modify the SOL of any objects apart from your own or anything passed in object parameters to the current condition/action. Doing so will break the event engine optimisations aimed at avoiding the above performance problem.

  • Do you mean on Android? Those keys are OS level buttons and are not normally hidden.

  • Yes, that's right.

  • The drift is just the difference between the moving angle and the object angle, which are both accessible via expressions. I'm not sure 'is accelerating'/'is decelerating' are useful conditions to add, I think they map pretty straightforwardly to the user's controls and should be part of the game's logic (i.e. 'is accelerating' is the same as when the player is holding the accelerate control, and 'is decelerating' is more or less the opposite).

  • It's a bug in Safari: https://bugs.webkit.org/show_bug.cgi?id=138506

    The workaround is to remove the offline.appcache file, but that in turn breaks offline support, which is nice to have especially when adding to the home screen...

  • It's something you need to figure out with Comodo, or perhaps their support. It should still be possible to trust node-webkit even though its files are now in a different location.

  • If we made our own exporters, it would amount to writing a new browser engine, which companies like Google do pretty well already. Also even if we somehow had the resources to take on Google's thousands of engineers, the result would likely be far poorer quality than what is already available. Consider how many bugs and missing features there are in Canvas+.

    This is an awkward time where a Chrome bug got inherited by node-webkit which is on a slower release cycle. It will inevitably be fixed though. I understand the frustrations, but one bug with a fix on the way isn't an argument to reinvent the wheel!