So I finally put something simple together and put it up on the Chrome Store in Test, but I am having a hard time with the window size, no matter what I do the window created by Chrome has scroll bars and dosen't see to be the size I set in the C2 Project.
Anyone run into this/have experience with Chrome Store project? I suspect I should/need to edit the manifest after export to tweak some values. Would appreciate any help you have. I have ready the Articles about Publishing to the Chrome Store and the one about Supporting Multiple Window Sizes, but this is different, my app is not running as expected.
No tips on Window Size? Any idea how to know what was used for the C2 Space Blaster on Chrome?
I am having the same problem with my game on Chrome Store.
I also have the same issue on Kongregate: the game always has scrollbars. To avoid them I had to set a bigger iframe and this causes ugly black padding on left and bottom.
Is there anybody out there that knows how to fix this? It's in Constructs 2 interest too that games look properly. Thanks! :)
Develop games in your browser. Powerful, performant & highly capable.
I think it is also interesting to show the way Spelunky (made with Game Maker) looks when launched from the Chrome Store. I did put it side by side with the way Constructris (made with C2) looks.
<img src="https://dl.dropboxusercontent.com/u/12003764/issuechromestore.JPG" border="0" />
Why is this happening? How can we have our games in Chrome Store shown like Spelunky (borderless, only with title bar) or at least with no ugly scrollbars? I repeat that there is the same issue when posting C2 games on Kongregate, or at least I had this issue.
Please can anyone help?
I still hope someone will eventually answer about the scroll-bars issue in Chrome Store and Kongregate, in meantime I want to add a bit of info about the Spelunky borderless mode: Spelunky looks like that because it's not uploaded as an hosted app (like my Constructris and C2 games are) but as a packaged app. You can quite easily turn an hosted app into a packaged one and have it run borderless; I did it for Constructris in a couple of minutes and it worked just fine, it's a matter of editing some files.
Google says there are issues though, because:
* you can't update an hosted app to turn it into a packaged app and this means you must upload a new copy and get rid of the already uploaded one
* even more important, packaged apps are still not compatible with macosx and linux so we should avoid them and stay with hosted apps
All this info comes from a lot of research into the Google websites for developers.
So, while we wait for packaged apps to become practical, can we know how to fix the scrollbars issue? Thanks! :)
Hey people, is there anyone that can help?
Yes, unfortunately there are problems with the chrome web store. I have struggled with it myself and also made a thread about it not long ago, which remained without reply.
The one game I got running properly on the store isn't using fullscreen and I used the version you can download from clay.io through their distribute options, when you upload your game there. So that might be worth a try.
I am always hoping for some fixes regarding the chrome web store exporter or at least some viable workarounds. <img src="smileys/smiley18.gif" border="0" align="middle">
Thanks for your reply PixelRebirth! I frankly think it's amazing this issue has so few attention. The way C2 games are being experienced by users is crucial; I spent months working on a game that looks terrible 'cause of ugly scroll-bars on both Chrome Store and Kongregate. Not happy.
Revisiting this thread again, because I seem to have fixed my issues with the Chrome Web Store.
What worked for me: remove the div element in which the canvas is enclosed in the index.html file. I know it says "The canvas must be inside a div called c2canvasdiv" in the file, but that doesn't appear to hold ground.
Then change the canvas tag to look like the following:
<canvas id="c2canvas" style="display: block; margin: 0px auto;">
Projects that are exported with fullscreen off have some unnecessary space at the bottom of the canvas. This change gets rid of it.
It also makes the canvas always be centered even if you resize it at runtime btw.
I didn't test these changes exhaustively, but it does indeed work for my project. But do this at your own risk of course, keep backups.
Another chrome web store related hint: if you make use of a plugin like Clay.io, which will communicate with an external server, you need to add an additional line to your manifest.
"content_security_policy":"script-src 'self' 'unsafe-eval' clay.io https://clay.io:846; object-src 'self'",
Of course the specified URLs are for the Clay.io plugin. Switch them with the ones you need.