TransMagic Knowledge Base

3D Studio Max saves:
*.ase,*.fbx,*.3ds,ai,*.atr,*.blk,*.dae,*.df,*.dwf,*.bwg,*.dxf,*.flt,*.htr,*.igs,*.ive+osgb+osgt+osg,*.lay,*.lp,*.m3g,*.obj,*.sat,*.stl,*.vw and *.wrl.

The first step is to output a .tif image from TransMagic. This can be done from using "File->Save As" within the GUI, from TransMagic Batch or TM Command.

Next you will need conversion software, this method is different depending on your level of process integration/automation.

• Manual Conversion:There are many image editors that can work to do this conversion, and they all give you additional functionality to do many other image manipulation tasks like crop and re-size. Here is a list of free applications that have work very well for these types of conversions:
  1. Windows 7 version of Microsoft Paint
  2. Gimp image editor:http://www.gimp.org
  
  
• Automated Conversion:Most modern programming languages contain image conversion utilities, either built in or through third party libraries.
1. Java has conversion built right in, just a few lines of code and you are done. Here is a sample:
   public static void main(final String[] args) throws Exception{
   final BufferedImage tif = ImageIO.read(new File("V4Sample03.tif"));
   ImageIO.write(tif, "png", new File("V4Sample03.png"));
   }


2. Php, .Net, Python, Perl and others will require a third party image tool. Image Magick, no relation to TransMagic (we spell correctly :-), is a free toolkit to do these conversions that I have used, and it works very well. See their web site form more information http://www.imagemagick.org

TransMagic does not currently support "PMI Write" - it's view only.  However, we do support PMI to XML output.  Our XML output includes assembly hierarchy data AND PMI. 

TransMagic does support many SolidWork's file formats.  However, we do not currently support eDrawings.  The supported formats are *.sldprt and *.sldasm formats.

The WorkGroup Administrator is supposed to uninstall old versions automatically.  Sometimes it isn't able to do this and an error occurs.  In these cases, please first uninstall the old WorkGroup Administrator and then install the new version.

TransMagic does support exporting these file formats.  It writes these files into their kernel formats.  For SolidWorks, TransMagic writes our Parasolid.  For Inventor, TransMagic writes out ACIS.

Additionally, TransMagic PowerPacks, translator plug ins for SolidWorks and Inventor, combine the capabilities of TransMagic with SolidWorks and Inventor. In this case, TransMagic PowerPack has the added functionality of all SolidWork/Inventor supported formats in addition to its own.

TM Command is a programmatic interface to TransMagic that supports enterprise process integration.  This can include extending your PDM/PLM systems to support all of the multiple CAx 3D formats.  In addition, TM Command is currently being used to add "File --> Open" capabilities within third party software products like AshlarVellum, VX, Dimensional Control Systems and SolidWorks.

Currently, TransMagic is not Unicode\MBCS.  TransMagic has started the Unicode/MBCS process; however, we still need to migrate over a fair amount of code to get TransMagic Unicode to 100%. 

Currently, this function is unavailable.

TransMagic always translates files in their original orientation.  When you see the part upside down in th e receiving applicatoin, this is just an application specific view thing.  TransMagic displays using a "right-hand" coordinate system as do most engineering systems.  However, you will see many European developed applications use a "left-hand" coordinate system for display.

CATIA V4 ad V5 are significantly different.  Between CATIA V4 and V5 the geometric kernels were changed.  Thus, CATIA V5 can directly use the V4 models, but CATIA V4 must be converted into V5.

Because OBJ is a polygonal format, TransMagic can only convert it to other polygonal formats such as JT, STL, HSF etc.  The OBJ format does not actually contain any 3D geometric data which is required to convert to a geometric format like IGES, STEP, etc.

The "Semi-Auto Repair" is where TransMagic finds the areas in the model that need repairing (i.e. open edges) and then you perform the repair (like with MagicSurface).  Here is a link to a tutorial about Semi-Auto Repair on You Tube: http://www.youtube.com/watch?v=COQxyNgKwys

JT export and import works just like all the other files from within TransMagic and BATCH.

First, make sure that the file format is supported by TransMagic.

Sometimes, files are top-level assembly files that are missing their subordinate part files. To determine which part files are missing, in TransMagic, go to File->Settings, click the General Tab, and check the "Translation Log" option, click OK.

Then, re-read the file and TransMagic will display the translation log after the translation (or attempted translation).  Then scroll down in the log file and you'll notice several warnings, for example see below.  This portion of the log lists all the missing part files that TransMagic cannot find.  These part files need to be in the same directory as the assembly files in order for TransMagic to read the assemblies.  This was the case with all of the files you submitted.  They are all assembly files missing their part files.  You can copy\paste the missing files from the log and ask your supplier for these files.

TransMagic only works with and converts 3D file formats.  So, for dra or drw, TransMagic will not convert these into other formats.  TransMagic cannot convert from 2D to 3D file formats.

TransMagic will not directly read or write a DXF or DWG file.  However, AutoCAD and Inventor are both able to produce and read a 3D CAD format (ACIS - .sat) that can be used in place of DXF or DWG files.

To convert from a supported file to a DWG:

1. Save the file into a ACIS or SAT file format. This file format is produced and readable by AutodCAD or Inventor.

2. You can then import the file into AutoCAD or Inventor and save it as a DWG or DXF

Yes.  It's called "PMI" in TransMagic. 

First, the function needs to be turned on:

- Go to File -> Settings

- Click the "General Tab"

- Check the option "Enable PMI Translation"

Now, when you open a Catia V5 file, you should be able to see the annotations.

  There are two options in the IGES Write settings area that will instruct TransMagic to create the most “benign” IGES file that typically all applications can handle well. The user should try checking the options “Write All Surfaces As Spline Surfaces” and “Write All Curves As Spline Curves”. This should create an IGES file that plays well with any application.

UGS offers a command line executable called TxJT2co. It is not a standalone application; it is part of CAD Translator module which comes on top of Robcad or Tecnomatix.

  

  This application converts *.jt assembly or *.jt part to a RobCAD/Technomatix .co file. The translator contains flags that enable you to select the *.jt file for conversion, the destination location, and several optional flags to customize the output according to your needs.

STL’s are a bit weird too since our STL generation requires real geometry, you can’t load in an STL file and then re-save it as STL because we need geometry to base the tessellation on. So you can only save it to HSF, HMF or JT soon for 3D Viz formats.

 

For whatever reason the Inventor toolkit we use does not yet give us the ability to input names into Inventor. They are there in TransMagic and we do support them when possible – it’s just that the Inventor toolkit doesn’t. So the work-around for this would be to read the assembly into TransMagic, save as a STEP file and then import the STEP file into Inventor. The Inventor STEP reader supports names.

TransMagic does not convert *.stl to geometric formats. The reason is that *.stl files are comprised of triangular polygons vs. true geometry such as spheres, planes, torus, cones, free form surfaces (NURBs), etc. The conversion from true geometry to triangles is very easy (CAD to *.stl); however, the inverse, *.stl to true geometry is very difficult. In fact, no software actually does this automatically as there is simply not a straight conversion.

  There are some reverse engineering software's out there that will take a point cloud (which is essentially what an *.stl file is) and with significant user intervention, they are able to map NURBS surfaces to these points; however, in most cases the user has to define the boundary curves manually. This process is extremely tedious and difficult as there are many ways to introduce errors into the reverse engineering process.
  
  Further technical information:

  TransMagic could very easily take an STL file and generate a geometric file using a technique known as a Polygon Point Mesh Body (PPMBody). A PPMBody is the conversion of lightweight planar polygons (always found in STL and other visualization formats) to true geometric planar faces in a solid body.

  One of the primary drawbacks of a PPMBody conversion is one of file size explosion. For example, if the STL file had 400,000 polygons - which is typical or even small for some models (such as a medical model) - the resulting geometric solid model would have 400,000 planar (and triangular) faces. This could be done automatically with no user intervention. The problem is that the 400,000 polygon STL file that was maybe 3 MB could now be 100 MB in a geometric format. This is because instead of just a "bag of triangles" like an STL file, you now have solid topology (the glue that holds a solid model together). For every triangle in the STL file, which originally consisted of 4 pieces of information: 3 vertices and a normal, you'll now have:

  1 body

  - Under which is:

   - 1 Lump

   - Under which is:

   - 1 Shell

   - Under which is:

   - 1 Face

   - Under which is:

   - 1 surface

   - 1 loop

   - Under which is:

   - 3 edges

   - Under which is:

   - 3 coedges

   - 3 curves

   - 6 vertices

   - 6 geometric points


  No one can imagine how a file would grow from 4 pieces of information for each triangular face to 27 (and this leaves some information out!).


  Products to look at include

  http://www.rapidform.com/Contents/Product/Skin/ProductETC/category_id/53

  http://www.ugs.com/products/nx/imageware

There is an issue with Inventor that prevents it from reading both solids and lines in the same file.  The work around is to output two *.sat files: one with the wires and another with everything else.

You can do this in TransMagic, using the following procedure:

1.) Click on the backgroud in the 3D Display (this will unselect everything so you get the correct menu in Step 2)

2.) Right Click -> Filter Selection -> Window Selection Options -> Body: Wire Only

3.) Window select the entire part, only the wires should be highlighted in yellow.

4.) File -> Export -> Save the selected geometry as a wire.sat

5.) Right Click -> Filter Selection -> Window Selection Options -> Body: Solid Only(and/or Surface Only)

6.) Window select the entire part, only the surfaces/solids should be highlighted in yellow.

7.) File -> Export -> Save the selected geometry as a solid.say

8.) Read both of these individually back into TransMagic to verify that they contain the entities separately.

9.) Read one of the files and impor tthe second into Inventor.

You should now have everything you need in Inventor 10.

The Catia flat file is a compressed collection of files.  TransMagic does not currently support reading this file type.  Request the file in a *.model or *exp format and read that in.

TransMagic has a rule of thumb regarding RAM.  We call this the 10x4 rule: When translating a file (assembly) TransMagic will typically consume 10x the file size in RAM (either physical or swap).  SO in the case of a 100 MB file, this means that TransMagic would likely consume around 1.0 GB of RAM to read this file into TransMagic.  Once in TransMagic, meaning post-translation, RAM will fall to about 4x the file size.  So, 400 MB.  So the best thing you can do for TransMagic is have plenty of RAM when dealing with large files.  Also, in previous versions of TransMagic, the application could only utilize the standard Win32 limit of 2 GB RAM.  However, as of TransMagic R7 SP1, TransMagic can utilize the "3GB Switch" and use up to 3 GB of RAM 9or swap file).

TransMagic BATCH:

We recommend you look into the TransMagic Batch interface too, for extremely large files.  The advantage of the TransMagic Batch processor is that you do not visualize the part.  You simply select the input file(s), the output format, where to save the output file and click "Go."  TransMagic Batch processes the file until complete.  You could start one file or a collection of files before you leave the office and have the output files sitting in the output folder when you get back to the office the next day.  This unattended process also saves you time and frees up your system resources while you're working during the day.

Bellow is the complete list of all Unistall keys that TransMagic is looking for.  The oldest keys start at the b The uninstall keys that TransMagic R7 sp2 is looking for are under:

  HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstall

  Then if any of these sub-keys exist, then delete them:

  {ABFB2DE3-5DFF-417A-B5E2-40CFD30D2473}

  {7A5373D4-5BC5-4369-9E4C-09C2BBCB1081}

  {D90CA3EA-87C5-43FB-B6ED-79350544B456}

  {FAA46883-A8F8-4EA8-88C3-081444E2E63F}

  {1C190E4E-8C0B-4FE1-A4E9-09BBA802F8FF}

  {8FE5A80D-7B2C-4B14-9506-0F330B8AF806}

  {AE7C093A-A6D3-4756-83FE-24A66847B50C}

  {B522E507-70F5-4A87-92B0-E6F3B94D8E70}

  {AB9FA4E3-F929-4B19-B1F0-D68A0172ED52}

  {48951166-ECD0-49DE-96E2-A92CB7F21504}

  {C4DF8A91-4344-4F0D-B35B-9C9E48E130CD}

  {71D3DCC5-EFAD-47B4-855B-BD17239C0977}

  {1B3E4B45-1677-4207-B16C-171FA1EBCC3F}

  {6F9CCBAE-3D94-43CE-968C-355B1B8CB100}

  {A310CB75-1CB1-4BB0-B62B-23ECD66C6DD2}

  {296C8B00-F3A9-4974-8B80-E80B65B7378E}

  {837BB49F-A616-4453-959A-55130F14C4D7}

  {0075A2BE-CF23-4852-8A52-46163FD2EB7A}

  {D84D7E04-DCFF-48B5-839F-D25C5CB8289D}

  {AB9FA4E3-F929-4B19-B1F0-D68A0172ED52}

  {48951166-ECD0-49DE-96E2-A92CB7F21504}

  {C4DF8A91-4344-4F0D-B35B-9C9E48E130CD}

  {71D3DCC5-EFAD-47B4-855B-BD17239C0977}

  {8CB52EB4-658F-481D-9512-D91F0F4097C8}

  {95A66AAE-A1BE-40D1-A3EE-F800053D8D90}

  {50608A5C-641E-4D3F-8E6C-809B2A7C9BAC}

  {EC281D96-0A53-495F-821A-A4985C9B420B}

  {39E944B2-5F02-4B09-A1E2-593CD3AE85AC}

  {4EE3B6F4-0308-423E-8386-BF10C13BCE25}

  {B4EB599F-B52A-40B8-9C4F-DE73CED34583}

  {542B3749-20B7-4917-86FE-D96D9C0645B8}

  {D28B8EC8-6EF2-4AC7-9191-E7FC2F5F4E85}

  {966D3EB6-6B50-4C06-8DDA-8C9DB422053E}

  {DE3D3E3C-A9ED-424E-826E-8EE2F0B08A80}

  {31652E0A-477A-4C6D-9049-583D98E21397}

  {9129D9AC-8E06-465A-8BCF-6E19B6649B1F}

  {D1FF9794-1C26-48CF-8777-F9AF24D2B3B7}

  {8807E7C3-1857-4BF6-A6A0-EB33FA93F419}

  {2D6F057B-DCBA-4011-91F9-087EE9E81B23}

  {2d7d2a41-2e22-447a-a7cb-4ffb535d4055}

  {1a1189c4-7780-4198-a62c-26a71cccd5bb}

  {eeed91e4-c6d5-4925-beaa-0f9996fc4d7f}

  {4500b5af-22c2-4061-8ce5-480a7d595763}

  {68b95e59-0eef-44d5-b50e-7d93b4c992b2}

  {88933307-441f-45dd-a8c3-c35822d8ec33}ottom and the newest keys are at the top.  So R7SP0 is probably the second one.

Right click the TransMagic program icon.

Then, select "Run as Administrator."

TransMagic 1.1 -- Release Date Unknown

TransMagic 2.0 -- Release Date Unknown

TransMagic 2.2 -- Release Date Unknown

TransMagic 3.0 -- Release Date Unknown

TransMagic 3.1 -- Release Date Unknown

TransMagic STANDARD V4.0 or V4.1, TransMagic V4.2 -- Released 11/17/2003

TransMagic V4.3 -- Released 5/26/2004

TransMagic STANDARD V3, Batch View 05, TransMagic Plus OLD, TransMagic Batch Direct 2005 TransMagic Plus V4.2 -- Released 11/17/2003

TransMagic PLUS 2005 OLD, TransMagic Plus V4.3, TransMagic STANDARD V4.2, TransMagic 2005 SP 4 --Released 03/18/2005

TransMagic 2005 SP5 CATIA V5 V5 READ -- Released 09/12/2005

TransMagic SP5 BATCH (NEW) -- Released 09/12/2005

TransMagic 2005 SP5 CATIA V5 WRITE, SP3 AutoDesk Interface -- Released 9/12/2005

TransMagic SP5 STANDARD -- Release 09/12/2005

TransMagic 2006 SP0 BATCH, TransMagic 2006 SP0 CATIA V5 READ -- Released 03/06/2006

TransMagic 2006 SP0 CATIA V5 WRITE -- Released 3/06/2006

 TM 2006 SP0 STANDARD -- Released 3/6/2006

  TM 2006 SP1 STANDARD & PLUS -- Released 10/10/2006

  TM 2006 SP1 BATCH -- Released 10/10/2006

  TM R7 SP0 -- Released 4/27/2007

  TM R7 SP0 BATCH (Network Enabled) -- Released 4/27/2007

  TM R7 SP1 (New product offering; Win2k no longer supported) -- Released 11/12/2007

  TM R7 SP1 BATCH -- Released 11/12/2007

  TM R7 SP2 BATCH -- Released 6/12/2008

  TM R7 SP2 -- Released 6/12/2008

  R8 SP2 -- Released 07/22/2009

  R8 SP2 BATCH -- Released 07/22/2009

  R8 SP3 -- Released 12/18/2009

  R8 SP4 -- TBA

This issue only affects machines with certain security profiles or virtual machine settings.  The TransMagic License Key is stored in the public area of the registry (HKEY_LOCAL_MACHINE) and hard drive (C: Progam Files) and is not user specific so there is technically no reason for this to occur.  Theoretically, only one user needs to license TransMagic and 99% of the time, there are no issues with multiple user logins.  Each user who is prompted to register should follow the registration instructions so that they can activate TransMagic for their login.

TransMagic is currently offered in 32-bit and 64-bit native. 

You may not have all of the coponents or updated drivers installed to fully support TransMagic.  Please see the list of Required Components for comparison.  You can find this list on our Support/Downloads page at http://www.transmagic.com/support/install/downloads.  Also, if you have a 3D Connexion device, please check to see if you have the latest driver.

TransMagic will not read or write a DXF or DWG file.  However, AutoCAD and Inventor are both able to produce and read a #D CAD format (ACIS - .sat) that can be used in place of DXF or DWG files.

TransMagic does not currently support writing to the Pro/e* .prt* or .asm* formats natively.  We have plans to add the ability to write to the Pro/E neutral 3D modeling kernel format */neu in the future.  In the meant time, TransMagic can convert to several other 3D geometric formats supported by Pro/E such as STEP*.stp, ACIS*.sat and Parasolid *.x_t.

The MagicSURFACE feature is available in the evaluation version of TransMagic.  The icons are greyed out until something appropriate, like a face or an edge, is selected.  Tutorials for the MagicSURFACE feature can be found at www.transmagic.com on the Support/Video Tutorials page under the Semi-Auto Repair section.

If you haven't already done so, please create a user name and password at www.transmagic.com.  You will receive an email to validate your account - please follow those steps first.  Then, go to our Support/Downloads page where you will see a link to the "Legacy Downloads" page at http://www.transmagic.com/support/install/legacy-downloads.  Click the "TransMagic R8 SP1" link to download the installation file.  After installation, you will be prompted to register.  Please copy your Reference Code and paste it in the space provided on our Request License Key page at http://www,transmagic.com/support/install/license-request.  A license key will be emailed shortly thereafter.

Two questions will help debug this issue:

1.)  Which version of TransMagic is installed?

2.)  Is a 3DConnexion device attached to the system?

If a 3D Connexion device is attached to the system, then there was a known issue with TransMagic R8 SP0 and SP1 which caused this crash.  The solution in this case is to simply go to the 3D Connexion website and install the latest version of their drivers.

Thank you for your interest in TransMagic.  If you have not already done so, please check your inbox for an email with instructions to verify your login information.

Your website permissions have been updated.  When you login again, you will see more navigation options.

To avoid delay with future requests, please provide business contact information for our licensing records.

The latest beta version of TransMagic is available for testing. 

1.)  When you are ready, please login at www.transmagic.com. 

2.)  Then go to the Support/Downloads page. 

3.)  Click the link under the "TransMagic R8 Test Versions" section at the bottom of the page. 

4.)  Then click the link to download the installation file.

5.)  You will be prompted to register after you install the software.  Open the TM License Manager.  Then, under the Primary License section, click "Register License Key."  Then click "Register...".

6.)  Copy the Reference Code under the "Note to Existing Customers and Prospects" section.

7.)  Click the license key request form link. 

8.)  Paste the Reference Code in the space provided and click the "Submit" button.

9.)  A beta test license key will be sent in reply.

Thank you for your interest in our Reseller Program.  We have a special page on our website, www.TransMagic.com, with information that will help you support customers who need TransMagic.  To obtain access to the Reseller Portal page, follow these instructions:

1.)  Go to www.TransMagic.com.

2.)  Select the "login" link in the upper right of the website.

3.)  Select "Create New Account"

4.)  Provide the required information.

5.)  Validate the email.  An email will be sent to verify a login request.  The login will be active after TransMagic receives verification that the email is valid.

6.)  request reseller permissions.  Once you have a login, you can identify yourself as a TransMagic reseller by going to www.transmagic.com/support/requested support and selecting the "Request Elevated Permissions" link.  In the form field, please indicate that you are requesting reseller permissions, the company you are with and other needed information.

7.)  You will only need to do this once.  When your TransMagic reseller login is approved, you can access the TransMagic Knowledge Base, Support Documents, Video Tutorials and Reseller Information including new marketing materials.

8.) We'd also like to know more about you and your market.  Please go to www.transmagic.com/community/resellers/become-reseller to fill out our Initial Reseller Application.

9.)  Please contact Jerry Eshbaugh (jerrye [at] transmagic [dot] com) if you have any questions.

Our standard delivery, registration and installation procedures for TransMagic products are below:

Delivery

  We release a new version of TransMagic 3-4 times a year.  CD's become quickly outdated so, as a rule, the standard method of delivery for transmagic software products and updates is to provide a web page for electronic transfer (download) of the TransMagic product installation file.  If desired, you may request that a CD be shipped to you for a fee.

Registration

  Please login in at www.transmagic.com.  Then, go to the "Support/Downloads" page.  From there, please download the latest version of TransMagic by clicking on the "Download TransMagic" button on the end-user's computer.  You will be prompted to register after you install the software.  Please copy your Reference Code, then, go to our "Support" page.  Click on the "License Key Request" link in the list to the left.  On the License Key Generation page, look for the "Note to Existing Customers and Prospects" sections and click the link provided there.  Paster the Reference Code in the space provided and click the "Submit" button.  A license key will be emailed shortly thereafter.

Please register at www.transmagic.com.  Then, go to our "Support" page to download the following files:

1.)  Download and install the Workgroup License Administrator application.  After installation, the Quick Start Guide will open automatically. Please follow the instructions from there to complete the installation, registration and license activation.

2.)  Download the latest version of TransMagic for the Client Installations.  You will be prompted for the server IP address with each installation.

This issue is due to Microsoft prerequisite install failure.  To correct this, please login to our www.transmagic.com site.  Click "Support" -> Click "Downloads" (on the left) and install the following component:  Microsoft Visual C 2005 SP1 AT: Update Redistributable.  After installation, TransMagic should operate correctly.

It appears you have selected the "Netwrok" option when installing TransMagic.  However, for the eva;uation you would need to select the default "Node-Lock" (Stand-Alone) version.  You can correct this in the following two ways:

1.) If you are comfortable editing the registry you can navigate to this value in the registry:

32-bit PC:

HKEY_LOCAL_MACHINESFTWAREMicrosoftWindowsCurrentVersionAppPathsTransMagic.exe

64-bit PC:

HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftWindowsCurrentVersionAppPathsTransMagic.exe

Then change the "Network" value from "true" to "false."

2.) Unistall TransMagic R8 and re-install it - this time selecting the default "Node-Lock" (Stand-Alone) option.

Then after correcting this, when you start TransMagic, you will be asked to submit youre "Reference Code" on-line and you will be emailted you License Key.  Then, you should be all set to go.

The Annual Maintenance subscription must be current to upgrade.  The 64-bit version has been released to all products with TransMagic R9.

You can send us files via the online support form in the following way:

1.) Go to www.transmagic.com

2.)  Login -> Click "Support" -> Click "Request Support" (on the left)

3.)  This form will allor you to upload up to 500 MB of data and describe the issue.  If it's a large upload, make sure you wait long enough to see the form change and display the "Your support request has been submitted, expect a response soon" message.

PMI is turned off by default for performance reasons. To enable PMI translation and see a sample, here is the recipe:

1.) File -> Settings -> General Check Enable PMI Translation

2.) To test, open Program Files/TransMagic Inc/Transmagic R8/Sample Files/CATIA V5/V5Sample01.CatPart

3.) Once the model is loaded, PMI can be toggled on and off using the bottom right button in the bottom toolbar.

The safest method is to un-install and reinstall the product, selecting Node Locked license when you are reinstalling.

If you are comfortable changing your Windows Registry, and understand the risks you can simply change the following Registry key values:

On a 32 or 64 computer change this key to false:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\TransMagic.exe\Network

The TransMagic Workgroup Administrator will allow you to add your new TransMagic license while continuing to serve the existing TransMagic license that your user’s are currently using.  Follow these instructions:

• We’re going to manually add the new TransMagic license to the server.  So start the TransMagic Workgroup Administrator that you’re currently running on the server.
• Click the “Register Products” icon:   and this will launch the “Register Products” dialog:
• 
• You will want to enter the Product Name / Product ID combination for the product that you want to license.  Here is a list of some current TransMagic products at the time of this writing.  If the product you wish to license is not in this list please send and e-mail to TransMagic Support requesting the Product Name / Product ID combination you wish to license:
  • TransMagic R9 sp0 / 5367-8791-2129-7642-5710
  • TransMagic R8 sp5 / 5370-8811-2329-7643-5723
  • TransMagic R8 sp4 / 5379-8811-2329-7643-5722
  • TransMagic R8 sp0-sp3 / 5375-8851-2229-7643-5723
  • TM Batch R8 sp5 / 5366-8721-2029-7642-5713
  • TM Batch R8 sp0-sp4 / 5368-8721-2429-7642-5711
  • TransMagic R7 sp2 / 5360-8721-2429-7642-5713
  • TransMagic Batch R7 sp2 / 5369-8721-2429-7642-5712
  • TransMagic R7 sp1 / 5371-8891-2229-7643-5723
  • TransMagic Batch R7 sp1 / 5372-8891-2229-7643-5724
  • TransMagic R7 sp0 / 5370-8821-2129-7643-5726
  • TransMagic Batch R7 sp0 / 5366-8751-2129-7642-5715
• Enter the Product Name / Product ID combination you wish to license into the Register Products dialog and click the “License” button:
• 
•  This will launch the “License Product” dialog:
•  
• Copy the “Reference Code” from the License Product dialog and submit it to TransMagic in the usual way to obtain your License Key.  Once you receive your License Key enter it into the appropriate field and click “Save”.
• Your TM Workgroup Administrator is now serving up both licenses for your old version of TransMagic and your new version of TransMagic.  You can now migrate your users to the new version of TransMagic at your leisure without disrupting their workflow.

Tolerant edges, also called "gaps" are not actual "holes" in the geometry. To be precise they are surface-to-surface intersections that exist at a lower tolerance. They also should not be considered a measure of quality. Every contemporary CAD system uses tolerant edges and creates them during modeling operations. There are many modeling operations that could not succeed without tolerant edges.

In TransMagic the "Show Tolerant Edges" function exists as simply another metric with which to analyze the model. Here's an example:

Let's say a cube was created in CATIA V4. CATIA V4 is a fairly low precision system and TransMagic is a very high precision system. In fact the value that TransMagic considers zero (0) is 10e-6 mm, which is smaller than most CAD systems. Depending on how the cube was created, TransMagic could report all 12 edges as tolerant because this measurement is relative to TransMagic's zero value. Then let's say we run Full Repair on the cube. Since the cube is comprised of 6 planar surfaces, TransMagic is able to extend and re-intersect all six surfaces perfectly due to the underlying infinite plane of each surface. So Full Repair will in this case will produce zero tolerant edges - meaning that every surface-to-surface intersection in the cube is now precise to TransMagic's zero value. However, this is not to be expected as the "correct" result as there are countless other cases where an underlying surface cannot be extended and thus tolerant edges will remain. This is perfectly acceptable and correct in all contemporary CAD systems.

Also keep in mind that since the TransMagic "zero" is very precise that what TransMagic detects as a tolerant edge may be considered precise to zero in the receiving CAD system. Therefore, tolerant edges should not be considered a measure of quality but rather a relative metric to gauge the geometric composition of a part. It's also a useful metric to gauge geometric composition before and after Full Repair.

Yes, Please see the following link for a complete description:

Using TransMagic For Validation

Error Dialog:

A: Your “Windows Script Host” is not fully initialized.  This can be due to a number of reasons but the fix is quite simple:

Window XP:

• Go to Start->Run and enter the following:
  • regsvr32 scrrun.dll
• Click OK
• You should receive a message that registration completed successfully:
• 
• Go to Start->Run again and enter the following:
  • regsvr32 wshom.ocx
• Click OK
• You should again receive a message that registration completed successfully.

Window Vista:

• Click the Windows Key + R and enter the following:
  • regsvr32 scrrun.dll
• Click OK
• You should receive a message that registration completed successfully:
• 
• Click the Windows Key + R again and enter the following:
  • regsvr32 wshom.ocx
• Click OK
• You should again receive a message that registration completed successfully.

Window 7:

• Got to Start->All Programs->Accessories, find the "Command Prompt" icon, right-click it and then select "Run as administrator".
• At the command prompt type: regsvr32 scrrun.dll
• Click OK
• You should receive a message that registration completed successfully:
• 
• Now install TransMagic using "Run as administrator".

By default TransMagic requires a "Power User" account.  However, you can give a Limited User account specific rights to the areas of the registry that TransMagic accesses and also it's DLL (System) directory.  To run TransMagic on a Limited User Account you will need to give the account read\write access to the following areas of the registry:

32-bit Windows:

HKEY_CURRENT_USER\Software\TransMagic

HKEY_LOCAL_MACHINE\SOFTWARE\Acudata

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\TransMagic.exe

64-bit Windows:

HKEY_CURRENT_USER\Software\TransMagic

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Acudata

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\App Paths\TransMagic.exe

Also, you will need to give read\write access to the following directory on the hard drive:

%ProgramFiles%\TransMagic Inc\TransMagic R8\System

Yes. TransMagic uses what is called a "partitioned" approach to multiple cores\processors. For example you can be loading one part and working on another opened part at the same time. TransMagic can also be translating\working on a part and allocate resources to other processes like memory management, geometry checking, etc. However, currently TransMagic does not use parallelization during a single translation. For example if you are loading in a multiple part assembly - TransMagic will not send multiple parts out to multiple processors for translation. That is a project for a future release though.

TransMagic's server application can send multiple files out to multiple processors simultaneously for background translation. This is sort of a partition\parallel hybrid.

The TransMagic License Key combination is based on a "machine signature". This machine signature is called the "Reference Code" and it is unique to each machine. The following things can cause an existing TransMagic License Key to become invalid and require a new one:

• PC crash 
• BIOS change 
• New hard drive
• New motherboard 
• New network card
• TransMagic is improperly shut down
  • The most common cause here is when the computer is forced into a "hard shut-down" (holding down the power button until it turns off) while TransMagic is running.
• TransMagic is installed on a different computer 
  • Each machine is unique and requires a unique Reference Code/License Key combination.
• TransMagic License Key expires 
• TransMagic software upgrade 

There are a few reasons that older versions still show up even though they've been removed.  However, the end result is always the same: They need to be removed manually.  Follow these steps to remove the older version of TransMagic from your system:

1) First make sure you've tried to remove the older TransMagic version via the Add/Remove Programs Group.
2) Start a copy of Windows Explorer and navigate to "C:\Program Files", locate and delete the "TransMagic Inc" directory.
3) In Windows go to Start->Run for XP or for Vista click the Windows Key+R and enter "regedit".  Click "OK".  This will bring up the Windows Registry Editor.
4) In the Windows Registry Editor navigate to the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\

5) Each version of TransMagic has an uninstall "Key" and sometimes this Key fails to get removed, this is why the newer installer is falsely detecting the older version even though it has been removed.  Each version of TransMagic has it's own unique Key.  Below is a list of all previous versions of TransMagic.  You will need to find your version and then search for that Key.  Many versions list multiple Keys but typically only one of these will exist and it we've listed them in order of most likely to least likely.  Here are the Install Keys of all previous versions of TransMagic:

TransMagic R7 sp2 Series Keys
{ABFB2DE3-5DFF-417A-B5E2-40CFD30D2473}
{7A5373D4-5BC5-4369-9E4C-09C2BBCB1081}
{98C102C9-429E-47D8-8E51-805D8420670F}
{EF59091C-294D-4184-9334-65DC2D41A525}
{8D1F64CF-5F30-41EE-83DB-695A4625EE43}
{270DCE87-1858-4048-9BBD-5EEE391E918C}
{055660EA-2CD2-4B5C-B528-E522125B7516}

TransMagic R7 sp1 Series Keys
{AE7C093A-A6D3-4756-83FE-24A66847B50C}
{B522E507-70F5-4A87-92B0-E6F3B94D8E70}
{D90CA3EA-87C5-43FB-B6ED-79350544B456}
{FAA46883-A8F8-4EA8-88C3-081444E2E63F}
{1C190E4E-8C0B-4FE1-A4E9-09BBA802F8FF}
{8FE5A80D-7B2C-4B14-9506-0F330B8AF806}

TransMagic R7 sp0 Series Keys
{1B3E4B45-1677-4207-B16C-171FA1EBCC3F}
{6F9CCBAE-3D94-43CE-968C-355B1B8CB100}
{A310CB75-1CB1-4BB0-B62B-23ECD66C6DD2}
{296C8B00-F3A9-4974-8B80-E80B65B7378E}
{837BB49F-A616-4453-959A-55130F14C4D7}
{0075A2BE-CF23-4852-8A52-46163FD2EB7A}
{D84D7E04-DCFF-48B5-839F-D25C5CB8289D}
{AB9FA4E3-F929-4B19-B1F0-D68A0172ED52}
{48951166-ECD0-49DE-96E2-A92CB7F21504}
{C4DF8A91-4344-4F0D-B35B-9C9E48E130CD}
{71D3DCC5-EFAD-47B4-855B-BD17239C0977}

TransMagic 2006 sp1.0 Series Keys
{8CB52EB4-658F-481D-9512-D91F0F4097C8}
{95A66AAE-A1BE-40D1-A3EE-F800053D8D90}
{50608A5C-641E-4D3F-8E6C-809B2A7C9BAC}
{EC281D96-0A53-495F-821A-A4985C9B420B}
{39E944B2-5F02-4B09-A1E2-593CD3AE85AC}
{4EE3B6F4-0308-423E-8386-BF10C13BCE25}
{B4EB599F-B52A-40B8-9C4F-DE73CED34583}
{542B3749-20B7-4917-86FE-D96D9C0645B8}
{D28B8EC8-6EF2-4AC7-9191-E7FC2F5F4E85}
{966D3EB6-6B50-4C06-8DDA-8C9DB422053E}
{DE3D3E3C-A9ED-424E-826E-8EE2F0B08A80}

TransMagic 2006 sp0.2 Series Keys
{31652E0A-477A-4C6D-9049-583D98E21397}

TransMagic 2006 sp0.1 Series Keys
{9129D9AC-8E06-465A-8BCF-6E19B6649B1F}

TransMagic 2006 sp0.0 Series Keys
{D1FF9794-1C26-48CF-8777-F9AF24D2B3B7}

TransMagic 2005 sp5 Series Keys
{2D6F057B-DCBA-4011-91F9-087EE9E81B23}

TransMagic 2005 sp4 Series Keys
{2d7d2a41-2e22-447a-a7cb-4ffb535d4055}

TransMagic 2005 sp3 Series Keys
{1a1189c4-7780-4198-a62c-26a71cccd5bb}

TransMagic 2005 sp2 Series Keys
{eeed91e4-c6d5-4925-beaa-0f9996fc4d7f}
{4500b5af-22c2-4061-8ce5-480a7d595763}
{68b95e59-0eef-44d5-b50e-7d93b4c992b2}
{88933307-441f-45dd-a8c3-c35822d8ec33}

TransMagic 4.X, 3.X & 2.X Series Keys do not apply as they were not using the same type of installer.

6) You may now close the Registry Editor and install the new version of TransMagic.

TransMagic's Network License works like so:

You'll need one central server and on that server you'll want need to install the TM Net Admin application.  This is an application for installing and administering your TransMagic license.  This is also a Windows only application so you'll need to either put it on a Windows machine or maybe a Windows emulator on a non-Windows machine but this configuration is not tested/supported.

Program links for the TM Net Admin application are available for download from your TransMagic.com account.  Click Support and then click the "Downloads" page.  If you have purchased a network license you will see a link for the TM Net Admin installer.

Download and install TM Net Admin on the server.  A Quick Start Guide will pop-up after installation and getting your License Key is a straight-forward on-line form.  This is the point where TM Net Admin will give you a Reference Code and you'll submit that code to get your License Key.  The Reference Code is based on a machine signature and is unique to each server machine.

Then for the client application you'll simply download the installer and then copy/install it on each client - making sure to select the Network install option vs. the default Stand-Alone option.  The client will typically only need the server's IP Address.  Once the client app starts up it will ask for the server IP, enter it, and that's all there is to it.  The TM Net Admin runs an automatic service that will notice the client pinging it and serve up the license.  The download link for the client will also be available for download from the Downloads page using your TransMagic.com account.

TransMagic utilizes what is called the “/3GB Switch”.  Normally a Windows 32-bit application can only utilize up to 2GB of RAM (both physical and virtual combined).  However, if an application is built with a special set of options it can utilize up to 3GB of RAM – even if your system has only 2GB – the other 1GB will be swap space (hard drive – much slower but still works).  The caveat here is that you also have to tell your OS to utilize this /3GB Switch by manually configuring a couple settings and rebooting.  The extra 1GB makes a huge difference as it’s a 50% RAM increase.  For instructions on setting the /3GB Switch:

Go to the Start->Control Panel->Double-Click "System"->Click "Advanced" Tab

At the bottom of the Advanced Dialog in the "Startup and Recovery" section, click "Settings"

At the top of the Startup and Recovery Dialog in the "System Settings" section, click "Edit"

This will open the system's BOOT.INI file. It should look something like:

[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /NoExecute=OptIn

You'll want to copy the last line and edit it so that it looks like the following:

multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional 3GB" /fastdetect /3GB /NoExecute=OptIn

You don't want to replace the last line, you want to add to it so now the BOOT.INI should look something like:

[boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional 3GB" /fastdetect /3GB /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /NoExecute=OptIn

Click File->Save and close the text editor. -->Now reboot your system. When your system starts up again, you'll have the option to boot with the /3GB Switch or without it. This is a 50% increase in RAM access and this should make the difference in loading/saving your files.

For Windows Vista or Server 2008:

Go to Start->All Programs->Accessories->Command Promt --> At the command prompt enter:

bcdedit /set IncreaseUserVa 3072

Restart the computer.

Keep in mind that translation is a very RAM intensive process and in order to translate all the geometry it must first all be brought into RAM and then translated.  The RAM limitations of a 32-bit application are not TransMagic bugs but rather Windows 32-bit Operating System imposed limits so there’s nothing TransMagic can do about this.  One thing that can help is to break the assembly into smaller pieces.  A good general rule of thumb when translating geometry is that the data itself will consume 10x the file/assembly size in RAM during translation.  So if you have a 200 MB file/assembly then you can expect that the translation will consume at least 2GB of RAM.

However, the TransMagic R8 series is offered in a native 64-bit support.  This requires that you have a native 64-bit machine, of course.  With native 64-bit support for Windows, theoretically an application would now be able to consume up to 2 Terabytes of RAM.  Although 2TB machines don’t exist yet 64-bit machines with large quantieis of RAM are certainly available now.  64-bit TransMagic on a 64-bit machine eliminates the need for the 3GB Switch.

Yes.  Today there is a process involved.  In the future we intend to automate this process; however, it can certainly be done. 

Before this can be done please understand the following:

1. The version of TransMagic must be the same on both machines.
2. The TransMagic License is based on a machine signature, called the “Reference Code”.  This Reference Code is unique to every machine and can change for a variety of reasons – it is not always static.
3. This exchange is not facilitated via a dongle, it is a software based license and as such you will need access to both machines during this process.

With that said, here is how to move your TransMagic License from Machine “A” (moving from) to Machine “B” (moving to):

• Launch TransMagic on Machine B.  You should see the “Register TransMagic” Dialog:

• Click “Register”, this will launch the “License Key” dialog:

• Copy the “Reference Code” from this dialog.  You will need this information to move the License from Machine A.  Don’t close this dialog.
• On Machine A, Click here to download or run the TMNetAdmin.exe application.
• Once the TMNetAdmin application (also called the “Sheriff Administrator”) is running, click License->Move.
• Select your product in the “Product Name:” Window, then click the “Move” button.
• This will launch the “Move License” Dialog:

• Here is where you’ll paste your Reference Code from Machine B (step 3). 
• Click the “Generate” button.  This will simultaneously remove the license from Machine A and generate the license for Machine B.
• Copy the “License Key” as this will be needed for Machine B.  Do not lose this key.
• On Machine B, the “License Key” dialog will still be open. 
• Paste the License Key into the “License Key” box and click “OK”. 
• The TransMagic License has now been moved from Machine A to Machine B.  Repeat these steps to move the license to other machines or back to Machine A.

Yes.  TransMagic licenses from Spatia (a software component company owned by Dassault Systemes) the CATIA V5 Kernel called CNext with the “AL2” configuration which includes all available configurations.  The AL2 configuration is only available through licensure of the kernel or for demonstration purposes during the sale of CATIA V5 itself.  It is not offered for sale.  The CNext kernel can be viewed in the following folder under TransMagic:

%ProgramFiles%\TransMagic Inc\TransMagic R8\System\lib3dx

The “lib3dx” directory is the CNext kernel and the same directory structure can be observed under an actual installation of CATIA V5 itself.  The CNext binary DLLs, components and supporting utilities can be viewed under the directory:

%ProgramFiles%\TransMagic Inc\TransMagic R8\System\lib3dx\intel_a\code\bin

This again is the same directory structure as CATIA V5 itself.

Zemax supports the following geometric formats in order of preference:

1. ACIS *.sat
2. STEP *.stp
3. IGES *.igs

Note; however, if you are importing prismatic shapes composed of flat surfaces then the STL format is the preferred format.

TransMagic translates part and assembly Names, Layers, Colors, Assembly Hierarchical information & Product Manufacturing Information (PMI for CATIA V5, Pro/E & NX only).  However, true feature support is a very resource intensive development because most feature trees are truly moving targets as they can and do change from release to release.  Although TransMagic does not support native feature based translation, it should be noted that TransMagic’s Full Repair tool provides improved classification of solids entities and acts as an effective pre-processor for feature reconnection tools within the target CAD system.   Virtually all of the major CAD systems, i.e. Unigraphics, Pro/E, CATIA V5, SolidWorks & Inventor, have feature recognition capability which is very efficient in populating a useable feature tree.

If you have special circumstances where feature translation is required, there are solutions on the market.  Here is what you can expect:

• These solutions start at $50,000 and can run well over $100,000 per seat.
• Virtually all feature translation products also require a seat of each CAD system you are translating between on the same computer as the feature translator.  This will likely add another several thousand to the overall start-up cost.
• Custom feature translation requires custom development which can be costly and time consuming.
• Features representations within the CAD files are a very dynamic, requiring frequent updates, reverse engineering, and result in a partial solution.
• Most feature translation systems only support the base features, i.e. fillets, holes, bosses, pockets, ribs, etc.  These are usually the same features that are typically populated with feature recognition tools within the CAD system for much lower cost.
• These solutions are targeted at people with very strong business case (and budget) for feature translation.

TransMagic, coupled with your CAD systems feature recognition, provides a solution that you can start using today for majority of feature interoperability requirements.

CATIA V5 States the following requirement:

BRep Continuity Compliance
Imported geometry that is not compliant with the continuity requirement (C2 continuous) of CATIA V5 formats are split on discontinuities. Based on continuity requirements, the topology is modified accordingly.

In other words, some CAD systems represent surface math differently than others.  There is no correct method.  CATIA V5 does not allow “lower degree continuity” to exist in a surface.  For CATIA V5, this requirement is technically called sub-C2 internal discontinuities.  Anywhere this lower degree continuity is found, CATIA V5 will automatically place an edge in that location.  Depending on the part being saved to CATIA V5, you will end up with more surfaces than the original part had.

It is critical to understand that even if there are more surfaces, the original surface math is preserved and the converted part will still be mathematically identical.  Keep in mind the two following items:

1) The surfaces that are split are still mathematically identical.  It's just that in some CAD systems sub-C2 internal discontinuities are permitted and in CATIA V5 they are not.
2) The term "discontinuity" is not a negative term when speaking of 3D solid math.  It's a term that is analogous to the meaning "a change in curvature derivatives."

It is possible that a translator from another company that does not use the native CATIA V5 Kernel (called CNext) for CATIA V5 translations will not have surface splits in these locations.  However, even though these parts may appear visually identical to the original model, the fact is that their surface math has been changed.  In CATIA V5, you would actually be looking at a non-identical copy of the original model.  When inquiring to Dassault Systemes regarding this behavior, they state precisely this:

"Even we can generate no splits but that would require us to alter the tolerance which V5 uses to fit data - thereby altering the translated data."

“…thereby altering the translated data” is the important quote here.  The TransMagic mandate is to never change the original design intent of surfaces or solids - this could result in errors in manufacturing downstream.

While TransMagic does not support the I-DEAS application natively, it does support several formats that I-DEAS does.  I-DEAS can read/write both Parasolid *.x_t and JT *.jt files and so can TransMagic.  So if you can obtain a *.x_t or *.jt file from I-DEAS then you can use these formats in TransMagic to interoperate with I-DEAS.

Also, keep in mind that the most common I-DEAS native file is *.prt.  Coincidentally the *.prt file extension is used by many CAD systems such as UG NX, KeyCreator (formerly CADKEY), and several others.  If you have a *.prt file that TransMagic won't read you can submit it to TransMagic Support by clicking the "Support" Tab and then "Request Support".  We can tell you if the file is an I-DEAS file or a UG NX file.

The TransMagic CATIA V5 translator is based directly on a real seat of CATIA V5 "under the hood" of TransMagic.  Like CATIA V5 itself, a few things can occur to its environment that prevent it from being launched properly.  Follow this checklist to debug your TransMagic CATIA V5 translator:

·         Do you have the proper TransMagic License?  Start TransMagic.  Then, select Help->About.  At the bottom of this dialog it will list your “TransMagic License Properties."  Your “Configuration:” should read one of the following:

o   TransMagic Expert (includes CATIA V5 Read AND Write)

o  TransMagic PowerPack for SolidWorks (includes CATIA V5 Read and Write)

o   TransMagic PowerPack for Inventor (includes CATIA V5 Read and Write)

o   + V5 Read (CATIA V5 Read Add-on feature)

o   + V5 Write (CATIA V5 Write Add-on feature)

·         Did you install TransMagic on a supported Operating System?  The TransMagic R7 series requires Windows XP, Windows Vista, Windows Server 2003 or Windows Server 2008.  Make sure you have one of these operating systems.  The TransMagic R8 series will not allow itself to be installed on an un-supported operating system to avoid this issue.

·         Did you download and install the Microsoft prerequisite components?  The TransMagic R7 series requires two components to be installed.  The installer will warn you of these during the install but it does not force you to install them.  The TransMagic R8 series and beyond will install these components automatically to avoid this issue.

o   Microsoft .NET Framework 2.0.  To determine if you have this component, go to your Add/Remove programs and look for "Microsoft .NET Framework 2.0”.  If you do not have this component you can download it from the Microsoft website via the following links:

§  32-bit: http://www.microsoft.com/downloads/details.aspx?FamilyID=0856EACB-4362-4B0D-8EDD-AAB15C5E04F5&displaylang=en

§  64-bit: http://www.microsoft.com/downloads/details.aspx?familyid=B44A0000-ACF8-4FA1-AFFB-40E78D788B00&displaylang=en

o   Microsoft Visual C++ 2005 SP1.  You cannot determine if you have the SP1 package from the Add/Remove programs dialog.  Since this component is a very small download the best recourse is to simply download and install this package.  It does not hurt to re-install this package if you already have it.  Also, there was a Windows Update that corrupted this package on some machines so re-installing it is a good idea in any case.  You can download this component from the Microsoft website via the following link:

§  32-bit: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=200b2fd9-ae1a-4a14-984d-389c36f85647

§  Note: for the TransMagic R7 series you’ll want to install the 32-bit version whether you’re using a 32-bit or 64-bit OS as the TransMagic R7 series is 32-bit only and will run on a 64-bit machine in 32-bit mode but it will need the 32-bit version of this component installed.

·         Do you have another application with a V5 translator that is conflicting with the TransMagic translator?  CATIA V5 itself will NOT conflict with TransMagic; however, there are other applications that also license the V5 CAD Kernel from Dassault Systemes and one of these applications could have a CATIA V5 Kernel that is conflicting with TransMagic.  The most common cause of this is that the application developers did not observe Windows best practices for DLL paths and instead of putting the DLL paths in the  registry they will put them in the “Global Windows Path Statement”.  You can check for this in the following way:

o   Go to Start->Run, enter “cmd” and click “OK”.  For Windows Vista click your Windows button + the letter R, enter “cmd” and click “OK”.

o   At the command prompt type “path” and click Enter.  This will display the Global Windows Path Statement. 

o   If there are any translators or CAD systems or other non-Windows programs in this path then  they will need to be serched for CATIA V5 DLLs.  When an application puts their DLL paths in the Global Windows Path statement this means that those DLLs will always be found first for every application.  The problem is that let’s say there is a 3D viewer application that uses a V5 Kernel and that application puts its V5 DLLs in the Global Path.  Then when you start TransMagic, which may be based on another version of V5 Kernel tries to run – it will find only the DLLs in the Global Path first.  This will cause a DLL conflict and TransMagic won’t be able to run.  Examples of applications that now or in the past put their V5 Kernels in the Global Path:

§  Actify SpinFire Viewer

§  SmartTeam (a Dassault Systemes PLM system).  Note the directory “C:\Program Files\SmartTeam\XCADTrans” in our screenshot.  In this example, this directory contains CATIA V5 DLLs that conflict with TransMagic’s V5 Kernel.  See the next bullet.

o   If you see a suspicious path in the Global Path, then browse to that directory and search for the following string “CAT”.  A large majority of CATIA V5 DLLs start with “CAT”.  If you find any of these then this is likely your offending path and it will need to be removed from the Global Windows Path Statement before TransMagic will run.  Keep in mind that removing a directory from the Global Windows Path Statement could very well cause the application that put the path there to malfunction or stop working entirely.  Please consult your IT department before performing the next step.

o   Go to your Windows Control Panel, switch to “Classic View”, click the “System” icon.  This will launch the “System Properties” dialog:

o   Click the “Advanced” tab and then click the “Environment Variables…” button.  This will launch the “Environment Variables” dialog:

o   In the “System variables” section, find the “Path” statement, highlight it and click “Edit…”.  Locate the offending path and delete it.  Click “OK”, “OK” again and “OK” once more.  Now this path has been removed from you Global Path and TransMagic’s V5 translator should work.

o   It’s possible there could be more paths with V5 Kernels in them so you may need to repeat this process to find and remove them all.

o   Also keep in mind that if an application was installed just for a single user vs. all users on the machine then there may be a “Path” Variable under the “User variables” section at the top of the “Environment Variables” dialog that needs to be edited.

·         If an application was found with conflicting DLLs but you still need to use this application, you can create a *.bat file for this specific application that puts the DLL path back into the Global Windows Path Statement and then launches the application.  This method protects other applications from DLL conflicts but allows the offending application to operate as well.  Contact your IT department for creating a *.bat file that employs this method.

·         TransMagic R8 and beyond now employ the CATIA V5 "setcatenv" tool which will set-up a specific CATIA V5 environment that only applices to TransMagic.  Even if an application observes poor windows DLL path programming practice, this should no longer interfere with the TransMagic CATIA V5 translators.

We have a mandate called the "TransMagic stated geometric tolerance specification".  It reads as follows:

TransMagic stated geometric tolerance specification:

Analytic Surfaces

Analytic surfaces are converted to a precision of zero or machine tolerance.  This means that where-ever an analytic surface is present, such as a cone, sphere, plane, torus, etc. we will convert it to an analytic surface in TransMagic with an identical surface.

Free-Form Spline Surfaces

For free-form spline surfaces such as NUBs, NURBs, Bezier, etc. the geometry internal to the surface is translated at a precision of 10e-6mm - which is an extremely tight tolerance and also essentially zero.  In fact this value, 10e-6mm, is the value that TransMagic considers zero (.000001 = 0).

Trim Boundaries

Trim boundaries are precise to exactly what they are in the original file.  Depending on the file, this can be anywhere from .1 mm to zero. TransMagic will translate what-ever is in the CAD file. So if a CAD model is generated at a very loose tolerance (very common in V4), we will simply translate at that tolerance.

Class A Surfaces

For Class A surfaces, this refers to a mathematic curvature continuity of the second derivative (C2) between two surfaces.  Meaning that the two surfaces have identical speed, direction and radius of curvature at their boundary.  This allows two different surfaces to appear as though they are the same surface when subjected to visual inspection and testing such as light reflection line testing.  If the math is present to support C2 continuity or even G2 continuity (geometric continuity of the second derivative), then TransMagic will absolutely support and translate that continuity.  Note however, that C2 or even G2 is fairly uncommon except in automotive and aerospace sheet-metal applications.  The data weight required to support true C2/G2 is pretty high and these surfaces are typically generated by a dedicated add-on to most CAD systems.  Most
continuity math found in the surface boundaries in any given CAD file is C1 or G1 - this is usually the curvature associated with blend radii and lofting/sweeping operations.  C1 means that the two surfaces have identical speed and parallel radius of curvature (but not identical).  This is a much lighter data representation and yet still looks very pleasing to the eye.  In any case as will all math data contained in any format that TransMagic supports - TransMagic will simply support what is represented in the original CAD model.

Bezier Surfaces

Some antiquated CAD systems use Bezier surfaces vs. the current industry standard NURBs surfaces, an example being CATIA V4.  TransMagic's math engine is based on NURBs and analytics so a conversion must be done between Bezier and NURBs to bring such files into TransMagic and vice versa for files being saved out of TransMagic.  There is more than one way to perform this conversion and TransMagic has spent a significant amount of resources developing the mathematic algorithms to perform this conversion to our stated tolerances consistently and reliably.  In fact in the case of CATIA V4, TransMagic has numerous CATIA V5 customers who have chosen TransMagic for it's CATIA V4 import into CATIA V5 as TransMagic's conversion is more consistent and reliable than CATIA V5's own CATIA V4 translator.  Note also that when an application such as CATIA V4 outputs an IGES file for example they themselves are still performing this conversion and the results are quite literally always sub-standard when compared to TransMagic's mathematic conversion on a native CATIA V4 file.

In summary

TransMagic will translate original geometry at the same tolerance as the original geometry. - TransMagic will keep in tact the mathematic definition of Class A surface boundaries when they are present or more precisely, TransMagic supports and will keep in tact the mathematic boundary condition of the original model regardless of it's class.  TransMagic includes technology (Full Repair) to actually generate more precise intersections (boundary conditions) but this is and will always be a user's decision to use this technology to do so.

The file you have opened is most likely the product of a function in Pro/E called "Shrink Wrappping".

Shrink-wrapping is the name of a function in Pro/E. The intent of this function is to create a part whose surfaces describe the overall assembly yet eliminate the internal components and detail. The intent is to protect intellectual property. It can be presumed that the designer/engineer/company that created this assembly either wanted to protect their intellectual property OR they wanted to reduce the file size of the original assembly so that it was not so unruly. It can also be presumed that they believed that using the Pro/E shrink wrap function will do so. It does; however, the shrink wrap function is extremely unreliable, trims surfaces poorly, eliminates many surfaces altogether, and essentially creates a useless file as the result. A non-solid, unusable surface model at that.

There are really only two solutions to this:

1) Spend an unreasonable amount of time fixing the part to a semi-useable state in TransMagic. This is possible but would require an expert user and would probably take about the same amount of time as re-creating the design.

2) Ask the sender of this Pro/E file to release at least the critical SOLID parts of the original assembly. The sender could just include the critical assembly parts that include mounting locations, etc. They don't have to send all the proprietary working innards.

In our experience there are always a multitude of unstitched edges and missing surfaces resulting from the Shrink-wrap function. Not missing because TransMagic failed to translate them but missing because the shrink-wrap function had completely eliminated them way before your read the file into TransMagic. In order to fix this file you would need to manually re-create these missing surfaces and use TransMagic's Lite Repair function to stitch the surfaces into solids among potentially other things to get these models into a useable form.

The bad news is that no single person or software application would be able to automatically produce a useable CAD file from this file. Your best bet would be to exercise Option 2 above.

The good news is that there are some settings in Pro/E that will help to improve the quality of the Shrink Wrap function output.  To achieve the best results please observe the following Pro/E Shrink Wrap settings:

This is a known issue with TransMagic R7 and will be resolved with TransMagic R8. However, the issue is related to a graphics card driver and the work-around is very simple:

• Start TransMagic
Click File->Settings, the “Appearance” page will be the default.
• Find the section labeled “Rendering Options” and switch your “Driver” pull-down from “OpenGL” to “Direct3D”:


• Click “OK” and then “OK” again.
• You might also want to shut-down and re-start TransMagic to make sure the settings get saved to the Windows Registry.
• Now re-load the file that caused the crash before.

A SolidWorks *.sldasm assembly file does not contain any "true" geometry. It simply refers to *.sldprt files - which are the individual part files that do contain the geometry.  As TransMagic is primarily a 3D geometric translation and Repair application, it needs the *.sldprt files that contain the actual CAD geometry to be present when reading a *.sldasm file.
 
One confusing aspect of a *.sldasm file is that it does contain a "visual" representation of the assembly that you can load into eDrawings and other viewers; however, rest assured none of the CAD geometry is in the *.sldasm file.

TransMagic does not convert *.stl (or any other polygonal) format to geometric formats.  The reason is that *.stl files and other polygonal formats are comprised of triangular polygons vs. true geometry such as spheres, planes, torus, cones, free form surfaces (NURBs), etc.  The conversion from true geometry to triangles is very easy (CAD to *.stl); however, the inverse, *.stl to true geometry is very difficult.  In fact, no software actually does this automatically as there is simply not a straight conversion.
 
There are some reverse engineering software's out there that will take a point cloud (which is essentially what an *.stl file is) and with significant user intervention, they are able to map NURBS surfaces to these points; however, in most cases the user has to define the boundary curves manually.  This process is extremely tedious and difficult as there are many ways to introduce errors into the reverse engineering process.

Further technical information:
 
TransMagic could very easily take an STL file and generate a geometric file using a technique known as a Polygon Point Mesh Body (PPMBody).  A PPMBody is the conversion of lightweight planar polygons (always found in STL and other visualization formats) to true geometric planar faces in a solid body.  One of the primary drawbacks of a PPMBody conversion is one of file size explosion.  For example, if the STL file had 400,000 polygons - which is typical or even small for some models (such as a medical model) - the resulting geometric solid model would have 400,000 planar (and triangular) faces.  This could be done automatically with no user intervention.  The problem is that the 400,000 polygon STL file that was maybe 3 MB could now be 100 MB in a geometric format.  This is because instead of just a "bag of triangles" like an STL file, you now have solid topology (the glue that holds a solid model together).  For every triangle in the STL file, which originally consisted of 4 pieces of information: 3 vertices and a normal, you'll now have:
 

1 body
- Under which is:
  - 1 Lump
  - Under which is:
    - 1 Shell
    - Under which is:
    - 1 Face
    - Under which is:
      - 1 surface
      - 1 loop
      - Under which is:
        - 3 edges
        - Under which is:
          - 3 coedges
          - 3 curves
          - 6 vertices
          - 6 geometric points
 
So one can imagine how a file would grow from 4 pieces of information for each triangular face to 27 (and this leaves some information out!).
 

Actually, a score of 100% "percentage of good geom" is not very common and 80% or better is considered a good result.  Here’s the explanation: 

TransMagic’s geometry engine is extremely precise; in fact the value that TransMagic considers zero (0) is .000001 mm.  That’s a very small figure in the CAD world and in fact a higher precision working value than most engineering systems.  So percentage of good geom refers to the percentage of surface-to-surface intersections that are precise to “TransMagic Zero” or 10e-6mm.  Every single edge in the model could be precise to 10e-5mm and you would get a 0% percentage of good geom result after Full Repair – even though that’s still beyond most engineerings systems precision and still a very precise water-tight solid.  We’ve never seen that happen but it’s theoretically possible.

The first question is really what does manifold or non-manifold mean?

Manifold is a geometric topology term that means: To allow disjoint lumps to exist in a single logical body.  Non-Manifold then means: All disjoint lumps must be their own logical body.  Of course that definition is often more confusing so perhaps the best way to think of Manifold and Non-Manifold is this: Manifold essentially means "Manufacturable" and Non-Manifold means "Non-manufacturable". In other words manifold means: You could machine the shape out of a single block of metal....and with a non-manifold shape you could not.

Take a look at the following image, it depicts a simple non-manifold body:

If you have a copy of TransMagic, click here to download this file and load it into your copy of TransMagic.

This file consists of two cubes that were Boolean United along a single shared edge - resulting in ONE logical body.  This is a simple yet effective illustration of a non-manifold body - where each block is a "disjoint lump" yet there is a single body.  The shared edge between the blocks is the actual non-manifold condition.  Since this edge is infinitely thin there is no manufacturing process that could create such a shape as an infinitely thin edge can not be manufactured. In reality, eventually you'd just separate the two blocks.

TransMagic is an example of a non-manifold geometry engine - a math engine where these types of shapes are allowed to exist.  There are two types of modeling engines: manifold modeling engines and non-manifold modeling engines.  TransMagic, ACIS, CATIA V4, CATIA V5, & Pro/E are all examples of non-manifold modeling engines.  NX, SolidWorks, SolidEdge and Parasolid are all examples of manifold modeling engines.

Manifold modeling engines are not allowed to represent disjoint lumps in a single logical body.  Each lump must be its own body.  To see proof of this concept for yourself do the following:

1. Load the non-manifold.tmr file into TransMagic.
2. Open the Assembly Browser (Tools->Assembly Browser) and note the single part.
3. Save this file as a Parasolid *.x_t file.
4. Re-load this Parasolid *.x_t file and open the Assembly Browser.

You will notice that a by-product of simply saving the Parasolid *.x_t file out of TransMagic is to separate geometry where necessary to conform to Parasolid's manifold requirement.  When using a non-manifold modeling application such as CATIA V5, for example, during the creation of very large and complex parts it is entirely possible that non-manifold conditions get created inadvertently from operations such as Booleans, blending, sweeping, lofting, shelling, etc.  When TransMagic takes these very large and complex non-manifold solids and saves them out to a manifold modeling format such as Parasolid - these conditions will necessarily need to be "split" at the non-manifold locations.  When solids can’t be created then a surface model is created.

It's simply a matter of communicating two different mathematic models and this splitting cannot be avoided.

Currently, the best format to use for importing into 3D Studio Max is the OBJ file format. Open the file in TransMagic. Save as OBJ.  This will import with the highest quality into 3D Studio Max.

To adjust the resolution of the OBJ output:

1. CTRL + A (Select All)

2. Right-Click and select Change -> Facet Resolution

 

In mold making, among other domains, you may need to convert from a part to the mold geometry. This is done in TransMagic using the Split/Trim function:

• Import a Cube in the correct location in your CAD system
  
• Open the Cube into TM
  
• Import the Part into the same view as the Cube
  
• Select the Part solid geometry and right click ans say use as Split/Trim Geometry
  
• Select the Cube and say Change/Split.

If a previous un-installation did not finalize correctly, you may find yourself in a state where a newer version of TransMagic is asking you to un-install an older version, but the older version can not be un-installed.

WARNING do not continue without reading this!  Modifying the registry can result in corrupted data, or even destroy your installation of Windows.  If you are un-experienced with modifying the registry it is highly recommended that you defer this task to someone who is.

In this state you will need to preform a manual un-installation by deleting a registry key.  Below is the complete list of all un-install keys that TransMagic is looking for.  The most recent keys are listed first.   The un-install keys that TransMagic R8 is looking for are under:

  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

  Then if any of these sub-keys exist, then delete them then reboot:

  {B96CF7E1-FCFF-4450-A26D-DD05B5CE49B8}

  {573DEC1E-7DC2-4525-800A-2E0BCDD1D4BB}

  {754EB164-E474-4D8E-A25E-CDDCBFD83078}

  {F3B44954-06AE-4409-B107-70A2BE903227}

  {754EB164-E474-4D8E-A25E-CDDCBFD83078}

  {ABFB2DE3-5DFF-417A-B5E2-40CFD30D2473}

  {7A5373D4-5BC5-4369-9E4C-09C2BBCB1081}

  {D90CA3EA-87C5-43FB-B6ED-79350544B456}

  {FAA46883-A8F8-4EA8-88C3-081444E2E63F}

  {1C190E4E-8C0B-4FE1-A4E9-09BBA802F8FF}

  {8FE5A80D-7B2C-4B14-9506-0F330B8AF806}

  {AE7C093A-A6D3-4756-83FE-24A66847B50C}

  {B522E507-70F5-4A87-92B0-E6F3B94D8E70}

  {AB9FA4E3-F929-4B19-B1F0-D68A0172ED52}

  {48951166-ECD0-49DE-96E2-A92CB7F21504}

  {C4DF8A91-4344-4F0D-B35B-9C9E48E130CD}

  {71D3DCC5-EFAD-47B4-855B-BD17239C0977}

  {1B3E4B45-1677-4207-B16C-171FA1EBCC3F}

  {6F9CCBAE-3D94-43CE-968C-355B1B8CB100}

  {A310CB75-1CB1-4BB0-B62B-23ECD66C6DD2}

  {296C8B00-F3A9-4974-8B80-E80B65B7378E}

  {837BB49F-A616-4453-959A-55130F14C4D7}

  {0075A2BE-CF23-4852-8A52-46163FD2EB7A}

  {D84D7E04-DCFF-48B5-839F-D25C5CB8289D}

  {AB9FA4E3-F929-4B19-B1F0-D68A0172ED52}

  {48951166-ECD0-49DE-96E2-A92CB7F21504}

  {C4DF8A91-4344-4F0D-B35B-9C9E48E130CD}

  {71D3DCC5-EFAD-47B4-855B-BD17239C0977}

  {8CB52EB4-658F-481D-9512-D91F0F4097C8}

  {95A66AAE-A1BE-40D1-A3EE-F800053D8D90}

  {50608A5C-641E-4D3F-8E6C-809B2A7C9BAC}

  {EC281D96-0A53-495F-821A-A4985C9B420B}

  {39E944B2-5F02-4B09-A1E2-593CD3AE85AC}

  {4EE3B6F4-0308-423E-8386-BF10C13BCE25}

  {B4EB599F-B52A-40B8-9C4F-DE73CED34583}

  {542B3749-20B7-4917-86FE-D96D9C0645B8}

  {D28B8EC8-6EF2-4AC7-9191-E7FC2F5F4E85}

  {966D3EB6-6B50-4C06-8DDA-8C9DB422053E}

  {DE3D3E3C-A9ED-424E-826E-8EE2F0B08A80}

  {31652E0A-477A-4C6D-9049-583D98E21397}

  {9129D9AC-8E06-465A-8BCF-6E19B6649B1F}

  {D1FF9794-1C26-48CF-8777-F9AF24D2B3B7}

  {8807E7C3-1857-4BF6-A6A0-EB33FA93F419}

  {2D6F057B-DCBA-4011-91F9-087EE9E81B23}

  {2d7d2a41-2e22-447a-a7cb-4ffb535d4055}

  {1a1189c4-7780-4198-a62c-26a71cccd5bb}

  {eeed91e4-c6d5-4925-beaa-0f9996fc4d7f}

  {4500b5af-22c2-4061-8ce5-480a7d595763}

  {68b95e59-0eef-44d5-b50e-7d93b4c992b2}

  {88933307-441f-45dd-a8c3-c35822d8ec33}

There are two options in the IGES write settings area that will instruct TransMagic to create the most “benign” IGES file that typically all applications can handle well. The user should try checking the options “Write All Surfaces As Spline Surfaces” and “Write All Curves As Spline Curves”. This should create an IGES file that plays well with any application.

As always the best results are obtained by avoiding IGES altogether.  TransMagic gives you the option to save a CAD Direct file like CATIA or CAD Kernel file like ACIS (*.sat) or Parasolid (*.x_t)  which will insure the highest level of first time success.