You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SolveSpace version: 3.0~5df53fc5
Operating system: Ubuntu 19.04 in VMWare
Expected behavior
When I drag points quickly or set constraints that move points a moderate distance, sometimes objects tunnel through their constraints to a different local solution (for example, if a point-line distance is specified, the point will flip to the opposite side of the line). My hope is that this occurrence is reduced in frequency.
Additional information
If the numerical solver reuses previous state and flows along a gradient to the new state, maybe smaller steps would help. Alternatively, if a point is moved a large distance, a line can be drawn between the two positions and then the solution incrementally iterated along this line. This creates a smooth path between the start and end position, preventing discontinuous jumps.
#76 is related and the preferred solution. Mine is just a bandaid.
The text was updated successfully, but these errors were encountered:
ad8e
changed the title
Objects flip to the opposite side constraints
Objects flip to the opposite side of constraints
Jun 12, 2019
System information
SolveSpace version: 3.0~5df53fc5
Operating system: Ubuntu 19.04 in VMWare
Expected behavior
When I drag points quickly or set constraints that move points a moderate distance, sometimes objects tunnel through their constraints to a different local solution (for example, if a point-line distance is specified, the point will flip to the opposite side of the line). My hope is that this occurrence is reduced in frequency.
Additional information
If the numerical solver reuses previous state and flows along a gradient to the new state, maybe smaller steps would help. Alternatively, if a point is moved a large distance, a line can be drawn between the two positions and then the solution incrementally iterated along this line. This creates a smooth path between the start and end position, preventing discontinuous jumps.
#76 is related and the preferred solution. Mine is just a bandaid.
The text was updated successfully, but these errors were encountered: