Ashley's Recent Forum Activity

  • You can display fullscreen in the browser too, which works in Chrome for Android.

  • Actually, C2 is capped at 60 FPS rendered

    That's not true actually - C2 games run at the refresh rate of the display, at least in modern browsers. Also even if on some platform the game is being capped at 60 FPS, it's not C2 doing it, it's the browser engine - we've coded our engine to run at any refresh rate.

    You generally can't get hardware information in a browser. Browser developers are very cagey about giving out hardware details since it improves fingerprinting on the web which has privacy implications. I don't think you actually need to get the refresh rate for what you described though - if you measure the FPS and the system is fast enough, then the FPS will report the refresh rate. You can default your graph to 60, but if the FPS goes over then set a new maximum for the graph. You could even round it up to known common refresh rates like 75, 120 etc.

  • I could create an action queue to handle this so that when the player resumed, all the actions updated one after the other (and it would work) but it would end up slowing the game down as the resumed player waits for all the animations to run through (the player only needs to analyse what is currently on the board in order to make a move).

    I don't see any fundamental reason you have to make the player wait for all the animations. Surely you'd make a catch-up mode which works instantly instead of making them sit and wait?

    IIRC triggers still fire when suspended, so 'On received' etc. should still fire as messages come in. Also you could send messages in 'On suspended' and 'On resumed' to notify players you've gone AFK, so they know they won't be responding.

  • No, as per the guidelines we cannot normally accept bug reports for complete projects anyway, since they are nearly impossible to debug. Try to reproduce the problem in a new project, then you can share it and we actually have a chance of being able to fix it.

  • C2 compiles all shaders the project uses on startup, so I'm afraid it will crash on WP8.1 if the shader is used anywhere in the project.

    I'm not sure there's much point filing a bug report since as far as I can tell it's already fixed (since the latest IE is not affected) - the only problem is the fix hasn't reached WP8.1 since it's on a much slower cycle. So it's just a matter of waiting for the already-fixed code to reach devices.

  • You can give the progress bar an ID (in its properties), so then you could do more advanced styles by using rules like #myprogressbarid::-webkit-progress-value { ... } - but to get that CSS in to the page I think right now you'd need to modify the exported HTML, or use a third party plugin which can write more advanced CSS rules...

  • Please file a bug report following all the guidelines if you want me to investigate.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • It's really very simple: Construct 2 creates a <progress> element, and 'set css style' sets CSS on that element (as in, it goes on the style attribute of the progress element). That is all!

    I had a quick look and there doesn't appear to be any standardised way to modify some parts of the progress bar, since some browsers implement it via shadow DOM with different internal elements, but I don't think the standard requires that. It's another reason to go with your own composed of objects so you have 100% control over the appearance. The progress bar plugin is intended for apps which want a system or platform styled progress bar which fits with the rest of the apps on the system - so you'd want to keep it the same.

  • We can't fix issues with the Intel XDK, it's developed by Intel - please report this issue to them.

  • FYI Chrome got a patch aimed at fixing the v-sync issues on Windows which should go in to v41, which I've also heard from Intel will be the next version node-webkit is based on. So I'm pretty sure the next node-webkit update will fix this.

  • Are you sure you are saving over the existing file? The way the feature works is you save over the same .png file that is opened (which exists somewhere in a temp folder) and then it re-loads the same file again to get the changes. Normally this just means pressing the save button. If Photoshop is saving to a different file somewhere else then C2 won't pick up the changes because the original file was not modified. The fact it works with other apps suggests the C2 feature is working and Photoshop is perhaps saving to some other folder maybe?

  • It's probably a bug, please file a report in the Bugs forum following all the guidelines.

Ashley's avatar

Ashley

Online Now
Early Adopter

Member since 21 May, 2007
Last online 27 Oct, 2026

Twitter
Ashley has 1,834,650 followers

Connect with Ashley

Trophy Case

  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Forum Unicorn Made 10,000 posts in the forums
  • Forum Mega Brain Made 20,000 posts in the forums
  • x126
    Coach One of your tutorials has over 1,000 readers
  • x74
    Educator One of your tutorials has over 10,000 readers
  • x6
    Teacher One of your tutorials has over 100,000 readers
  • Sensei One of your tutorials has over 1,000,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • RTFM Read the fabulous manual
  • x44
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs