Ashley's Forum Posts

  • I could not reproduce any issue when testing on iOS 6, but it doesn't seem like it matters much, since everyone will be on iOS 7 soon enough anyway.

    The events you posted don't look reliable - it looks like it'll break the landscape fullscreen mode, and it will be brittle (since it depends on hard-coded numbers which could easily change in later releases). So we wouldn't want to build something like that in to the engine, although you can try to hack something like that with events if you want.

    I would reiterate this is a problem with Safari on iOS 7 - anything that runs in the browser will be affected, not just Construct 2 games.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It's an architectural flaw in Classic. Including an event sheet literally means "copy and paste the entire event sheet's events here". So if you have 100 levels each including a common sheet, the common sheet is exported 100 times in duplicate. So if the common sheet has 500 events, in this case it exports (and generates on every preview) 50,000 events.

    There is no chance of this being fixed in Classic, but it's fixed in C2, where we have a proper include system where an include references the same sheet rather than duplicating it. This keeps previews, exports and load times fast.

  • I doubt it's related to Java in any way. My best guess is you're not actually using 8.1 GA, because IE11 had some WebGL bugs in RTM and earlier and it looks most like WebGL rendering bugs. Perhaps check the Visual Studio console for any errors or warnings on the broken machine. If they relate to WebGL, I'd think that is even more likely the case.

  • It's an architectural quirk. If no objects exist anywhere in the project, C2 doesn't know what to use for its properties. E.g. if you don't have a Text object anywhere in the project and you try to create it at runtime, what font should it use? It could fall back to a default I guess, but then if no objects exist in the project, the only thing you can do is create blank default objects. If there is at least one instance in the project, C2 uses the properties from that object.

  • Can you make a minimal .capx which reproduces the problem? The .capx is huge, over 70mb.

    Could you also clarify the observed result vs. expected result? Your observed result appears to be a description of what to do, as opposed to what you observed compared to what you expected.

  • Closing as not a bug. IE and Safari simply do not support the features necessary for User Media to work. Use the 'Supports user media' condition first to check whether support is available or not.

  • Please always include the version of C2 you tested with. This should already be fixed in r148.

  • Can't reproduce with Windows 8.1 GA and VS2013 RTM. Looks just fine. Are you absolutely certain you are using the GA (general availability) build of Windows 8.1 - which is newer than RTM - and the final release of VS2013? You must have both, we don't support older versions at all.

  • You do not have permission to view this post

  • What version of Windows are you using? Are you sure you're not running any other server software on your computer that might be conflicting?

  • Or just give the objects the 'Destroy outside layout' behavior.

  • We'll look in to this in the near future. I think last I looked it was based on Cordova (PhoneGap).

  • Looks like straightforward piracy. We'll be blacklisting that license and following up with the owner. Thanks for the heads up. (Locking thread)

  • You do not have permission to view this post

  • The 1px transparent border is necessary. If we used your last example, in some cases resizing the red object will show green and blue fringes down the sides. With the transparent gap, it blends correctly at the edges.

    This should not be a significant problem. Some people use power-of-two sizes for sprites out of habit - just use any size or two pixels less than power-of-two e.g. 126x126.