autosave e 3d-data

[cacciatorino]

modeling planted me during a "face shift" and there was no way out of it with sdkill -8, I had to use sdkill -9 and then lose the job unsaved until that moment.

recovering the autosave file, and then going to save the "3d changes", he simply solved all the assembly by adding the suffix "-1" to the file name, so he duplicated all the files.

But there's no way to force the overwriting of the parts without this file duplication? In the rescue there's the options command from which I can force the name to the file, but do I have to do it on all files one by one? this assembly will have hundreds of components....

 

[MFT]

modeling planted me during a "face shift" and there was no way out of it with sdkill -8, I had to use sdkill -9 and then lose the job unsaved until that moment.

recovering the autosave file, and then going to save the "3d changes", he simply solved all the assembly by adding the suffix "-1" to the file name, so he duplicated all the files.

But there's no way to force the overwriting of the parts without this file duplication? In the rescue there's the options command from which I can force the name to the file, but do I have to do it on all files one by one? this assembly will have hundreds of components....

I'm sorry I can't help you self-saving pkg so I have no idea you have to wait and president

 

[reb_bl]

have you tried with the versions?

if you don't work the -8 test with the pause key, many times it works best

 

[cacciatorino]

have you tried with the versions?

if you don't work the -8 test with the pause key, many times it works best

for the sdkill told me the afternoon assistance that with the new releases you do so.

I don't know what we're talking about, but maybe I'll go straight to the pdm so we'll get over this once and for all.

 

[reb_bl]

with the versions you can have to video the 'old' and the new one, then if you want to replace it you do it otherwise you keep the old one. I think this might come in handy with the pdm in case of crash.
sdkill definitely works (with 32 bits) but sometimes it happens that it goes into loop and you can unlock even with the break

 

[Er Presidente]

modeling planted me during a "face shift" and there was no way out of it with sdkill -8, I had to use sdkill -9 and then lose the job unsaved until that moment.

recovering the autosave file, and then going to save the "3d changes", he simply solved all the assembly by adding the suffix "-1" to the file name, so he duplicated all the files.

But there's no way to force the overwriting of the parts without this file duplication? In the rescue there's the options command from which I can force the name to the file, but do I have to do it on all files one by one? this assembly will have hundreds of components....

from the passenger car, then untied by everything.
But when you framed osd, you didn't have to build everything ex novo!

load the car, save everything with the "less one" somewhere, load the axieme as it was before the patatrack. loads "the monster originated from the car," what happens?

 

[Er Presidente]

with the versions you can have to video the 'old' and the new one, then if you want to replace it you do it otherwise you keep the old one. I think this might come in handy with the pdm in case of crash.
sdkill definitely works (with 32 bits) but sometimes it happens that it goes into loop and you can unlock even with the break

Here, so you should only be able to select the parts that had been modified between the last rescue and that of the car.

eye to the imported parts in step, they are often messed up and also simple operations create loops.
if the part that planted you osd is an import, separates all the faces (just lay a face) and regroups the solid, if there are small cases (faces with the wrong direction, osd warns you and also manages to solve, then go up the part.
a similar thing also happens by exporting in step and reimporting, during export should either arrange or warn you of messed up faces.

 

[cacciatorino]

from the passenger car, then untied by everything.
But when you framed osd, you didn't have to build everything ex novo!

load the car, save everything with the "less one" somewhere, load the axieme as it was before the patatrack. loads "the monster originated from the car," what happens?

You see, so he would have shared the instances already present instead of charging them from the car hire... .

experience for the future, however this 3d-date requires an excessive effort of intellectual energies, so as to distract me strongly from the project commitment. ...

very best to use modelmanager, so he thinks about it and I can devote myself to designing, modeling, ironing, copying (a level), sharing, straightening, aligning-double, etc... :biggrin:

 

[Er Presidente]

You see, so he would have shared the instances already present instead of charging them from the car hire... .

experience for the future, however this 3d-date requires an excessive effort of intellectual energies, so as to distract me strongly from the project commitment. ...

very best to use modelmanager, so he thinks about it and I can devote myself to designing, modeling, ironing, copying (a level), sharing, straightening, aligning-double, etc... :biggrin:

I was natural, you know, another mold. .
:smile:

 

[cacciatorino]

I was natural, you know, another mold. .
:smile:

ehhh, you with painted sheet metal dashboard and disc phones! :biggrin: