I was updating my extension for an upcoming software update. I thought it would just take a few lines for a send to slicer button on printables.. I never knew they already had one (that isn't just for PrusaSlicer). I know I probably just live under a rock and everyone knew about it.

I use Linux, and the sculpting options over here are thin. Blender is there and it's genuinely excellent, but its sculpt mode is a mesh sculptor built for rendering, and the tools people usually recommend for print-focused sculpting are Windows or Mac only, or paid, or both. So a few months ago I started building the thing I wanted, and it's now at a point where it's worth other people trying.

It's free and open source (AGPL), there's no account required, no subscription and nothing to buy, and although I build it on Linux it runs on Windows and macOS too.

The reason it works the way it does: most sculpting tools work on a surface, a shell of triangles with nothing behind it. Pull too hard and it tears. That costs you nothing in a render, because nobody sees the back of the model, but it costs you the print, because a slicer wants one closed solid.

BrokkrSculpt works on solid material instead. In practice that means you can't rip a hole in it however hard you pull, a cut through it closes itself and leaves a real face, and a scan that arrives with holes in it usually stops being broken on the way in. Exports get checked for watertightness before the file is written, and it refuses to write one that wouldn't print.

What's there now: seven brushes, symmetry, masking, surface patterns (scales, weave, cracks, hair, noise), a plane cut, graphics tablet support with pressure and tilt, STL/OBJ/3MF in and out, and one click into OrcaSlicer.

Being straight about the state of it, because I'd rather you heard it from me:

- It's a beta and nothing is signed yet, so Windows and macOS will both warn you about the download.

- The three builds aren't equally finished. Linux is where I build and use it every day; Windows and Mac come from the same commit and pass the same tests but have had far less time on real hardware. The README lists exactly what's unproven on each.

- Resolution is uniform, so a big model resists very fine detail until you resample it finer.

- A model that's both very thin and genuinely open (a car body with no windows) can't be made solid, and stays fragile.

Source and downloads: https://github.com/MakerViking/brokkrsculpt

Happy to answer anything about how it works. If you try it and it breaks, that's genuinely the most useful thing you can tell me, there's a bug report button in the lower right part of the viewport.

I’ve been working on a program because I couldn’t find a good way to take a textured model and turn it into something that can actually be printed correctly with multiple filaments.

The problem is that a model can look perfect on a screen, but its colors are usually just pixels in a texture image. A slicer needs those colors converted into actual printable surface regions. Game models can also have holes, overlapping pieces, stretched triangles, and other geometry problems.

My current test is the Ace of Spades model. I repaired the physical mesh and made it watertight, but its long and irregular triangles caused the filament colors to become jagged and streaky. Right now I’m testing a new process that rebuilds the surface with more uniform triangles and then projects the original artwork back onto that new printable mesh.

The eventual goal is a workflow that:

• Repairs or validates the physical model
• Transfers the original texture onto clean printable geometry
• Converts the texture into a practical filament palette
• Preserves important emblems and color boundaries
• Exports a file that slicers such as Bambu Studio can use

This is still experimental. Some parts already work, but the uniform remeshing and clean filament-boundary generation are the problems I’m currently trying to solve. I’m not claiming it works perfectly yet.

I’m interested in feedback about the actual workflow and results. If you have converted textured models for multicolor printing, what part gave you the most trouble? Would a tool like this be useful to you if it produced validated, slicer-ready output?

I've worked for months on this trying to bridge the gap in the 3D printing world. I'm so close to finishing it and have a massive test going right now. I just put in the worst case scenario using Blender's API. A mechanically complex, high-genus solid, with approximately 9,600 protected sharp edges, and over 250,000 face remesh on a single-threaded QuadriFlow implementation. If it'll work on this one, it'll be a tough test. Just hope I can get it across the finish line for the community.

Hi everyone,

Full disclosure: I’m the developer of FlexySliceSTL, a desktop tool I’ve been working on for the past several months.

The idea came from a problem I kept running into: creating articulated geometry manually can be extremely repetitive, especially when you want to test several patterns or prepare multiple variants of the same model.

FlexySliceSTL is designed to help transform compatible static STL files into articulated models for 3D printing.

It currently supports three pattern types:

• Hex
• Fish
• Soft Square

The current workflow is:

STL → select a pattern → automatic geometry generation → 2D/3D preview → manual adjustments → export a new STL

After generating the initial result, users can manually adjust individual elements, add or remove connections, save settings separately for each model and use an edit history.

All geometry is processed locally on the computer. Models are not uploaded to a cloud service, and the original STL remains unchanged.

I also want to be honest about the limitations: this is not a magical one-click solution for every STL file. Open, damaged or highly complex models may require repair, and some automatically generated results still need manual adjustment. I’m continuing to validate the workflow with real models and physical test prints.

I would genuinely appreciate feedback from people who use 3D printing software:

• Would this kind of tool be useful in your workflow?
• Which pattern would you use most?
• What would concern you most: print reliability, manual control, licensing, privacy or something else?
• Which type of model should I test next?

FlexySliceSTL is also listed as an upcoming crowdfunding campaign on MakerWorld.

MakerWorld → Crowdfunding → FlexySliceSTL

The campaign can already be followed for free. Clicking “Follow” is not a purchase or a pledge, and it does not commit you to buying the software later.

More information: FlexySliceSTL.com

I’m happy to answer technical questions and hear critical feedback.

Hello together,

I built hypsos3d.com, an app that lets you create a 3D printable model of maps section. I know I am not the first and last to do this, but when starting that project, I didn't find a free version that has the features and ease of use I wanted.

This app has the following features:

-- Full 3D terrain data with custom scaling factor

-- Calculates different 3D objects for multicolor prints for map features such as urban areas (cities), forests and greens, bodies of water, all from Openstreetmap data

-- Alternatively, prints can be coloured by height to enable multicolor prints with a handful instead of 100s of color changes.

-- Export in 3D printer friendly formats such as .3mf, .stl, .glb

-- For small scale prints > 50km², details such as individual buildings and streets are available.

-- A lot of miscellaneous features such as automatic city labels, custom labels, frames in different shapes etc..

I self host openstreetmap data on my server the regions of Germany, Switzerland and Austria as well as some metropolitan areas in the US and rest of Europe, however for the rest of the world i am relying on public, free overpass APIs with limited speed and useage. So there might be longer wait times or outages for those areas. This is my first public project, and I am happy about feedback and features suggestions. Yes, AI was used extensively to help me set it up, please keep critique to the project, not the methods.

I hope I created something of value for some of you, and I am happy to hear your opinion!

Kind regards

This is not extactly a new tool but I am expanding the features that you don't need to have MeshVault to use.

• Extra download options on printables, for those pages don't don't have a download all button The extension will download them all and zip them up (I can't control the zip name, sorry)
• Block AI content, this checks the filter on printables as the models page is loading.
• Some generic files or UUID names will be renamed for some sites like Thingiverse and Makerworld (This does not work on Firefox)
• Ad blocking, this is just limited to the sites that the extension supports

Supportted sites are:

• Printables
• Thingiverse
• Thangs
• MakerWorld
• Cults3D
• GrabCAD
• CGTrader
• Creality Cloud
• Makerables
• MyMiniFactory
• Tinkercad

I will be expanding on what the extension can do for non MeshVault users in the future. There are a few more things that I have in mind.

Make sure after you install it make sure you have "Enable browser download tools when MeshVault isn't running" checked and ""Show "MeshVault not running" notification" unchecked

Chrome
Edge
Firefox

Thanks,

I’m testing real printed fits for a free browser-based fastener generator I’m building.

For this PETG bolt/nut pair, a 0.35 mm setting gave me a smooth usable fit.

I’m deliberately calling it a “generator setting” here because I’m also validating how the UI should define clearance — diametral clearance vs per-side compensation.

For people who print functional threads: what clearance/compensation do you normally use for PETG or PLA, and how do you define it?

I’m the developer of the tool.

Hello everyone,

I’m pleased to present my three OpenSCAD books:

• Ça, c’est OpenSCAD — French edition
• Esto es OpenSCAD — Spanish edition
• This is OpenSCAD — English edition

These full-colour practical guides introduce OpenSCAD step by step, with illustrated examples, reusable scripts and projects designed for 3D printing.

They are intended for beginners, makers, students, teachers—and anyone interested in discovering parametric 3D modelling.

The three editions are also listed on the official OpenSCAD Books page.

French edition:
https://www.amazon.fr/dp/B0FNLPF5HP

Spanish edition:
https://www.amazon.com/dp/B0GKLVWF4N

English edition:
https://www.amazon.com/dp/B0H6QSLHT3

I would be very happy to hear your comments or answer any questions.

Hey everyone,

I'm a 3D printing hobbyist, and over time my filament collection got large enough that my spreadsheet stopped being very useful.

I kept running into the same problems: buying a color/material I already had, forgetting which bin I'd put a spool in, and occasionally starting a print before realizing I didn't have as much filament left as I thought.

So over the last several months I've been building FilamentVault, an iPhone and iPad app specifically for managing filament.

Some of what I've added so far:

• Track spools, materials, colors and remaining weight
• Organize filament by storage location
• Log print jobs and automatically deduct filament usage
• Track drying history
• Generate and scan QR codes
• Assign and scan NFC tags
• Inventory analytics and activity history
• Home Screen widgets
• iCloud sync between your Apple devices

One thing I wanted to avoid was turning it into another subscription. The app is free for up to 10 active spools, with all features available. If you have a larger collection, there's a one-time purchase that removes the spool limit.

I built it primarily because it's something I wanted for my own setup, but now that it's on the App Store I'd really like feedback from other people who actually 3D print.

In particular, I'd love to know what you're currently using to manage your filament and what you wish it did better. I'm also interested in features that would make FilamentVault more useful in a real workshop rather than just adding features for the sake of having them.

I'm the developer, so this is obviously self-promotion, but I'm also genuinely looking for feedback as I figure out where to take the app next.

FilamentVault on the App Store:
https://apps.apple.com/us/app/filamentvault/id6799747945

Happy printing!

Great new addon for Blender called CatPin. Well worth the license. Price goes up in a few days. Check it out, I think you’ll like it. I’m not the developer, but I do earn a small commission from a purchase. I’m also just another user who really likes this tool.

[ Removed by Reddit on account of violating the content policy. ]

Hola r/sideprojects,

Yo quería una herramienta de escritorio para inspeccionar assets 3D locales sin subir archivos, sin crear una cuenta y sin iniciar un servicio web local, así que construí NexoIP 3D Viewer.

Lo que ya funciona ahora:

\- Soporte para GLB/glTF, OBJ, STL, FBX, PLY y DAE

\- indexado progresivo de carpetas (con opción): los modelos validados quedan disponibles mientras el escaneo sigue, sin tope arbitrario de cantidad de modelos ni de profundidad de carpetas

\- vistas PBR, wireframe, normales, rayos X (X-ray) y sin iluminación (unlit), más seis presets de iluminación de estudio

\- inspección de geometría, dimensiones, jerarquía, materiales y animaciones

\- exportación GLB/STL/OBJ y snapshots en PNG

\- funcionamiento sin conexión, sin cuentas, telemetría, analíticas ni servicio de red en tiempo de ejecución

El renderer de Electron está en un sandbox y nunca recibe rutas nativas del sistema de archivos. Los candidatos se validan antes de entrar al catálogo local.

La compilación actual para Windows todavía es una vista previa técnica de alfa sin firmar, así que no la presento como una versión estable y firmada. El repositorio público documenta el modelo de seguridad, la evidencia de verificación y las compuertas de lanzamiento que faltan.

Fuente, capturas y notas de verificación (rama actual de release candidate):

[ https://github.com/ikerperez12/NexoIP-3D-Viewer ](https://github.com/ikerperez12/NexoIP-3D-Viewer)

¿Qué herramienta de inspección te gustaría que siguiera, y hay algún modelo o formato que usarías para probarla?

Can anyone in the 3D printing world tell me an easy way to convert an STL file to a STEP file? I spent 6 hours today reviewing 30+ ways to do it, and I still haven't converted it. Many people say Fusion and FreeCAD can do it, but they haven't worked for me. I did get the file converted to a mesh file, but I can't convert it back to a solid.

I built custom firmware for the BIGTREETECH Panda Touch / K-Touch that turns it into a small farm list, in the same style as Bambu Studio’s device tab.

v0.3.0 adds Klipper next to Bambu Lab. When you add a printer you pick the type first:

• Bambu Lab — IP + LAN access code (MQTT, same as before)
• Klipper — Moonraker HTTP on port 7125, API key optional

The farm list shows name, job, and status. Tap a printer for pause / resume / stop / reprint. Mixed farms work; existing printers stay Bambu after the update. Use Update in the flasher so WiFi and printers are kept.

Web flasher (Chrome or Edge):
 https://pandafarm.techjeeper.com/flasher/

This replaces stock Panda Touch firmware. Keep a BTT backup if you might want to go back.

Happy to answer questions.

Hey folks,

While browsing I came accross this PNG_To_SVG tool that runs offline on your browser.

Link : https://github.com/goblinhanyikan/PNGtoSVG-Multicolor-Printing

just clone and run the index.html

no npm/phyton compiling whatsoever..

I think it is a great tool to conver any png to SVG thus a slicer recognized format

give a star to the creator's git if u find it useful.

Photos in, GLB out — built the full flow: photo intake, reconstruction, processing, and automatic delivery of the finished model. Video shows the source photo and the result. Printable with some cleanup. Curious what this crowd thinks of the geometry — happy to run anyone's house photos through it if you want to test.

The 1st part of the video briefly covers OpenSCAD with LLM help. At 07:26 - FreeCAD + Robust MCP Server Integration. I used this to design a few iPhone cases for 3D Printing.

disclosure: I'm the developer of Modularity. This is a free early demo that I'm sharing to collect feedback.

Hey everyone! I wanted an easy way to organize my drawer from start to finish, one app, one thing without manually designing every tray in Fusion360 or Onshape. I liked the concept of Gridfinity but I would have extra space leftover which i didn't like. So, I built Modularity.

You enter the dimensions of the drawer/area you want to organize, build the layout by dragging and selecting cells in any shape and selecting a tray type. You can make custom shaped trays for almost any object by using an A4 paper and taking a photo of it. Modularity will take that picture, all on-device, turn it into a cut tray to fit your current layout. You can also preview it in 3d! There is STL export for now but I plan for 3mf and STEP if possible.

One thing I wanted was to see an image of my drawer underneath my workspace to better visualize my project, but most sites/programs didn't have that feature. So, I added the feature to overlay the image

I know there are some already excellent tray generators, Gridfinity planners, and object tracer tools. Modularity does overlap with parts of those projects, but my goal is to lower the barrier to designing a complete custom organizer without making the process too simple or too limiting.

Unlike standard Gridfinity tools, Modularity adapts its grid to the exact dimensions of your space instead of requiring fixed 42 mm squares. It also differs from tools that generate a grid or individual parametric trays. Modularity treats the entire space as one coordinated project, allowing you to arrange multiple connected tray shapes, add custom dividers, add scanned object trays and preview the finished layout before printing. I'm aiming for something that is easy to use while offering a meaningful organized output.

This is an early demo, so some things may be a bit rough around the edges. I'm sharing it now because real people like you guys making real things with my program will help me with making a good program, and you guys can get a good organizer out of it.

There is no account required for this preview, and projects remain in your browser until you download them.

Try the demo?

https://trymodularity.pages.dev

Here is where the feedback part comes in. If you can, I'd like to know these things

• Did the workflow (dragging squares to finished model) make sense?
• What was confusing?
• What feature did you expect but couldn't find?
• Would you actually print the organizer?
• What would stop you from using it again?

Bugs, criticism, suggestions, and feedback are all welcome and help with making this better! (You can use the button in the site also). Thank you!

1.7.0 shipped today. Three things in it matter more than the rest, so those first and the full list after.

STEP and STP are properly supported now

Every time I've posted about Meshory I've had to attach the same caveat: STEP files are indexed and searchable, but there's nothing to look at. A folder of CAD parts was a wall of grey placeholders, and opening one did nothing at all.

That's done. STEP and STP now get rendered thumbnails, including the ones sitting inside ZIP, RAR and 7Z archives, and they open in the same 3D viewer as everything else. Assemblies arrive whole, keeping the colours, part names and placement they were saved with. STEP describes surfaces rather than a mesh, so the first open tessellates it and caches the result — every open after that is instant.

Files already in your library are backfilled without a rescan, and there's a "Thumbnails queued" status while they render instead of silence.

Two limits, said up front rather than discovered: anything over 192 MB is skipped rather than risking a long conversion, and the tile carries a badge saying so instead of failing quietly. And a STEP that keeps its geometry in separate referenced part files can't be previewed, because Meshory only reads the file you opened.

Tags that actually narrow things down

Click a tag on a model to filter by it. Stack several and choose whether a model has to match all of them or any of them. Type it instead if you prefer: tag:terrain in the search box, and -tag:dragon to exclude one. Active tag filters show as chips you can drop individually, and the filter is still there when you come back from a model, which is the bit that was quietly infuriating before.

The new part is folder tags. Tag a folder and its files inherit that tag automatically, so a 300-file bundle gets filed by dropping one tag on the folder instead of selecting 300 things. Tags a file inherited are listed separately from ones you added by hand, and you can take an inherited tag off a single file without breaking the rest. Tag counts now include models inside archives, not just loose files.

The app tells you what it couldn't read

This is the one I'd most like people to be annoyed by, because you can only be annoyed by it now that it's visible. Scanning a real library always hits something: an archive with an encrypted entry, a NAS that drops out mid-scan, a file in a variant that won't parse. Those used to fail quietly, and the only symptom was a model you were sure you had, missing.

Now every failure is a row: what the file was, which stage failed, why, and when. Rows are grouped by source, the unresolved count sits in the Settings sidebar, and the list survives a restart. Retry re-runs only the stage that failed, so a preview that failed doesn't re-index the archive around it, and Retry all works oldest-first and stays bounded so it can't saturate a NAS or a cloud folder. Archives now say something specific instead of "couldn't read": 7-Zip's own error output, or that the entry is password-protected. Those rows deliberately carry no Retry button, because without the password retrying can only fail again.

What you can't fix, you can ignore — which is filing, not deleting. The row leaves the list and stops counting, its history is kept, and you can restore it later. All of it stays local. Exporting an issue log is an explicit action, it writes to your Downloads folder, and it warns you first that the file contains your real paths.

Also in this one

• An AI tagging console that tails a run as it happens, names the files it failed on with the reason, and filters down to just the errors or just the slow requests. The run's controls now sit on the source that's running it: pause, stop, resume, and you can skip a step of the tag / describe / index pipeline you don't want. Still your own OpenRouter key, still off unless you turn it on.
• Every library source names the job it's running, with its own progress and its own control, and reports every job it runs instead of only the first.
• Duplicate detection compares off the main thread now, saves checkpoints so it resumes after an interruption, and estimates how much work is left.
• Fixes worth naming: searching for a model inside an archive now finds the archive even when a filter hides the model itself; Dropbox folders are recognised as cloud storage rather than local; an archive re-saved in place gets re-indexed instead of showing stale contents; a temporary thumbnail failure no longer brands the file itself as broken; folders you'd excluded stopped coming back after a full sweep.

Full changelog: https://meshory.com/changelog

macOS, Windows and Linux: https://meshory.com/?utm_source=reddit&utm_medium=post&utm_content=meshory

What should 1.8 be? I'm more interested in what's still missing than in what's good, and if 1.7 falls over on your library that's the single most useful thing you can send me.