@Lappa I don’t want to belabour the point, but I repeat, gSender does not need Chrome to work. I have gSender on 3 computers and none of them have ever had Chrome installed on them. As @KGN said in his post, gSender does need webgl, but webgl is independant of Google Chrome.
That’s great - your computer doesn’t need Chrome. Nowhere have I stated EVERY computer needs Chrome. However, If I remove Chrome from my NVIDIA card, on MY computer, gSender WILL NOT RUN - period - no Ifs or Buts. Believe you me, I have tried all different configurations.
On my other computer, I can turn hardware acceleration OFF on Chrome, Firefox and EDGE and and Webgl reports that it’s not enabled and gSender works fine.
This peculiarly is happening only on my workshop computer, not any other.
I’ll leave it at that. It works the way I have it set up so I can get my work done.
Read my reply to gwiiki.
@Lappa I meant no offense. I apologize if I came across that way. Since you have it working, I’ll mark this topic as solved and close it.
1 Like
@Lappa just to add, I spoke some more with Kevin about this and we couldn’t come to a reasonable conclusion about the peculiarity of your issue. As he mentioned gSender does use WebGL for visualization, and by extension so do most modern web browsers. This stems from gSender being built as a web-app so it inherently uses Chromium to help package it up and make it cross-platform. As far as needing the Chrome browser, or any other browser, installed - it shouldn’t need them and should be able to run standalone.
If I could make a guess, it’d be that maybe your computer is old enough that it’s having issues with WebGL but your graphics card is able to override that compatibility issue - but maybe as a part of that fix only Chrome is exposing the right flag to make that work meanwhile gSender doesn’t? This is all a shot in the dark, so one way or another I’m just glad to hear you found a solution for your setup. If anyone else stumbles upon the same issue hopefully they can similarly benefit too 
For further help I’ll also link this to the Git Issue you submitted to leave a paper trail.
Think through that logic, please. You’ve just proved that the problem on your computer is NOT with gSender and has nothing to do with gSender. So, I don’t know why you’re complaining about it on a gSender forum.
As the problem, at first, only affected gSender, and by reloading gSender settings I could fix the problem, so wouldn’t this forum would be a logical place to ask the question?
If you read my first post , I stated that I thought it was a computer problem rather than a software problem.
The problem did change in nature
I main gripe, if you bothered to read all the posts was with Chrome
I only questioned whether gSender was dependent on Chrome (on GitHub it mentions one method of deployment for gSender is browser driven)
Nowhere have I complained about gSender. All I wanted was an explanation of why gSender failed operate unless I had chrome attached to my NVIDIA card.
We now have a theory which Tech support have said may help others and have posted it on GitHub.
1 Like
Thanks for your help Kevin and Chris.
There is another work around that doesn’t involve the use of a browser.
As the GitHub post is now closed, should I post it here or on GitHub?
I think if you have another workaround then post it here since I linked this thread in the Github 
- another option is to edit your comment with the original solution to add in the second solution if you think they’re equally good.
I think it’s perfectly valid you’re asking questions about stuff like this since there certainly is overlap in the wording explaining how all this stuff works together - especially when you’re experiencing a unique case
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.