The XBox 360 controller works best with the Gamepad object, AFAIK.
As you've found, CocoonJS is not a real browser so jQuery does not work.
If all you're doing is making an AJAX request, there's no need to use jQuery anyway - just create an XMLHttpRequest object directly.
Same old issue with seams, same old answer: use pixel rounding, point sampling and letterbox integer scale.
If the player has line of sight to the tile's position, then erase the tile.
Have you tried r150? Are your graphics card drivers up to date?
Having to close this since there is nothing we can do without detailed enough reproduction steps for us to follow and see the issue ourselves.
— - if you're using the Tilemap object, you should definitely use the Tilemap.PositionToTileX/Y expressions instead.
That's odd, I've not noticed that effect before. I think Chrome is noticing there's an offline cache and the loading progress is reflecting the offline cache progress - but it's not programmed to do that... hmm...
Develop games in your browser. Powerful, performant & highly capable.
I'd report it as an issue to WineBottler, they might be able to fix it.
How to get Construct 2 beta releases on Steam
I think you'll be able to keep using Chrome Frame, just it won't be updated any more. Alternatively a message on your site suggesting to switch to Firefox or Chrome is better than nothing. Given enough time, these browsers will disappear in to history eventually anyway...
You do not have permission to view this post
I'm having trouble understanding what the .capx is supposed to be doing. Can you create a minimal example? It looks like you should be able to demonstrate the problem with say two objects and two events.
Does it work for you on Windows 8.1? The crash logs are not useful; we need to be able to reproduce the problem or at least find out more detail about the exact error. I can export and run it on Windows 8.1 using VS2013 so it seems to work just fine.
Yeah, looks like it would be useful if it still worked when the bar is auto-hidden. Should be fixed in the next build.
Closing: chalk that one up to a driver bug (if tiled backgrounds display wrong, the same issue would cause that here as well - broken non-power-of-two texture support). Looks fine here as well.