I think they are going to publish news about the engine, features or something, nothing of a launch until after at least a year.

I don't think so.

Hello, I installed win10 and it seems like this does not happen anymore.

EDIT: Ok, I understand what it means to apply scaling.

This problem would be solved either by increasing the jumping force or by applying scale.

Although it would also be nice to put some kind of solution for the platform behavior to work well with small scales.

I'm not sure I understand what increasing the scale supposes.

Does it mean increasing the resolution of the game?

I did not mean that C2 included another behavior platform, what I say is could I edit my own behavior platform? Could you do it by editing the original?

Could you edit platform behavior to work correctly with small resolutions ?.

I mean if anyone could alter this to have 2 platform behaviors.

1 the original

2 for small resolutions

I could ask it in the forum to see if anyone would be willing to edit the behavior platform to work with resolutions like 256x144, i think is an acceptable resolution for mobile and retro games.

**I hope they solve this somehow in C3.

Okay, this is the information I bring.

-The error occurs when you use letterbox integer scale, sorry if there was confusion before.

-When the error occurs (with LIS) the resolution shown by the browser object and the WindowInnerWidth and WindowInnerHeight property is the same.

640x360

Capture without error:

Http://imgur.com/pyOub5V

Capture with the error, you can see the same resolution.

Http://imgur.com/sD0Z3r4

• It also happens (with LIS) that when you start the game, sometimes a dark bar appears at the bottom of the screen.

On this occasion the resolution is different.

To solve it you have to send the game to the background and recover it again or close it and open it again.

Http://imgur.com/zGB8F7v

You can see that the captures are the size of the resolution of my phone galaxy 6s 1440x2560

• With letterbox scale mode the error does not seem to happen, but this is not the solution because the scaling is different from letterbox integer scale and there are visual differences.

**All tests with WebView.

You didn't answer the question - does it still reproduce with letterbox scale (not the integer version)?

400x240 doesn't fit exactly in to a 1920x1080 display, so the black borders are to be expected in that case. On the other hand if the resolution does fit that exactly, then there should be no borders. So to figure out which one is the bug, what is the resolution of the device you are testing on?

Also one thing you can do to find out more: display the Browser plugin's WindowInnerWidth and WindowInnerHeight expressions on the screen and see what they say in both cases. If they change, it's probably a browser bug, and is caused by the browser telling C2 the wrong window size. On the other hand if they're always the same even in both cases, it's probably a C2 bug. Could you give that a shot?

Resolution of my galaxy 6s 1440x2560

I'm pretty sure I tried letterbox scale but I'll try again, although I do not like that scaling mode.

I'll try everything you say as soon as I can.

I think this topic speaks of the same.

https://www.scirra.com/forum/my-player-won-t-stop-moving_t185963

Problem Description

Edge seems to be confusing with the touch object.

In this example the sprite sometimes continues to move even though you are not playing anything.

This seems to have something to do with touch.

Attach a Capx

https://dl.dropboxusercontent.com/u/60803633/testControlesEdge.capx

Description of Capx

Sprite object with touch object and keyboard

Steps to Reproduce Bug

Press and release the left or right cursors repeatedly.

At some point the sprite will move even if you are not pressing anything, if you move the mouse, the sprite will stop.

Observed Result

The sprite continues to move even if no key is pressed and no touch is being made, this should set the variable "var" to 0, but it does not.

Expected Result

The sprite should not move if no key is being touched and the mouse is not pressed on the screen.

Affected Browsers

• Chrome: (NO)
• FireFox: (??) -> No test with firefox
• Edge: (YES)

Operating System and Service Pack

Win10 Pro 64bits

Construct 2 Version ID

R241 64bits

Is there an updated guide for compiling a game with xdk? It's been a year since I tried it and I'm happy to build for the future and skip crosswalks bloat in favour of webview to target 5.0+ android versions. With cocoon I only used Adsense and leaderboards, and I bought cranberrys but never used them. The old shutter box guide is down now, is there one I could follow that's up to date?

To me webview has always given me a problem, when you start the application, often a dark color bar appears at the bottom of the screen, this causes the full screen does not run, then you have to send the application to the background and recover it again, or close it and reopen it. I like WebView but it should be a bit faster and fix that problem.

Or maybe it's a C2 problem?.

I do not know an updated guide but I think it is not difficult to compile with XDK.

I tried my game in the two, Cocoon had some lags with the data load that I did not notice in XDK, also cocoon does not do the fseek function correctly in the sound, that is to say, change of temporal position a sound or song, there is also lag there. I also had black screen error. In this occasion XDK was much better for me but in the management of plugins and all that cocoon affair seems to me faster.

If you put the music in the sounds folder instead of the music folder, you can loop seamlessly.. At least I'm pretty sure I did that before... I'm always using looped music, so...

Are you sure this will not cause any problems?

celoko Hello, I've been looking for a solution for setting up the custom loader screen for mobile apps. I have a game screen that to be displayed as a loading screen. It is working fine when I run it on a browser but the default loader screen comes up when run it on my mobile.

Is there a way to fix that? Please help.

Use this in the "properties" window:

Use loader layout = no

Loader style = Nothing (not recommended)