A

AIA CES Credits

AV Office

Abstract Publication

Academic Affairs

Academic Calendar, Columbia University

Academic Calendar, GSAPP

Admissions Office

Advanced Standing Waiver Form

Alumni Board

Alumni Office

Architecture Studio Lottery

Assistantships

Avery Library

Avery Review

Avery Shorts

S

STEM Designation

Satisfactory Academic Progress

Scholarships

Skill Trails

Student Affairs

Student Awards

Student Conduct

Student Council (All Programs)

Student Financial Services

Student Health Services at Columbia

Student Organization Handbook

Student Organizations

Student Services Center

Student Services Online (SSOL)

Student Work Online

Studio Culture Policy

Studio Procedures

Summer Workshops

Support GSAPP

Close
This website uses cookies as well as similar tools and technologies to understand visitors' experiences. By continuing to use this website, you consent to Columbia University's usage of cookies and similar technologies, in accordance with the Columbia University Website Cookie Notice Group 6
Arch ng ramirez arrazola fa25 render

Orbit

Project by Mario Ramirez-Arrazola

The process which foregrounds this analysis is that of orbiting. The process and method of endlessly looping around your model in CAD software. Orbiting in relation to the command Make2D in Rhino is another rabbit hole. Make2D is such a common command that we tend to forget how profound it is; this premise came to me when I started to realize that technically every single frame of movement in Rhino is a drawing, or, every single frame of orbiting can be Make2D’d. Perhaps an even further entrenched normality when we utilize Rhino is the lack of perspective blur in the model. Orbit your model in any which way, everything stays in perfect focus. Then, in order to study and subvert our expectations of Make2D, I wanted to find a way to induce a sense of blur, or of “lag” in our model; how could I “Make2D” blur?