Jump to content

Bill C

IronCAD Employee
  • Posts

    273
  • Joined

  • Last visited

Posts posted by Bill C

  1. 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.

  2. 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

     

     

    Thanks Cary for pointing this out. I will pass it on and this something I have failed to look upon. I will correct the pdf guide. By the way, if I load the StocktblMetricEU.txt as it is, it gives me flag as error in line 558 message but doesn't occur with StocktblMetricUS.txt. I have read both txt files and the difference between them is that the EU version used comma as decimal separator, while the US used the period as decimal separator. Could this be the cause?

     

    Again, regards and thanks - joseph

    38247[/snapback]

     

  3. 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.

     

     

    A few questions on ICAD and Keyshot:

     

    Can the Keyshot integrator for ICAD be configured to work with Keyshot 5 or is their going to be a new translator for V5? Currently, ICAD will only work in Keyshot 4...(but I'm not ruling out operator error).

     

    Also, how is ICAD sending its data to Keyshot...is it exporting the file (as a .step, xt, obj, etc.) and then importing (or is it something completely different)? The reason I ask is that previously when I had to export /import files, (usually high piece counts with assemblies and subassemblies), more often than not  I would be missing pieces (or entire assemblies) in KS...very frustrating. The integrator seems to have gotten rid of that problem...(although I still get the occasional exploded part showing up, but that's rare).

     

    How does the ICAD model stay linked to KS? If you do a "save as" on the KS file you lose the ability to edit and update the from ICAD. It seems only the original file keep this functionality.

     

    Thanks,

     

    Mike

    38091[/snapback]

     

  4. 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

    37463[/snapback]

     

  5. 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

     

     

     

     

    It's now time for the acquisition of new notebooks for our company. For a long time we have been wondering about whether it would be worth investing in Quadro graphics cards, or whether the GeForce cards would work just as well or possibly even better.

    We got the hint that Quadros would be better at OpenGL while GeForces would shine with DirectX but apart from that, there seemed to be very little solid info on that subject.

    Luckily, Schneider in Germany lent us two notebooks that were absolutely identical but for the graphics cards, so we were able to directly compare a Quadro K1000 to a Geforce GTX770.

    We are always working with smooth shading and drawing parts edges and we usually have a lot of transparent parts in the scene. So that was the base for our tests.

     

    The interesting outcome was that we couldn't see a significant difference between the two cards. The quality of the images rendered by the two cards were identical, pixel by pixel even, as far as we could say, whether we compared under OpenGL, OpenGL2 and DirectX. We also used tools to check the load on the GPU and on the CPU.

     

    Our findigs:

    Transparency rendering was best (but for an annoying bug) AND fastest under OpenGL.

    Part edges are rendered by the CPU and not by the GPU. An this is what limits the speed. As long as we rendered part edges while rotating the scene, one CPU core would go to 100% while the GPU load rarely exceeded 25%. As soon as we switched part edges off, the frame rate would go up several times, CPU load would go down and GPU load go up to 60-90%. According to a (older) white paper by Nvidia, one of the differences between Quadro and Geforce cards should be, that the former are able to render edges. It appears that IronCADs rendering engine doesn't make use of that capability of the Quadro cards. Or at least, we haven't found a setting the would put this burden on the GPUs shoulders. IronFolks, can you comment on that? 

    Our conclusion: at the moment, it looks like the frame rate when rendering part edges is limited by the CPU not by the GPU, so it seems more beneficial to invest in a faster CPU than in a great graphics card.

     

    Any comments and contributions are welcome, but please don't ask me for a protocol of all the settings we've tried. We were three people investing maybe 20 hours in total, but still, there so many possible combinations,that we could only test a small fraction.

     

    Cheers, Beat

    37315[/snapback]

     

  6. 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

  7.  

    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

×
×
  • Create New...