The problem is now intermittent and Webgl settings are now changing with the problem.
When its working, typing Chrome:gpu reveals Webgl and Webgl 2 and WebGPU are all active and are set for hardware accelerated.
When its not working they are set to software acceleration with hardware acceleration disabled although hardware acceleration is enabled in settings.
That’s strange as you would think it would be one or the other?
Well, after some research, I have found that my Intel Graphics HD 3000 onboard graphics and my NVIDIA GT540M add on graphics card (which are fine for Autodesk Autocad, Fusion 360, Blender Rendering etc. etc.) do not meet the lofty ideals of Chrome and hence gSender.
They are fine with Firefox and Edge but not Chrome. Since gSender relies heavily on Chrome for its Electron section, any problems with Chrome’s acceptance of graphics and acceleration is reflected in gSender.
Both my graphics card have the latest drivers and are working properly is just that Chrome doesn’t approve.
Why Chrome approves on one boot then rejects on another (hence the intermittent nature) is beyond me. You would think it would work all the time or not at all.
Can the software engineers at Sienci explain why gSender needs hardware acceleration to that extent? Maybe they could look at a solution that will allow people with older computers to keep using gSender. If it cant be fixed then I have a choice:
- buy another up to date computer so I can use gSender just because gSender uses Chrome and Chrome doesn’t approve.
- keep my old computer (which is fine for every other program) and look elsewhere for a CNC program.
Any help from the Software guys would be appreciated.