There is NO “Use OpenGL” option.
Only this:
OpenGL could be seen as a programming language to allow your graphic card and processor to communicate together
If you’d like to read up on it;
https://openglbook.com/chapter-0-preface-what-is-opengl.html
Resumed:
On the most fundamental level, OpenGL is a software interface that allows a programmer to communicate with graphics hardware. Of course, there is much more to it than that
Like VB and C# for SW macro. OpenGL is “VB”.
This is really great information. Thank you for sharing this.
I thought it was an API of sorts to the graphics driver. Sort of a “universal” language to the layer between applications/OS and the various GPU architectures.
They are API. A higher level “Library” that hide hardware from developer.
Looks like Vulkan will replace OpenGL.
I think SW is testing Vulkan.
Logical.
The Viking roaming about the afterlife sim game ‘Valheim’ is testing Vulkan as well, it works great for murdering wild pigs.
But back to SP.4 any red flags?
Did they fix the it takes a million years to save your file issue? or CTD on clicking save from SP2?
This is a strange issue, but it only started after I upgraded to 2022. Some of my assemblies now open as “Shaded.” These assemblies are released in PDM, so I know I didn’t somehow change them. I ONLY uses “Shaded with edges”, so this isn’t something I would have ever changed.
edit: I guess this could have happened when I updated all of the files to 2022. I used #task to do this.
I get that in 2019 sp4, it seems random. Sometimes washed out light gray parts on a white background in shaded [without edges] is frustrating enough for me to look up “who did this!?!” and I look in file history and who checked it in last. They swear they didn’t save it that way. I thought we had it figured down to the “larger” assemblies opening the components in lightweight. I changed my settings, bumped up the limits; I still see assemblies load up in shaded [without edges] even when all the components are resolved. There’s just not enough time to trace down all the strange behaviors/bugs/enhancements in SW. Like trying to sweep a dirt floor, just get the big stuff and move on.
I’ve seen some batch programs turn off certain features to speed up the batch updates. We do this to some system features when running model configurations for orders. Shaded though is file specific instead of system, not sure why in that case.