MillMage 0.9.00 RC-2 Release Candidate

The second version of our Early Access release for MillMage 0.9.00 is available for download now, and we are closer than ever to the launch of MillMage Pro! (Hey, we can’t get further, right?)

Just as with LightBurn RCs, you can install MillMage RCs side-by-side with the current official release. That means if you encounter any workflow-breaking bugs in the RC, you can quickly switch back to the official release to keep working.

If you are currently using MillMage with a Core license, head to HelpLicense Management and click the Trial Pro button to get access to all Pro features for two weeks. We will extend Pro trials for our existing Core users for the duration of the 0.9 RC period.

Changes Since MillMage-v0.9.00-RC-1

Bug Fixes

  • Relief roughing / finishing issues
  • Toggle Panel visibility was missing toggling the Pages panel.
  • Pocket lift retracts were checking the wrong bounds
  • Final offset pass bug
  • Fixed issue causing all library tools to be treated as project tools, preventing tool deletion and certain modifications.
  • Roughing shapes with holes that contained other shapes could repeat some areas
  • Solve error generating shapes after deleting shapes or pages.
  • Fixed issue causing device settings dialog to cutoff custom gcode options.
  • Removed limit 50% maximum from stepover in tool library.
  • Fixed a bug causing the preview window texture tooltip to display the same image for all textures.

Existing Feature Updates

  • Nest to pages
  • Auto un-cache pro op errors
  • Auto-exclude bitmaps from pocket operations
9 Likes

wow reading the list in the install popup you have been busy , have you guys even slept in the last week

4 Likes

The sun never sets on LightBurn. Not even kidding. We have people as far west as Vancouver, BC and as far east as Brisbane, Australia. And none of us sleep much :wink:

4 Likes

sleeps over rated, plenty time for that when your dead

2 Likes

@adammhaile, don’t forget our NZ team. :new_zealand: :wink:

2 Likes

And don’t forget my love of sleeping. :sleeping_face:

1 Like
3 Likes

Edge buffering :partying_face: hell yeah :smiley: :smiley:, going make my life so much easier with full sheet lay outs

1 Like

Windows 10.
The menu text disappeared and this also happened with 0.9.00 RC-1 but didn´t said nothing due to lack of proof.
The proof:

As with 0.9.00 RC-1 just moving the window a bit “redraws” everything fine.

For normal images I can access the Properties and adjust the image.
This doesn´t work for DepthMaps is this the expected behavior?

Don´t know if this is possible but if it is, it will free PC resources:
If we change from Normal Detail to Fine Detail MillMage redraws everything, as the paths are the same can MillMage be done to redraw only the preview image?

Maybe minor UI issue, the Texturing Op is on the Preview but doesn´t update the Final Depth in the Ops Panel:

..

Well that’s good news considering my problem, and it may not even be a LB issue. My Falcon 10w stopped engraving unless I was at 100% power and a slow speed. So I bought a Laser Tree Module, and all my settings are messed up. My settings for the best engraving now are 400/80 . Well I can go 100/500 but with the original module i was doing engraving 3000/ 45 more or less.

What has happened, anyone.
Thanks, Dennis

rc 2 is telling me trial has expired :cry: , how or where do i get extension

cheers

Depth maps are 16 bit and all the image processing code is written for 8 bit maps, so yes, this is expected. Before too long you’ll have to change the type of an image to a “depth map” object in MillMage, and those controls will disappear.

We’ll be adding code to do similar things to depth maps at some point, but they aren’t “visual”, so controls like “brightness” and “contrast” aren’t the correct way to do this.

2 Likes

Because the texturing op doesn’t have a Final Depth - It has a Max Depth. They’re different values.

1 Like

Email support@lightburnsoftware.com

1 Like

The rendering of the wireframe image is not the slow bit, and the way the drawing happens at the moment, they’re coupled enough that it’s difficult to separate them.

1 Like

Windows 10.
With this file:

depth cut.mage (3.6 MB)

As there are open shapes, if I Break Apart then Auto-Join this is the output:

i then Undo the Auto-Join and MillMage takes a while to undo.

After Delete Duplicates and MillMage not responding for 4´30´´ to Auto-Join.


This Time the output is correct.

1 Like

I´ve read this one before:

Usually I pay attention to these little things – I failed!

And reading some posts, seems that a lot of us are auto-connecting with Final Depth, maybe make it other color or different to click our brains?

1 Like