Bug Reporting

• 

  Bug Reports - a quick update
  • Martin  

  1
  10
  Votes
  1
  Posts
  322
  Views

  No one has replied

• _

  Colour Picker in the image editor...
  • _λιεχ_  

  6
  0
  Votes
  6
  Posts
  105
  Views

  

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

  strEndsWith has a little bug
  • fgalliat  

  1
  4
  Votes
  1
  Posts
  47
  Views

  No one has replied

• 

  Object Collision is broken
  • ILoveFuze  

  8
  0
  Votes
  8
  Posts
  91
  Views

  

  I too have been experiencing a collision bug.
• 

  Crash When Making A Project
  • ILoveFuze  

  1
  0
  Votes
  1
  Posts
  25
  Views

  No one has replied

• 

  Crash when entering author
  bug • • ILoveFuze  

  3
  1
  Votes
  3
  Posts
  79
  Views

  

  It happend again. This time I just entered fuze4
• 

  Can't look straight down
  • ILoveFuze  

  1
  0
  Votes
  1
  Posts
  33
  Views

  No one has replied

• 

  Map Editor bug
  • SteveZX81  

  1
  0
  Votes
  1
  Posts
  32
  Views

  No one has replied

• 

  Can't edit a project
  • ILoveFuze  

  5
  0
  Votes
  5
  Posts
  63
  Views

  

  @Martin English
• 

  FUZE4 randomly crashes when opening a project
  • ILoveFuze  

  6
  0
  Votes
  6
  Posts
  42
  Views

  

  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.
• 

  Some of the assets in the Pipo/Misc folder are not correct sprite sheets.
  • vinicity  

  3
  3
  Votes
  3
  Posts
  74
  Views

  

  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.
• 

  Unexpected behaviour with sprite user vars
  • pobtastic  

  7
  1
  Votes
  7
  Posts
  103
  Views

  

  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 )
• 

  len(text) does not work for umlauts
  • spikey  

  7
  0
  Votes
  7
  Posts
  173
  Views

  

  @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.
• 

  Snap to object doesn’t seem to work for some tile sets after scaling the tiles.
  • vinicity  

  1
  2
  Votes
  1
  Posts
  25
  Views

  No one has replied

• 

  Out of memory despite never having much allocated at any one time
  • Z-Mann  

  11
  1
  Votes
  11
  Posts
  255
  Views

  

  @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.
• 

  ref does nothing when feeding array elements to a function
  ref • • Z-Mann  

  15
  3
  Votes
  15
  Posts
  223
  Views

  

  That's correct- in version 2.15.0 ref only works with arrays and structures. We're working on expanding it to all variable types for the next patch!
• 

  "if <struct> then" oddity
  • Z-Mann  

  6
  2
  Votes
  6
  Posts
  110
  Views

  

  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.
• 

  Non-QWERTY keyboards have issues with shortcuts.
  • Doriphor  

  3
  0
  Votes
  3
  Posts
  58
  Views

  

  @Willpowered Hi! Thank you for your reply! That is correct! The software behaves as if when holding CTRL, it still uses the QWERTY layout for the rest of the keyboard, but when typing normally it works as intended. As far as I know, the shortcuts are the same everywhere (CTRL-Z, X, C, V, etc. )
• 

  Nontrivial assignment can corrupt variables in outer scope
  • Z-Mann  

  6
  1
  Votes
  6
  Posts
  117
  Views

  

  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.
• 

  setMode() doesn't affect touch()
  • pobtastic  

  4
  5
  Votes
  4
  Posts
  78
  Views

  

  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