This only with Driver 220.127.116.1164, Driver 18.104.22.16863 works fine.
In particular I get the value "2147483648" (0x80000000) for zMin and zMax for all primitives (always the same value).
With the old driver (22.214.171.12463) and other Cards (NVidia and ATI) my Program gets the correct results.
There is some new driver that I can use that correct this?
(Hey, you get the honor of my first post, ever.) I've started looking into this issue, but Icould use a little more information. Do you have a code snippet that you'd be willing to share that shows exactly what calls you're making? I'd like to make that we can replicate the behavior here, and if necessary try to get the drivers updated to work as expected. Alternatively, maybe there's a different way to accomplish what you're trying to do and we can highlight that as well.
It is written in Delphi (Object Pascal), I've tried to isolate some piece of code. here is the first part (it draw the scene in "Selection mode"):
Note: SELECTION_BUFFER_SIZE is a constant: 30000
"Self" in Delphi means "This" in C++
Self.FWorld.DrawFastEx(NIL,FALSE); // Draw the Objects
// Back to render mode (see OpenGL Develop Guide)
if Self.FSelCount>0 then
Here is an extract of the code of the Method "ProcessHints" that analize the response:
for i:=0 to Self.FSelCount-1 do
zMax:=Self.FSelBuf[k ]; // Maximum depth value of primitives (range 0 to 2^32-1)
zValue:=zMin; // I use zValue to detect the neares primitive selected
What I see is that the Items are all detected, but I need to detect the nearest one. So I use "zMin".
Objects are drawn (more or less) in this way:
glPushName(GL_ITEM_SELECTED); // This is an Item ...
for i:=0 to IList.Count-1 do
if not Item.Draw then result:=FALSE;
The problem is that zMin and zMax values are completely wrong for all primitives.
Well, sure seems like it ought to work logically, at least as I understand it. (Delphi is a little Greek ) I'm checking with the validation team to see if they have selection tests that mimic this functionality and find out what their results are. In the end I may have to write a little app to demonstrate this on our side and see if I can duplicate the failure for the driver guys. Either that ormy little testapp will work and we can figure out what the difference between that code and yours is.
Please try to solve it.....
P.S. Note that with driver 126.96.36.19963 works fine (zMin and zMax are returned well) with the same binary (tested with my old Laptop a HP Compaq nc6120). If I update the driver on the nc6120 I get the same error, so I'm forced to use my old PC with an old driver... :(
My card is the G33/G31 Express Chipset. I have confirmed this works fine on other cards.
No matter what the max and min distances are returned as 2147483648. Thought it was a bug in my code until I checked it out on other cards.
I have a test application that i can give to anyone who is interested? Would like to know if there has been a fix for this?
We are facing the exact same problem. We have had our product running without problems on nVidia and ATi and it's hard explaining to our customers that their Intel-based laptops won't work 'cos of a driver bug.
Can someone from Intel please respond to this?
Hi, more than six month ago I've received thie e-mail from Intel connected to this thread:
> Greetings from Intel Software Network Support.
> We have been following your technical thread on the Intel IIG forum, and
> we were wondering whether you are doing your development work for a software
> company (and if so, which one), or whether you are an individual developer.
> If you work for a software company, you might be able to receive some
> additional engineering assistance (as well as marketing assistance) through
> membership in the Intel Software Partner Program (www.intel.com/partner
> If you'd like us to have an ISPP recruiter contact you with some more
> information, please let us know.
> Lexi S.
> Intel Software Network Support
After I've answered that I'm a freelance --> Silence....
Thanks for the tip. I've just registered. But I still do not know who to contact regarding this issue.
I remember filing a bug report some time ago under some general feedback page but there was no response.
Now let's hope there's someone reading this forum