Jase00's Forum Posts

  • Multiselection is a "nice to have" imo, but not crucial.

    I mainly was curious if this stuff was incoming due to the recent update making changes to touch/pen.

    I feel there's an easier approach than needing to heavily modify the event sheet view, but maybe I am missing something. There's already a dedicated global "Mobile mode" that allows the windows to pop out from the sides of the screen, so I'd have thought this wouldn't affect the general desktop user.

    What about a scroll area on the left side of the event sheet view that scrolls JUST like it does when using touch, but then the rest of the event sheet view is treated as a mouse with click/select/drag? For a sacrifice of squishing the width of the event sheet view slightly, it would grant fuller functionality.

    E.g. In Construct terms: if touch.x < viewportleft()+64 then "SCROLL" , else "BEHAVE LIKE MOUSE (I.e. Tapping would select, dragging would drag the events/actions)

    I like to think this would be relatively straightforward to implement as the "touch scroll" code already exists in c3, as well as how mouse behaves within the event sheet view.

    You could scroll with your left thumb and you could hold onto a drag with your right thumb and just drag n drop like you would with a mouse.

    If it's complicated then I will stop chasing this as it probably is a niche suggestion that won't get much attention, I just hoped a basic method to drag n drop could be thrown in for mobile users.

  • Well like, actions specifically - if you had 10 actions in an event, and wanted to move the 5th action to the 4th place, you'd have to cut and paste each action 1 by 1 until its in the correct order.

  • I gotta say, the recent update really gets my hopes up that maybe scrolling/dragging events in the event sheet view, might actually become a reality. Even a clunky solution would be used a huge amount by myself.

    ... Is this on the cards at all?

    Being able to drag events, in any way even if it's clunky (but at least possible), feels like the last hurdle to being able to fully using the event sheet view on mobile!

  • I was wondering about this a couple of months ago too.

    I understand that it's a tricky thing to implement, but I do wish something like a toggle button could exist that switches between "Scroll" and "Drag n' Drop" mode, anything would do, I'd use it a huge amount.

  • Thanks for the info! I gather this means that photon is a paid service that is more easy-to-use but less flexible (I.e you cannot control who receives messages; photon just broadcasts everything out)?

    I was under the impression you could setup a "dedicated host" type of setup with the Multiplayer plugin too, I thought running an instance of your Construct project on a server or a computer that is permanently on, would act as a sort of dedicated server.

    Do a fair percentage of people struggle to connect to the Scirra multiplayer signalling server?

    Very interesting nonetheless, having more options is always good!

  • I see "Photon" mentioned often. I use the Multiplayer plugin when I make online games and have never really looked into Photon - Are there any notable pros/cons to using Phonton?

  • You could delete the LiteTween behaviour using C2, then load your project in to C3.

    C3 has an official Tween plugin, so you could recreate the missing events afterwards.

    It's a bit tricky doing this blind, but you could open C2 with the original project, then do a search for "LiteTween" and then have C3 open at the same time to compare and re-add events.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
    • Post link icon

    I mean, the OP of this post is clear as anything - The GIF shows the issue, Sine behaviour + jumpthru on the platform, platform movement on the player.

    It's certainly to do with the Sine platform skipping beyond the player as it moves up, right? - It can't be the player moving too fast DOWN because I think the platform behaviour has stepping and such to prevent this.

    Just from the OP, no detail appears to be missing in this case.

    Thing is, I wouldn't have reported this bug if I encountered it, because I have the strongest feeling I would spend time making a repro c3p file, fill otu everything, make a screenshot, upload it all, post it on Github... then I'd wait unknown amount of days, and eventually get a reply saying "Ah it's complicated" and that's it, no workaround offered or anything.

    This happened with me posting a bug about the Drawing Canvas - an actual feature in C3 is to "Paste Effects into Drawing Canvas"...and it's broken for a bunch of effects. No fix, no timeframe like "This may be fixed in a year, or when we recreate the effects compositor", no workaround (ironically, posting to the forum afterwards, someone from the community offered a workaround).

    I respect things can be complicated, but what would make that whole experience less frustrating would be either: A) If the reporting process was much faster (e.g. reporting directly within C3), or B) If more could be offered if a bug cannot be fixed, such as a suggested workaround or something.

    • Post link icon

    mOOnpunk - You're right, and that's also an amazing idea!

    It'd rule out false reporting if someone claimed to use a specific version too, as C3 would just collect this info in the bug report.

    Anything to speed up the reporting process.

    • Post link icon

    I agree with Ormus, but I guess the main question is - When we pay for our subscription to C3, are we paying to be able to use the software, or are we paying for support? Or both?

    Even if you're not subscribed to C3, I know Scirra will still check any bug report from anyone, which is great!

    Once you sub to C3, do you get more perks in terms of support?...not really, no, because anyone, free or subbed, gets the same level of support.

    With other companies, when you pay for support, they have ticketing systems that staff and customers can both use, so you could email-in a bug a report, or pop it on the forum, and a staff/mod/volunteer would submit a ticket for you (because you're paying for this support) and they'll communicate back and forth until you feel happy it's resolved. OR you could submit a formal ticket yourself. If I could choose, I'd post bugs to the forum - I like the discussion that can come with it, and I like staying in 1 website.

    With C3, you MUST submit it to Github (Unless there was a lot of noise on the forum post with other users complaining, then that'll attract immediate action). But that's absolutely fair, if we are not paying for support, which I don't think we are.

    Time is money, especially when we are paying subscription fees. Noone wants to be bug-reporting for a subscription-based software, everyone would much rather be USING C3 to make their games and such.

  • It's alright! With functions, I don't think it'd break your project or anything major, but worst case might require reworking some of your functions to use the new c3 functions type.

    Thankfully there's an option in C3's event sheet view, where you can right-click an old function and convert it to the new c3 function type, which worked well for me when I've used it!

    I think there's something that other users have come across, I think "calling functions within expressions" becomes a bit different? You can read about "function maps" in the c3 manual if this is the case.

  • Ayy, I think it would be a generally smooth transition for you as you do not use 3rd part plugins. I think you can open capx files in C3 even if you are not subscribed, so you could check it out maybe.

    One thing you may want to do when you do load your capx in, is convert all your functions to the new C3 functions - it works a bit differently to C2 functions so I'd recommend checking out the C3 manual on functions. This might cause problems depending on how you use functions in your original capx.

    I can relate with you - I sometimes don't develop anything for months at a time - but thankfully this year, Scirra have started offering monthly subscriptions, which is great as you could just unsubsribe when you realise your time is limited. I've found I've not used C3 for some months and have saved money by unsubbing (my subscription recently ran out again as I'm working on a project in C2 that doesn't really gain much from being ported to C3, not to mention I use a lot of 3rd party plugins and it's a pain to delete 3rd party plugin events in c2 and need to cross reference from c2 to C3 to recreate events/actions).

    C3 is great! It's very comparable to C2 and the fact its in a browser doesn't ruin anything really.

    The recent scene graph feature makes it really easy to pair up objects, rather than needing to make a variable for each objects.

    Some things will randomly catch you out, like, the "Crop" scaling mode was removed in c3, even though some of my projects depend on this for dynamic screen sizes with UI positioning and such. But this can be worked around with the other options and some events.

    One hot take - I don't think there's anything you can do in C3 that you can't do in C2. C3 makes some things easier, but in the end, you could have made whatever you were trying to make in c2, though you'd have to rely on 3rd party plugins for this.

    I'd say check C3 out for a month, it's a great bit of kit.

  • I think I know the answer:

    Once you use a "wait" action, even if you used "wait 1 second", the function parameters will not be stored, so you will end up with "0" if you put "function.param(0)" after the wait action.

    This is fixed in C3 I believe, where "wait" actions will still remember the parameters.

    But yes, storing the value elsewhere like you said, is a fair workaround.

  • I think they've chosen to go with the unofficial launcher now.

    I don't know the guy/gal but I'm confident that Scirra will not get any redundant bug reports from gustavoChico being on r218 when they're using the unofficial launcher. Judging by their posts, they sound competent and aware of what they are doing and understand the risks of remaining on the older version. They just wanted a way to actually stay on the version of their choice, which sounds like there are 2 (unofficial) ways to do now.

    dop2000 that's excellent, this gives people more choice in how they arrange their workflow! Not an "official" solution but the logic stacks up - just changing 1 URL in the official launcher sounds like it shouldn't go wrong (but then again, still not "officially" supported).

  • I somewhat agree, but the main thing being: Considering the "Forced update" can be avoided by using other official means (web version) but the web version doesn't work with Github, then it does make it a bit weird that there's pushback for the official desktop version behaving the same way as the web version. Inherently not everyone is keeping up-to-date.

    To be honest I'm out of the loop because I work alone and use the unofficial launcher and I keep up with latest betas, I was mainly unhappy seeing the false accusation of "It's not fair you come here to tell us to *blah*" when it was never said nor implied. But hey, miscommunications happen.

    Infact, I'm so out of the loop - You mention the package.json, you can simply edit this in the official launcher to pop the /r218 link directly in? That sounds like a fine solution if so - Still using the official launcher but having a fixed URL to the version of choice! I must have missed that.