“CivilCAD 2016,” he said. “The 64-bit one.”
At 5:47 AM, he rendered the final 3D walkthrough—a feature that used to take 45 minutes and often froze. The 64-bit version completed it in six minutes, smoothly animating the path of stormwater through the proposed channel.
The triangulated surface appeared in 3D, colored by elevation: blues in the low-lying creek beds, reds on the unstable hillsides. Rodrigo rotated the view. No lag. No crashes. civilcad 2016 64 bits
“Told you,” she said. “64 bits. More address space. Less drama.”
Now, Rodrigo opened the software. The splash screen appeared—a familiar bridge silhouette against a stylized sun. Within seconds, the interface loaded faster than he remembered. He imported the raw total station data: 14,632 terrain points. On his old machine, this would have taken four minutes. CivilCAD 2016 chewed through it in 22 seconds. “CivilCAD 2016,” he said
He saved the file: Cacuaco_Drainage_FINAL.dwg . Embedded metadata showed CivilCAD 2016 x64 as the last modifying application.
CivilCAD 2016’s Conflict Analysis module flagged it automatically. A pop-up appeared: “Potential underground obstruction detected. Show section?” The triangulated surface appeared in 3D, colored by
He clicked Topography → Generate TIN (Triangulated Irregular Network) . A dialog box appeared, offering advanced filtering options he had never noticed before. He selected Robust Edge Removal and Slope Analysis . The progress bar moved smoothly, using over 5.8 GB of RAM—something impossible under 32-bit addressing.
Then he noticed something odd.
By 4:00 AM, Rodrigo had redesigned the channel’s alignment, shifting it 14 meters north to bypass the old foundation. CivilCAD recalculated cut-and-fill volumes in 11 seconds. He generated longitudinal profiles, cross-sections at every 20 meters, and a runoff simulation that accounted for a 1-in-100-year storm.