OK, confirmed that it is definitely doing something odd while paused. I'm not entirely convinced it's a simple cause of it's still running because sometimes all my enemy sprites will vanish, sometimes things seem OK and so on. It needs looking at though so I'll raise it internally.

Thanks for reporting.

I'm guessing the -0.0 and +0.0 are an artefact of the floating point format (it has both a + and - 0.0 due to how it works) and Fuze is taking your "-0.00" literal and converting it to the +0.0 instead whilst the 0.1 - 0.1 is giving -0.0 because of precision limitations in the floating point format.
fract() is then handling -0.0 and +0.0 differently, which may be a bug?

i had separate sheets for my previous game but the way im doing it now wants all my characters on one sheet im pretty much locked in with what i know thus far.
one way i can create layers but no enemies items this way im doing now i get enemies and items but cant do layers

@pianofire Glad to be of some kind of assistance.

@Richard Yes I have confirmed that. I will raise an issue

Well, as I was typing in my code demonstrating the bezier bug for the forum here I realized I screwed up while scaling the interpolation fact which caused it to be ~0.5 for the first half of my loop. That's what I get for trying to debug things without sleep, but good news anyway.

I created a twitter account to share the createCurve bug since I didn't feel like retyping it here after having made a demo for it and also retyping my entire bezier program then erasing it because it wasn't actually a bug

The demo program draws a few curves via createCurve then plots the points supplied during the creation in the order they were supplied to illustrate where the points are supposed to be.

It appears that the given vertices aren't being drawn at their assigned locations, although using getVertex returns the same points that were supplied upon creation

I can confirm that this still happens and I have raised an issue

Thanks for reporting. This a known issue that is already on the todo list 😀

Please wait for the next patch before worrying too much about any of this

That's been tested and confirmed. Thank you for pointing this out, I'll raise an issue internally and this will be addressed.

@Martin Thanks for your replay, I checked all the places playerCount appear and I really found some other bugs in my code which caused the error.

Man, I'm sorry, missed this! You're absolutely right. Will create a new issue internally for it if one doesn't already exist.

Thanks for reporting.

Hmm, yep - just confirmed this.

However, It didn't happen straight away though and I couldn't make it happen a second time after restarting Fuze.

Thanks for reporting, this is being looked into.

PS: I can probably confirm this - I hadn't really paid any attention, but now you mention it, the sound is much more comparable to that of the PC also connected to the same speakers, I just hadn't noticed that I no longer need to keep turning the volume up and down !!

@SteveZX81 thank you that's helpful. I believe it is different to the problem experienced by @Nisse5 pre-patch (which I also had once or twice). I beleive that may have been a sharing issue, my working theory for yours is different but I don't want to speculate.

Mine was with portable mode, even with headphones. Would need to double check with docked mode.

I wonder if this frees the memory taken by c.

Thank you for pointing this out!