He hesitated. “I’m not a computer person.”
“You don’t have to be,” she said. “Just look at the screen.”
But then came the dread. Mr. Hemlock was a tactile man. He would ask, “What does it sound like?” You can’t render sound. Or could you?
She noticed things she couldn’t see in the plan view. The steel columns, perfectly spaced at 6 meters, created a rhythmic shadow that fell directly across the accessible ramp—a glare hazard for a wheelchair user. In Revit, that was a code compliance issue. In Enscape, it was a human failure.
It was eerie. It was perfect.
“That,” she whispered, “is satisfying.”
The lobby loaded. The sun had set. The virtual lights, tied to Revit’s lighting fixtures, flickered on automatically based on the time of day in her operating system.
That night, Maya saved her Revit model. The .RVT file was 480 MB—large, but stable. Embedded in its metadata were Enscape assets, view settings, and material roughness maps. She closed Revit. She opened Enscape standalone—just to check.