You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
folle76
Guest
You should carefully check with the viewer references if the incriminated parts have dependencies with other parts outside the axieme. It happens to me with some part of the rescue. or clean dependencies or save them by name and then redefine everything in the final axieme.
DANI-3D
Guest
I always prefer rename in session, it is a much slower system, but much more versatile and safe.
greetings
greetings
tartufon80
Guest
Bye!
working with pdmlink (I don't know if you use it too), sometimes I happened the same mistake, and turns around I discovered that there was some connection left by a "load" performed earlier. It was enough to charge the updated axieme again to "push" that old bond, and everything is smooth yarn.
I agree with mad76: in these cases the only system to try to understand where the hippo is the reference viewer.
working with pdmlink (I don't know if you use it too), sometimes I happened the same mistake, and turns around I discovered that there was some connection left by a "load" performed earlier. It was enough to charge the updated axieme again to "push" that old bond, and everything is smooth yarn.
I agree with mad76: in these cases the only system to try to understand where the hippo is the reference viewer.
blubossa
Guest
Hi.
I'll let you know.
Thank you.
bb
I'll let you know.
Thank you.
bb
Beth
Guest
I am reading the discussion and would like to politely ask dani-3d a delucidation on rhino in sesion .
I've never understood the function of this operation well.
Can it be used to make copies instead of the copy save?
When I need components in other directories I usually go to take them and usually back up them in the work directory, do you think it's best practice?
I've never understood the function of this operation well.
Can it be used to make copies instead of the copy save?
When I need components in other directories I usually go to take them and usually back up them in the work directory, do you think it's best practice?
DANI-3D
Guest
ciao ciao
much better use the search.pro.
Of course, especially for big assemblies is very indicated, it is slower than a save copy, but you decide which details rename and which reuse.Can it be used to make copies instead of the copy save?
I always try to avoid this method, because by doing so you will have the same details in different folders, and you will never be sure to open the right piece, not to mention the changes, you must chase all the details and fix them.... I backup it in the work directory ...
much better use the search.pro.
Beth
Guest
are you right, but will you agree with me that you might need parts not present in the search pro in that case is short to use the backup?Hi.
Of course, especially for big assemblies is very indicated, it is slower than a save copy, but you decide which details rename and which reuse.
Please let me understand if I want to create a copy of pippo.asm that is called pippo2.asm! I can rename in session pippo.asm in pippo2.asm? but pippo.asm is maintained? I'm sorry if I'm twisted but I want to avoid harming and especially understanding all the experiments I've done after your quotation have always failed unfortunately and my startegia is very interested, thank you for patience.
I always try to avoid this method, because by doing so you will have the same details in different folders, and you will never be sure to open the right piece, not to mention the changes, you must chase all the details and fix them.
much better use the search.pro.
I have done a little bit of dick with the search pro when it comes to recalling, perhaps, the conflict between constraints, you suggest that you use it only for the parts where I have found it to be absolutely reliable?
DANI-3D
Guest
with the rename in session make a copy to all effects, so you will have a new set called pippo2.asm and unaltered mantini pippo.asm, not only, all references of the individual details are updated automatically towards the new set.
with the search.pro deserves to make us peace and organize it to the best, because it is basic for our work. all objects that can be recalled in multiple projects, whether particular or axiemic, must be stored in common folders inserted in the search.-pro, and avoid doubling of which you will surely lose control.
with the search.pro deserves to make us peace and organize it to the best, because it is basic for our work. all objects that can be recalled in multiple projects, whether particular or axiemic, must be stored in common folders inserted in the search.-pro, and avoid doubling of which you will surely lose control.
Beth
Guest
I understand dani-3d good advice as always.
Thank you very much
Thank you very much
MORENO100
Guest
Hello blubossa,Bye to all,
I am working with cero2 and I often get a mistake when doing the save copy, in practice if I want to reuse some parts it does not allow me..... I have attached an image to better clarify everything.....
How come? is it a bug?
Thank you.
bb
as mentioned by others, red ban icons appear next to those details that have features with ties defined in the axieme from which you are saving copy. in the hypothesis that you wanted to get a simple save copy of a set leaving all those ties reported in the starting aid, I suggest:
- make a "entry point" excluding all components
- save by name
- open the new set (I recommend to do it quickly: prizes "alt+f" and then "1")
- cancel the "entry point"
I hope I've been helpful.
Bye!
Beth
Guest
with the search.pro deserves to make us peace and organize it to the best, because it is basic for our work. all objects that can be recalled in multiple projects, whether particular or axiemic, must be stored in common folders inserted in the search.-pro, and avoid doubling of which you will surely lose control.
hi dani-3d back on your quote and I'll ask you a couple questions
We assume that we work on the axioms that use components recalled by search.pro, then one day I decide to make a change to these components and certainly all the children of these components will be updated.
but how can we control the updates on the various assemblies since the physically milling moficies etc. have not been made? am I firing wires?
hi dani-3d back on your quote and I'll ask you a couple questions
We assume that we work on the axioms that use components recalled by search.pro, then one day I decide to make a change to these components and certainly all the children of these components will be updated.
but how can we control the updates on the various assemblies since the physically milling moficies etc. have not been made? am I firing wires?
DANI-3D
Guest
Bye-bye
I honestly didn't understand what you want to get, before giving you information that could take you off the road, I would need further explanations, or an example.
I honestly didn't understand what you want to get, before giving you information that could take you off the road, I would need further explanations, or an example.
Beth
Guest
Of course I'm a mess.
then we put that I make a project that contains a set containing a plate recalled by the search path.
later and independently of this project I modify this plate by magnifying it because so it is decided. When I reopen the axieme/project mentioned at first I would like the updating of the seat relative to the plate not to be updated to the new form because it would compromise the old project.
What is the best thing to do?
then we put that I make a project that contains a set containing a plate recalled by the search path.
later and independently of this project I modify this plate by magnifying it because so it is decided. When I reopen the axieme/project mentioned at first I would like the updating of the seat relative to the plate not to be updated to the new form because it would compromise the old project.
What is the best thing to do?
DANI-3D
Guest
All clear. the best method is always the rename in session of the plate, so doing the old project will have the old version and the new together will have the modified plate.
p.
I've done nothing else in the last few weeks, renames in continuous session. I have to substantially review the project of a machine, keeping the old project unchanged.
p.
I've done nothing else in the last few weeks, renames in continuous session. I have to substantially review the project of a machine, keeping the old project unchanged.
Beth
Guest
OK I understand, I hope, listen, when you have to do the storage of backup projects for example on servers or on disk what you recommend to do? simply drag the folder to the support or make backup.
last thing the search path paths should be specified until the last subdirectory? do you not risk having an infinite file? forgives questions from neophyte
Thank you.
last thing the search path paths should be specified until the last subdirectory? do you not risk having an infinite file? forgives questions from neophyte
Thank you.
DANI-3D
Guest
What exactly do you mean by backup? Because the archive of the projects is good to have it at hand and less the move and better, or do you refer to the security copies? and here is a strategy to follow.... when you have to do the storage of backup projects for example on servers or on disk what you recommend to do? simply drag the folder to the support or make backup.
Yes, in the search path you have to specify each directory and subdirectory, the file length depends on how fragmented the common workbooks, note that increasing their pro-and number a little slows down.... should the search path be specified until the last subdirectory?
Beth
Guest
What exactly do you mean by backup? Because the archive of the projects is good to have it at hand and less the move and better, or do you refer to the security copies? and here is a strategy to follow.
We have a server, when we finish a contract, we pick up the directoy containing the project, we throw it in it, this sever automatically saves periodicals.
I don't understand what you mean by security copies.
DANI-3D
Guest
a real backup on external hard-disk to reuse in the unfortunate case that the computer burns. or, and this happens often, to recover a damaged file, or modified by mistake.I don't understand what you mean by security copies.
Beth
Guest
All right, sorry, and the procedure?