TheRealDannyyy's Forum Posts

    Here we are again with the classic case of Native

    VS

    HTML5. Well I think you can say as much as you want for both, in the end they both come with their own set of limitations and issues. Over the period of 2-3 years that I've actively used and still use C2, I never really had problems with the web itself.

    One of the few things I'd complain about is the way Scirra (I guess Ashley in particular since he handles the most of the stuff) deals with bugs. Don't get me wrong I fully understand that there are bugs not caused by C2, however I think re-directing the user to those 3rd party websites to report the bugs by themselves is not the right way to go.

    Let me go a little further by giving an example on the "correct" way of handling bugs by 3rd parties from a well known competitor named Unity.

    If you would for example use their native engine and experience a bug, you'd report it to the issue tracker and wait for their response.

    Usually you get a quick response and a bugfix within the next few update cycles (just like C2 does), however if you'd experience a driver issue for example caused by buggy AMD drivers. They don't re-direct you to the AMD forums and say something like "It's not our fault, report it to them please." no, they take the information they got and report it there for you. This is the behaviour I'd like to see from Scirra, being more helpful in regards of fixing 3rd party bugs instead of blaming them and then keeping quiet about it.

    Before people start with arguments like "Don't be lazy and just do it yourself!", indeed that is something that more advanced users can and will do, in fact I'm doing it sometimes as well but please try to see this situation from a beginners perspective. They already have it difficult enough to learn C2 and now you expect them to go ahead and report a complex bug with next to no knowledge about how a game engine works, I don't think that's right.

    I understand that there currently might be no time for Ashley to do the things I've mentioned but as soon as the work on C3 is done, I'd really like to see some improvements.

    In the end it counts as some sort of customer support right or am I wrong?

    This is also a response for THIS topic which had a discussion about the same issues that I tried to explain above.

    As always share your thoughts below and keep calm, it's alright to criticise the things you like.

  • I tried manually with "--single-process" but still couldn't launch the game.

    My bug report is still open, so I guess they didn't fix it.

    Gonna try it out later by myself to make sure.

    Lol. I stopped using C2 for a while, i'm currently studying C# for Unity. I'll just come back when C3 is done.

    Honestly, C2 is great but (performance + better export) is greater.

    Do yourself a favor and learn Javascript instead, just for the case when you have to come back you could join the JS Plugin magicians around here.

  • Update

    Add new code "img" to embed image, for example

    [ img=smile]

    sample capx

    See demo in first post of this thread.

    TheRealDannyyy

    Finally it could embed image.

    Niceone, gonna check it out soon!

  • Yeah it's actually mentioned a bit up in this thread, but here you go: https://github.com/nwjs/nw.js/issues/4947

    Whoops, I should've paid more attention thanks either way.

    Looks exactly how I expected it to be, just earlier today I saw a guy getting bashed in a topic about this "passing the blame" issue that's happening frequently.

    Well I guess we are on our own, since this issue doesn't seem to happen within chrome, their team will blame it on the software or back-end we use.

    Keeping things short we either enter the endless loop of waiting and getting nothing done or do it by ourselves.

  • Thanks. I've released it with NWjs 0.13.2, so there will most probably be no feedback regarding this flickering. I'm busy with other things now, but once I'm done I'll try to replicate it and simplify capx as much as possible. We'll see if we can identify the issue. I think it is purely NWjs issue. There's no flickering when you test in Chrome. But I'm not an expert and as NWjs team ignored this issue stating it's not their fault, then maybe it's not. They know more than me. And it's also weird that it's related to the Audio plugin. I'll update the capx when I'm done.

    OK sounds like the classic case of passing the blame, if the problem persists in the newer versions (v19+) I will start another bug report on their git.

    They won't be able to get rid of me that easily.

    Anyway, do you have the link to the report for me? I'd like to check it out by myself.

  • >

    > or perhaps an action to record gameplay directly in C2 like some emulators do but I do not see that hapenning anytime soon.

    >

    Check out the user media plug.

    I would be careful with that, as a self proclaimed "fanboy" of the canvas recorder I have to say that it's not very stable right now.

    Although VP9 recording got fixed by Ashley a few weeks ago, there are still bugs left like for example bloated memory use and even crashes when using NWjs (32bit).

    Finding a fix for those (bug-reporting to the browser vendors) is my task now though, as it seems like C2 is not at fault.

  • It works fine with NWjs 0.18.1. I have no flickering any more.

    0.13.x - no flickering

    0.14.x to 0.17.x - gives flickering

    0.18.x - no flickering

    I tested it only for around 10 minutes, but usually it started flickering within a minute, so I'm pretty sure it's fixed.

    I think you got a game on Steam right (congrats btw), might want to check out their reviews.

    The more different setups we test this on, the better we can identify and hopefully find a fix for this bug.

    I rolled back to 0.13. No flickering.

    I'm not on Ashley's level when it comes to things with the web but I've had similar issues to this one in the past with native software and directX.

    For me this all sounds like there is something terribly wrong with the drivers, this doesn't necessarily mean that you guys are at fault.

    No, it might be more of a bug from NWjs's side of things, however if that would be the case then you'd also experience this in Chrome itself.

    I would like to request a basic example.capx where this bug is occurring so that I (and maybe others) could investigate it.

    If you got some free time, I'd very much appreciate if you could share the following helpful information:

    • Basic info about your graphics and cpu drivers
    • Any 3rd party plugins that you use, even if they don't seem to be related to this
    • The content of all 3 package.json files found in your nwjs folder (X:\xxx\Construct2\Construct2-Win64\exporters\html5\nwjs) You can upload those files to make things simple, they are just about 3KB big.

    What you also could do right away is to clean install the latest version of NWjs.

    At first use the uninstaller and then go back to the actual folder and delete everything that's left (nwjsforC2 folder only).

    As useless as this sounds, I had my fair share of "experiences" with NWjs and I got them fixed by exactly doing that twice already.

    Thanks for your time and looking forward to the helpful information.

  • You might be able to achieve different font colors by using the "Set Color" effect.

    It will not help you for the case of changing single chars though and that's what you're looking for I guess.

    Godot's visual scripting appears to be one of those 2D flowchart type systems, which are very different to events. They also quickly turn in to a mess, which they seem to have already noticed themselves

    I also saw that tweet yesterday, didn't bother mentioning it tough.

    Have you ever tried the Editor? It's far from as easy to use as Construct's in my opinion...

    I think there's always a tendency to look for the "perfect engine". It happens on every user forum of all the mentioned software packages that i've ever been to. There are always things that could be better or optimized etc. I think there are a lot of people who never start actually making a game, because they keep looking at different game engines every other week. I know i had that problem for much too long. In the end what counts is, which tool makes you actually realize your project the quickest and most convenient to you, which is very subjective. For me PERSONALLY i really always came back to C2 because i didn't see any other program, where i could get something done so easily and still remain a great deal of flexibility. So i'll stick around for sure and i'm looking forward to see what C3 will offer

    I've tested one of the older versions, the version that came with their Steam release to check out what it has to offer besides 3D support.

    If I had to define what "easy" means, for me it's basically meaning that I can understand the use of the engine with just a little effort.

    When I started it, I could easily identify all the core elements (e.g. scene editor, behavior systems ...) of the engine without opening up their documentation.

    The only difference in comparison was that C2 is using eventing instead of programing so in their case, that was the point were I was forced to open it up and check on how things are done. Might be worth mentioning that their custom programing language is quite similar to python and I knew how to program in python before I've tested Godot.

    I think generally any kind of alternative to programing, flowchart or event based counts as "easy" and it depends on the engine if it looks messy or not.

    Just compare CTF to C2 and you'll understand what I'm trying to say with that.

    For me personally it's too late anyway, I'm too far in game development to change to a different engine and start all over again.

    I'm not trying to say that it's "bad" to use C2, it's just that a lot of the limitations that I didn't know about before I've started working with C2, now reveal themselves.

    Nah, I think Scirra should let them do the first step.

    Would be good to see what those "praised" new versions/programs really have to offer.

    Game Maker Studio 2

    Does GMS2 also come with a visual scripting editor? I couldn't find any details about that.

    ClickTeam Fusion 3

    CTF was always more of an "ugly" version of C2 for me, If they plan to clean it up a little for their 3rd version, it might be a serious competitor.

    Spark (Full Release)

    I've lost all the hope I got about Spark, I think it's either going to be dropped soon or come out within the next 5-10 years.

    Godot 3.0

    Now Godot 3.0 is something that Scirra should really worry about, not only is it open source (FREE!) but it could also easily compete with C2's editor in terms of usability. The major thing that was kinda missing is the visual scripting editor. Now it seems like it's about to be added, this might be interesting to follow.

    EDIT: Of course there are also other problems and errors that need to be fixed too.

    SuperPowers 3.0

    Superpowers looks like one of the many script based game engines that you can find on the Internet, nothing to worry about IMO.

    These are just my opinions about the competitors, if you disagree or want to add something feel free to do that below!

    It's always nice to compare things and find out the dis/advantages that they might have.

  • Alright. I tried with --single-process and the game won't even run.

    ...

    It's a known bug, I've already reported it and they've confirmed a fix in some of the future NWjs updates (probably v0.19.0)

    I hope all of our worries about weird glitches using Steam + NWjs will be fixed, once we can make use of the single processing function.

    As always, we have to be a little patient and everything will be fine.

    EDIT: Sorry I missed that Silverforce already told you that, whoops.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • TheRealDannyyy - yeah, it's a bit outside the scope of Spriter to handle physics and and collisions. I think the best alternative would be to create the joints based on the Spriter bone positions. I don't have time to look in depth into chipmunk physics at the moment, but one thing I've considered adding and might be able to add (probably not too soon) is a hierarchical 'for each bone' condition that would loop through the base bones, and then each of their children, etc, and corresponding expressions to give you the 'current child bone'/'current parent bone' type info. Would that be helpful?

    It's hard to tell right now, it might help but I think I will just keep on going with the current method and unfortunately skip the use of the new spritesheet function.

    However if there are any news about this in the future, I'd appreciate a tag.

  • That's the best way to go with it if you want results quickly and work on other features instead of waiting for something that might take weeks to months to materialize. Yes, you have to rebuilt all the animations for each part in new scmls for separate parts. Easier than imagined since you already have all the important details in your original scml. Tedious but doable in several days.

    I've never said that I want this feature in a few days, infact it can even take up to a year if it has to.

    So far the workarounds are mostly more difficult or tedious than my actual method, which leads me to believe that there is no "better" way to approach this.

    Anyway, thanks for the idea Sethmaster.

    I really hope that Brashmoney will revolutionize 2D Construct games a little further on this end, I don't see any negative aspect about this TBH.

    It's already a standard feature that comes with the most 3D game engines, so why not make it a standard with 2D engines as well?

  • Why do you just divide the objects that you want the physics on into separate parts and scmls to be inserted into C2 and combined them back with behaviors, instead in a singular scml?

    That way, your old methods still work without too much effort.

    I think I don't understand you quite well, you want me to import ~12 different spriter parts and connect them with each other?

    How would the spriter animations still work if I use different scml files anyway?