megatronx's Forum Posts

  • hi, I would like to report a problem with this plugin (not posting in "bugs" section since it's 3rd party).

    I have the following event:

    And when I pressed J, I got this:

    I would also like to point out that this behavior has absolutely no properties, or any possible event conditions, and only two actions. I would highly suggest improving it.

    I think you might want to enable path first, then add point.

  • You might want to ask our buddy lucid from brushmonkey, rather then scirra, since he's the spriter dev.

  • [quote:1josnnx3]I think Ashley should hire part-time another dev to help him out.

    Or two.

    But that's another story

  • I don't think regressing NW versions is a good permanent solution - we need to find out what's actually causing the issue and get it fixed.

    I agree. Also PREVIEW WORKS so why export doesn't is beyond me!

    Maybe it has something to do with caching on hdd?

    >

    > Obviously, that would be best solution for us! I think Ashley should hire part-time another dev to help him out.

    >

    I wonder if John Carmack is available xD

    > Who knows XD. For now we're somewhat sorted as they are going to maintain 0.8 for some time. But what's gonna happen later once they drop it but the freezes will continue in the newer versions? eh, guess got to stay optimistic XD

    >

    Could you please stop editing your post while I'm trying to replay? I had to start over cause you changed a context in your sentence xD

    There still one interesting question to answer. Why it's freezing only on export and why it's working fine on preview? C2 is using exactly same NW version to preview and export.

    John Carmack is busy developing his LSD Binoculars for fb

    Could you please stop editing your post while I'm trying to replay? I had to start over cause you changed a context in your sentence xD

    Hehe Sorry, I sometimes write something then to realize that it's not what I meant to say XD Non-Native-English speakers thing.

  • shinkan I hope I have explained who we are and what we are doing. Its fair to recognize where we are in our rollout and the credibility we have from our previous efforts. We are only at the start. I have indicated our next steps. Every product has its beginning and entry. Anything new will have its critics. We expect nothing less and the reaction we get to our product will help guide future decisions.

    We are in a competitive situation bringing out a new solution that will work in a way that others don't today. There are some characteristics of our previous work that have gone into TideKit but is a new code base. We expect folks to be skeptical until they see it creating apps. That what our free trials are about when we release.

    Our reservations are there for folks that support what we are doing, who may already know us from our previous work, and want 30 days to use TideKIt as early as possible. We have been building TideKit to end development multiple times for multiple platforms with the goal developers can monetize on a single effort and customers can gain ubiquity across devices with your app.

    Keep in mind we also have APIs to bridge to native widgets for the OS. So TideKit is not simply a HTML wrapper, it is a solution to construct web, hybrid and native apps. We will offer unlimited builds using our build services and folks will be able to deploy for distribution, or a host (or cloud service) if deploying to the web.

    You know, it's the internet and it's better if people stay skeptical. But I'm pretty sure that any doubts will vanish once the examples will start rolling out.

    All Best

    M

  • Maybe we could ask Ashley to develop his own native exporter? (lol, rotfl, etc. xD)

    Obviously, that would be best solution for us! I think Ashley should hire part-time another dev to help him out.

    hehe

    So they fu*ked up 0.9.2 then. Nice

    Who knows XD. For now we're somewhat sorted as they are going to maintain 0.8 for some time. But what's gonna happen later once they drop it but the freezes will continue in the newer versions? eh, guess got to stay optimistic XD

  • scaffa not sure how this exactly works but there are two branches of NW v0.8.6 - Apr 18, 2014 and v0.9.2 - Feb 20, 2014 and they depends on which Node module you are using - but don't know what's the difference between these Node's

    megatronx since R164 C2 uses NW 0.9.2

    Yep... the moment I saw your post, same moment my test started to freeze! XD

    Ok, so back to 0.8.6 then.

  • So far 0.8.6 also seems to be working here. Yesterday I tried 0.9.2 but that one did freeze for me. Am I reading it right on the node-webkit page that there are two different versions now that they maintain? 0.8.6 is 2 weeks ago so thats pretty recent.

    Is this related to this problem? https:// groups.google.com/forum/#!msg/node-webkit/2OJ1cEMPLlA/09BvpTagSA0J

    Yesterday I posted this link here to the node-webkit github, sadly the issue is closed, it also mentions a freezing problem.

    https:// github.com/rogerwang/node-webkit/issues/1363

    So probably they know about those freezes, and they decided to work on 0.8.x. My guess.

    Is this related to this problem? https:// groups.google.com/forum/#!msg/node-webkit/2OJ1cEMPLlA/09BvpTagSA0J

    No. Post is about upload button that is not working.

  • > For anyone who's suffering from NWK freezes after exporting, try reverting back to 0.8.0, as it is working for us.

    >

    That's good...and bad same time hehe NW 0.8.0 is quite old. Newer versions have plenty of nice bugfixes and features added. Like fixes for audio, random crashes or window resize actions. And thats only few I remember.

    But well, it's better than freezes anyway. Maybe someone could post this on their bug reports or something to let them now that kind of issue exist between 0.8.0 and newer versions.

    Which version is using c2 currently? You can try 0.9.x ? It works for me although will do more tests.

  • megatronx gtx 560 Ti TOP

    I might try it again since I used a bit different approach to run it.

    I've got gt560 non-ti and it runs.

  • [quote:v6h85xxm]I can't remember now, if there was some gpu blacklist problem in nwk 0.9.x or not?! Does anyone remembers?

    Don't know about that, but node-webkit-v0.9.2-win-ia32 didn't work for me.

    Works for me. But that means I wont use it. What gpu do you have?

  • I can't remember now, if there was some gpu blacklist problem in nwk 0.9.x or not?! Does anyone remember?

  • At this time it is on the front page under downloads and Prebuilt binaries (v0.8.6 - Apr 18, 2014):

    https://github.com/rogerwang/node-webkit

    Cheers. I'm trying 0.9.2 now.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Almost cannot believe there is fix to this finally :,)

    I would dare to say that v0.8.6 works as well (been running a while now without problems). Probably any v0.8.x will do.

    [quote:36ctgtz2]I'm still curious to know why preview works, and exported file does not!

    I don't claim to know anything, but on Construct 2\exporters\html5\node-webkit there is

    package.json

    package-previev.json

    package-win.json

    so maybe there is still some difference.

    Dunno. If I'm not mistaken 0.8.1 is the one that is in construct currently ( or is it 0.9.1 ? ). If you have a link to latest nwk version that works for you, please post link here Glad to hear it's finally solved. I saw it was some time for you unfortunately.

  • Yeah so far this seems the solution to fix it. Still no freezes on both machines. Will keep on testing for awhile longer. Thanks everyone for the help and suggestions.

    Thanks!

    I'm still curious to know why preview works, and exported file does not!