USER FORUM
(you are viewing a thread; or go back to list of threads)
to modify the import file (by normandajc)
it is possible in the software to import a file xxxx.slv to obtain a solid model as union, difference or assemble
If you must modify the choice of the import file, you must use a text editor.
Can you expect a box to modify
import geometry from file
'/..../..../xxxx.slv' [modify] <----------
scaled by 1.000 [change]
For example if you create an assembly with files in the same directories.
If you made a copy of this directory on another computer. The assembly do not know the import directories of files. you must use a text editor to change
If you must modify the choice of the import file, you must use a text editor.
Can you expect a box to modify
import geometry from file
'/..../..../xxxx.slv' [modify] <----------
scaled by 1.000 [change]
For example if you create an assembly with files in the same directories.
If you made a copy of this directory on another computer. The assembly do not know the import directories of files. you must use a text editor to change
(no subject) (by whitequark)
In my latest nightly (https://github.com/whitequark/...eleases/tag/nightly.2016-01-11), if, during loading, an imported file is missing, you will be prompted to locate the file. Then, it will be loaded.
(no subject) (by normandajc)
My antivirus has deleted your solvespace.exe file. I managed to test.
I propose rather that the imported file is in the same directory as the assembly file.
With a text editor, I edit the following lines
Group.impFile=E:\Pierre_Documents\SolvespaceRun\example\axle.slvs
Group.impFileRel=E:\Pierre_Documents\SolvespaceRun\example\axle.slvs
AddGroup
I change these lines
Group.impFile=axle.slvs
Group.impFileRel=axle.slvs
AddGroup
and so I can transfer the directory on another computer without not change.
files example example.zip
I propose rather that the imported file is in the same directory as the assembly file.
With a text editor, I edit the following lines
Group.impFile=E:\Pierre_Documents\SolvespaceRun\example\axle.slvs
Group.impFileRel=E:\Pierre_Documents\SolvespaceRun\example\axle.slvs
AddGroup
I change these lines
Group.impFile=axle.slvs
Group.impFileRel=axle.slvs
AddGroup
and so I can transfer the directory on another computer without not change.
files example example.zip
(no subject) (by whitequark)
That is certainly a false positive--nightly builds of SolveSpace, regardless of a platform, are performed on a machine that is wiped and replaced with a fresh installation before every build. More often than not, the utility provided by antivirus software is negative.
Group.impFileRel should have had the value axle.slvs, i.e. the relative path, in the first place. I think there is a bug in SolveSpace 2.0 which caused it to output Group.impFileRel incorrectly. You will find that if you re-save the files using the executable I provided you with, you do not need to re-locate the imported files if their path relative to the importing file does not change, i.e. if you just move the entire folder to another computer.
Group.impFileRel should have had the value axle.slvs, i.e. the relative path, in the first place. I think there is a bug in SolveSpace 2.0 which caused it to output Group.impFileRel incorrectly. You will find that if you re-save the files using the executable I provided you with, you do not need to re-locate the imported files if their path relative to the importing file does not change, i.e. if you just move the entire folder to another computer.
(no subject) (by normandajc)
I tested with a new assembly using solvespace 2.1.
This works perfectly for both solvespace 2.1 installed on windows or linux.
If the assembly was created with solvespace 2.0 and I use solvespace 2.1, I get an error message.
I now use that solvespace 2.1.
Thank you
This works perfectly for both solvespace 2.1 installed on windows or linux.
If the assembly was created with solvespace 2.0 and I use solvespace 2.1, I get an error message.
I now use that solvespace 2.1.
Thank you
(no subject) (by whitequark)
You should update to a later build, i.e. https://github.com/whitequark/...eleases/tag/nightly.2016-01-13, since the one I linked earlier in this thread had a bug impacting certain extrusions.
Post a reply to this comment: