Don't get me wrong, it looks amazing.

It's those devil in the detail dollar things that people need to know before committing

Your "drawing" route looks like a very interesting route

There are many out of production items from the 20th and 19th century that would benefit from modern methods

edit: and MOI can scale items very precisely, so the initial output only needs accuracy in any scale whatsoever

Pilou,
You can use open-source AI libraries to achieve this.

Ah yes i remember this one! ;)
My Ai process from the some "bad" first image! :) False image of course like Canada dry! :)

ado1,
I understand your point — nowadays, everyone working with AI has to keep an eye on costs.

Your drawing looks intriguing — it might be a nice test drive. Thanks!
Regarding the scale of output, I agree. The main idea behind forcing the question of units in a fresh, unitless setup was to keep the workflow clean for the upcoming skill (e.g. if dimensions are written in a specific unit on the drawing by hand).

Claude understands prety well itsself precive dimensional drawing (video in the header of the GitHub repo show the modeling based on a sample Design Spark drawing:
https://www.rs-online.com/designspark/designspark-mechanical-drawing-add-on-maxing-its-potential

Yes. If you have a few precise measurements for a few easy parts contained in the original drawing then it will give the AI a good leg up.

@ Gabriel

You will not have the sort of same result in using "Windows Voice Access" ?

Pilou,
to my knowledge Windows Voice Access can't print in just any software because it relies entirely on the app's built-in design.
For Voice Access to trigger a print job, the software you are using must do at least one of three things:
- Support standard keyboard shortcuts (like Ctrl + P)
- Have a visible, accessible "Print" button that the AI can read and click
- Be built with standard Windows code structures that allow assistive technologies to "see" and control the menus.

Exactly for that reason, and as you mentioned, to avoid using a paid tier, I started building one on my own with Python and free AI speech-to-text libraries. Unfortunately, it's a closed repository at the moment (it's for my day job, so I can't publish it yet, but hopefully I will be able to in the near future).
If you're interested in AI-driven software development, I can tell you that, as far as I know, there are two major open-source players: "Whisper", published by OpenAI, and "Moonshine". These are the two I've been building my Python project on, and both work pretty well. Note: I was experimenting with 'Faster Whisper', as the name suggests. – it is faster. Here are both repos:

https://github.com/SYSTRAN/faster-whisper

https://github.com/moonshine-ai/moonshine

Cheers!
Gabriel

Ado1,

I was curious to give you a rough idea of the cost per token. Generally, input tokens are the data that you provide to the AI agent (e.g. text or drawings). The output is what the agent gives you back (text answers in the 'chat' — or the 'session', as it is called — and all the output needed to build the 3D model in MoI in this case).

To try out a more complex task, I provided Claude with your sample drawing (it took some thought, but I don't think "high" makes much difference at the current stage of MCP development). I also asked it to research additional sources online for precise dimensional drawings.
It started with my work-in-progress 'Sketch to 3D' skill, found some additional information on the web, and after about 13 minutes it gave me the attached scene.
I completely agree that this is far from the original drawing, with some obvious errors. I created the MCP server mostly for conceptual design, to produce rough 3D shapes as prototypes for different 3D printing projects.
But in terms of tokens: It used around 50,000 tokens on this model, which, on my paid 'Claude Pro' subscription, is around 8% of my usage limit within a five-hour window. This is basically how these plans work: you work, then you wait until the time window unblocks, then you work again.
This means it didn't use up many tokens, which makes me think that many MCP calls to MoI generally don't use up many tokens either.

It is also always interesting to observe the thinking process of an agent. For example, I asked iClaude to summarise all the uncertainties in an MD (Markdown) file, which it saved at the end of the session. I have also attached it here for reference.

Use cases are obviously always a consideration; I'll work on improving my 'sketch-to-3D' skill in the meantime and see what I can come up with.

Cheers,
Gabriel

@ Gabriel for complete that you said

How to set up voice control (workaround):
Since MoI3D relies heavily on keyboard shortcuts (hotkeys) and scripts to launch commands, you can use voice-recognition-based dictation or macro tools on Windows.

Compatible software: Applications such as VoiceMacro, Talon Voice, Dragon, or the native Windows Voice Access tool.

How it works: You map a spoken word to a specific MoI3D keyboard shortcut.

Example: Saying "Line" simulates pressing the "L" key (or whichever shortcut you have configured for the Line tool);

saying "Circle" simulates the "C" key.

Limitations of this method: While voice control is convenient for quickly triggering tools or scripts, it quickly proves inadequate for precision 3D modeling.

Point placement: MoI3D requires precise clicking in 3D space or the entry of exact numerical coordinates. Voice input lacks the precision needed to target vertices or draw smooth curves on the screen.

Therefore, it works well as a supplementary method (for accessing menus or functions) but is difficult to use as a sole means of drawing.