Skip to content

Blog

Fixing Wavy Walls & Sagging Bridges: OrcaSlicer 2.3.2 Flow Tuning

Even after extensive tuning, such as running resonance compensation, 3D printed parts can still exhibit visual artifacts. Common issues include sagging bridges and “wavy” or “bulging” outer wall textures, which persist despite standard calibration efforts. OrcaSlicer 2.3.2 (Release Candidate) introduces highly granular software adjustments to address these specific hardware-extrusion bottlenecks.

This technical guide documents the process of utilizing structure-specific flow ratios and high-density bridging to achieve injection-molded surface qualities.


The Hardware Bridge: Extrusion Consistency

Section titled “The Hardware Bridge: Extrusion Consistency”

Software flow tuning is only effective if your hardware maintains consistent volumetric pressure. For these tests, we rely on the Creality K2 Plus to ensure baseline stability, utilizing eSUN PLA+ to accurately gauge the effect of flow modifications.

Affiliate Notice: Purchasing through these links supports the Minimal 3DP ecosystem at no additional cost to you.


Granular Flow Control: Eliminating the Ripple Effect

Section titled “Granular Flow Control: Eliminating the Ripple Effect”

Previous slicer iterations relied heavily on a global flow rate multiplier. OrcaSlicer 2.3.2 allows users to independently adjust the flow ratio for almost every distinct print structure (outer walls, inner walls, first layer, etc.).

When utilizing a uniform flow rate, the volume required for optimal layer adhesion on inner walls or infill often causes slight over-extrusion on the outer perimeters, resulting in a visible “ripple effect” or wavy interface on thin walls.

By navigating to the Quality tab and checking the “Set other flow ratios” box in the Walls and Surfaces section, we can decouple these values.

  1. Establish Baseline: Determine your optimal global flow rate. In our K2 Plus testing, the baseline flow was 0.98, whereas OrcaSlicer defaults to 1.0.
  2. Isolate Outer Walls: Decrease the flow rate strictly for the “Outer Wall” parameter.
  3. Result: Lowering the flow rate specifically on the outer perimeter eliminates the wavy texture, resulting in a visually smoother face and sharper corners without compromising the structural integrity of the infill.

High-Density Bridging: Structural Overhauls

Section titled “High-Density Bridging: Structural Overhauls”

Bridging unsupported geometry traditionally involves stretching filament across a gap. OrcaSlicer 2.3.2 introduces a setting designed to increase the density of the bridging surface, placing the extruded lines closer together to form a solid sheet.

Using the Unsupported Bridge Experiments Model, we observed the following:

  • Untuned Bridging: Lines are spaced far apart, lacking adhesion, resulting in gaps and severe sagging.
  • High-Density Enabled (Flow = 1.0): The top surface solidifies significantly, but requires further flow tuning.
  • High-Density + Altered Flow: The release notes advise using a lower flow rate paired with higher density. Testing with an erroneously high flow rate produced poor top surfaces. The ideal configuration requires matching the high density (closer lines) with a proportional drop in bridging flow to prevent material pooling.

When pushing high-density bridging and rapid flow transitions on high-speed machines, your Klipper extruder settings must be configured to handle sudden spikes in max_extrude_cross_section, especially if overlapping perimeters occur.

# Minimal 3DP Extruder Baseline (printer.cfg)
[extruder]
# Ensure this value accommodates high-density bridging calculations
max_extrude_cross_section: 5.0
# Ensure your pressure advance is tuned for the specific filament
# to prevent bulging during the rapid decelerations of bridging
pressure_advance: 0.04
pressure_advance_smooth_time: 0.040

OrcaSlicer v2.3.2 Beta 2: The Data-Driven Slicer Overhaul

The community has been waiting for a major update to the OrcaSlicer interface, and v2.3.2 Beta 2 delivers. This release isn’t just about small bug fixes; it represents a fundamental shift toward real-time monitoring and granular control—perfect for those of us who view our 3D printers as precision engineering tools.

In this deep dive, we’re exploring how these new UI changes and technical features can revolutionize your workflow.

[!WARNING]

Before you dive into the new features, remember that this is beta software. To avoid the “Foundation of Sand” issue where your profiles are lost during an update, back up your configuration folder immediately.

Pro Tip: In OrcaSlicer, go to Help > Show Configuration Folder. Zip that entire directory and save it to a safe location.

1. The Improved G-Code Viewer: Real-Time Flow Analysis

Section titled “1. The Improved G-Code Viewer: Real-Time Flow Analysis”

One of the most significant updates in v2.3.2 is the integration of an improved G-code viewer, ported directly from PrusaSlicer.

For the “Engineering Enthusiast,” this is a game-changer. You can now analyze your prints in real-time with specific views for:

  • Actual Speeds: Visualize exactly how fast your toolhead is moving at every point of the model.
  • Volumetric Flow Rates: Identify potential bottlenecks before you even start the print.

2. Fine-Tuning with “Set Other Flow Ratios”

Section titled “2. Fine-Tuning with “Set Other Flow Ratios””

OrcaSlicer now allows you to set individual flow ratios for nearly every feature of your model. This is critical for achieving “Gold Standard” quality.

If your base flow is even slightly off, your entire print can fail. By isolating flow ratios for different parts of the model, you gain the granular control needed for high-performance engineering prints.

3. Modular Printer Agents: Multi-Material Sync

Section titled “3. Modular Printer Agents: Multi-Material Sync”

The new Modular Printer Agent Architecture allows for seamless synchronization with multi-filament units like the AMS (Quitty, Snapmaker, Armor Turtle box). This architecture ensures your slicer and your hardware are always in sync, reducing the friction often found in multi-material workflows.

  • Compact Printer Interface: The new UI lists your printer, nozzle diameter, and bed type in a more informative, streamlined layout.
  • Wi-Fi Connectivity: Management has moved to a more visually pleasing location above the printer settings.
  • New Profiles: Dozens of new printer and filament profiles have been added, ensuring your hardware is supported out of the box.

In the next part of this series, we’ll be doing a technical deep dive into bridging and further testing these new flow rates.

Watch the full video walkthrough here: https://youtu.be/16ZUGGPG-pI


Your support helps me continue developing technical tools and guides for the maker community.

Transparency Note: Some of the links in this post are affiliate links. If you go through them to make a purchase, I will earn a small commission (which helps support M3DP!). You will not pay a penny more.

From Chromebook to Dev Machine - Setting up a Modern GIS & Python Stack

Chromebooks are no longer just for web browsing. With the built-in Linux subsystem, they are now capable of running a professional development environment. This guide walks you through setting up a “Gold Standard” stack: VS Code, Git/GitHub via SSH, Python (via uv), and Containerized PostGIS (via Podman).

First, you need to unlock the ability to run Linux apps on your ChromeOS device.

Open Settings > Advanced > Developers.

Turn on the Linux development environment.

Once the terminal opens, update your package list:

Terminal window
sudo apt update && sudo apt upgrade -y

Don’t settle for the web-based editors; get the full desktop experience.

Install Git: sudo apt install git -y.

VS Code: Download the .deb file (x64 for Intel/AMD, ARM64 for mobile chips) from the official site. Right-click it in your Files app and select Install with Linux.

SSH Keys: Generate a key for secure GitHub access:

Terminal window
ssh-keygen -t ed25519 -C "your_email@example.com"
cat ~/.ssh/id_ed25519.pub

Copy that output and add it to your GitHub Settings > SSH and GPG keys.

Standard pip and make are fine, but for speed and clarity, we use uv (an extremely fast Python manager) and just (a modern command runner).

Terminal window
# Install uv
curl -LsSf https://astral.sh/uv/install.sh | sh
# Install just
sudo apt install just -y

With these installed, you can initialize a project with uv init and use a justfile to automate your chores. Instead of typing source .venv/bin/activate && python main.py, you simply type just run.

Since GIS work requires a database, we use Podman. It is a great “rootless” alternative to Docker that runs smoothly inside the Chromebook’s Linux container.

Install: sudo apt install podman -y

Alias it: Add alias docker=podman to your .bashrc so your existing scripts work without changes.

Spin up PostGIS:

Terminal window
podman pull postgis/postgis

5. Putting it All Together: The Genesis Template

Section titled “5. Putting it All Together: The Genesis Template”

The ultimate goal is to clone a “Gold Standard” template (like the genesis-template) and be ready to code in seconds.

Terminal window
# Clone your template
git clone git@github.com:your-username/your-template.git
cd your-template
# Sync dependencies and start the stack
uv sync
just start

Your Chromebook is now a full-fledged GIS development workstation, running a FastAPI backend, a PostGIS database, and a high-speed Python environment.

  • Port Forwarding: When you run a server on port 8000, ChromeOS automatically maps it. You can access it at localhost:8000 in the Chrome browser.
  • Storage: If you plan on running multiple containers, go to your Linux settings and increase the disk size to at least 20–30GB.

Enhancing Print Strength: A Deep Dive into the GeekDetour BrickLayers Implementation

If you’ve been following the channel, you know I’m a big fan of the BrickLayers concept. By offsetting layer lines—much like a bricklayer offsets joints in a wall—we can significantly improve the mechanical strength of 3D prints, particularly along the Z-axis.

Recently, I updated the Minimal 3DP Web Tool to include a second, more “hefty” implementation: the GeekDetour version. While the original Tenager Technologies script is excellent for its simplicity, the GeekDetour version offers granular control for power users.

However, because this script is more complex, your slicer settings need to be dialed in correctly to avoid errors. Here is everything you need to know to get the most out of this new implementation.

The Core Requirement: “Classic” Wall Mode

Section titled “The Core Requirement: “Classic” Wall Mode”

The most critical setting for the GeekDetour implementation is your Wall Generation mode.

Modern slicers like OrcaSlicer and PrusaSlicer often default to “Arachne” for wall generation. While Arachne is great for variable line widths, it can confuse the BrickLayers script, which relies on consistent pathing to calculate the offsets.

The Fix: Switch your Wall Generator to “Classic” before exporting your G-code. This ensures the script can accurately identify and shift the perimeters without creating pathing conflicts.

Key Setting Differences: GeekDetour vs. Tenager

Section titled “Key Setting Differences: GeekDetour vs. Tenager”

When using the GeekDetour version via the Minimal 3DP web app, you’ll notice a few default behaviors that differ from the original version:

  • Starting Layer: GeekDetour defaults to starting the effect at Layer 3. This ensures your first few layers (the foundation) remain untouched for maximum bed adhesion.
  • Extrusion Multiplier: The script uses a slightly smaller default extrusion multiplier. In my testing on the Creality K2 Plus, this helped manage the “bulging” that can sometimes occur when layers are shifted, though it can lead to slightly more stringing.
  • Z-Hop Integration: This implementation handles travel moves differently to account for the shifted paths. If you see “wispy” stringing, don’t panic—this is a known trade-off for the increased structural integrity.

You no longer need to struggle with Python environments or terminal commands. I have containerized this logic so you can run it directly in your browser:

  1. Slice your model in OrcaSlicer or PrusaSlicer (remember: Classic walls!).
  2. Export the G-code to your desktop.
  3. Upload to the Minimal 3DP BrickLayers Tool.
  4. Select “GeekDetour” from the implementation dropdown.
  5. Download and print.

I’ve personally verified the output by running the web-processed G-code against local Python script results using AI analysis. The movement commands are identical; the only difference is the metadata. Your prints will be just as strong as if you ran the script manually.


Support & Tools

If you found this technical deep dive helpful, consider supporting the lab:

Transparency Note: Some of the links in this post are affiliate links. If you go through them to make a purchase, I will earn a small commission (which helps support M3DP!). You will not pay a penny more.

BrickLayers Without the Code: Get 3D Printed Brick Wall Strength in Your Browser

Featured Image - Bricklayers

If you have been 3D printing for a while, you have likely heard of the “BrickLayers” technique. Originally popularized by CNC Kitchen, this post-processing method significantly increases the structural integrity of printed parts by offsetting layers—just like a real brick wall.

The engineering is sound, but for many makers, the execution has been a barrier. Until now, using BrickLayers required installing Python, managing dependencies, and running local scripts.

Today, I am removing that friction. I have updated the workflow to make it accessible to everyone through a free, browser-based tool.

The Theory: Why “Brick Wall” Patterns Matter

Section titled “The Theory: Why “Brick Wall” Patterns Matter”

To understand why this tool is valuable, we have to look at how FDM 3D printing handles stress.

In a standard print, layers are stacked directly on top of one another. When stress is applied perpendicular to these layer lines, the print is prone to delamination—basically, the layers rip apart because the failure point runs in a straight line down the part.

The BrickLayers concept borrows from masonry. By alternating the perimeter starts and creating an offset pattern (a “running bond”), you interrupt that direct line of stress. The interface between layers becomes complex and interlocking, making the part significantly stronger without changing the material.

While the result of BrickLayers is fantastic, the process was designed for engineers and developers. Running a Python script on your local machine to post-process G-code isn’t difficult if you code, but it is a hassle if you just want to print a strong part.

I decided to revisit this technique with a focus on usability. I wanted to bridge the gap between the engineering concept and the everyday printing workflow.

I have ported the BrickLayers logic into a web application. This means:

  • No Python installation required.
  • No command line usage.
  • Secure processing: The tool streams your G-code through our secure server for processing and immediately sends it back. No files are ever saved to a disk or database.

You can access the tool here: Minimal 3DP BrickLayers Tool

Data Verification: Does it Slow Down Printing?

Section titled “Data Verification: Does it Slow Down Printing?”

A common concern with altering G-code is the impact on print time. Does a more complex toolpath ruin your efficiency?

I ran a comparison using a standard Benchy to verify the data:

  • Standard Print: 29 minutes, 49 seconds

  • BrickLayers (Python Script): 30 minutes, 14 seconds

  • BrickLayers (Web Tool): 30 minutes, 14 seconds

The Result: You are looking at a difference of roughly 25 seconds (less than a 2% increase) for a part that benefits from structurally superior layer adhesion.

  • Slice your model as you normally would.
  • Save the G-code file.
  • Go to the BrickLayers Web Tool.
  • Load your G-code.
  • Let the browser process the file and download the new version.

If you have been reluctant to try this technique because you didn’t want to configure a development environment, give the web app a try. It is free to use, and it brings engineering-grade wall strength to your standard slicer workflow.


Support Minimal 3DP:

Transparency: We may earn a commission when you make a purchase through our links. Minimal 3DP is a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com.