E3D: Export rvm and txt attribute file to Navisworks

thanks flip but yeah this works in PDMS but E3D uses UTF-8 (or some type of encoding) and Navisworks can't read it
I've tried stripping the file down and to different encoding but nothing seems to work

you can put in your evars SET CADC_LANG_NEW=ISO. This will make the output to be in pure ASCII format.  Try that.  You can also use the transc program to convert them but it is an extra step.

is this for PDMS and/or E3D? coz i can't find this in the E3D evars file

For either.  E3D: The out of box evars.init is located C:\Program Files (x86)\AVEVA\Plant\E3D1.1.0. You need to put it in the evars you use for your project. PDMS: Otherwise it is in the evars.bat located C:\AVEVA\Plant\%PDMSVERSION%\

Hi mate,

I placed it in my evars file and it still doesn't work :(

Is the att file still UTF-8?

we had the same probs with the Att file with our automated navis create tool. I've wrote a short powershell tool to convert the UTF-8 file to utF-8-w/o bom.

convert.ps1 File


param(
[string]$i,
[string]$attfolder
)

   cd $attfolder
   $file = get-content $i
   $encoding = New-Object System.Text.UTF8Encoding($False)
   [System.IO.File]::WriteAllLines("$attfolder" + $i, $file, $encoding)

call out of pdms:

SYSCOM 'powershell.exe /C "C:\FOLDER\convert.ps1" -i $!attFilestr -attfolder $!pdmsuser'

!pdmsuser: folder where you want to store the file
!attfilestr: path and filename to the att file.

but we are running the script on a windows Server.
after this like allways the simple basic NWD convert out from pdms with a syscom

 SYSCOM 'CMD /C "C:\Program Files\Autodesk\Navisworks Manage 2011\ROAMER.EXE" -NWD $!nwdfile $!rvmFile'

For what it is worth I am a brand new E3D user and we needed this export to Navisworks to function for us to use the product so I did a lot of digging. Here's what we did to make it work. It turns out that Navisworks doesn't know anything about E3D but it does know about PDMS so once the attribute text file is created if you go in there and change two things in the header it will work fine in Navisworks, at least it did for us.

First line change "AVEVA_Attributes_File" to "CADC_Attributes_File"
Third line change "Everything3D Data..." to "PDMS Data...."

Once I did this the PDMS tab showed up in the quick attributes definition and I was able to set the tool tip to the AVEVA attributes.

Hope this helps.

Brian

thanks guys i will let you know how i get on with your suggestions

Thank you heaps Brian :)
Just curious how do you work it out?
I didn't need to change the everything3D data part, only AVEVA to CADC

When I was looking at all the replies on here I noticed the tab that is added to Navis was PDMS and that got me thinking so I compared the header some posted here to what I was seeing and then just started experimenting.

Seems I spend most of my time doing that. Most of the time I just screw thing up, this time got lucky.