TiAm's Forum Posts

  • I wonder if this fix will get rolled into Chromium v41? If so, we could have much better compatibility on linux within a couple months.

  • Huh...maybe it's something on my end. I'm on Win 7 x64. Well, here's what I get:

  • I was trying to build a test project to evaluate the aprox fillrate of a device, and I came up with this. It works fine and all....but take a look at how IE renders vs other browsers.

    https://www.dropbox.com/s/ivjwxealg0pk7 ... .capx?dl=0

  • Contact them first. Give them a chance to take the content down:

    http://www.atomicgamer.com/contact.php

    As Ashley suggested, a DMCA will most likely get their attention. It's a dirty bit of law that has been bent to some less-than-scrupulous purposes, but if AG refuses to remove your content, this is the biggest gun you have available, and you would be more than justified to use it.

    Unfortunately -- and fittingly -- googling for DMCA doesn't turn up a government website with applicable information and forms, but http://www.dmca.com, a private organization that's looking to help you...have a lighter wallet.

    Since you would only need to file a single takedown, this would probably be your best bet:

    http://www.whoishostingthis.com/dmca/

    Honestly, if it were me, I might just skip to the DMCA. AtomicGamer looks downright slimey: full of other peoples content (indies no less), a bunch of ads that link out to malware, trying to scrape more cash thru accelerated downloads. For shame.

  • Colludium

    What do you see with Canary when you start in windowed mode? What about when you resize the window; does this clear up any janking? I just tested a couple games to judge the subjective performance, but I was getting great results fullscreen and maximized...the only issue was when I started the browser windowed. In those cases, a simple resize would fix it.

    eli0s

    Sorry you were never able to figure that out, but I'm glad your subjective results are better.

  • FYI, Chrome Stable v39 is a bit better than 38, but it still jerks and halts more than IE or the current Canary(smooth as butter once it locks in).

  • Canary is now up to v41. It seems like they have some other fix in place, as it was it terrible shape post-revert, but now seems to be functioning pretty well. The only kink is that if you bring a game up in the browser while it's windowed, the vsync fails...until you resize the window. After resizing it, canary will sync very well, whether windowed or maximized.

    Haven't tried 39 stable yet...I'm updating to it now.

    Honestly, at this point I'm not that worried about chrome, though I'd hate to have to use a version of node-webkit based on v38. The real problem is Firefox. It's just abysmal, even on simple games. It jerks, halts, drops frames, and screen tears (sometimes horizontally, which is a new one on me). Project Silk appears to address this...but what's going on with it? I may be wrong, but it looks like Silk has been getting less and less attention over the last couple months.

    Firefox never quite matched chrome's performance, but I don't know how it got this bad, and I don't know why this isn't higher on their todo list...you can see all these things on webpages as much as with gaming. I'm going to dl the developer and nightly versions tonight and see if there are any improvements in the pipeline for this (though looking at the feature lists, my hopes aren't very high).

  • You do not have permission to view this post

  • Makes sense. Seems simple enough. +1

  • I just noticed this yesterday when testing a large layout, though I didn't take note of the exact point at which the slider bar glitched up. It doesn't seem to cause any functional difference to the layout itself though.

  • It depends on what version of node is shipped with the next stable...and I assume r189 will be the next stable.

    Ashley:

    Please let us use the previous version of node with r189...however it has to be managed.

  • —

    Well, at least the last 2 or 3 versions. We can't expect Ashley to support every old version of node, but new versions seem to have a tendency to break things...

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Canary is still nerfed, though not as bad as Chrome Stable (38). Chrome 38 even stutters slightly on the autorunner template...and that's on a 3570k after disabling scaling.

    But the worst...is Firefox. I mean, it was never great, but it's become an absolute joke. Auto-runner is a slideshow...even as it reports 60 fps. How it got this messed up just boggles the mind.

    IE is smooth as silk.

    Ladies and gentlemen: welcome to the twilight zone.

  • You do not have permission to view this post

  • You do not have permission to view this post