Making Depth Maps and using 3D slice on Brass Coins
3 uses per day for Unpaid version
thank you for sharing these. They look great!
1 Like
These are awesome! I found one of your other threads with process details. Really cool.
2 Likes
@Bigchepin Thankyou
Good day, can you share what power machine you have and the settings used to create these awesome coins…
2 Likes
Do you have a MOPA fiber
Thank you ,
G2 galvo 20w
1 Like
My settings are for a 60 watt MOPA 150 mm lens
Sorry
1 Like
What are all of you charging for your coins? They take so long to make it just seems like you can’t charge for the time.
Curious about the setting, I have the same machine and interested in the setting for this.
f
@redregal Sorry I usually Post
1800/90%/120 Khz/ 100 ns
256 passes
1000 DPI 3D sliced
LightBurn
2 Likes
Those are amazing!
You mention DepthR, I started with that but found I had to do too much reprocessing of the images and then I found SculptOK which seems to do a much better job for me.
4 Likes
ZoeDepth v3 + OpenCV for local run depthmap. sculptok and Depth-r have pretty loose wording on what rights you still have with your files you upload.
Off-the-cloud alternatives (when the design is truly proprietary)
| Service | What the published policies say | Practical takeaway
| Depth-R | The privacy policy focuses on GDPR compliance and log data; it doesn’t explicitly address IP ownership of user-supplied images. Data is hosted by DesignGecko GmbH in Austria and logs are purged after seven days (DepthR - Create Depth Maps From Images) | Legally they might still store or reuse images; the absence of wording means your IP rights aren’t contractually protected. |
| SculptOK | Section 5/6 of the ToS states they may “utilize Prompts and Output … to deliver, sustain and enhance our services” and reserve broad rights over IP inside the service (SculptOK). | Your uploads and generated reliefs can be stored, reviewed, and used to improve their AI. You keep copyright, but they keep a royalty-free licence. |
1 Like
just curious to know roughly the time it takes to scan a coin with the level of detail shown here.
Is this the math?..
1800mm/s, 0.0254mm scan interval (1000DPI), 78.5% x d^2 (ratio of cir:sq area, d=dia), x 256 scans, answer in seconds
d=38mm (1.5")
38mm / 0.0254mm = SL (# of scan lines one pass)
SL x 38mm x 78.5% = SD (scan lines total distance in circle one pass)
SDmm / 1800mm/s = SS (total scan seconds one pass)
SS x 256 / 60s = minutes to scan all slices
106 minutes to etch the coin ?
