Link to .capx file (required!):
Steps to reproduce:
1. Have two different variables.
2. One one of them, add 1 "Every 0.01"
3. On the other variable, add 1 "Every 0.1"
"Every 0.1" and "Every 0.01" give different time results when using them. It appears that "Every 0.01" will count slower than "Every 0.1".
When adding 0.01, the 3RD digit holds the Seconds, whilst adding 0.1, the 2ND digit is the seconds
Also, whilst setting up this bug, I decided to add a second timer method that also appears to be completely out of sync. The second timer method is adding dt to a variable ("dt3"), and when "dt3" is >= 0.1 , it will add 1 to the miliseconds and reset "dt3" back to 0.
This should logically add time up in the same way as the "Every" event, but this seems to not stay in sync with the Every events.
There is also "dt4" checking if it reaches >=0.01
I found this whilst trying to make a visual timer using sprites, I thought it was to do with the ordering of events, but found that I couldn't have accurate milliseconds if I add 1 millisecond (0.01) and can only add 10 milliseconds (0.1) to avoid being out of sync.
"Every 0.01" should be keeping synced with time.
Operating system & service pack:
Windows 7 Home 64-bit
Construct 2 version: