USER FORUM
(you are viewing a thread; or go back to list of threads)
message: Unable to create a GL context (by Andrey)
When run SolveSpace version 3.0~827f54f2
reseive message: Unable to create a GL context
(OS Ubuntu 16.04)
reseive message: Unable to create a GL context
(OS Ubuntu 16.04)
help, pls (by Andrey)
help, pls
(no subject) (by whitequark)
This error message means that your graphics drivers do not support OpenGL 3.0. Either upgrade them, or use SolveSpace 2.x.
not everyone can upgrade (by FOSS Advocate)
'
Hi, just to report that I too had the " Unable to create a GL context " problem.
Linux Mint 18 ( based on Ubuntu 16.04 ) is the OS, which actually runs wonderfully, but this old Intel hardware is capped at OpenGL v2.
After wrestling with Git and GitHub eventually I managed to build it locally from the "2.x" branch, and it worked enough to follow the first extremely helpful, highly recommended Tutorial http://solvespace.com/bracket.pl for which many thanks Devs!
So, don't give up Andrey, it might still be possible to get something working. I posted my actual steps on another thread : http://solvespace.com/forum.pl?action=viewthread&parent=1830
And to the Developers, please don't abandon those of us trapped on old hardware.
It would be a shame to have only just discovered this exciting project and immediately find we're being flipped the digit, especially if we're keen and able to help with the testing and feedback.
Thanks
'
Hi, just to report that I too had the " Unable to create a GL context " problem.
Linux Mint 18 ( based on Ubuntu 16.04 ) is the OS, which actually runs wonderfully, but this old Intel hardware is capped at OpenGL v2.
After wrestling with Git and GitHub eventually I managed to build it locally from the "2.x" branch, and it worked enough to follow the first extremely helpful, highly recommended Tutorial http://solvespace.com/bracket.pl for which many thanks Devs!
So, don't give up Andrey, it might still be possible to get something working. I posted my actual steps on another thread : http://solvespace.com/forum.pl?action=viewthread&parent=1830
And to the Developers, please don't abandon those of us trapped on old hardware.
It would be a shame to have only just discovered this exciting project and immediately find we're being flipped the digit, especially if we're keen and able to help with the testing and feedback.
Thanks
'
(no subject) (by whitequark)
The 2.x branch is still supported. In fact, the 3.x branch has not yet seen a release and probably should not be generally used yet.
In any case, there are performance (rendering complex designs quickly), quality (rendering certain features, such as hidden lines, legibly) and maintenance (keeping a single renderer base on every supported platform) reasons to migrate to OpenGL 3. I cannot support old hardware forever and it is my decision as a maintainer to migrate going forward.
Also, no one is "flipping a digit" to you. It is not fair to inflict a disproportionate workload on the few developers of SolveSpace so that a few people with extremely old hardware can avoid upgrading. You do not want to bear this cost, why should I?
In any case, there are performance (rendering complex designs quickly), quality (rendering certain features, such as hidden lines, legibly) and maintenance (keeping a single renderer base on every supported platform) reasons to migrate to OpenGL 3. I cannot support old hardware forever and it is my decision as a maintainer to migrate going forward.
Also, no one is "flipping a digit" to you. It is not fair to inflict a disproportionate workload on the few developers of SolveSpace so that a few people with extremely old hardware can avoid upgrading. You do not want to bear this cost, why should I?
not all the world has the luxury of ''CHOICE'' (by FOSS Advocate)
'
You're upset. That was not the intention. :o(
Clearly poor wording on my part and for that I offer humble apologies.
The sorely-disappointed underlying sentiment is a rollover emotion borne of discovering yet another interesting FOSS project (the fourth in a row) just as it's on the cusp of migrating and excluding what we have available.
> "You do not want to bear this cost"
We're not all wealthy Americans on this planet.
It's far from a case of "not wanting to."
I still want to express respect and gratitude, and wish you and the project well. :o)
Namaste
'
You're upset. That was not the intention. :o(
Clearly poor wording on my part and for that I offer humble apologies.
The sorely-disappointed underlying sentiment is a rollover emotion borne of discovering yet another interesting FOSS project (the fourth in a row) just as it's on the cusp of migrating and excluding what we have available.
> "You do not want to bear this cost"
We're not all wealthy Americans on this planet.
It's far from a case of "not wanting to."
I still want to express respect and gratitude, and wish you and the project well. :o)
Namaste
'
(no subject) (by Jonathan Westhues)
Maybe we just need to make it more obvious that non-developers who nonetheless build SolveSpace from source should be running 2.x, regardless of the graphics drivers available to them? That (a) stops people from running unstable software, and (b) postpones the GL version issue until even fewer people would encounter it.
Alternative : use software rendering (by Imad MHAMDI)
Hi,
Having the same issue on a debian 11 system (Bullseye) with old hardware (Intel(R) Core(TM)2 Duo CPU L9300 @ 1.60GHz with Intel Corporation Mobile 4 Series and i915 kernel module)
Any solution on the drivers side seems locked with such old hardware, but I was able to run solvespace sucesslly with the shell commandline:
env LIBGL_ALWAYS_SOFTWARE=1 solvespace
the idea here is to force the backend used by my linux system to use mesa software rendering (thus using the main X86/64 CPU instead of GPU);
the overhead for the CPU is not noticeable on small projects and I was able to run all tutorials sucessfully;
for Andrey and FOSS Advocate the trick may also be useful for other tools
Thanks @whitequark for producing such a good piece of software
@Jonathan Westhues : as of 2022 this trick is probably the easyest on all Linux system, thus leaving old windows and mac systems with the option of building 2.x if still relevant ?
Having the same issue on a debian 11 system (Bullseye) with old hardware (Intel(R) Core(TM)2 Duo CPU L9300 @ 1.60GHz with Intel Corporation Mobile 4 Series and i915 kernel module)
Any solution on the drivers side seems locked with such old hardware, but I was able to run solvespace sucesslly with the shell commandline:
env LIBGL_ALWAYS_SOFTWARE=1 solvespace
the idea here is to force the backend used by my linux system to use mesa software rendering (thus using the main X86/64 CPU instead of GPU);
the overhead for the CPU is not noticeable on small projects and I was able to run all tutorials sucessfully;
for Andrey and FOSS Advocate the trick may also be useful for other tools
Thanks @whitequark for producing such a good piece of software
@Jonathan Westhues : as of 2022 this trick is probably the easyest on all Linux system, thus leaving old windows and mac systems with the option of building 2.x if still relevant ?
Post a reply to this comment: