NetOne's Forum Posts

  • Good call, money well spent IMO.

    Give the family all the instance variables (and any behaviors etc) you need for the enemies then just chuck all the enemies into the family and they will inherit them.

    Then run the bullet clash and any other events against against the enemy family instead of individual enemies and construct takes care of the rest. makes life super easy.

  • Just tried

    | Global number boxspeed‎ = 5

    + (no conditions)

    -> Sprite: Rotate boxspeed degrees clockwise

    + Touch: Is touching Sprite

    -> System: Subtract 0.1 from boxspeed

    works as expected - box slows down then goes anticlockwise. Must be something else in your events.

  • you really need families to do that efficiently. then you just add all your enemies to the family. (but that is in the paid version)

    only other efficient way i can think to do it is have all your enemies in one sprite but on say different animations.

    otherwise you could make a bunch of ORs or a mapped function (is that only on paid?) but these will take up a lot of lines which you dont have.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Just to follow up here, ive become a little obsessed with touch event to audio response time (which I will call lag from now on) for the last few days.

    I have found the following.

    1. If I have nothing updating on the screen there is a lot less lag
    2. On phones, APK are less laggy than visiting the website , even without the desync option (looks like the APK allows the phone work harder than the website version. there is a doubling of CPU utilization from 2% in the browser to 4% when running the APK)
    3. An android 5 lollipop build is less laggy than an android 8 Oreo build.

    I have no way to measure but basically the android 5 lollipop build (at least on my phone cubot power) is getting a reasonable enough response time to make a real time instrument viable, at least for slow medium speed playing.

    I just have two questions.

    1. On phone. Is it not possible to make the website version as snappy as the APK version?
    2. With the APK, Why is the lollipop build snappier than the oreo build? I thought it should be the opposite, and is there any drawback using the old lolipop build?

  • OMG....

  • Note I am very happy with C3 performance

    but I am just wondering. (And I have no idea what I am talking about....)

    if... as halfway house to native, could construct export to something like React Native (or similar) facebook.github.io/react-native

  • tried with the incognito as u suggested get same, snapped the error it is the same as the closed bug on git.

  • drive.google.com/open

    had to use 167 as have already used the new betas

    sorry i forgot to check the error but am ssure it is same as github.com/Scirra/Construct-3-bugs/issues/3365

  • Hi Ashley

    im pretty sure it came up it again recently for me.

    Note it is only a specific case where you have downloaded a new version.

    You get the download ready for offline message then maybe shut down close up with the idea that next time you will be off line.

    But then later, when you are off line, you go to preview, or debug preview, and it will not work.

    I have found the way to get around it, is, once I see the downloaded message, then run a blank preview and a blank debug while on line, and then go off line.

    Then they will work off line later. but if you dont pre run the previews on a new version while on line they wont subsequently work off line. The issue is separate for both preview and debug.

    is there maybe something happening out in the wild that is not occurring in your development environment?

  • anyone know how to play tin whistle?

    phones only!

    yamaforce.com/ironpan/open/1

    looking for feedback on lag.

    on my phone CUBOT power (some lag but very little maybe 50 ms so is very playable.

    on my other phones MOTO G4 and G5 (terrible lag like 300-600 ms totally unplayable.)

    • Top Right button - full screen
    • Diamonds - start the drones and pipes.
    • Rectangles - Drone keys.
    • To Play - face phone away from you and place fingers over squares like tin whistle.
    • You can swerve notes by moving finger to outside of line near square.
    • Tilt back to change octave/register the litle lever button can change trigger angle
    • kind of need a big phone, as so fingers should not touch each other, also make sure your fingers and screen are very clean or the sound will jump all over the place

    youtu.be/kPOEQuLrsKo

    Subscribe to Construct videos now

  • I was complaining some time ago that you couldn't preview if you were off line unless you had at least once previewed before going off line. construct.net/en/forum/construct-3/general-discussion-7/regular-issues-running-144132

    I think you may have found the reason.

  • hmm sounds like some sort of system overload. is your project hosted can we have a try? or try to replicate the issue in a simple project and maybe post here or send into he github bug tracker.

  • Unless you have uncovered a bug the only thing I can think that would cause such distortion and audio related crashes are stacked samples or effects.

    Make sure no sound is being re-triggered repeatedly without stopping it first.

    especially for longer samples, especially if mistakenly being triggered every tick, will cause sample stacking, amplifying and distorting the sound and can also kill some audio processors.

    Also check effects use.

    In a similar way it is easy to make the mistake of adding the same effect again and again to a sound rather than changing the effect.

    This stacks the effect causing the same issues as stacked samples.

    edit - if you solved the crashing by reducing file sizes then maybe check your samples in an audio editor, maybe those pops and clicks are actually in the files. also if the samples are heavily compressed and maximized then probably not a good idea to play at 0 db as this can cause clipping in some audio hardware giving pops and clicks.

  • Ashley

    Using desynced compositing for apks results in black-screen/load fail.

    I assume this is a bug?

    So will raise.

  • Appreciate that Ashley.

    I didnt even know that last two settings existed.

    I have implemented and do believe there is a slight improvement.

    Thanks!