[r197] Timer (Timescale) Bug

Problem Description

The Timer is not affected by timescale.

According to the manual: "The rate of On timer triggering is affected by the time scale."

So I thought this may be a bug because it is not.

Attach a Capx

Done

Description of Capx

At displays how long the timer took to trigger.

The first value is with default timescale (1).

The second value displays is with timescale 2 (Double Speed)

Observed Result

The second value is ca. 1 second

Expected Result

The second value should be ca. 0.5 seconds

Affected Browsers

• Chrome: YES
• FireFox: YES
• Internet Explorer: YES

Operating System and Service Pack

Windows 10 TP 64-Bit

Construct 2 Version ID

197

The timer is affected by timescale as is the time expression. Try printing out wallclocktime.

The 'time' expression is affected by the time scale too! So in this case it is working correctly - when you set the time scale to 2 then the 'time' expression increases twice as fast as well. Like ramones says use the wallclocktime expression for a non-timescaled time.