Ashley's Forum Posts

  • What exactly is different? Where specifically are you hearing it cut off? What device are you using and which version of Crosswalk? Does the Crosswalk beta version reproduce it? Does this reproduce in Chrome for Android as well?

  • Closing, can't reproduce and report does not follow the guidelines.

  • Closing, please only file bugs with the latest version of C2. You have indicated you are using r173 and we have fixed many bugs since then.

  • Reverted the previous tab change so it always uses the colored tab style. It looks like our UI library does not support this, so it should just be back to how it used to be for the next build.

  • As far as I am aware, this is not a bug, but just how mipmap selection works in OpenGL. Mipmaps generally improve downscaling quality, but at extreme aspect ratios (such as 1/4 as wide but 4 times taller) it picks the lower dimension to select the mipmap, and the reduced quality becomes apparent.

    I don't think there's anything to be done here, it's just the normal working of OpenGL.

  • Closing, this is just a mistake in your events. When the right analog is moved left, event 13 (testing if it's right) is false, therefore the else event in event 14 runs, which sets IsAimingDown to false. You can see that happening in the C2 debugger (when you point left it does not set that flag to true). Since you only scroll left when IsAimingDown is true, it never scrolls left.

    Please refer to the bug report guidelines; this is why we require .capx files with the minimum objects and events possible, to eliminate the possibility of mistake and unequivocally prove there is a bug in C2.

  • Closing as won't fix. This is just a quirk of canvas2d mode: it draws the text directly to the canvas, so it can end up drawing text outside the bounding box. WebGL mode by necessity uses an intermediary texture, and ends up clipping the text outside the bounding box. Fixing canvas2d mode to match WebGL mode would come with a performance penalty, and WebGL is approaching ubiquitous support now, so I'd prefer to leave it as is.

  • Closing as not a bug.

  • I made it disable the default application/x-www-form-urlencoded type if you use 'Set request header' to set Content-Type, so should be fixed in the next build.

  • But when you have to write tons of events, it would be so nice to have charts you can quickly reference to. Here on the forum, or even better inside C2.

    Something like this:

    lerp to an angle, use this:

    lerp to a position, use this:

    lerp to speed, use this:

    lerip to scale, use this:

    lerp to variable value, use this:

    every tick events: don't use if this and this. Use if this and this.

    every X second: don't use.

    If you're rotating, moving, accelerating or basically anything else, the answer is just add s * dt. "Every X seconds" is already framerate independent because it measures time, not frames, but people often get confused about it so the original delta-time tutorial specifically covers it.

    Lerp is kind of a special case so I added it to the tutorial. I think that basically covers everything?

    • Post link icon

    Closing due to basically admitting to using a pirated version of Construct 2. It's asking a lot to expect anyone to help you in that case.

  • We used to run polls for the most wanted feature, and multiplayer always won by a huge margin even with a warning like "it could be very difficult to use".

    We spent months researching and developing the feature. It was a fun project to work on, but a lot went in to it. After release we've seen it hasn't had much uptake - nowhere near what the original polls suggested. As far as I can guess, it's because it's pretty difficult to get in to (not because the feature is unnecessarily complicated, it does a massive amount of work internally for you, but just the mindset of thinking about the flow of data between the host and peers).

    We can't justify spending even more time working on more advanced features when not many people are using it. All in all I think it was a pretty interesting lesson in how people's imagination of features is more exciting to them than the reality.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Write a function to stop all audio, then call the function from JS.

  • Creating exporters for Unity is completely bonkers. Firstly it's not really technically possible - it faces the same challenges as writing a native engine (for example how do you make it be able to run all the existing Javascript code for plugins and behaviors without just using a browser engine?). Secondly you're tied in to Unity's licensing model, so if you want a pro feature like "Custom splash screen", that's $1500.

    A better question is why is it even necessary? What does it do that browsers currently don't? And whatever the answer to that question is, surely the better thing to do is to improve the browsers instead of completely abandoning the entire existing engine?

  • sometimes when freezing it also kills the graphicscarddriver.

    This strongly suggests a problem with the graphics driver, not Construct 2. Are you sure your drivers are up to date?