In an earlier post, what I said about "select then command" vs "command then select" on SCALE breaking my 2021 SP1 system was not correct. I now see that both approaches will either work or fail depending on some time-dependent mouse cursor movement.

If I highlight my house plan, then type SCALE (or if I type SCALE, then highlight the house plan), I am asked to specify the base point. I then click on the bottom left corner of the building, and the system then requests that I Specify scale factor. All is well to this point ... it's the next step that can cause my crashes.

If I just start typing 1.25 (or whatever), then everything works fine (as it should work), but ... if instead of typing, I start to drag my mouse cursor toward the command line area (as I am in the habit of doing), then about 3 to 5 seconds later the DraftSight system will crash. Getting my cursor to the command line is not necessary to trigger the crash. The system will crash if I just move the mouse cursor a few pixels in any direction, then wait 3 to 5 seconds.

I sent a sample crashing DWG file to support, and it didn’t crash for them (with my new instructions), but they didn’t mention if they were testing with SP1 or SP2. I went ahead and downloaded SP2, and it’s working for me now for SCALE, ROTATE, and MIRROR.

I’m running the most current version of Windows 10 … Version 21H1 Build 19043.1052 just installed today (just before downloading, and switching to SP2).

Your mileage will probably vary, but it’s working for me.

Bob​​​​​​​