For the sake of sanity, we made a requirement that QOpenGLContext::thread() is the same thread that you make it current in. Is it possible for you to move the QOpenGLContext to the rendering thread in question? (using QOpenGLContext::moveToThread(renderThread)).
Or is OSG moving constantly moving the QOpenGLContext between threads? cheers, Gunnar On 19 Jun 2014, at 14:25, Rollastre Prostrit <rollas...@gmail.com> wrote: > Hello. > > We recently upgraded our Qt&OSG application to Qt 5.3 from Qt 4.8.4. The > result is that the application does not work anymore and crashes when > realizing the graphics context no matter which version of OSG or how we > build it. It always ends up giving the following message > > "Cannot make QOpenGLContext current in a different thread" > > There seems to be a consensus in the OSG community that this is not an OSG > fault but Qt's. There are also several patches provided by external users > which claim to solve the problem. However, we didn't succeed applying them. > So the situation seems to be that we have to choose between going back to Qt > 4.8 ( losing quite a lot of work we have done and doubling the maintenance > for our products running in two Qt versions), or hope that there is some > solution/initiative from Qt's side to solve this problem. > > Is there anybody in the list knowing some sort solution for this? > Any Qt developer know if it will be ever possible to continue enjoying these > two wonderful software packages together as it has always been? > > Best > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest