USER FORUM
(you are viewing a thread; or go back to list of threads)
constrain symmetric causing "constraints are incompatible" (by wolfv)
The message in the Property Browser says:
the following constraints are incompatible
same-orientation
pt-on-line
The error is reproduced in the attached box_on_floor-asm_error.slvs
I think the error has something to do with the "constrain symmetric" in box.slvs
Constraining the other and of the box in the same way works fine in box_on_floor-asm.slvs
the following constraints are incompatible
same-orientation
pt-on-line
The error is reproduced in the attached box_on_floor-asm_error.slvs
I think the error has something to do with the "constrain symmetric" in box.slvs
Constraining the other and of the box in the same way works fine in box_on_floor-asm.slvs
original post but with more clarity (by wolfv)
The error message in the Property Browser says:
the following constraints are incompatible
- same-orientation
- pt-on-line
I was expecting the assembly to constrain without error.
The error is reproduced in the attached box_on_floor-asm_error.slvs
I think the error has something to do with the "constrain symmetric" in box.slvs
Constraining the other end of the box in the same way works fine in box_on_floor-asm.slvs
the following constraints are incompatible
- same-orientation
- pt-on-line
I was expecting the assembly to constrain without error.
The error is reproduced in the attached box_on_floor-asm_error.slvs
I think the error has something to do with the "constrain symmetric" in box.slvs
Constraining the other end of the box in the same way works fine in box_on_floor-asm.slvs
(no subject) (by Tom)
What version are you using? I think box_on_floor-asm_error.slvs works for me, draggable along the line.
Is it a bug? (by wolfv)
Is this a bug or am I not understanding something?
(no subject) (by wolfv)
I am using solvespace version 3.1
(no subject) (by Tom)
I was using 3.0, so maybe it's a new bug?
(no subject) (by wolfv)
Thanks Tom.
I reported the bug on https://github.com/solvespace/solvespace/issues/1466
I reported the bug on https://github.com/solvespace/solvespace/issues/1466
(no subject) (by ruevs)
The problem is that the objects are "too large". See my longer explanation here:
https://github.com/solvespace/...s/1466#issuecomment-2173545087
The difference between 3.0 and master is that the solver uses Eigen for the numerical solutions. It is possible that this change made the problems with "large" objects worse, but they certainly existed before.
https://github.com/solvespace/...s/1466#issuecomment-2173545087
The difference between 3.0 and master is that the solver uses Eigen for the numerical solutions. It is possible that this change made the problems with "large" objects worse, but they certainly existed before.
Post a reply to this comment: