Many Mac ports of things that use OpenGL or Vulcan use a wrapper that redirects the internal pipe from the old API to the new one.
Previously it would report as Apple GPU or something below the area that would have said OpenGL.
Maybe an error showing something else, or maybe a workaround to help keep certain extensions working?
Hmm. It turns out that we are finally getting our wish, sooner or later.
I wonder how big the task will be, after 23 years, to switch to something else.
Certainly a big task: even the smallest changes in this year’s version cause difficulties for users and developers.
2 likes
I hope the guy who loves OpenGL doesn’t try to sabotage this move. Every time I’ve posted or commented on a post about Sketchup changing the API, he comes up defending OpenGL, stating that it’s not OpenGL’s fault.
Although OpenGL does what it was designed to do, it’s old, creaky, and Apple has stopped supporting more updates. So, it’s time to rethink the SketchUp dependency. Posting announcing a change is proof that Trimble is aware of it. Regardless of what is chosen as a replacement, there will be a lot of work to be done and a high risk of failure. If the release is delayed, it doesn’t mean that some OpenGL fanatic is blocking progress, it just means that this is a major change that needs to be done with caution.
1 like
hey, you don’t know, I can imagine a meeting at Trimble HQ with someone in a suit nervously saying “guys, we have a problem, we have to delay our update for the millions of users, Jimmy420 on our forum I don’t think leaving OpenGL is a Good idea. We have to abort now! 
Also, Anssi’s point was not that openGL is superior to metal and d12. He wrote that claiming that one change in technology would solve all problems was incorrect. and has a point. The change will solve some problems, but you can be sure that it will generate new ones and fix bugs.
Just look at the framework change on the PC version in 2023, the impact on its appearance, and the bugs it generated along the way. However, I’m pretty sure most developers would say that the new framework is better than the old one.
That is unfolding for you. That’s why they often try not to fix what isn’t broken in the first place. unless they have to.
Just my point. Also, being an average retired old man in Finland who doesn’t work for SketchUp greatly decreases my chance of sabotaging SketchUp development.
I’m pretty convinced that the SU team has people who know what makes it tick and have an idea of where the bottlenecks are. I am also afraid that there is no magic wand; if it existed, it would have been used already. The only quick fix to things I’ve seen was around 1988-90 when Autodesk rewrote the snap algorithm in AutoCad. That’s why I’m skeptical about the ability of users to tell developers how to do their job.
3 likes
Totally agree! Having been a developer in a previous career, I’m always bummed out when someone who isn’t a developer posts something like “it would be easy” or “app x does this, so it must be possible for SketchUp too” without knowing how. SketchUp is actually programmed or what it would take to make the “simple” change.
Again, okay.
2 likes
Can’t. For two reasons:
- Trimble has already shown a willingness to take SketchUp in bold new directions that users either objected to or didn’t ask for, such as the web version and subscription license.
- A much more likely scenario would be a meeting where the Suit tells the developers “that will cost HOW MUCH!! We are not going to spend that just to appease users.”
In your own words, can you tell us why OpenGL is the problem?
I don’t think OpenGL is the problem, rather the SketchUp renderer itself is very inefficient, but that’s another thing.
I think the I.Pad version uses metal (I think Apple already dropped OpenGL support).
And guess what? It doesn’t work much differently than the other versions.
Anyway; the point is that changing the graphics API itself will have little benefit.
