Why does tween property not always tween to exact number?

Post reply

❤Follow Topic(4)

0 favourites

5 posts

From the Asset Store

Add Number - Mobile support

$9 USD

Add Number - Select match number to total required numbers

clarkgame

- Radiowaves
- - Joined 23 Mar, 2014
  - 28 topics • 90 posts
- 1
- 7 Dec, 2025
- Quote
These events should tween the car object to 0 or 45 degrees, but it always ends up on 1, 3, 43 etc degrees. There is nothing stopping the tween midway.

I have noticed similar inaccuracies before in other projects where I eventually switched to sine behaviour because it was more accurate.
Tagged:

behaviours
bug
events
inaccuracy
tween
- R0J0hound
- - Joined 15 Jun, 2009
  - 91 topics • 7,692 posts
- 1
- 8 Dec, 2025
- Quote
I can't reproduce that. Tween always stops at an exact value in my tests.
- dop2000
- - Joined 26 May, 2016
  - 148 topics • 13,737 posts
- 2
- 8 Dec, 2025
- Quote
It's probably conflicting with the Car behavior - both are trying to control the angle.
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- Radiowaves
- - Joined 23 Mar, 2014
  - 28 topics • 90 posts
- 1
- 8 Dec, 2025
- Quote
It's probably conflicting with the Car behavior - both are trying to control the angle.

Might be. Problem is that at that moment, car is not turning. But I assume slide etc is still affecting it. Is there any way to resolve this or do I have to write my own car behaviour?
- dop2000
- - Joined 26 May, 2016
  - 148 topics • 13,737 posts
- 1
- 8 Dec, 2025
- Quote
You can try tweening a value, and setting the angle directly with this action:
Car Tween "turnadjust" is running Car Set angle to self.Tween.value("turnadjust")