Ashley, yes you are right its my driver, which unfortunately is not supported any more by AMD!

Is there any (easy) possibility for you to add software rendering option to C2 so it doesn't have to rely on the graphics card? My processor would definitely be fast enough.

BTW it only exists in a capx I created with win8 and open in win8.1. If I create a new file, the issue doesn't exist.

Ashley it needs to be tested with windows 8.1!!

I think thats the problem. Please take a look.

Link to .capx file (required!):

dl.dropboxusercontent.com/u/108499873/TileBackgrdbug.capx

Steps to reproduce:

My project suddenly previewed tiled backgrounds incorrectly. I don't know why.

1.

2.

3.

Observed result:

There's a big gap between each image.

Expected result:

There shouldn't be any gap

Browsers affected:

Chrome: yes

Firefox:

Internet Explorer:

Operating system & service pack:

windows 8.1 (!!!! maybe, I just updated)

Construct 2 version:

   149

Place all your UI global objects in a family, then 'set Visible/Invisible'. Also use the family for 'set layer'.

It looks like the fix needs to be added to the package or installer. So it might be something that you need to do, not expect C2 to do for you.

I guess at some point node-webkit will fix the issue by building it on the latest version of linux, but then it won't work on older versions.

The crash needs to be reproducible for the developer to fix it. Can anyone give steps to reproduce a crash.

Does Game Closure implement a browser engine or just 2d canvas or something inbetween?

A

Here's a comparison of ports of box2d. Its an interesting read when box2dweb is compared to asm.js

click here

If a developer wants to support a number of browsers, then each browser supported needs to be tested. Its just of reality of software development that you test each platform that your program runs on.

HTML5, C++ or whatever language you want to write your game in, all have pros and cons for implementation, deployment etc. If HTML5 isn't providing a good enough user experience, then choose a different technology. If there isn't a 'perfect' solution, then spend some time choosing the best solution for your needs, being fully aware of its short-comings.

Construct2 suits my needs (I'm using node-webkit and cocoonjs).

Another approach: rather than relying on browsers, use wrappers like node-webkit and coccoonjs. This is a different deployment model, but at least its consistent.