Importing actual Tinkercad geometry / parts

[taylormadearmy]

@henmedia - I/Codex have figured out how to export the actual full Tinkercad parts/geometry (not just STL/OBJ files) that can then be converted to Layerling files - you interested in incorporating that into Layerling directly?

[henmedia]

@taylormadearmy that sounds interesting, people moving over from Tinkercad would like to keep their shapes editable. Before I can say yes, a few questions:

• Where does the data come from: a file Tinkercad lets you download, or an internal interface behind the login?
• What comes across: the shape types with their sizes, holes, groups, colours?
• Can you show it, e.g. a small Tinkercad design and the .lyl it turns into, or the code in a repo or a PR?

If it relies on an undocumented Autodesk interface, I would rather not build it into layerling itself, since it can break or go against their terms at any time. A converter that works on a file the user saves themselves would fit much better.

If you'd like to support the project, a small donation is very welcome.

[taylormadearmy]

To answer your questions: the current prototype reads from the open, logged-in Tinkercad editor using its internal get_design_data interface and Three.js geometry. It is not based on a file Tinkercad lets the user download, and that interface could change.

It captures the design tree and evaluated meshes for individual parts and boolean groups. The result retains names, colors, visibility, grouping, and hole operands, with the evaluated boolean mesh used to display the correct cut result. The parts remain editable as meshes, but their original Tinkercad primitive settings and parametric features are not reconstructed.

I tested it on a real design: the generated .lyl retained 594 nodes, and all 537 stored meshes matched the captured source vertices with 0 mm error. I also saved and reopened the project in Layerling. I'll post to a private repo and share to you when I have a moment.

[henmedia]

@taylormadearmy thanks for testing it so thoroughly, 537 meshes with 0 mm error is impressive. Since it reads Tinkercad's internal interface from a logged-in editor, I'll keep it out of layerling itself: if Autodesk changes that interface, it breaks inside layerling and I can't fix it. As a tool of its own that writes a .lyl file, it would still be really useful for people moving over. If you publish it as its own project, I'm happy to mention it in the guide.

[taylormadearmy]

ok - will try to work out the best way to release this - currently its a bookmarklet that downloads the geometry as JSON from tinkercad and a python script to convert it... Any ideas?

[henmedia]

@taylormadearmy The easiest for users would be one step: let the bookmarklet do the conversion itself in JavaScript and save the .lyl file directly, so nobody needs Python. Put it in a public GitHub repository with a short README: how to add the bookmarklet, a screenshot or two, a license (MIT is common), and a clear note that it is unofficial and can stop working when Tinkercad changes. If you keep the Python script, the README should explain how to run it. Send me the link when it is up and I'll add it to the guide.

[taylormadearmy]

Makes sense - on it.

[BigToyBox]

Please strive to make ALL imported STL and STEP files editable. BasicCAD is the only CAD software that I am aware of that can do it. The CAD/3D printing hobby needs this desperately to attract users that have no cad experience. Having their converter code with the ease of layerling wold be a owrld changing advancement.

[henmedia]

@BigToyBox a good part of that is there already. A STEP file comes in as an exact CAD body: you can round or chamfer its edges, delete or push its faces, hollow and split it, and export it as STEP again. An STL, OBJ or 3MF comes in as a mesh, and that can be cut with holes, grouped, split, scaled and simplified too.

What layerling won't do is turn a mesh back into shapes with their sizes, a box with its width and height for instance. There is a reason hardly any software can do that: it is a very complex task, really an application of its own. layerling is meant to stay a simple, friendly tool for designing your own parts, and I'd rather keep it that way.

[grmonsey]

Its kind of a pain, but the way I have been moving my tinkercad files over has been:

1> in tinkercad, ungroup a part down to its smallest item, I change all holes and cuts to solid. While it doesn't matter on the import side, I wished the colors would import as well but I also change all the colors of holes to red so that I can keep things straight in tinkercad.
2> Select all the parts that you just ungrouped and bundle them.
3>In tinkercad, Export stl.
4> In layering, import the new bundled stl.
5> select the imported part, and use the button to separate parts.
6> rebuild your model.

Like I said it is a pain, but it works. I have been slowly moving 10 pages of models from Tinkercad to Layerling using this method.
It does have the upside that I am able to remove some redundant stuff that I forgot was there. And once the stl is separated, you have the opportunity to simplify a mesh before rebuilding the model.

[taylormadearmy]

Should have my exporter ready tomorrow hopefully. That will also preserve colours.

[grmonsey]

Now that I think about, I may be able to export the bundled model as an obj, I believe it would keep colors. will experiment.

[grmonsey]

So, after playing around with it. once you ungroup a part down to its smallest part, and change all holes to solid with red color. Bundle them up and export it as a obj. the colors come with it.

I should have messed with this 10 tinkercad designs ago......:(

[henmedia]

@grmonsey thanks for sharing your way, and good to know the OBJ keeps the colours. layerling reads a coloured OBJ as one body per colour, so all your red parts should come in as one body that you can switch to Hole, while the other colours stay solid. That may save you some of the separating and rebuilding.

[foofoodog]

@grmonsey I had AI look at the options for doing something similar and it said this, fwiw:

Layerling’s layerling_import_mesh endpoint accepts raw in-memory arrays of vertex coordinates.
layerling_import_file accepts file data directly as a string via its text argument (for OBJ or ASCII STL formats).
If using binary STL or 3MF for compactness use layerling_import_file with base64.

[taylormadearmy]

I've published a standalone importer: Setup page · Source code

1. Show your bookmarks bar and drag Export to layerling from the setup page onto it.
2. Open your design in Tinkercad and click the saved bookmark. If Tinkercad reloads the first time, click it again once the design is ready.
3. Open the downloaded .lyl file in layerling.

I've only tested it on Windows with Chrome. If you try another browser or operating system, please share how well it works and which browser/OS you're using!

[taylormadearmy]

@rickmb66 thank you for the details. On the error window there is a small "Error message" line: could you open it and paste the text here? That tells me what runs out of memory. Also, how many parts does that project have?

A general note on performance with large imports, since several of you (@prmod3d, @HopGabor62, @rickmb66) ran into it.

Layerling works with real CAD bodies wherever it can, and avoids triangle meshes. A CAD body stores a shape by its description: a cylinder is a circle, a height and a position, and a rounded edge is one curved face. That is a few numbers, no matter how smooth the shape is. A triangle mesh has no such description. It approximates the surface with triangles, and the smoother it should look, the more triangles it needs. A single round hole or a rounded corner can already be hundreds of triangles, and a detailed part easily has tens of thousands.

That difference can be huge. The same part can be a few kilobytes as a CAD body and many megabytes as a mesh. A mesh also cannot be rounded, shifted in a face or cut cleanly afterwards. Every change has to work on all of its triangles, and everything has to be kept in memory and redrawn on screen.

This is where the slowdowns come from. A Tinkercad project with thousands of parts, each saved as a mesh, adds up to hundreds of megabytes. The browser has to hold all of it at once, and every nudge of a part touches that much data. When the memory of the browser is used up, the file will not open at all.

What helps:

• Keep files smaller: fewer parts per file, and split a big project into several files.
• Where a part is a simple shape (box, cylinder, hole), rebuild it from layerling's own shapes. That is much lighter than the imported mesh.
• Close other tabs and apps before opening a big file.

@henmedia

Would you consider optional rebuildable boolean groups in the .lyl format?

The importer could write supported native shapes, transforms and the complete group/hole hierarchy. Could Layerling regenerate a missing group result using its existing group-building code, rather than requiring every intermediate result mesh in the file?

Ideally, only needed results and operands would be loaded or calculated, with progress and cancellation. Unsupported groups would retain their baked meshes, and Ungroup would preserve the original construction.

This would be a generic Layerling capability, with no dependency on Tinkercad’s internal interfaces. I can provide a small box-minus-cylinder example to establish the format and verify the result.

[henmedia]

@taylormadearmy thank you, that is a good idea and it goes to the root of the size problem: a group would be stored by what it is made of, not by every intermediate mesh. I think the best way is that you build it yourself as a pull request, because you know the format you need and can test the import locally with your exporter before anything goes in. I'd start small and optional: a group in the .lyl file may carry its operands and no baked result, layerling builds the result with its existing group code when it loads, and a group that cannot be built keeps the mesh as a fallback. Your box-minus-cylinder file would be the first test. If you tell me where you want to start, I can say where the group code and the .lyl model are.

[rickmb66]

I tried this morning with version 0.2.4. The file has 747 parts. Same error. I tried on another computer and had the same issue. I tried one with only 83 parts and it worked fine.

[henmedia]

@rickmb66 thank you for trying 0.2.4 and for the two computers. 747 parts is not many, so I would like to see the exact error. In the error window there is a small line "Error message": could you copy its text here? A bug report from the editor right after the error (the "Bug report" link in the footer) would help as well.

[rickmb66]

I tried again with latest version of the export and Layerling 1.105.0 and everythin works. Thanks for the changes!

[prmod3d]

I can confirm this works. AMAZING! I tried it in Firefox, with a couple of my more complex Tinkercad projects: a design that has over 2,300 parts, and another with around 1,200. Neither took very long to convert to a LYL file -- about 30 seconds -- and about the same amount of time to open in layerling.

The LYL file sizes are 234MB and 118MB. Once opened, layering becomes extremely slow, and just nudging a part takes nearly 30 seconds. I'm using Windows 10; 32GB RAM; Intel Core i7 CPU; 2GB graphics card, and using layerling in a Google Chrome app.

Objects can be ungrouped down to their individual elements, and sketches are not editable. Still, a huge timesaver over exporting/importing STLs. The majority of the parts in these designs were created with Extrude and Revolve sketch. Thanks @taylormadearmy for coding this genius bit of magic!

As an aside, I noticed the Property panel on the right side has become a lot smaller, and nearly impossible to read or use.

[taylormadearmy]

Thanks for your testing! Looks great 😃

[taylormadearmy]

@prmod3d Thanks again for testing. I've released v0.2.3, including lossless compression and an Export smaller assemblies option that may help you work on sections of those larger designs.

Refresh the setup page, replace your existing Export to layerling bookmark with the updated button, then reload Tinkercad and export again. Choose Export smaller assemblies when offered, extract the downloaded ZIP and open a numbered .lyl in Layerling. Complete groups, editable operands and original positions are retained.

Compression makes downloads smaller; it doesn't reduce the triangle count or guarantee faster editing. Working on separate assemblies avoids loading the entire design together, although a single detailed group can still be large. Could you try it and let me know whether opening and moving parts is more manageable? Final Layerling save/reopen testing remains outstanding. Release notes.

[HopGabor62]

Another idea. It saved a 600+MB file, which Layerling cannot handle. Would it be possible to write an app that can split such big .lyl files to half, of course by keeping track of the objects? Yes, it is possible to make copies delete objects and save smaller parts, but being the whole process slow, it helped a lot. I'm planning to migrate my hundred TC files under Layerling.

Thanks.

[HopGabor62]

@henmedia I'm glad to hear that it helped you. To be honest, this drawing is a collection of my tools for this and that, a box for my HDDs with numbers, some stuff to our caravan and such, and I dealed with them for years, so I don't know which one may have 19 nested groups. I tried to delete all that were meshes, but I'm not sure I could find them all after 1-2 years.

Thans for all of you efforts!

[henmedia]

@HopGabor62 1.104.0 is out with the fix for the deeply nested groups. You do not have to find them: just open your assembly files with the new version. If a file still crashes, send a bug report from the editor right after the error.

[HopGabor62]

@henmedia It works fine, thank both of you very much. I never thought that the biggest lyrs contains the vacuum cleaner parts.
Stefan, one idea. Because this saving method makes several lyr files, could you please make the drag box act like the "insert into this design" possibility? Maybe with a question or a checkbox. It's easier to drag than select from a list, because when selecting I have to remember which one I already loaded, while when dragging, I can see the last file with the cursor on it - at least in TotalCommander.

[henmedia]

@HopGabor62 your idea is in 1.105.0: drop one or more .lyl files on the drop zone of the import window and their bodies are added to the open design, just like "Insert into this design". So you can drag the parts of a split Tinkercad export one after the other from Total Commander. Reload the page to get it; the installed app needs a restart.

[HopGabor62]

@henmedia Thank you very much Stefan!

[grmonsey]

Worked for me, exported the file, imported to Layerling.
My only question is it changed my default colors and grid lines.
So, a restore defaults button in Layerling would be nice, unless I am missing it somewhere.

Vivaldi browser for download from tinkercad, chrome for layering,btw. Do not trust Vivaldi with my Layerling files.

edited for fat finger spelling.

A whole bunch of misc parts that some will get added to the shapes library.

[henmedia]

@grmonsey glad it worked. You can get the standard colours and grid lines back in the workspace settings: "Use app defaults" resets the colours and other settings, and "Reset grid" resets the grid.

[KimA998]

This is a really awesome feature - BUT it fails on large TC projects. It simply runs out of memory (and it´s NOT my PC that has memory problems).

I tried to make a stress test on one of my TC project and after 8665 objects exported - BANG! out of memory! (Happens in Edge and Chrome)

BTW is it normal that the first time you click on TC to LL export button TC reloads the whole project (happens in both Edge and Chrome)

[HopGabor62]

@KimA998 The memory error seems to me a Chrome problem. For me it crashed after using about 7,5GB memory, while Firefox did not have the same problem. Edge is AFAIK Chrome based too.

[taylormadearmy]

@KimA998 I've just released v0.2.3 with changes aimed at these large-export failures: reading meshes on demand, fewer retained geometry copies, lossless compression, better progress, Cancel and downloadable failure reports. Could you update and try the same project again? This doesn't guarantee that every large design will fit in browser memory.

Refresh the setup page and replace your existing Export to layerling bookmark by dragging the updated button onto your bookmarks bar. Existing bookmarks keep the previous code. Reload the Tinkercad design, wait until it is ready, then run the new bookmark; the panel should show 0.2.3.

Yes, the first-use reload is expected: Tinkercad reloads to enable its editor tools. Once the design is ready, click the bookmark again.

If export completes, large designs offer Export smaller assemblies. Extract that ZIP before opening a numbered .lyl in Layerling. If export fails, please share the last stage/count and exact error, plus the failure report if offered. After a tab crash, reload and click the bookmark to check for a recovered report. Release notes.

[henmedia]

@HopGabor62 thank you for the picture and the steps. I want to be sure I get the last point right: you group the imported parts, save the design and open it again, and then they are separate parts again? Or do you mean that the file comes in as separate parts at the first import, and you can pull them apart without separating anything? Those are two different things for me, only the first one would be a bug.

[HopGabor62]

@henmedia Well, I've tried it again. The one I uploaded was something when I tried if I svae not grouped shapes as obj from TC, could it be used in Layerling (well before @taylormadearmy 's posibility arrived), and it worked that way. Now I made a similar stuff without the half sphere and it separated as two solids. My bad that I did not tried again before.

[KimA998]

I simply can´t export any of my large projects - Tried in Edge, Chrome and Firefox.

Here are some screen shots with error messages.

[makinglayerschannel]

If you designed that in Tinkercad, I need to quit making videos and learn from you :)

[KimA998]

I can´t drag the updated button up in the book mark line in firefox - I could do it with the old one. I tried in Chrome and got this error - error report attracted [cid:c8f0b491-59b0-4b95-9150-4c096ec8fb12] Kim

…

________________________________ Fra: taylormadearmy ***@***.***> Sendt: 23. oktober 2026 12:09 Til: henmedia/layerling ***@***.***> Cc: KimA998 ***@***.***>; Mention ***@***.***> Emne: Re: [henmedia/layerling] Importing actual Tinkercad geometry / parts (Discussion #683) @KimA998<https://github.com/KimA998> I've just released v0.2.3 with changes aimed at these large-export failures: reading meshes on demand, fewer retained geometry copies, lossless compression, better progress, Cancel and downloadable failure reports. Could you update and try the same project again? This doesn't guarantee that every large design will fit in browser memory. Refresh the setup page<https://taylormadearmy.github.io/tinkercad-layerling-importer/> and replace your existing Export to layerling bookmark by dragging the updated button onto your bookmarks bar. Existing bookmarks keep the previous code. Reload the Tinkercad design, wait until it is ready, then run the new bookmark; the panel should show 0.2.3. Yes, the first-use reload is expected: Tinkercad reloads to enable its editor tools. Once the design is ready, click the bookmark again. If export completes, large designs offer Export smaller assemblies. Extract that ZIP before opening a numbered .lyl in Layerling. If export fails, please share the last stage/count and exact error, plus the failure report if offered. After a tab crash, reload and click the bookmark to check for a recovered report. Release notes<https://github.com/taylormadearmy/tinkercad-layerling-importer/releases/tag/v0.2.3>. — Reply to this email directly, view it on GitHub<#683?email_source=notifications&email_token=A7MAD3XGIWMH6GSSDS44RDD5VMU6TA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRGQZTKMBTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-19143503>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7MAD3QQSSAIHL4KTCKNPAD5VMU6TAVCNFSNUABJKJSXA33TNF2G64TZHMYTGNZTGY3DAMZRGI5UI2LTMN2XG43JN5XDWMJRGA4TINRTGKQXMAQ>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/A7MAD3UM6PX2TZ6HZGCKCMT5VMU6TA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRGQZTKMBTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android<https://github.com/notifications/mobile/android/A7MAD3WPDG3SNUVPSLUVF2D5VMU6TA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRGQZTKMBTUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[taylormadearmy]

@KimA998 I found a problem with our v0.2.3 bookmark: it exceeded Firefox's saved-bookmark URL limit. I've released v0.2.4 with a smaller self-contained bookmark and added a build check to prevent this happening again.

Please refresh the setup page and drag the blue Export to layerling button onto your bookmarks bar again. After reloading your Tinkercad design, the export panel should show Version 0.2.4. Actual export compatibility still needs your retry; this change addresses the bookmark size, not a confirmed cause of the Chrome error.

The image/report in your email reply hasn't appeared on GitHub: the comment only contains an inline image reference. Could you open this discussion directly on GitHub and attach the downloaded tinkercad-export-diagnostics.json, plus paste the exact error text and your browser/version?

If export fails normally, use Download failure report in its panel. If the tab crashes, reload Tinkercad and click the bookmark to check for a recovered report. Please upload the JSON directly in a GitHub comment rather than attaching it to an email reply.

[Ga3Tano]

New to Layering since a couple of hours, it is a really good upgrade to Tinkercad, for what I've played with.
I just imported with no errors, a TC project in Layering on Safari 26.6.2. Colors, names and notes were maintained. @taylormadearmy great job! Very grateful!
Going to keep on testing...

[henmedia]

@Ga3Tano welcome, and thank you for trying it and for the kind words. Good to hear that colours, names and notes came over. If you'd like to support the project, a small donation is very welcome.

[henmedia]

For everyone here working with large Tinkercad imports: since 1.105.0, cutting, grouping and splitting large meshes, the print estimate and Simplify run in the background, so layerling no longer freezes while it calculates. This does not change the memory limits of very large files, they stay as they are. What changed and what it brings: #800

[makinglayerschannel]

What a cool tool! I posted a video about it. I'm sure you are expecting this question, so I'll ask it. Are there plans to make this a batch process so we don't have to click into each project individually? I suspect the answer is no for various reasons, one of which is how Tinkercad loads projects and often has to load additional steps before it's "fully loaded" and depending on their server load, can take a while. But it had to be asked. Nice tool!
I ran it in Chrome on a mac.

[taylormadearmy]

Great video. Just commented on it!
Not sure if that's possible, will take a look.
I'm busy trying to get the importer to use native layerling components rather than meshes. Will look at this after that.

[henmedia]

that would be a game changer if that would work, even if it's just for a few parts

[KimA998]

With import version 0.2.4 there is still import problems.

Tried again to import my Volvo FH 16 but ran into this error

tinkercad-export-diagnostics.json

My second test with my Triumph Tiger Bike worked fine - BUT it is NOT importing my notes from TC.

[taylormadearmy]

@KimA998 I've released v0.2.5 with a change for the Honeycomb Grid failure and support for spatial notes.

The exporter was accepting an empty geometry placeholder as ready, then rejecting it as "Invalid triangle positions". It now requests evaluation and waits for triangles. A completed result that is still empty stops explicitly; no parts or cutters are discarded. This passes synthetic regressions, but I still need your retry to confirm it resolves your Volvo.

Notes were missing from our export path. This release retains their text and world positions. Notes also survive Layerling's file reader/writer save/reopen checks; visual browser verification remains outstanding.

To update:

1. Refresh the setup page and replace your saved Export to layerling bookmark by dragging the updated button onto your bookmarks bar.
2. Reload the Tinkercad design and run the new bookmark. The panel should show Version 0.2.5.
3. Retry the Volvo and recapture the Triumph to include its notes. Earlier JSON captures without notes cannot recover them.

If the Honeycomb still fails, please attach the new failure report and paste the exact error. A minimal shareable example containing the failing shape would help; please keep private designs private. Note export stops explicitly if it exceeds Layerling's 200-note or 2,000-character text limits rather than silently truncating text.

Release notes.

[KimA998]

Still not working with the Volvo FH16 - Sorry! (Haven´t tried with the Triumph yet)

tinkercad-export-diagnostics (1).json

[taylormadearmy]

@KimA998 thanks for the new report. It confirms that v0.2.5 now tries to evaluate the same Honeycomb Grid, but no triangles become available during the two-minute wait.

Could you share a Tinkercad link to a separate copy containing that existing Honeycomb Grid and its surrounding group(s)? Please keep the original Volvo unchanged. Using the actual part from the Volvo, rather than adding a fresh Honeycomb shape, matters because its saved settings and group context may be involved.

If isolating it is awkward, a share link to a copy of the full Volvo would also help, if you are comfortable sharing it. You do not need to publish the whole design publicly.

I can investigate stock Honeycomb generators independently, but your particular failing instance is what we need to confirm a fix. An STL or OBJ would lose the generator and construction information needed for this investigation.

[KimA998]

TC Triumph imported via 10 files and was complete WITH my notes - all good so far!

Now it becomes scary..... When I try to open the project again in Firefox then my project is TRUNCATED!!! (That´s not FUNNY)

When loading Firefox uses shortly 21 GB RAM and then drops to 2,4 GB (I have 64 GB in my PC)

[henmedia]

@KimA998 good that the Triumph came across with its notes. The Volvo failure is in the exporter, so I'll leave that to @taylormadearmy.

The missing parts after reopening are on the layerling side, and I'm sorry about that. Most likely the copy in the browser was not saved completely. layerling saves the design in the browser after each change, so after each of your 10 inserts. If one of those saves fails, the saved copy stays at the last state that worked, and that is what you see when you open it again. With a design this large, one save can run out of room. The 21 GB of memory while loading point the same way, as with the two designs in #847.

Two questions so I can find out where it stopped:

• Did a message appear in the lower right while you were inserting, such as "Could not save design shapes" or "This design is too big to save"?
• Is the Triumph as large as the planes? The Tinkercad export tells you the number of parts; I'd also like to know the size of the 10 files together.

Until this is clear: after inserting a large Tinkercad export, also save it as a file (Ctrl+S or "Save as"), so you have a complete copy whatever happens in the browser. Splitting a model into a few designs (frame, engine, bodywork ...) also keeps each one well within what the browser can hold.

[KimA998]

Have not seen "Too big to save" sign. All 10 files are about 92,5 MB When loading the Kreidler in TinkerCAD Chrome peaks at 7.6 GB RAM and falls to 6,4. Why Firefox peaks at 21 GB I don´t know.

…

________________________________ Fra: Stefan ***@***.***> Sendt: 24. oktober 2026 19:19 Til: henmedia/layerling ***@***.***> Cc: KimA998 ***@***.***>; Mention ***@***.***> Emne: Re: [henmedia/layerling] Importing actual Tinkercad geometry / parts (Discussion #683) @KimA998<https://github.com/KimA998> good that the Triumph came across with its notes. The Volvo failure is in the exporter, so I'll leave that to @taylormadearmy<https://github.com/taylormadearmy>. The missing parts after reopening are on the layerling side, and I'm sorry about that. Most likely the copy in the browser was not saved completely. layerling saves the design in the browser after each change, so after each of your 10 inserts. If one of those saves fails, the saved copy stays at the last state that worked, and that is what you see when you open it again. With a design this large, one save can run out of room. The 21 GB of memory while loading point the same way, as with the two designs in #847<#847>. Two questions so I can find out where it stopped: * Did a message appear in the lower right while you were inserting, such as "Could not save design shapes" or "This design is too big to save"? * Is the Triumph as large as the planes? The Tinkercad export tells you the number of parts; I'd also like to know the size of the 10 files together. Until this is clear: after inserting a large Tinkercad export, also save it as a file (Ctrl+S or "Save as"), so you have a complete copy whatever happens in the browser. Splitting a model into a few designs (frame, engine, bodywork ...) also keeps each one well within what the browser can hold. — Reply to this email directly, view it on GitHub<#683?email_source=notifications&email_token=A7MAD3XFGHJRVETMIKQNRRL5VTQBDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRGY3TGNBUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-19167344>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7MAD3V6KHNAC5QN4TFYUR35VTQBDAVCNFSNUABJKJSXA33TNF2G64TZHMYTGNZTGY3DAMZRGI5UI2LTMN2XG43JN5XDWMJRGA4TINRTGKQXMAQ>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/A7MAD3UVTYGA4SLDDANPPD35VTQBDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRGY3TGNBUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android<https://github.com/notifications/mobile/android/A7MAD3W745GERDJIGQN2FJL5VTQBDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRGY3TGNBUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[KimA998]

Triumph design has 5484 parts P51 has 3108 parts

…

________________________________ Fra: Stefan ***@***.***> Sendt: 24. oktober 2026 19:19 Til: henmedia/layerling ***@***.***> Cc: KimA998 ***@***.***>; Mention ***@***.***> Emne: Re: [henmedia/layerling] Importing actual Tinkercad geometry / parts (Discussion #683) @KimA998<https://github.com/KimA998> good that the Triumph came across with its notes. The Volvo failure is in the exporter, so I'll leave that to @taylormadearmy<https://github.com/taylormadearmy>. The missing parts after reopening are on the layerling side, and I'm sorry about that. Most likely the copy in the browser was not saved completely. layerling saves the design in the browser after each change, so after each of your 10 inserts. If one of those saves fails, the saved copy stays at the last state that worked, and that is what you see when you open it again. With a design this large, one save can run out of room. The 21 GB of memory while loading point the same way, as with the two designs in #847<#847>. Two questions so I can find out where it stopped: * Did a message appear in the lower right while you were inserting, such as "Could not save design shapes" or "This design is too big to save"? * Is the Triumph as large as the planes? The Tinkercad export tells you the number of parts; I'd also like to know the size of the 10 files together. Until this is clear: after inserting a large Tinkercad export, also save it as a file (Ctrl+S or "Save as"), so you have a complete copy whatever happens in the browser. Splitting a model into a few designs (frame, engine, bodywork ...) also keeps each one well within what the browser can hold. — Reply to this email directly, view it on GitHub<#683?email_source=notifications&email_token=A7MAD3XFGHJRVETMIKQNRRL5VTQBDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRGY3TGNBUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-19167344>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7MAD3V6KHNAC5QN4TFYUR35VTQBDAVCNFSNUABJKJSXA33TNF2G64TZHMYTGNZTGY3DAMZRGI5UI2LTMN2XG43JN5XDWMJRGA4TINRTGKQXMAQ>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/A7MAD3UVTYGA4SLDDANPPD35VTQBDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRGY3TGNBUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android<https://github.com/notifications/mobile/android/A7MAD3W745GERDJIGQN2FJL5VTQBDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRGY3TGNBUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[henmedia]

@KimA998 thank you for all the numbers and for testing so patiently. I want to be honest with you about where this stands. layerling works differently from Tinkercad: Tinkercad does the work in its cloud, layerling does it on your own computer, in the browser. What you are doing, a model with 5,484 parts and 92.5 MB of Tinkercad geometry, is far beyond what most people build, and it is more than a browser tab can reliably hold and save. I cannot change the number of triangles such a model brings with it, so I cannot promise that it will work as one design, and I will have to step back from this topic here.

What does work: split the model into several designs (frame, engine, bodywork ...), and save each one as a file (Ctrl+S or "Save as") as soon as it is inserted, so that you have a complete copy whatever happens in the browser. If a smaller design fails to save, or a message like "Could not save design shapes" appears, tell me and I will look at that one.

[KimA998]

For your information, many of my TC design has been used by the TC team as bechmark for TinkerCAD 😁24. okt. 2026 19.54 skrev Stefan ***@***.***>: @KimA998 thank you for all the numbers and for testing so patiently. I want to be honest with you about where this stands. layerling works differently from Tinkercad: Tinkercad does the work in its cloud, layerling does it on your own computer, in the browser. What you are doing, a model with 5,484 parts and 92.5 MB of Tinkercad geometry, is far beyond what most people build, and it is more than a browser tab can reliably hold and save. I cannot change the number of triangles such a model brings with it, so I cannot promise that it will work as one design, and I will have to step back from this topic here. What does work: split the model into several designs (frame, engine, bodywork ...), and save each one as a file (Ctrl+S or "Save as") as soon as it is inserted, so that you have a complete copy whatever happens in the browser. If a smaller design fails to save, or a message like "Could not save design shapes" appears, tell me and I will look at that one. —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[KimA998]

I have now separated the honeycomb pattern in the design and now it exports fine. I can´t think of other shapes where I have used the honeycomb from TC. Here is a link to it in TC: https://www.tinkercad.com/things/gdTgsxrfy0T-copy-of-honeycomb-pattern?sharecode=pGSdneqPEy0XrbxUqHaFKK2sEfmwgPL5OPrym6pvo78 I could be nice if your export could point out witch object is failing in TC. That would make it easier to trouble shoot. Kim

…

________________________________ From: taylormadearmy ***@***.***> Sent: Saturday, October 24, 2026 8:39 PM To: henmedia/layerling ***@***.***> Cc: KimA998 ***@***.***>; Mention ***@***.***> Subject: Re: [henmedia/layerling] Importing actual Tinkercad geometry / parts (Discussion #683) @KimA998<https://github.com/KimA998> thanks for the new report. It confirms that v0.2.5 now tries to evaluate the same Honeycomb Grid, but no triangles become available during the two-minute wait. Could you share a Tinkercad link to a separate copy containing that existing Honeycomb Grid and its surrounding group(s)? Please keep the original Volvo unchanged. Using the actual part from the Volvo, rather than adding a fresh Honeycomb shape, matters because its saved settings and group context may be involved. If isolating it is awkward, a share link to a copy of the full Volvo would also help, if you are comfortable sharing it. You do not need to publish the whole design publicly. I can investigate stock Honeycomb generators independently, but your particular failing instance is what we need to confirm a fix. An STL or OBJ would lose the generator and construction information needed for this investigation. — Reply to this email directly, view it on GitHub<#683?email_source=notifications&email_token=A7MAD3UFKWZZPUH2NY4PBV35VTZNNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRGY4DCOJYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-19168198>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7MAD3S25OBYRTDVDUYC6QT5VTZNNAVCNFSNUABJKJSXA33TNF2G64TZHMYTGNZTGY3DAMZRGI5UI2LTMN2XG43JN5XDWMJRGA4TINRTGKQXMAQ>. Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/A7MAD3TDJ2TITLF6G66R56L5VTZNNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRGY4DCOJYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android<https://github.com/notifications/mobile/android/A7MAD3SBHBF3ANEG5OWXXDT5VTZNNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOJRGY4DCOJYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[taylormadearmy]

Thanks, Kim — glad separating the Honeycomb pattern lets the design export. Your request to identify the failing object is now available in v0.2.6.

Refresh the setup page, replace your saved export bookmark, then reload the Tinkercad design. The export panel should show version 0.2.6.

If capture fails on an identifiable part, the panel shows its group path and a Locate failing part button. For a nested part, this selects its containing top-level group and shows the path to the failing child. It does not ungroup, reveal or unlock anything, or change the model's geometry. Hidden, locked or changed targets may be refused.

There is also a separate Download detailed report button with the part names/IDs, path and available diagnostic counts/state. Please review that file before sharing it, as it contains model identifiers. Nothing is uploaded automatically.

This is a diagnostic aid, not a confirmed fix for the Honeycomb timeout. The generated bookmark passes automated selection/report checks, but live Tinkercad selection still needs verification. If you can retry the failing version of the model, please let us know whether the locator highlights the expected group and, if you are comfortable sharing it, attach the detailed report here.

[KimA998]

I have now tried your version 0.2.7 with following result

It still is waiting for a honeycomb shape and it gets a time out. I then locate the shape and this is wat I get:

• A honeycomb shape that is locked despite I have prior export unlocked ALL of the design.
• When I unlock it labels with XYZ and Z height is shown with "Infinity" - as it is a shape that does not exist!
• I can´t move the honeycomb object.
• I can delete the object and if I try to locate failed object again - it cannot be found.
• When I continue the export it´s again waiting for a honeycomb object.

Then I got the idea - what if TC has a bad data structure with deleted / ghost objects....

I copied my truck to a new fresh project and tried to export. AND IT EXPORTED my design but now there was 20 object less in the design.

tinkercad-export-details.json

[taylormadearmy]

Thanks, Kim — the report and your fresh-project test are useful. Good to hear the locator helped identify the Honeycomb objects.

The report shows a Honeycomb generator with no geometry that stays busy until the two-minute timeout. Together with the infinite height and successful fresh copy, this suggests stale or invalid objects in the original project, although we have not confirmed the cause.

Does the fresh copy look complete, including the intended holes, hidden parts and notes? With 20 fewer objects, I would like to check what changed before treating any of them as safe to skip.

If you are comfortable sharing them, could you provide Tinkercad share links to the successful fresh copy and a separate, untouched copy of the failing truck? The earlier link contains the isolated Honeycomb; comparing both full versions would help us identify which objects disappeared and whether they affect the model. Please keep your original unchanged; there is no need to delete more objects for this investigation.

For now, the exporter will continue stopping when geometry is missing, so it cannot silently leave out a valid part or hole. Once we understand the difference, we can decide whether to improve detection and the error message.

[KimA998]

I have imported my truck into LL, but sadly LL is not capable to have my full design in one file. I have to split it to 3 LL files.

But all what I have imported looks GOOD!

[KimA998]

Do you have another direct email to you for the links to TC design?26. okt. 2026 14.19 skrev taylormadearmy ***@***.***>: Thanks, Kim — the report and your fresh-project test are useful. Good to hear the locator helped identify the Honeycomb objects. The report shows a Honeycomb generator with no geometry that stays busy until the two-minute timeout. Together with the infinite height and successful fresh copy, this suggests stale or invalid objects in the original project, although we have not confirmed the cause. Does the fresh copy look complete, including the intended holes, hidden parts and notes? With 20 fewer objects, I would like to check what changed before treating any of them as safe to skip. If you are comfortable sharing them, could you provide Tinkercad share links to the successful fresh copy and a separate, untouched copy of the failing truck? The earlier link contains the isolated Honeycomb; comparing both full versions would help us identify which objects disappeared and whether they affect the model. Please keep your original unchanged; there is no need to delete more objects for this investigation. For now, the exporter will continue stopping when geometry is missing, so it cannot silently leave out a valid part or hole. Once we understand the difference, we can decide whether to improve detection and the error message. —Reply to this email directly, view it on GitHub, or unsubscribe.Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS and Android. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[taylormadearmy]

You can email layerling at tragic dot name.
Thanks!