Troubleshooting
Fix common AnansiBuild issues: RohoSuite tab missing, preview slow, glass not separating from frames, wrong AMS colors in Bambu Studio, settings not persisting.
If something's not working, find your symptom below. If nothing here matches, email support@rohosuite.com with a description and (if you can) the project name and Revit version.
The RohoSuite tab isn't showing up in Revit
A few things to check, in order:
- Did you close all Revit sessions before installing? The installer can register the add-in but Revit only reads the addin folder at startup. Quit every Revit window, then relaunch.
- Is the bundle in the right place? Open File Explorer and navigate to one of these locations:
- C:\ProgramData\Autodesk\ApplicationPlugins\ (all users)
- %AppData%\Autodesk\ApplicationPlugins\ (current user)
You should see a folder called AnansiBuild.bundle with a PackageContents.xml file at its root. If you don't, reinstall.
- Are you on a supported Revit version? AnansiBuild ships with builds for Revit 2026 and 2027 only. Earlier versions aren't supported.
- Did Revit silently fail to load the add-in? Revit doesn't show a UI list of failed add-ins, but it logs every load attempt to the journal file. Check the most recent file in
%AppData%\Autodesk\Revit\Autodesk Revit 2026\Journals\(orAutodesk Revit 2027\Journals\for Revit 2027). Open it in any text editor and search forAnansiBuild— if you see an exception, stack trace, orJrn.AddInfailure on its line, that's the source. Common cause: a corrupted bundle or a missing dependency. Reinstall to fix. - Confirm the add-in is registered. In Revit, the Add-Ins ribbon tab → External Tools dropdown should list any installed external commands. AnansiBuild's button lives under its own RohoSuite ribbon tab rather than under External Tools, so absence here isn't itself a failure — but presence of other add-ins confirms Revit's add-in loader is working at all.
"Please run this command in a 3D view"
AnansiBuild needs a 3D view to extract geometry. You'll get this message if you click Export 3MF from a plan, section, elevation, or sheet view.
Fix: Open or create a 3D view (Default 3D View works fine), make it the active view, and click Export 3MF again.
My section box isn't cropping the export
The section box in your active 3D view should automatically clip the export. If it's not:
- Confirm the section box is enabled. In your 3D view, the Properties panel should show "Section Box" as checked. If you can see the model fully, the box is off.
- Confirm the section box actually crops something. A section box that contains the entire model isn't cropping anything — it's just a box around all the geometry.
- Verify in Revit's view properties. With your 3D view active, the Properties panel should show the Section Box parameter as checked. If it's checked there but the export isn't being clipped, toggle it off and back on, then re-run the export — sometimes Revit needs the nudge to re-emit the box bounds.
The preview is slow / Revit feels sluggish
Large models (whole-building, full MEP, detailed topography) take time to extract and render. A few ways to speed things up:
- Use a section box to limit the export to one floor or one wing.
- Hide categories you don't need in the Revit view before exporting (MEP and topography are common offenders).
- Toggle categories off in the Preview Window. This rebuilds the preview without those categories. Combined with the previous bullet, you can shave a lot of time off the preview generation.
- Close other Revit views. Each open view holds its own geometry cache. For a big export, having only the active 3D view open helps.
If the preview is consistently slow on small models, something else is going on — email support with a description.
The colors are wrong in Bambu Studio
Two layers to this:
The colors look right but the filaments are wrong: AnansiBuild assigns each category to a stable AMS slot. You need to tell Bambu Studio which physical filament is in which slot. Open the Prepare tab → click the AMS panel → match the slot icons to the filaments you actually have loaded. AnansiBuild does the slot assignment; you do the filament-to-slot assignment in the slicer.
The colors are wrong in the actual viewport: Make sure you're opening the 3MF in the latest version of Bambu Studio. Older versions don't fully read the multi-color metadata. Update Bambu Studio and re-import.
If a category that should have its own color is showing up the same as another category, see "Glass isn't separating from the frame" below.
Glass isn't separating from the frame
AnansiBuild splits windows and doors into glass and frame parts based on material name keywords: glass, glazing, transparent, or clear. If your custom Revit families use a non-standard material name for the glass part, the glass gets routed to the frame category.
Fix: In your Revit project, open the Materials browser and either:
- Rename your custom glass material to include one of the keywords above (e.g. rename
MyTransparentv3toMyTransparentv3 Glass), or - Edit the family to use one of Revit's standard glass materials.
After the rename, click Export 3MF again. The glass should now show up as a separate WindowsGlass or DoorGlass category in the Preview Window.
A scale that should fit shows red
If a scale that you know should fit on your printer is marked as not-fitting:
- Confirm the right printer is selected in the PRINTER dropdown. The fit indicator uses the selected printer's bed dimensions, not your default.
- Check the model bounds. The Model card shows the model's overall dimensions in feet. If they look wrong (e.g. a building reading as kilometers wide), there's a stray element far from origin in your Revit model — find and delete it.
- Try a custom scale. If the standard scales don't quite fit, use the Custom box to type an exact ratio.
The exported 3MF won't open in Bambu Studio
Bambu Studio is the best-supported slicer. If the file opens with errors or shows nothing:
- Update Bambu Studio. Older versions had quirks with non-Bambu-generated 3MF files. Latest version is recommended.
- Check for a corrupt export. A 3MF that's only a few KB is suspicious — full models are usually 1 MB+. If it's tiny, your Revit view might be empty (everything hidden, all categories disabled, or section box clipping out everything visible).
- Try PrusaSlicer or another 3MF-aware tool to confirm the file is valid. If it opens elsewhere but not Bambu Studio, that's a Bambu Studio bug — let support know.
Boolean operation failures / weird missing geometry
The export log will sometimes report "Boolean operation failed" for specific elements. This usually means that element has degenerate geometry (zero-thickness faces, self-intersections, very small details). The element is skipped from the export but the rest of the model continues.
To fix the element:
- In Revit, isolate the element and inspect it in the Family Editor.
- Look for paper-thin extrusions, overlapping geometry, or sub-millimeter features.
- Rebuild the suspect part with simpler geometry.
The export proceeds despite these warnings — you don't need to fix every one before exporting. But if a critical visible element is missing from your print, this is the most likely cause.
Sliced pieces are named "Ground Floor" / "Floor 2" instead of my Revit level names
This is expected, not a bug. AnansiBuild names sliced pieces sequentially from bottom to top — Ground Floor, Floor 2, Floor 3, and so on — regardless of whether you used + Level or + Manual cuts, and regardless of what your Revit levels are named. Even if your Revit project has levels named "Lobby", "Mezzanine", and "Penthouse", the export pieces will still be Ground Floor, Floor 2, Floor 3.
The exported files follow the same pattern: {ProjectName}GroundFloor.3mf, {ProjectName}Floor2.3mf, etc. (Spaces become underscores in filenames.)
If you want different piece names, rename the files in File Explorer after the export, or rename the parts in Bambu Studio after import. Level-name propagation is on the long-term roadmap.
My settings aren't being remembered
Settings live in %AppData%\RohoSuite\AnansiBuild\settings.json. Possible issues:
- Permissions. If your
%AppData%is on a network drive or a managed corporate machine, AnansiBuild may not have write access. Settings reset every session in that case. Talk to your IT admin about granting write access to that one path. - The file got corrupted. Delete
settings.json— AnansiBuild will recreate it from defaults on next launch.
After installing an update, things behave oddly
Some updates change file formats or default behaviors. If the new version is acting strange:
- Quit Revit fully.
- Delete
%AppData%\RohoSuite\AnansiBuild\settings.jsonto reset preferences. - Relaunch Revit.
The welcome dialog appears every time, not just on first launch
The welcome dialog should only appear once, ever. If it shows up on every export:
- Permissions on
%AppData%. AnansiBuild can't persist the "have you seen the welcome screen" flag if it can't write to%AppData%\RohoSuite\AnansiBuild\. Common cause: managed corporate machines or a network-redirected%AppData%. Have your IT admin grant write access to that path. - Corrupted settings file. Delete
%AppData%\RohoSuite\AnansiBuild\settings.jsonand let AnansiBuild recreate it on the next launch. The first run will show the welcome dialog one final time, then never again.
The ☕ donate button doesn't open my browser
The donate buttons fire Process.Start on the URL with shell-execute, which uses your default browser. If clicking does nothing:
- No default browser configured. Open Windows Settings → Apps → Default Apps and confirm there's a default for "Web browser." Set Edge / Chrome / Firefox as default.
- As a fallback, you can copy the donation URL —
buymeacoffee.com/tiktokarchitect— and paste it into your browser manually.
A category I expect to see in the preview is missing entirely
The Categories tree only shows what's actually visible in the active Revit 3D view. If you're missing Site, MEP, Topography, or any other expected category:
- Check Visibility/Graphics in Revit. That category is probably hidden in the active 3D view. Unhide it (V/G or the Reveal Hidden Elements lightbulb), then re-run Export 3MF.
- Check workset visibility if you're on a workshared model. A whole worskeet can be hidden in the view.
- Check phase filtering. If the category's elements are in a different phase than the view's phase filter allows, they'll be excluded.
The 3MF opens but pieces are positioned wrong
AnansiBuild centers the model on the export's bounding box, but if multiple pieces look mis-aligned (e.g. floors don't stack on top of each other in Bambu Studio), check:
- Project base point vs. survey point. AnansiBuild uses your model's project origin, not the survey point. Make sure your geometry sits near the project base point in Revit. Far-from-origin elements can produce odd centering.
- Stray geometry. A single rogue element 500 m from the rest of the model can throw the bounding box off and make everything else look misplaced. Check the Model card's dimension readout — if the numbers are wildly larger than the actual building, hunt down the stray.
Revit crashed during export
If Revit hard-crashed during a 3MF export:
- Capture the journal file. Revit writes a journal of every action to
%AppData%\Autodesk\Revit\Autodesk Revit 2026\Journals\(or2027for Revit 2027). The most recent file (sorted by modified time) is the one from the crashed session. - Email support (
support@rohosuite.com) with the journal file, your AnansiBuild version, and a description of what you did right before the crash. - Don't send the .rvt file unless asked — the journal usually has enough to diagnose. Sending the project up front bloats the email and may not be needed.
Where do I find log output?
AnansiBuild writes detailed log output via Debug.WriteLine, which is captured by DebugView++ (free Microsoft tool) or by Visual Studio's Output window when AnansiBuild is run from a debugger. For users without dev tools:
- The Notices card in the Export Summary dialog is the user-facing surface for warnings (Boolean failures, degenerate geometry, change-log entries from the export pipeline). If something noteworthy happened during a successful export, it shows up there.
- Errors that prevent export appear in a TaskDialog with the error message. Take a screenshot and include it when reporting.
I think I found a bug
Send the following to support@rohosuite.com:
- AnansiBuild version (shown in the welcome dialog or About menu)
- Revit version (2026 or 2027)
- A description of what you did and what happened
- If possible, a small Revit project that reproduces the issue
- Any error messages exactly as shown
The more reproducible the bug, the faster it gets fixed.
Where to next
- Just installing? → Installation
- Need a refresher on the workflow? → Getting started
- Don't see your question here? → FAQ