opened
duncanspumpkin
username_0
Calculation was incorrectly adding the offset to the first tile instead of removeing the offset from the current tile. This meant that it would set the waypoint at the wrong location
Fix waypoint setting function
issue
created
AaronVanGeffen
username_1
How would we best go about testing this?

Perhaps we can share a CI build for testing with the users who reported the issue?
comment
created
duncanspumpkin
username_0
its immediately obvious when you try set a waypoint on curved track the waypoint changes position depending on where you clicked on the track. What is meant to happen is the waypoint is always at the first tile of the curve.
comment
created
senner007
username_2
@username_1 
Can it not be set to automatically create a windows executable for each pr?
comment
created
AaronVanGeffen
username_1
@username_2 It already does. You can find the CI artefacts in the Checks tab for this PR, for example. Unfortunately, this isn't very discoverable for most users.
comment
created
senner007
username_2
@username_1 
Yes I see
comment
created
senner007
username_2
This does not fix #798
comment
created
AaronVanGeffen
username_1
@username_2 The bug is in setting the waypoints. Did you remove and set the waypoints again? Otherwise, the bad waypoint will persist.
comment
created
senner007
username_2
Yes I did that. Could this be an original bug?
comment
created
duncanspumpkin
username_0
There's two issues with waypoints one is that people feel they are ignored the other was that setting them on multi tile tracks wasn't working. This corrects the second issue
comment