TiAm's Forum Posts

  • fisholith

    Thanks for putting this much thought into this. I'm trying to build a crt distortion stack that will scale from a desktop down to a mobile. Adding glow and noise to a scanline effect really sings, but my phone doesn't like it, especially glow.

  • It sounds like you are installing the x86 apk. Try the ARM one.

  • Do you have any webgl effects in your project? I've found that if I apply too many demanding effects, it can slow parts of the editor to a crawl, providing 'preview effects' is enabled.

  • Actually, it is a bit unclear in the manual. I had to do a little experiment to find out.

    Basically, if you have BOTH high dpi support AND high quality scaling enabled, games will render at native resolution if the browser they run in is 'zoomed'.

    For example, you can 'zoom' into a page in chrome or firefox, which will scale all the page elements up. I imagine that high-dpi devices generally have their browsers default to high zoom settings.

    There should be a more technical explanation of this in the manual. It could be helpful/hurtful on normal devices as well, assuming a zoomed browser window.

  • PSI

    Actually, just to clarify, you aren't talking about the actual C2 IDE are you? Doesn't matter whether you use the 64 or 32 bit version of C2; all that matters is the version of the node-webkit exporter.

  • PSI

    You shouldn't. Just smoother gameplay.

  • Paradox

    A whole game in two events. Love it.

    —

    700 events is pretty impressive for an RPG. Must have been a hard decision to junk the original and start from scratch.

    Ah, the power of a second draft.

  • Browsers are going to keep breaking from here to forever. What gets me is Ashley updating to a version of node that had severe, obvious problems. And sticking with it for no apparent reason (It has 64bit export! More bits!).

    It's easy enough to swap, but we shouldn't have to bother. I've said it before: C2 ought to commit to maintaining compatibility with the last 2 or 3 versions of node-webkit.

    Intel XDK, for example, allows you to export with stable, beta, and alpha versions (all based on different versions of chromium). IIRC, you can also choose to export using older stable versions. Bottom line: you have a choice.

    It's worth saying that chrome 39, the current stable, isn't bad. It's not completely smooth, but it's not as inconsistent as Canary, which, in its defense, is an alpha release.

  • Work fine for me on r190. Here's a dead simple wrap capx:

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

    But if it were malfunctioning, bug reports go here:

    bugs_f151

    In the future, try to finish all your wrapping before Christmas. <img src="{SMILIES_PATH}/icon_e_wink.gif" alt=";)" title="Wink">

  • For testing this is fine. But I wouldn't dare release a finished product this way. The reason that node hasn't switched over to the newer lib is that it isn't fully compatible with the old one. Editing the configuration to work with the wrong library will work, but could easily induce glitches and bugs.

    If it was an easy fix, it would have been fixed. Sadly, we just have to continue to wait on reliable linux deployment.

  • Healer Quest, the game I just finished, is... 23015 events. ^^'

    Jaw = floor.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • This is an amazing bit of work. Seems to run smoother than box2D!

  • Prominent

    Just look at my original post. All you would be doing is copying the mac files instead of the ones for windows.

  • Ashley

    Come to think of it, you're right. For some reason I thought space blaster had a couple webgl effects attached, but I guess it doesn't.

    GameThirsty

    Not fillrate; space blaster uses no webgl effects or large, transparent objects. My mistake. However, if you were piling on some webGL effects/large transparent objects, I'd watch out. But you are having some other problem.

  • Ashley

    His phone has a resolution of 2560x1440. Space Blaster defaults to high quality scaling.

    He's trying to push around almost 2x the number of pixels as you are on a Moto X. Fillrate issue.