CutStudio Installation

My favourite vectorial softwares

Vector-based programs, especially those from the Autodesk ecosystem such as AutoCAD and Revit, continue to be my comfort zone due to my architectural background. I also feel familiar with their interface and workflow logic. On the other hand, Rhino is still a bit more challenging for me, as I do not use it very often in my current professional practice.

Advantages and Difficulties

Each program has clear strengths and limitations within my architectural workflow:

AutoCAD
Maximum precision and speed in 2D drafting, although it offers a more limited spatial experience for 3D exploration.

Revit
Excellent for BIM coordination and technical documentation, but sometimes too rigid for experimental or organic geometries.

Rhino
Ideal for complex and organic forms, although integration with BIM workflows can require additional effort.

AutoCAD

As was mentioned before, I usually begin the design process in AutoCAD, developing the plans, proportions, and structural layout of the project in 2D before moving into spatial exploration.

AutoCAD is a vector-based program that allows precise drafting, dimensioning, and scale control. I mainly use it for technical drawing and fabrication preparation.

Main uses in my workflow:

  • Drawing floor plans
  • Creating elevations and sections
  • Applying accurate dimensions and scales
  • Organizing technical documentation
  • Exporting vector files for laser cutting and other digital fabrication workflows

Revit

One important aspect of my workflow is linking AutoCAD drawings into Revit. This allows me to preserve the precision of my 2D drafting while translating the project into a spatial and volumetric model.

Revit is especially valuable for connecting technical documentation with 3D visualization. Based on compatible plans and references, I can quickly build the model and work with real architectural elements through its family system.

Main uses in my workflow:

  • Linking AutoCAD drawings into BIM workflows
  • Creating accurate 3D volumetric models
  • Working with architectural families and real building elements
  • Developing technical documentation and coordinated views
  • Combining spatial visualization with construction logic

Rhinoceros

Let’s develop some details in Rhino. The micro-architecture proposal should include interactive elements that encourage play and physical interaction.

The idea is to incorporate components such as small games, movable manual mechanisms, or elements that users can touch, turn, climb, or manipulate. This approach transforms the structure into a more dynamic and engaging spatial experience, especially for children.

Modeling Steps

1. We started by creating a Sub-D geometry with a 4-4-4 subdivision in the X, Y, and Z axes, shaping the climbing hold and adding a support base.

2. A reference plane was generated to create a flat surface using Boolean Split, allowing the piece to fit correctly onto a wall.

3. The dimensions were adjusted according to ergonomic considerations for a 6-year-old child, ensuring a comfortable grip and interaction.

4. We modeled a bolt system and applied boolean operations to create the internal space required for the assembly and integration of an LED push button.

5. Finally, guide geometries were added to achieve a precise fit between the two components, preparing the model for 3D printing and future mold fabrication.

Photoshop

Let’s make some post-production in Photoshop. As a raster-based software, it is very useful for improving images, adjusting colors, textures, lighting, and adding visual details to architectural representations.

One of its main advantages is the possibility of working with layers, allowing easy manipulation, testing different compositions, and refining images without affecting the original file.

I also use external PNG libraries to enrich architectural visualizations with people, vegetation, shadows, and atmosphere elements.

Useful references:

  • >Skalgubbar – Free architectural cutout people
  • >Meye.dk – Trees and vegetation resources for architectural visualization

Post-Production & Visualization and Image Size Reduction

My favorite phase is definitely post-production and rendering. When I'm short on time, I usually work with Lumion using the LiveSync feature with Revit. It's incredibly efficient because I can see the materials and lighting change in real-time as I adjust the model. Once the base render is ready, I take it into Photoshop for post-production. This is where the project really comes to life—adding textures, atmosphere, and those small details that make the image feel "alive." The only struggle here is the file size; Photoshop files can get very heavy, which isn't ideal for web documentation. To keep everything organized for presentations, I use InDesign. Instead of pasting images, I link them to keep the file manageable. However, for this Fab Academy documentation, I’ve had to be extra careful with web optimization. I’ve reduced the image sizes and set the resolution to 72 DPI, ensuring that the webpage loads quickly without losing the essence of the design. This allows me to overlay my visuals onto the website template smoothly without crashing the browser.

Conclusions

This assignment reinforced the importance of combining both 2D and 3D design tools within the architectural workflow. Experimenting with different software allowed me to understand how each program contributes to precision, spatial exploration, visualization, and technical development.

As an architect, working between AutoCAD, Revit, Rhino, and post-production software is essential to communicate ideas clearly and efficiently. The process of modeling, rendering, and image optimization also highlighted how visual communication plays a fundamental role in contemporary architectural practice.

Overall, I hope this experience will allowed me to integrate creativity, technical control, and digital experimentation while continuing to develop my own professional design methodology.