Dancan
Guest
someone knows if cocreated native files can be imported directly into pro|e wf2.0 , recreating a stunt model tree of the features ,modifcare feature ..insomma manipulate the model as if it was created to pro|e .
I think in cocreate the features don't even exist when you're still in cocreate. . . .someone knows if cocreated native files can be imported directly into pro|e wf2.0 , recreating a stunt model tree of the features ,modifcare feature ..insomma manipulate the model as if it was created to pro|e .
That's right. .I think in cocreate the features don't even exist when you're still in cocreate. . . .
But you should use the plug-in with the converter, right?you can do it exporting from modeling in granite format (*.g) so pro-e releases the features. you can do one part at a time you can't export groups
: Jigggrin: : piggrin:I think in cocreate the features don't even exist when you're still in cocreate. . . .
but now modeling turns on granite? historically used acis, didn't he? Or do I remember badly?you can do it exporting from modeling in granite format (*.g) so pro-e releases the features. you can do one part at a time you can't export groups
ambetre, but dxf better.and now with granite it turns seriously
By the way, a question and probably the answer is yes: in me10 is it possible to import dwg and dxf formats?
If you in a couple of weeks I will need to save in me 10 a dozen pro/e tables.
If I carry out in one of these formats, who would do me courtesy?
Dear President, can I count on you?ambetre, but dxf better.
no since 16.50 there is direct lexport. the plugin you only serene if you go from pro-everso modeling (but then so much worth the step that does not change droop)But you should use the plug-in with the converter, right?
no continues to turn on its owner core. export to granite is an interface. centuries ago it turned on acisbut now modeling turns on granite? historically used acis, didn't he? Or do I remember badly?
..ehm ...if it's like with pro-and then you'll want to say it's really planting....:biggrin:and now with granite it turns seriously
By the way, a question and probably the answer is yes: in me10 is it possible to import dwg and dxf formats?
If you in a couple of weeks I will need to save in me 10 a dozen pro/e tables.
If I carry out in one of these formats, who would do me courtesy?
export from modeling in granite format (*.g), you must have the 16.50 though.I'm sorry, but I don't understand.
-What is the best way to transfer cocreate native models, x be able to put me in a position to work as best as possible with pro|e (wf2.0)? ?
Thanks
What would be the advantages of exporting in the format you say (*.g) rather than in iges or step ? ?export from modeling in granite format (*.g), you must have the 16.50 though.
you can changeWhat would be the advantages of exporting in the format you say (*.g) rather than in iges or step ? ?
You could ask someone in the forum to post a file in granite format and then upload it with your pro/e, so you realize yourself.What would be the advantages of exporting in the format you say (*.g) rather than in iges or step ? ?
That's what you do. exported to granite 3 (for wf2 and sucessive)You could ask someone in the forum to post a file in granite format and then upload it with your pro/e, so you realize yourself.
Bye.
with wf4 tells me that the files were created with a more recent version of pro/e, so they are empty.That's what you do. exported to granite 3 (for wf2 and sucessive)
I said that it only works for the parts but instead I found that it works with the assemblies. simply export to granite.zip :smile:
Try and make me know.
Bye.