Re: Possible PyOpenGL Material/Shader/Display List Bug

Ian Mallett <[email protected]>
Newsgroups gmane.comp.python.opengl.user
Message-ID <CAG4NV=uzUXojZH7n+S6SAGPGTuPdQRwOf32LowGLk03R-AcNVg@mail.gmail.com>
On Mon, Aug 29, 2011 at 8:32 PM, Alejandro Segovia <[email protected]>wrote:

> Hello Ian,
>
> On Sun, Aug 21, 2011 at 12:42 PM, Alejandro Segovia <[email protected]>wrote:
>
>> Hi Ian,
>>
>> Ah, the driver might be where the difference is. I am using PyOpenGL 3.0.1
>>>> but I'm on a Mac, so I'm not using the NVIDIA drivers at all.Best,
>>>>
>>>> I sent a bug report to NVIDIA, but evidently I have to be a registered
>>> developer to submit anything so technical.  I started the application
>>> process, so hopefully they'll be able to get the report in a few days.  Let
>>> me know how your tests go,
>>>
>>
>> Sorry for the delay, I was really busy last week. I tried the script on
>> Linux and, much to my surprise, I still can't reproduce the problem you
>> describe.
>>
>>  I initially get a red quad and then I can turn on and off the white quad
>> without any issues.
>>
>> This is my system configuration, I'm on Fedora 12 x86_64:
>>
>> >>> glGetString(GL_VERSION)
>> '4.0.0 NVIDIA 256.44'
>>
>> >>> glGetString(GL_RENDERER)
>> 'GeForce GTX 465/PCI/SSE2'
>>
>> >>> glGetString(GL_VENDOR)
>> 'NVIDIA Corporation'
>>
>> I'm starting to wonder whether this could be a Windows-specific issue.
>>
>
> Well, I've finally took some time to try this on Windows. Unfortunately, I
> still can't reproduce the symptoms!
>
> This is my system configuration:
>
> >>> glGetString(GL_VERSION)
> '4.1.0'
>
> >>> glGetString(GL_RENDERER)
> 'GeForce GTX 465/PCI/SSE2'
>
> >>> glGetString(GL_VENDOR)
> 'NVIDIA Corporation'
>
> I'm on a 64-bit Windows 7 (Professional).
>
> Is there anything I might be missing?
>
Well, I'm on 32-bit, and I have a different GPU.  I think it must be a
particular combination of my GPU and my driver that's causing the issue.

> Did you get any kind of reply from NVIDIA?
>
Sadly no.  I think I shall have to go yell at them again.

>
> I've read about them releasing OpenGL 4.2-capable drivers. Have you tried
> those?
>
The only ones I'd tried are 275.33, 266.58, and 280.26.

I wonder if this is a PyOpenGL problem.  Even though it seems like a
hardware issue, perhaps there's something underlying that's causing the
issue?  I'll see about writing a small C++ test.

Thanks for checking!
Ian

------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev

_______________________________________________
PyOpenGL Homepage
http://pyopengl.sourceforge.net
_______________________________________________
PyOpenGL-Users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyopengl-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.