Ashley's Forum Posts

  • Just hit 'reset dialogs' in Preferences. Without specific steps to reproduce the problem we cannot do anything, so closing this report.

  • It should work fine on iOS 6. What exactly isn't working? It shouldn't matter much anyway - soon iOS 6 will be gone...

  • Preview over LAN is accelerated, it should be just the same performance wise.

    It sounds like Crosswalk is performing the same as Chrome for Android, which means it's working correctly. If you didn't test your game on mobile from the start that's probably why it's slow, your desktop could be 100x faster than your phone. See also performance tips.

  • If your project is not bottlenecked on collisions it won't have any effect at all. What does the debugger profiler/system performance stats tell you? Is the performance difference the same across all browsers?

  • You do not have permission to view this post

  • In Chrome, if you get the "access denied" when you post usually you can just hit back and post again and it's saved the post and resubmits successfully. But I don't think all other browsers save the post text.

  • Did you try running it in Chrome for Android? Did you test on mobile from the start?

  • You do not have permission to view this post

  • You do not have permission to view this post

  • Some other engines don't even support floating-point positioning (i.e. pixel rounding is always on). People seem to get by OK with those tools. I would suspect other non-seaming games are using pixel rounding or point sampling.

  • You might get away with normal letterbox scale with point sampling, but I don't know how all graphics cards would handle that. Depending on what you do you might only need point sampling to solve seams (since it avoids the issue with mid-opacity edges not adding up to 100% opacity) - the integer scale and pixel rounding are just to make sure under all circumstances seams don't appear, and those are pretty good settings for pixel games anyway.

    Yes, games can appear less smooth this way, but it's a tradeoff you have to make. The difference should not be enormous. Remember lots of players aren't that discerning, some people happily play bejewelled at 4 FPS... and I've seen some games starting up in the wrong resolution for my monitor, using the hardware blurry linear filter that makes everything look awful, and they still shipped it with that and presumably it was not the end of the world for them. The only way to get that really silky smooth motion is to be able to scroll between pixels. If you scroll between pixels with linear sampling, you open a whole can of worms with the edge opacity issue, which is also a normal result in computer graphics and not a specific Construct 2 issue. It's a decision you have to make as a games designer. You can't always have it all.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • If you choose CC you're jumping on a sinking ship. At some point we will shut down support for it entirely, including closing these forums.

  • It's either the entire layout drawn so far (by default), or the current layer drawn so far only (if using its own texture). We can't force a separate texture per layer, it will murder the fill rate on low-end systems.

  • Yes, you can.

  • Did you try it?