Colludium's Forum Posts

  • this is great.. my game isn't ready to deploy, but would love to know if others are moving forward with this... maybe we can setup a thread somewhere that talks about deploying to Steam/Xbox/WiiU etc...

    I think this is a really good idea. Perhaps even community adjusted tutorials as well (for those with the rep), so that there are repositories of knowledge with easy access, instead of having to google search the forums...?

  • Cool. Happy that we tried and at least this thread will serve as a record for anyone searching about this in future.

  • Thanks glerikud - this demonstrating my inability to use my phone properly! Ashley - re-tagged in case my edit above doesn't do the trick. Thanks.

  • Ashley, could you please clarify whether or not the play sound at position is a web audio call and whether - if it is web audio - this sound induced jank is consequently a bug in chromium? Please take a quick look at the chromium bug report linked in the first post - I sense that this will not get fixed from comments so far, and I don't understand the c2 internals well enough to argue accurately. Thanks.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • C-7 - ooooh - I couldn't get it to happen in Edge. I submitted a bug report (here) but it was closed because it appeared to be a chromium only problem. Are you able to create a capx - perhaps it is a c2 problem...?

  • Just for everyone's information - there is a bug in Chromium engine where a sound played at a position (to give a stereo effect) causes a huge jank the first time it is played. I have created a bug report in chrome here as this is not directly a c2 problem; the problem appears on Chrome and nw.js...

    To work around it, play a quiet sound at an object during your start/splash screen and all should be well thereafter. I'll post here when the problem is resolved.

  • Yeah - that's a good work-around, but it probably should be documented somewhere so it doesn't catch people out in future, at least until it's fixed in Chrome.

  • Outstanding progress

  • Ah, yes - text objects are more demanding to render, so it might be better to render the display using a sprite font instead.

  • Maybe it's not telling the truth - can you add a text object fps indicator as well to compare them side by side?

  • This is not a bug. If you check what the font looks like you'll see that this is by design.

  • I just saw your comment in the closed bugs section, Quicksand - you could be right that the work around in this beta is the cause of this problem. Well, the original bug not being fixed is the real cause, but you know what I mean .

  • The symptoms I had was first start was OK, thereafter the preview/export would start to a background process unless the User/AppData/Game folder was deleted. I thought the antivirus bug was just a false positive preventing start?

  • No - I don't think it's to do with antivirus.

  • I tried v14 rc3 a few days ago and found that the old not closing bug was back, so I created and submitted a bug report to the nw.js github here a few days ago. Version 14 rc3 appears to be unavailable now - I am hopeful that this will help fix the problem. I would appreciate more experienced eyes on this just in case there's more that can be done to help them fix this that I might have missed.