Roll back to 2.0.05 > Export Bundle > Reinstall 2.1 > Import Bundle
i did contact support and emailed them the crash report. waiting for a reply.
No, they werenât - What happened was the UNITS the settings were displayed in changed, likely from mm/sec to inches/sec.
If you used 300 mm/sec, youâd see it now as 11.81 inches/sec. Same speed, different number.
Units on speeds are important - 50 mph is the same speed as 80 km/h even though the number is different. Laser speeds are the same - We store everything in your files in mm, regardless of what units you actually work in, and just format them when displaying them into the correct units.
When you installed the new update, if you were in inches in the last version, the new one would use that for displaying speeds. This was a bug, but it didnât actually change the speed, just how it was shown to you, and itâs trivial to change it back.
Go to Edit > Device Settings, and set it back to mm/sec here, and turn off the toggle under it to make it stay that way when you switch between inches/mm in the UI:
Thatâs it. Itâs a 10 second fix, and none of your files have been affected. It was the second upgrade that has done this because you havenât corrected that setting, and itâs remembered, so itâs going to keep happening with every update from now on, unless you just take a moment to fix that.
This wasnât intended, and weâve got a patch now that prevents this from happening for future people to update, but once youâve installed the new version, you now have the âcontrol unitsâ setting in your preferences, and thatâs the thing thatâs making the numbers display funny. Change it, and itâll be fixed and you can enjoy the update.
They are also usually in your download folder on your pc if you havenât deleted it! I make a habit of keeping the last version just in case!
Me too - so pleased I could roll back to a working copy
New version totally useless - wasted too many items finding out it I could not get settings to work
Weâve figured out why XTool D1 devices were affected by this update - itâs because they âpretendâ to be GRBL devices but have subtle differences in the ways that they process certain commands that break the GRBL spec, in this case the position query command.
We have an XTool specific device profile that you could use now (in 2.1) that generally works better than the GRBL compatible mode anyway, or you can wait for the 2.1.02 patch, which will have a fix for the GRBL mode too.