Bill C

It is not the length of the file name. It is the .2u at the end. The system thinks that you want the .2u as the file extension which doesn't fit with the expected .pdf extension so it just fails. You can get around it by simply putting in the .pdf after the desired file name. SG_MK5_LTHV2.2u.pdf The same problem occurs with other file types (ie., dwg or jpg) Admittedly this is not a friendly behavior. System should just take the file name as given, and add the .pdf as an extension. Just some poor logic in the implementation.

Hi Joseph, Please check the Regional Settings for your OS. Control Panel -> Region and Language. In the Formats page, at the bottom is "Additional settings...". Check the settings that you have currently setup for Decimal Symbols, digit grouping symbol, etc. The Tool and Stock tables are processed based on these settings. If you are trying to process a table where the decimals use the comma, while your system thinks Decimal symbol is a period, it will cause a problem. -bill

IRONCAD 2014 SP2 integration with KeyShot only works with KS4. There's a hotfix to make it work with KS5. It's a registry issue. Currently we send the facets data to KeyShot. It is not a specific file format. Raw triangles in a BIP file. The Update functionality is provided by the KS API. Currently, they only support association through structure and name (of part and material). So if you change the structure or naming in your ICS, that will break the update to KS.

Hi Beat, I'd like to clarify my comments below. Basically, we'd like to try to reproduce the CPU/GPU behavior you're reporting using only your graphical data. I'm thinking we can do that with just the HSF data. This eliminates the possibility that any of the behavior is related to other aspects of the IRONCAD application. To more directly address your question, I do not believe there is any logic in our system that says "Part Edges are rendered by the CPU". Part edges are just another graphical object like facets that are send to the rendering engine. That being said, we'd like to better understand the behavior that you are reporting. thanks. -bill

Hello Beat, When you say Part Edges are ON or OFF I assume you mean you change the settings in the IronCAD Rendering page. The way we implement Part Edges is going to make a big difference. The best thing for you to do would be to export as HSF two models for comparison. thanks. -bill

This bug has been fixed and will be in the next release.

J.H., while I am now able to load your original Korean named *.iam files , I don't seem to be able load your new A6.iam Could you please check these files to make sure they are correct? thanks. -bill

This issue should be solved in the final v2013 release. The problem was related to file names being in Korean characters. Regards, -bill

J.H., Could you please create a similar set of Inventor files, but with english names? You can just use simple names for testing (like A6.iam, A5.iam, ...etc) thanks. -bill

Tom, Have you tried the steps outlined in the following article? http://pcsupport.about.com/od/findbyerrorm...ssing-error.htm

As Kevin says. The license activation patches that have been provided are ONLY for the 32-bit versions of IRONCAD/INOVATE. There is not license activation patch needed for the 64-bit versions of the products.

We do not support the ability to move parts based on physical contact. I think this is what you are after Tom. Currently we support mechanisms that are driven through constraints. This is a filed ER to support the additional mechanism capabilities. Cary

Mike, One template has been changed for 7.0.1. It is the drawing A0 size template. As part of this change, PU1 will also need to change a registry setting that specifies the size of the A0 size sheet. Regards. -bill

This is being worked on. Testing phase now. Should be available soon. Cheers. -bill