EdwardP
unread,Feb 1, 2012, 11:07:46 AM2/1/12Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to G3D Users
Hi Morgan,
Thanks for your reply, but I can now add quite a bit more info from my
own investigations. Firstly I see exactly the same problem on my Sony
Vaio, which has the older (but just about respectable) GeForce 9300M
GS. Everything runs just fine on our 2 Dell Precisions (NVIDIA Quadro
2000M), however.
FYI, I did actually try the pre-built binary viewer, just to be sure I
wasn't screwing up my build process. I also 'downgraded' to G3D8, but
in both cases I see identical behaviour.
I finally got around to building the G3D8 source directly and
debugging through last week and I the source of the problem *appears*
to be a failure in Win32Window::init when trying to use the
compatibility profile. If I remove the WGL_CONTEXT_PROFILE_MASK_ARB,
WGL_CONTEXT_COMPATIBILITY_PROFILE_BIT_ARB attribute everything seems
to run on the failing machines, unfortunately it now fails on the
Dells!
My solution is now to explicitly test the m_glContext pointer returned
from g3d_wglCreateContextAttribsARB(m_hDC, shareContext, attribList)
and revert to wglCreateContext if this is NULL - regardless. This
version now seems to run in all cases - including my kid's netbooks
that I threw in for good measure! ;)
The troublesome machines all report OpenGL 3.0, the others are later
versions.
I appreciate that you're moving onto G3D 9 now and these legacy cards
will not be supported (not even my Alienware, I am dismayed to
discover!) but I thought this info might still be useful to others who
may experience something similar.
Cheers
E