VertexZero's Recent Forum Activity

  • Ashley, thanks for fixing this so fast

  • I agree with the fact that file size at the end matters little.

    Personally, my only complaint with NW.js is the fact that at multiple times had issues like lag, fps drops and now debugger not working (bug report can be found in the bug report section done by another user).

    Please correct me here if I'm wrong but since there's a store, maybe someone could make a new exporter for C2?. Personally I'm ready to pay for an exporter tailored for bigger pc games since the few issues with NW.js slow me down.

    Personally, I feel its a shame for C2 to limit itself to just mobile devs (maybe I'm wrong).

    Cheers!

  • Solomon

    Double the file size in x64 comparatively to 32 bits.

    Also, 32 bits not working at all. I cannot start the exported file.

    The debugger is not working, and a few users in the forums are experiencing the same problem with the same versions of C2 and NW.js.

    NW.js in the past had several issues with performance and this worries me.

  • to me NW.js file size is not a problem, but I feel is (as I previously posted it) not reliable.

    With the last alpha and latest C2 version I cannot use the debugger as an example, and with just a prototype game I have sometimes slow downs in fps which are sudden drops.

    In my case, I'm (sadly) slowly moving to Game Maker which represents for me to learn a new software plus learn the coding language as well.

  • Ashley, thanks for your time.

    Some users already filed a completed report with the same issues I'm having with the debugger. Strangely, this does not happen if I switch to Chrome.

    But in Chrome, the debugger slows down until unplayable in just a few seconds of use.

  • Is there any news on this? So far I still problems with the debugger in NW.js. Is there any other way we do not depend on NW for desktop games?

    So far, I've been slowly doing a transition to Game Maker because of issues like this.

  • You set a family for the specific solid you want to disable and that's it pretty much. On family folder in the projects section right click and add the elements specific to each family.

    Then on an event use the family plus extra conditions to check if collisions are enabled . Then in the action section set Family (set collision disabled)

    If Family conditions enabled & Then -- Family Set Collisions disabled

    (extra conditions)

    Something like that should probably work but haven't tested it yet.

  • I just tried using a family to disable the collision. Seems to work but not sure if its what you need

  • Same, just with NW later version 0.13.7 alpha.

    If I switch to chrome I can debug for now.

  • Cant you use certain solids in a family and that family be ignored by the behavior?

    Sorry, I'm saying this on the fly and I don't know if it could really work but just an idea.

  • — the latest versions. r219 and NW.js 0.13.7 alpha

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Actually just using platform, AJAX, and FSM. I have at times drops of frame rate. They happen fast but still happen.

    Also, right now, its impossible for me to run the debugger. Trued with a new project and had the same issue. I think NW has been giving a lot of issues for the past year or so and its often slow down the process of creating a game.

VertexZero's avatar

VertexZero

Member since 13 May, 2013

Twitter
VertexZero has 1 followers

Trophy Case

  • 11-Year Club
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • RTFM Read the fabulous manual
  • Email Verified

Progress

15/44
How to earn trophies