Enabling multisampling returns error when it shouldn't.

[TyOverby]

Only recently, when I use with_multisampling in my glutin/glium project I get the error `Couldn't find any pixel format that matches the criterias.'

This never used to happen before, and in fact, multisampling is supported (and worked) on the computer that I'm testing on!

[tomaka]

On which platform?

[TyOverby]

Linux

[paulrouget]

Could it be because of #569 ?

[tomaka]

Chances are that #569 in fact fixes it.
I just published version 0.3.5, which includes #569.

[TyOverby]

I'll check and then report back

[TyOverby]

I updated to glutin 0.3.5 and glium 0.8.5 and the error is still returned.

[tomaka]

What does glxinfo say?

[TyOverby]

Glxinfo dump: http://pastebin.com/raw.php?i=kizztzDX

[TyOverby]

Does anything look suspicious?

[tomaka]

Oh I forgot about this issue.

The problem is that all your pixelformats will multisampling enabled are "non-conformant" (the Ncon in the last column means that).
Glutin automatically filters them out: https://github.com/tomaka/glutin/blob/b8b1b80631e1335a7ab747f34e1c67dfa0790a10/src/api/glx/mod.rs#L387-L390

I don't know what the best solution to this problem is. Should this be "won't fix" or shoud glutin accept non-conformant formats?

[TyOverby]

So the implementation is non-conformant but it just happens to work anyways?

Would it be possible to ask Glutin to "force" non-compat formats? Like I said in the issue, multi-sampling worked fine before you checked for conformance.

I don't know how other devs do it, but I get multisampling on all the games that I play on this computer somehow.

[TyOverby]

@tomaka Could you reopen this issue? I'm still getting the same error as before.

[dbarnhart]

I'm also getting this issue.
glxinfo.dump.txt

[c0gent]

Just started getting this same error as of v0.14.
glxinfo: http://pastebin.com/gYPW90gm

Perhaps a window builder setting to force/allow non-conformant modes?

[TyOverby]

I'm still getting this error.

[c0gent]

Working again now.

[jrmiller82]

Still getting this issue.

[no-longer-on-githu-b]

I can still reproduce this.

[Cxarli]

Not 100% sure it is related, but this might be fixed with the 18.* version of Mesa. (See PistonDevelopers/piston#1202 for more information.)

[goddessfreya]

Can you guys still reproduce this, or has it been fixed?

[goddessfreya]

Assuming fixed. Reopen if not the case.

[Syntaxxor]

I don't know if this will reopen, but I can say that I'm able to reproduce this on the latest version with an Intel HD Graphics 4000 device. Chances are, it's just because my laptop and integrated graphics are old, but it's still an issue.