SolveSpace Logo SOLVESPACE -- parametric 2d/3d CAD
Examples
Tutorials
Features
Download
Reference
Technology
Library
Forum
Contact
USER FORUM

(you are viewing a thread; or go back to list of threads)

Linked models show all #REF (by Steven Anderson)
First of all thank you for your hard work. This product is like 80% of being the best modeling software available hands down.


It appears this may be by design (rather unfortunate ):

I have 3 problems:

1) simple one would be nice to be able to import an image onto a plane (large high res image for tracing parts from an image

2) the import /export features are very outdated

3) This problem and this is the killer

When I create like 10 objects in solvespace (separately) and try and to make a 3d model from the components with the link feature all the objects import as #REF.

I purposefully set one of the lines (the top line of each component of the model ) as an adjustable length and used length ratios, mid points, angles and vertical horizontal constraints. Purposefully leaving the degrees of freedom in each part so that when assembled I cold make all these parts adjustable relative to one master parts dimensions.

Unfortunately the parts all import as #REF which breaks this. The only setting that I see totally shuts off the system for keeping the dimensions proper.

I have attached the model as an example.


This means my model can't be dynamically adjusted unless I make the complex model all in one piece.

Then their is the import and export limitations (very old formats of DXF and no support of SolidWorks or AutocCad formats that are newer) To simplify this process for me I could import large pieces from elsewhere and just make adjustments but this is not really possible and I cant get the model back out into SolidWorks (which I also use) but only own a very very old copy of.
Sun Nov 24 2019, 11:10:42, download attachment exampleModelofIssues.slvs
(no subject) (by Andrew)
After you link an object, you can use it to constrain subsequent groups. One thing with Solvespace, if you change a dimension in a linked object, you have to re-open and save object that import it to propagate the changes. Where useful you could make a construction drawing as a skeleton for sizing parts in other drawings. Hope this helps.

PS, when uploading a multi-file project, you need to zip up all relevant files and upload a the zip, otherwise necessary files are missing.
Sun Nov 24 2019, 19:19:22
"Sketch | Image" (by ruevs)
is want you want for your first point ;-)
Thu Dec 5 2019, 08:20:00
(no subject) (by Vicky)
I stumbled upon same issue. Suppose i have made a cube with height, width and depth dimension in cube.slvs file. Now if i create newFile.slvs and link cube.slvs inside it, any changes made in cube.slvs is not reflected in newFile.slvs. Moreover, all constraints made in cube.slvs are not shown in newFile.slvs

This would really help with Assembly point of view. Any workaround for this? Like on generate all, it delinks the file and links the file again?
Mon May 30 2022, 14:32:41
(no subject) (by Vicky)
In features list, under
"Parametric and associative assembly"
It's written
"changes in parts propagate automatically into assembly"

So technically this should work right?
Mon May 30 2022, 21:18:55
(no subject) (by Vicky)
OK, so I have narrowed down the problem. If you run two instances of solvespace and edit part of an assembly, it does not reflect changes made at the part level. For example, cube.slvs is part of assembly newFile.slvs, if we open both parts in different instances of solvespace and try to make changes in cube.slvs, even after regenerate all, it does not reflect changes in newFile.slvs. It runs fine it both files are open in a single instance turn by turn. So I guess I can make changes to part and return to assembly again.
Tue May 31 2022, 00:28:37
(no subject) (by Paul)
When you link a part, that part is treated as completely static in the assembly other than its location and orientation. The remaining degrees of freedom in the original file can not be changed withing the assembly. There is an option in the text window to scale/resize the linked part but that's it.

For extrusions like 80/20 you can link a 2D sketch and then extrude within the assembly sketch. This can be done multiple times using the same sketch but have each extrusion a different length.
Tue May 31 2022, 10:06:37
(no subject) (by Vicky)
@Paul Thanks for the input. I'll try to implement the sketch based suggestion. Also I am trying to read the overall solvespace library and will possibly try to contribute in the coding part. Do we have any documentation related to the coding style to follow or how the group and entities are co related, etc.
Wed Jun 1 2022, 12:36:48
(no subject) (by Paul)
@Vicky,

For contributors:
https://github.com/solvespace/solvespace/blob/master/CONTRIBUTING.md

For documentation there is also:
https://github.com/solvespace/solvespace/blob/master/exposed/DOC.txt

And some other less formal notes here:
https://github.com/solvespace/solvespace/tree/master/developer_docs

You can also ask questions on github under an issue or feature you'd like to work on. Also search the existing issues, both open an closed. Some of them have discussions around different ideas and areas of code.
Wed Jun 1 2022, 14:12:41
(no subject) (by ruevs)
Vicky, once SolveSpace opens a file it does not access or monitor the original file one the disk for changes.

Thus when you have two files open in two instances once you modify and save the "first" file in one instance you will have to re-open the "second" file in the other instance that links the "fist" file in.
Thu Jun 2 2022, 04:49:16
(no subject) (by Vicky)
@ruevs I get how it works now. May be we can track the changes in the link file and reload it ? Any downside of it?
Mon Jun 6 2022, 22:06:53
(no subject) (by Andrew)
Tracking the linked file only works for changes to the linked file. However if that file also links to a file that changes it needs to be opened and saved.. I.e. a changed to the lowest level file requires that the intermediate level files are also opened and saved, followed by opening, and saving top level files. This makes monitoring for changes, and dealing with them more complicated than just reloading a file.
Tue Jun 7 2022, 05:37:58
Post a reply to this comment:
Your Name:
Your Email:
Subject:
(no HTML tags; use plain text, and hit Enter for a line break)
Attached file (if you want, 5 MB max):
© 2008-2021 SolveSpace contributors. Most recent update Apr 18 2021.