TiAm's Forum Posts

  • This is why some sort of canvas / paster object would be really useful!

    Yup. My #1 item on the C2 wishlist. It's just crazy awesome all the stuff you can do with Paster.

  • WebM (VP8, vorbis) and OGV (Theora, vorbis) also fail. All of these videos run fine in chrome for android and firefox for android.

    Why doesn't crosswalk support this? Is there some additional step required? Where is the missing link here, in the video plugin, or in XDK?

    This is getting really aggravating...

  • Danwood

    Basically, for the very reason you mentioned: cpu use seems to be a bit higher. Also, I have seen some isolated stutter, though it's very minor and infrequent. On 0.10.5 I don't see any jitter after the first few seconds. And, of course, there is the 'alpha' part; 10.5 was a very stable release that has minimal bugs, whereas 12.x is still pretty new.

    All that being said, I'm thinking (hoping) this thread won't be relevant much longer, as the newest release is coming pretty close to parity.

  • ome6a1717

    I'm afraid I still don't quite understand. Which files are you replacing post-export that get the game to run correctly? Have you run dxwebsetup.exe (maybe you are defaulting to canvas2d mode)?

    Anyway, I'm also bumping this thread to let everyone know that Node-Webkit 10.5 still works in C2 r195, the latest stable. Personally, I still prefer it to the latest version of node, which has been renamed NW.js.

    Still, NW.js is the best version since 10.5, so it might be worth checking out. Here's a thread by Ashley where he links to an alpha version:

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • An interesting side note: Chipmunk has recently updated to version 7, which has all the pro features built in, and is being released free and open source.

    https://chipmunk-physics.net/chipmunkPro.php

    Apparently, v7 can take advantage of vector proccessing on mobile (NEON), which can give a huge speedup for physics. Though, a javascript port couldn't take advantage...yet. Here's hoping SIMD.js makes it to crosswalk sometime this year...

  • Ashley IntelRobert

    Just wondering: what is the state of video support in crosswalk? Can't get it to work.

    So far I've tried mp4 (h264, aac) and WebM (VP9, Opus) with no luck. Going to try WebM (VP8, vorbis) and OGV (Theora, vorbis) next.

  • Layout size really doesn't make much difference, even for gargantuan layouts.

    4000 objects isn't necessarily bad either, as long as most of them are static. Actually, if they are spread out across the layout, that makes things even easier, since the opts for collision cells and render cells come into effect.

  • ome6a1717

    Sorry, I just don't understand you. Are you say that node is 'janking' on preview, but not on export? Or that the 64 bit version is janking? What version of C2 are you on? I haven't migrated to r195 yet, so I'm not sure if this guide will still work with it.

  • — Some functions don´t work on mobile. Specially video and openGl (maybe it works using phonegap on ios8 and androidL)

    Video doesn't work on crosswalk? That's a bummer. Is it a fix on intel's end, or does the C2 video plugin simply not support XDK yet?

    What about CocoonJS's cordova exporter, does it support video?

    Iolva

    If the video is really short, you could just load it in as an animation, couldn't you?

  • Whenever you have a debug readout, use the spritefont object. Text object are too problematic on mobile, especially if you are trying to profile performance.

  • I don't know how it works when you are using physics, but C2 definitely has it's own internal collision system that has nothing to do with Box2D.

    Basically, the way I understand it, the collision system takes the following 'top down' approach:

    1. Only compare an object against other objects in it's current collision cell(s).

    2. Start by doing a cheap boundary box test to see if the BB of ObjA is intersecting the BB of ObjB.

    3. If so, do a more expensive polygonal collision test, where the engine checks if the polygons of the two objects intersect anywhere.

    4. If physics are involved, I'm guessing that the poly test is handed off to the Box2D behavior, which tests for collisions using it's own internal algorithms. But...I could be wrong about that.

  • Is there a way to tell C2 to default to "Set to Bounding Box"?

    Importing UI elements is a real pain and I'm always getting caught trying out buttons that don't work because the poly shape is not what I was expecting.

    This. This exactly.

  • What version of C2 are you running? I'm still on r190, maybe it's an issue with a beta version?

  • Animmaniac

    Know how that goes. I've been hoping to find some time to dive into GLSL myself, but just haven't got around to it yet.

    Here hoping you find the drive again sometime.

  • Never seen that particular error as far as I know. Are you getting it consistently?

    I've found that if you hit the run/debug button multiple times when it's starting up, it can corrupt the preview runtime.

    I've also noticed that clicking on the preview/debug button doesn't always start the preview; sometimes you need to click, hold for maybe half a second, then let up. Odd, I know, but I've seen it a dozen times if I've seen it once.