i actually have this problem also with my azerty keyboard and when selecting french (which uses azerty) in the switch locale settings. If i press the W key in the editor it actually types correctly the W character as it should, However the W key sits at the place where Z would be on the qwerty keyboard (W & Z are switch physically on the keyboard). But i intially tought there was no keyboard shortcut for undo as i tried ctrl-z while i later found it ctrl-w worked so it has to do with azerty keyboard (and maybe scancodes) and perhaps keyboard locale settings on the nintendo switch. Now that it know it it's not that big of a problem would have been more of a problem when the editor actually typed Z instead of W :)

this reminds me of RPGMAKER XP Tiles, an array can fix that just offset each frame by 2 to skip the 2 frames 0 -> ( 1-2 ) -> 3
i could be completely wrong

Thank you Will and sorry for being a moaning old boot.

I too have been experiencing a collision bug.
alt text

It happend again. This time I just entered fuze4

@Martin English

This happens to me too. I think it has something to do with switching between the editor and the projects screens too rapidly and then running the code sometimes? Not quite sure.

I noticed similar problems with parts of sprites being cut off or not available with Ansimuz - Warped Space Station - SpaceStationBunny and Ansimuz - Warped Extra - Portraits.

Oh yeah, the point is to be able to manipulate a vector other than the sprites own properties. I actually found this ages ago, I just randomly fired up a version of Jet Set Willy I have and found it again. The issue there being that, the characters "walk across the frame" and you only change sprite x once the tracking x reaches % 8 == 0.

Something like this;

// Work out the current frame based on the tracking "x". game.guardians[id].frame = ( int( game.guardians[id].pos.x ) >> 1 ) & 3 // Only update the sprite "x" on a byte boundary. if game.guardians[id].pos.x % 8 == 0 then game.guardians[id].x = game.guardians[id].pos.x endIf // Change frames based on movement, and not time. setSpriteAnimFrame( game.guardians[id], game.guardians[id].frame )

@vinicity I based the strLen() now on the byte size of a character and dropped the workaround over the pixel length of a string. https://fuzearena.com/forum/topic/1439/demo-high-scores-supports-now-unicode . Dividing the total pixel length through a single character pixel length caused a rounding error at some specific text sizes and 2.99999990 resulted in a string length of 2. This wont happen anymore now.

@Z-Mann I can finally confirm that a fix for this issue is complete and will be delivered with the next patch.

@romain337 The program you shared runs successfully on my end, and it should work for you in the next patch too.

You are 100% correct: The implementation of if does indeed silently give up if the input is not an int (bool) or a float. Neither path of the if/else statement will be executed in this case. We'll likely have this produce an error in a future patch.

Edit: A fix for this is coming in the next patch, to be exact.

Wee! And no worries, I did find a workaround for the real problem I was having. Everything works if I just restructure the code so the outer scope variable doesn't have to be used any more after the loop exits.

Thanks for the report! I put it on my list of things that need looking at. You can expect a fix in the next patch, because this is a big issue for the touchscreen.

Not 100% sure if these will work, but as possible temporary workarounds:

(First problem) Convert the touch coordinates to the range of your current mode (Keyboard problem) Before calling input, try setting the mode to 1280x720 and the view to 0, 0, 1280, 720, and change back after

I've just moved this to bug reporting!