Category CAD

Simplifying AutoCAD Transmittals with eTransmit

The post discusses the challenges of sending and receiving transmittals in Civil 3D and AutoCAD, highlighting common issues like missing external references and font conflicts. eTransmit simplifies this by packaging all dependencies accurately. It provides options for setup, packaging formats, and paths, ensuring recipients receive functional files. A checklist for effective usage is included.

Why CAD Can’t Just Use More Cores aka Multithreaded

Civil 3D and AutoCAD's performance issues primarily stem from predictable sequential math requirements that multithreading disrupts. Unlike parallel tasks like rendering, CAD calculations must remain consistent, as dependencies affect results. Thus, single-core CPU speed is crucial, while more cores benefit background tasks but won't resolve geometry-related delays in CAD operations.

The Browser That Ran Revit (And Why Autodesk Killed It)

In November 2013, Autodesk successfully ran full versions of its applications like Inventor and Revit in web browsers through a partnership with Mozilla, OTOY, AWS, and NVIDIA. Despite the groundbreaking performance, Autodesk chose not to launch the product due to pricing, internal politics, and fear of disrupting existing profits, ultimately opting for limited cloud features instead.

Groundhog Day for CAD Budgets: Will the Subscription See Its Shadow?

The annual budget season is a test of patience for CAD managers, where spreadsheets become battlegrounds as they navigate potential price increases. Expecting flat rates is a fragile hope, but the real threat lies in subtle cost escalations cloaked as 'simplification.' As loyalty wanes quietly, firms must prepare for an 80% solution that balances reliability and cost.

Autodesk Civil 3D Version Mismatch Can Cause Serious Issues

Serious CAD issues, particularly in Civil 3D, stem from simple mistakes, such as using incompatible software versions. Mixing versions leads to proxy objects, causing potential data corruption and performance degradation. To maintain data integrity, projects should consistently use one version throughout their lifecycle and confirm version alignment with all collaborators before file exchanges.