How strange. 5 seems to be the culprit and only when using the numpad as far as I can tell. Thank you for the report!

@Dinocoder duplicating the same line of code twice will apply the offset it's a minor fix for now.

I don’t understand enough about this to comment meaningfully myself, but if one of you could comment about workarounds or ‘usage guidelines’ or whatever, I would be interested to read. Seems as if you know all about this stuff already.

Thank you for the report! This will be addressed in the next patch.

@EvanTropFun If you are referring to the scenario for games measuring time that has passed since the last run, we could use https://fuzearena.com/help/view/clock to get the real clock.

@PB____ Ooooohhhhhhh I did this so many times on accident. That's what was happening!

@TitiMoby No but the documentation should at least be consistent. We will fix it

As a temporary workaround, try this:

setSpriteCollisionShape(sprite, shape, width, height, rotation) sprite.collision_offset_x = x_offset sprite.collision_offset_y = y_offset

Ansimuz also has missing tile boxes in the single animation states in / Warped and Warped Lava

Thanks for the report and sample code! We'll definitely look into this one for the next patch.

We are aware of this one, thanks for reporting.

@Z-Mann apologies for the delayed response. We will look into it.

Thank you for the report @Z-Mann! We'll be looking into this.

@EvanTropFun Well I obviously didn't!

Thanks for the report- I've put it on the to-do list!

This is being looked and currently and will most likely be fixed in the next patch!

@vinicity Thanks, I'll take a look! And yeeessss... deltaTime... that sounds exactly along the lines of what I was thinking...

In the interest of time, I'm tempted to just forge ahead with my game as-is, then make a "2.0 engine revision" with improvements like this, and which I (and others if they want) could also use for future projects...

@Willpowered thanks, luckily it's not easily triggerable unless you pressed accidently F5 in that location in the image selector (like i did).

There is also an issue with not all memory being returned when restarting the game.

In F4NS 3.0.0, the interpreter uses a pool for some internal resources, which are around 32MB each. These aren't cleaned up at the end of program execution, but rather reused on the next run. They're also reused during program execution. You may notice a lower available memory while running your games due to this, but it also increases speed. This system may change in a future version.

These two issues eventually causes an memory allocation error when I start my program (after a long Fuze session with lots of program restarts).

Possibly related to this issue: https://fuzearena.com/forum/topic/1598/actual-code-size-in-editor-is-affecting-available-memory-program-has-to-start-with-until-fuze-restart

Thanks for the report! I'm looking into the memory issues.