• 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • 🏆 Hive's 6th HD Modeling Contest: Mechanical is now open! Design and model a mechanical creature, mechanized animal, a futuristic robotic being, or anything else your imagination can tinker with! 📅 Submissions close on June 30, 2024. Don't miss this opportunity to let your creativity shine! Enter now and show us your mechanical masterpiece!🔗 Click here to enter!

Timer Fail?

Status
Not open for further replies.
This was posted in my bug report thread, and I wanted to verify it before adding it to the table:

[Custom]: If you have a periodic event (ie every X seconds of gametime), it will default to every 0.0625 seconds if it is a smaller interval than 0.0625 seconds.

Haven't tested with timers yet, map attached with an example.

EDIT: Just tested with timers. It fails there too.

EDIT2: It also fails for waits too.

So can anyone confirm this? It seems like a serious drawback if it is indeed true.
 
Level 11
Joined
Aug 1, 2009
Messages
963
See the attached file in the bug report thread.

It uses 3 different methods (infinite loop + waits, periodic event, and timers) to increase integers by one every 0.01 seconds, then a trigger to read off what they are every second. Instead of being 100, 200, 300 etc as you would expect, it goes 16, 32, 48. Very annoying.
 
Status
Not open for further replies.
Top