Hi Darrell, After several months I'm thankful to be starting a slow functional comeback. It was pleasant to read all you've been up to since June.
On 11-07-15 04:48 AM, DRC wrote: > I was able to actually reproduce this, completely by accident. I use a ... > so I had to add GLX_DEPTH_SIZE, 1 as well. Many months ago Nathan Kidd wrote, regarding your patch (in r4417): >>> I'm waiting to hear back on this test but hopefully will get a result soon. I never was able to get that tested with HFSS. It seems the folks with HFSS were so busy that as soon as my original patch worked they were on to something else. However, since you ended up reproducing that same weird StaticGrey behaviour I'm confident HFSS will work also. Many months ago Nathan Kidd wrote: >> if somebody comes >> along in the future with an app that manually chooses its visual via >> glXGetConfig and requires say, a stencil buffer, we could always >> introduce a "VGL_DEFAULTCONFIGWITHSTENCIL" option to modify the attrib Here we are in the future and it turns out Abaqus 6.10 CAE is exactly one such app; wrong drawing because it needs a stencil buffer, wants to do manual visual selection via glXGetConfig(), and we return the same set of (stencil-less) attribs for every config. Now, I can produce the same kind of patch as r4417 but adding a GLX_STENCIL_SIZE attrib and a fallback to disable that attrib if no configs found, which would be only a couple lines of code changed. I don't really like this approach since (in my limited understanding of GL driver internals) the app will use more memory with the stencil buffer, and may be somewhat slower too. I could create a patch that introduces the before-theorized VGL_CONFIGWITHSTENCIL (or similar) to enable the above behaviour only when set. This forces the end user to know about what the app does internally and to manually set the right flag. Not very pretty when the app could do the right choosing if given a chance. I know you weren't too keen on the last patch I proposed to provide a full variety of visuals by default. One of the factors was that the patch wasn't helpful for servers (e.g. VNC) that only export one visual. Another factor I think was just the size the patch. If I were to rework that idea to be fewer lines, and possibly add in some VGL_CONFIGWITH(DEPTHSIZE|STENCILSIZE|AUXBUFFERS) environment variables for the case where only one visual is available, would you consider such a patch? As time goes on I can see apps that want aux buffers, multisample, etc. and so I still like the idea of the last approach. However, as much as I don't like the game of whack-a-mole for every app that is broken from the same underlying issue, I also want to provide a patch that will get accepted, thus I'm trying to feel out an approach you like too. Take care, -Nathan ------------------------------------------------------------------------------ RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 _______________________________________________ VirtualGL-Devel mailing list VirtualGL-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-devel
