What is the size of *.att file that you are exporting? Navisworks has had problems when reading large att files.
You can create a folder with the same name in the same directory where rvm resides.
e.g. if rvm name is mynavisfile.rvm then create a folder named mynavisfile
and then export all pipe / equi / stru using pml macro.
[COLOR=#333333]Hello everyone, unfortunately I can not fully export all the attributes of my components in PDMS.I followed these steps:[/COLOR]
[COLOR=#333333]1) I create the export of my project in ". Rvm"[/COLOR]
[COLOR=#333333]2) Then I am aware of having to extract a file. "Txt" or in ". Att" so that Naviswork can read the necessary information.[/COLOR]
[COLOR=#333333]Then I will have to place this file within my directory where my file is present rvm appointing him the same way.[/COLOR]
[COLOR=#333333]Reflected the following problems though.[/COLOR]
[COLOR=#333333]2.a) If I run the export of the project with the command "Utilites-> DB Listing" I do not get all the necessary information, such as all the UDA are not recognized.[/COLOR]
[COLOR=#333333]2.b) If I run the export of the project with the command "Utilites-> Export-> Dump Attribute" is that you export the file. "Att" or. "Txt" in Naviswork do not see any information.[/COLOR]
[COLOR=#333333]In setting Naviswork in the "Global Option" I've selection all options except "Convert Origins" and "Convert Zero-Thickness Solids".[/COLOR]
[COLOR=#333333]Use Naviswork 2010, if this information can be considered relevant.[/COLOR]
U may try to convert .att or .txt(attrib file to utf8) also export .rvm to utf8..
If U can u may attachyour .att+ .rvm with few elements and we will see what U got.
In global options be sure you check the box that says search all attribute files, also make sure the attribute file and the rvm file are named the same.
[QUOTE=Mr P.;78553][FONT=arial black][/FONT]Hello everyone, unfortunately I can not fully export all the attributes of my components in PDMS.I followed these steps:
1) I create the export of my project in ". Rvm"
2) Then I am aware of having to extract a file. "Txt" or in ". Att" so that Naviswork can read the necessary information.
Then I will have to place this file within my directory where my file is present rvm appointing him the same way.
Reflected the following problems though.
2.a) If I run the export of the project with the command "Utilites-> DB Listing" I do not get all the necessary information, such as all the UDA are not recognized.
2.b) If I run the export of the project with the command "Utilites-> Export-> Dump Attribute" is that you export the file. "Att" or. "Txt" in Naviswork do not see any information.
In setting Naviswork in the "Global Option" I've selection all options except "Convert Origins" and "Convert Zero-Thickness Solids".
Use Naviswork 2010, if this information can be considered relevant.
I have already verified that both the name of the file that the directory of my file attributes coincides with that of my Rvm.
The size of my attribute file format. "Txt" is 36 Mb.
Unfortunately, using the "Dump Attribute" I still can not get the desired result.
I do not understand why with the Listing Db I get a file that can not connect to the file via Rvm Naviswork (even without the completeness total attributes) while using the "Dump Attribute" I can not get the same result.
[COLOR=#333333]I do not understand why with the Listing Db I get a file that can not connect to the file via Rvm Naviswork (even without the completeness total attributes) while using the "Dump Attribute" I can not get the same result.
[/COLOR]
RVM-file with graphical representation of 3D ATT-file where attributes of graphics
DBlisting-.txt macross which used by pdms to import data
This concept I got that.
Maybe I expressed myself badly, the thing that I do not understand is this: "Export to a file called myreview.rvm in the same folder and put a file called myreview.txt.
Because if the file myreview.txt the son with the "Dblisting" naviswork reads the attribute and if the son with "Dump Attribute" Naviswork no recognizes attribute?
[QUOTE=Mr P.;78634]This concept I got that.
Maybe I expressed myself badly, the thing that I do not understand is this: "Export to a file called myreview.rvm in the same folder and put a file called myreview.txt.
Because if the file myreview.txt the son with the "Dblisting" naviswork reads the attribute and if the son with "Dump Attribute" Naviswork no recognizes attribute?
I've never had luck giving it the .txt extension, try .att as the extension.
[QUOTE=Mr P.;78634]This concept I got that.
Maybe I expressed myself badly, the thing that I do not understand is this: "Export to a file called myreview.rvm in the same folder and put a file called myreview.txt.
Because if the file myreview.txt the son with the "Dblisting" naviswork reads the attribute and if the son with "Dump Attribute" Naviswork no recognizes attribute?
OK. It might be then worth to see the way these files are exporting information[Dump Vs DBListing]. Though they may look similar but may not be the same and then Navis might be opening it but then it is failing to read the format.
If you open .rvm through Navis manually then it shows conversion progress and shows if it opens att file. Does Navis at least open this file [I think it does but doesn't read]?
Not to be misunderstood I am not referring to the properties in the section "Selection Tree" but I refer to the property in the form Propriets that is opened using the command "View-> Control Bar->Proprietes" of Naviswork
