Saturday, December 2, 2023
Home3D Modeling2DTools doesn't work on MacBook M1/Ventura - Extensions

2DTools doesn’t work on MacBook M1/Ventura – Extensions


I do very very similar to to make use of TIG’s 2DTools, solely not all instruments work.

Concern

Rectangle

  • 1st click on and begin creating the primary line;
  • It’s potential to 2nd click on to set the endpoint and begin making the second line;
  • Beachball seems and retains spinning infinitely;
  • Can solely be stopped by SU compelled termination;
  • After termination, OS asks Apple to ship a notification to Apple, and restart SU;
  • SU asks to ship a Bug Splat. Did.

Freehand

  • Whereas deciding on the button, the beachball seems instantly;
  • Can solely be stopped by forcibly terminating SU;
  • After termination, OS asks Apple to ship a notification to Apple, and restart SU;
  • No request from SU to ship a Bug Splat.

Arc

  • Much like Rectangle. Solely no request from SU to ship a Bug Splat.

Circle

  • After clicking the start line of the circle, the beachball is popping infinitely;
  • Solely cease by SU compelled termination;
  • After termination, OS asks Apple to ship a notification to Apple, and restart SU;
  • No request from SU to ship a Bug Splat.

Polyline edit

  • After deciding on some extent, the seaside ball seems infinitely;
  • Can solely be stopped by SU compelled termination;
  • No request from OS Apple to ship a report;
  • No request from SU to ship a Bug Splat.

The instruments under work effectively:

  • Set Z-plane
  • Line
  • Hatching
  • Fillet
  • Alter
  • Line Model
  • Textual content

My setup seems to be like this
MacBook Professional 16-inch, 2021
Chip: Apple M1 Professional
Reminiscence: 16 MB
macOS: Ventura 13.3.1
SketchUp Professional 2023 23.0.396

I now perceive that on Home windows PCs and different macOS variations, there aren’t any issues with 2DTools, however that it focuses on Ventura 13.3.1.

@colin Are you aware extra about this challenge? Are you able to see what choices can be found to look into this?

Thanks upfront on your efforts.

I don’t know his 2D instruments in any respect. It seems to be like they haven’t been up to date since earlier than M1 existed, are you utilizing them by operating SketchUp in Rosetta?

@TIG could know extra.

You must also submit this over on SketchUcation, which is the place TIG supplies most of his extensions and is extra prone to see it.

Edit: On a Mac, when an app is aborted the OS presents to ship a report back to Apple. A lot of the time an abort is triggered by a recognized however unrecoverable error within the OS, equivalent to a deadly error in a graphics driver, and Apple needs to find out about such. However a guide pressure give up additionally generates an abort and will get the identical dealing with. I normally inform macOS to not trouble reporting an abort I do know occurred as a result of I selected pressure give up – Apple received’t be taught something of worth from the report.



1 Like

No Colin, I don’t use Rosetta. macOS Ventura signifies that SU 2023 is a totally ‘common’ functions. In that scenario, Rosetta is just not wanted, is it?

Thx Steve. TIG is already conscious of this challenge.

As for passing on the error messages to Apple; you will have an excellent level there. Makes little sense in that case :slight_smile:

The extension itself could also be benefiting from one thing pre M1 that isn’t there.
Or extra probably , one thing had modified in a latest OS replace that has brought about the extension to not work

The frequent theme to those points in a number of enter factors in a device – e.g. when drawing a 3-point rectangle
The primary two factors are OK, however after that the beach-ball-of-death begins…
These instruments work advantageous in different MAC OS variations and on all PCs, so one thing have to be completely different with specific MAC OS !?
I don’t have a MAC with this OS/model to check with, so if anybody else needs to mess on with the coding, then be at liberty…
The RB recordsdata within the subfolder will not be encrypted, so you may see what they’re doing, and take a look at your personal edits and so on…
I wish to resolve this, as I’ve one other [confidential] industrial toolset that’s failing on these newer MACs, with enter level points which are very related… On different MACs or PCs there’s no points.

I reproduced the problem on macOS Ventura 13.3.1 on my Intel-based 2019 MBP 16″ utilizing each SketchUp 2023.0.396 and SketchUp 2022.1.165. So it is just not particular to Apple Silicon nor to SketchUp 2023. I don’t have a pre-Ventura model of macOS operating, so I can’t confirm whether or not the problem additionally occurs on Monterey or earlier.

After some testing, I discovered that the extension was looping within the draw (view) methodology after the second level is picked (within the @state > 1 clause.) I believe the issue is that the code calls view.invalidate from inside the draw methodology, triggering a direct name once more to attract – countless loop! I commented out the view.invalidate, and the issue went away.

I’m not clear why the view.invalidate was wanted within the first place, even on Home windows. @TIG, maybe you may clarify? Whether it is wanted on Home windows or older variations of macOS, a easy department take a look at primarily based on OS model might repair it?

Edit: I posted this additionally on SketchUcation and TIG replied there. He’s on the case!



3 Likes

A wonderful instance of excellent troubleshooting and debugging.

It’s attention-grabbing that the bug has not been reported as occurring on Home windows.
Maybe there’s a distinction with the Ruby construct for Mac ?

I’d recommend that that is good candidate for an API Concern within the GitHib tracker.

Purely a guess, however I’m wondering if there’s a distinction in how occasions are queued on the 2 platforms, considerably like how webdialogs have been asynchronous on Mac however not on Home windows.

I’ve had SketchUp operating in Xcode all day, and been taking a look at this. I might see that it was getting caught on the second draw_polyline, and I had observed the invalidate line (and questioned about that).

Deleting that line does make the device work.

Curious that it doesn’t have an effect on older macOS, if that’s the case.

I’ve an up to date model now accessible for testing…

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments