robertosfield wrote:
>
> What you describe sounds like an Intel driver bug. The best thing you
> can do is check for latest Intel drivers.
>
I checked over some things and found that the FFP was removed in GL 3.1, and
that the Intel driver is reporting as that version. I tested on an
SMesserschmidt wrote:
> Hi Ryan,
> Can you create a minimal _compilable_ example, so more people might
> check what is wrong?
>
Sure - I've attached an osglight-derived example. Compile with:
Code:
g++ -o osglight osglight.cpp -losg -lOpenThreads -lGL -losgUtil -losgViewer
-losgDB
Your code works when my laptop is using Intel graphics, but when I switch to
Nvidia graphics, the glGetString calls fail for some reason (maybe the GL
context isn't switching?). Strange.
Switching the whole app to single-threaded works for both.
Ryan
--
Read this topic online
I recently started a project based on the osglight demo. I have a laptop with
switchable graphics, and under Linux the demo works great under both Intel and
Nvidia graphics. Under Windows 10 however, lighting doesn't appear to work
with the Intel driver, even though it works fine in Linux
SMesserschmidt wrote:
> I guess your interfering with the currently set context. You're not
> explaining where/when you call your snippet, but usually this would be
> done inside a "realizeOperation".
>
I'll try your code. I was doing the code snippet right after a
"viewer->realize()"
Hi,
I'm trying to query GL parameters such as GL_VENDOR, which require an active
graphics context to work. I looked another thread on this forum which explains
how to do it, but it only works for a single-threaded viewer. I'm running the
viewer in multithreaded mode, and am getting crashes
6 matches
Mail list logo