-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 4.0.4 #548
Comments
@tritao what do you think is EGL stuff production ready or are there any objections releasing it in version 4.0.4? |
I think it should be production ready, though I have only tested it on my system. What I mentioned before is that for FreeCAD it would be preferable if Coin supported both EGL and non-EGL backends, switchable at runtime, but we can postpone that for the next release. So no objections 👍 Hopefully that doesn't cause distro packagers any issue, if it does, and you see this, please let us know. |
If you release it soon, I push it to unstable. I hope it is ABI compatible, if not, please, bump ABI number. |
@lepalom I will do the test for ABI compatibility and the release over the weekend. |
@VolkerEnderlein Great!!! thanks!! |
I am not so sure it is production ready. Like I mentioned earlier (#531 (comment), #531 (comment)), I have a problem when using the EGL combined with the NVIDIA proprietary drivers, but it works fine with nouveau. Maybe a release of 4.0.4 is good so more FreeCAD devs can test with it but I think we need more people with NVIDIA proprietary drivers to confirm or reject the problems I have before pushing a Coin version with EGL to the masses. Maybe some sort of beta release is a better option?! |
@Rexbas could you show a simple example of problems with EGL + NVIDIA proprietary drivers + Linux so I can test it? |
Currently I have driver version 565.77. Build Coin with and this: Log
|
Alternatively, running examples from https://github.com/coin3d/ivexamples results in similar problems but black instead of white: Log
|
@Rexbas I could prepare a release candidate or beta release but I doubt it will find its way into the distributions as the maintainers add only real releases or patch sets to a release. Can you tell me how you build Coin libraries when developing for FreeCAD? Are you using tagged version to build Coin? |
Ah yes you are right, it was just an idea but better make sure to not push a release that only works for half of the users.
For FreeCAD I use the pixi environment from the FreeCAD repo which contains Coin 4.0.3. When I want to use a custom build of Coin then I usually change the target of the links in the .pixi folder to the output of my Coin build folder.
No, I usually use the master branch. |
I have built coin and soqt from last version of git. coin with COIN_BUILD_EGL = ON. I run a Debian Stable bookworm with Nvidia proprietary drivers: GBM platform:
|
@lepalom So I guess it makes no sense to create a 4.0.4 version now. We need to figure out how to make this feature stable before the release. |
I'll see if I can repro this week, I don't think I ever tried with SoQt, I built my own minimal example with GLFW and never had an issue, with Linux Mint 21. |
@tritao could you show me your minimal example with GLFW? I have used the ivexamples with Hello cone as a test. |
I can run the GLFW example without error messages. However, the yellow cone becomes black when I press my super key... Screencast_20250210_195154.mp4Hello Cone still doesn't work. |
I can also reproduce the black issue (when I press alt though). Also happens with the GLX backend for me, probably just some kind of camera issue. |
It's just caused by |
Where is this example? Is it based on Quarter? |
Hello Cone is here: https://github.com/coin3d/ivexamples/blob/master/Mentor/02.1.HelloCone.cpp.in. I believe it uses SoQt. Do you also have an NVIDIA GPU @tritao? |
Hi,
we have seen that 4.0.3 has problems with EGL [1] in Linux. The bug was solved in the repo but no release with the changes. Could you please release a new version?
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050302
The text was updated successfully, but these errors were encountered: