USER FORUM
(you are viewing a thread; or go back to list of threads)
3.1 Release, 3.2-RC or master? (by Tomasz)
Hi
There was no release for really long time, while there is lot of new commits.
Would you recommend to use old stable 3.1, maybe 3.2-RC tag, or latest master should be ok?
I would like to design a car suspension model for one wheel in various ways (multilink, MacPherson, double-wishbone) and generate an .csv data for axis alignment (position and rotation) for whole travel range with small step.
So I guess I would need to modify source code anyway to generate such output data. (or maybe it is possible to script something like this in a tool?)
So what version would you recommend to start?
Thanks,
Tomasz
There was no release for really long time, while there is lot of new commits.
Would you recommend to use old stable 3.1, maybe 3.2-RC tag, or latest master should be ok?
I would like to design a car suspension model for one wheel in various ways (multilink, MacPherson, double-wishbone) and generate an .csv data for axis alignment (position and rotation) for whole travel range with small step.
So I guess I would need to modify source code anyway to generate such output data. (or maybe it is possible to script something like this in a tool?)
So what version would you recommend to start?
Thanks,
Tomasz
(no subject) (by Tom)
Can you do it with "Step Dimension" and "Trace Point"? I guess you'd have to trace twice to get two points and then calculate angle yourself though.
(no subject) (by ruevs)
Master is very stable most of the time. So I always use the latest edge build.
(no subject) (by Paul)
I would recommend 3.2 RC. Almost all new functionality is present in the RC and there are no signs of issues.
There is currently a problem using master with assemblies. It may only be with files from previous versions, or it may only be with certain size sketches, or both. It's a tricky issue we're trying to work out and it involves what is or isn't written to files.
There is currently a problem using master with assemblies. It may only be with files from previous versions, or it may only be with certain size sketches, or both. It's a tricky issue we're trying to work out and it involves what is or isn't written to files.
(no subject) (by Tomasz)
In a meantime I prepared extension to Trace Point feature.
Now it supports multiple Points trace and/or Normals (traced as origin + quaternion).
Do you think it could be useful for more users and committed to main repo?
I think I could add also an configuration option to save Normal orientation as quaternion (this is already done) or set of N,U,V vectors.
My branch is here:
https://github.com/topyra/solvespace/tree/multi_trace
Code is not tested very well so far.
Now it supports multiple Points trace and/or Normals (traced as origin + quaternion).
Do you think it could be useful for more users and committed to main repo?
I think I could add also an configuration option to save Normal orientation as quaternion (this is already done) or set of N,U,V vectors.
My branch is here:
https://github.com/topyra/solvespace/tree/multi_trace
Code is not tested very well so far.
Post a reply to this comment: