VertexZero's Forum Posts

  • linkman2004, thanks!!

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Ok guys, sorry if this has been previously asked but I got a few questions:

    Presently I use a sprite of 96x144, This sprite is a resized X3 version of the original sprite. Now, I know I could do it smaller and resize afterwards, but thing is that I have different resizes for levels and characters (artistic choice).

    Now, if I export an animation sheet from asesprite with 4 frames. Its only 2kb, if I don't resize it 3 times its original size, its 1kb. Problem is if I use photoshop where even when using super png exporting plugin, I still have 16kb. So, Im curious about performance here.

    Will I have issues by resizing the sprite rather than resizing the layout at runtime?

    I'm trying to figure out whats the more optimal since my project will be fairly large.

    Thanks!

    Ashley, I posted it here in this thread, sorry if it wasn't in the bug sections, my bad.

    At almost the bottom of the page.

    https://www.scirra.com/forum/viewtopic.php?t=166653

    Ashley

    I'm having this same issue but I'm not using steam. It happens only with my working project. If I create a new project I'm not able to repeat this issue.

  • — having the same issues but only with my project. If I create a new project I don't have issues with NW.js

    Also, when testing in Chrome I dont have lag anymore. But Ive been optimizing.

    Having similar issue. Can't test my project with NW,js viewer. But I can test it with Chrome and Firefox. But I'm having this issue just with my project. If I test a new project I have no issues at all.

  • yes.

    My setup

    Windows 7 x64

    C2 64 bits

    with latest verions for both C2 and NW.js

    I'm having same issues as the Steam version.

  • Yes, that version.

    And I can test on browser but cant using nw.js.

  • Here is a link with a previous cleaned up project:

    https://drive.google.com/file/d/0B27TG57JCwl_TDI5RGRQS0N3Rjg/view?usp=sharing

    I can test with Chrome no problem at all but not with NW.js. The latest version that seems to work is NW.js v0.13.0 alpha 5

    So far the problem is found only on my project. If I create a new project everything works fine.

    zenox98

    No, nothing on debug either.

    If it can help, someone already reported NW.js staying open after closing game on the task manager. nw appears as listed in the task manager but window refuses to open.

    Thanks in advance!

  • Exactly, thats the problem, I tried a simplified version with same plugins and no problem at all. Its simply my project that seems to refuse to work with NW.js

  • Latest version for both r220 and latest NW.js

  • This is not really a bug per say but since the latest version plus latest NW.js beta I cannot test my project.

    It runs fine if I use chrome instead.

    With other projects NW.js runs fine though. Anyone having the same issue?

    I'm trying to figure out what plugin might be causing this.

    Thanks in advance!

  • 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.