Sorry for the delay... yes, basically the same issue as the link you posted. `getFullscreenModes` was returning an empty vector. I said that I could "arm-twist" a fullscreen mode by tampering with the source file (removing the `continue` as mentioned in someone else' thread), but even though the vector was no longer empty, the result wasn't correct visually (I'm not a computer wizard, so I don't really understand what's going on with resolution and scaling).
I'd like to put some of my projects on GitHub (and have fullscreen work properly if at all possible), so I need to make sure the public has access to the same SFML release that I use, so fullscreen works the same everywhere.
Currently my code doesn't switch to fullscreen mode implicitly, but checks whether the `getFullscreenModes` vector has length before doing so.
Even if that potential crash is removed in 2.6.2, is there any news on whether the actual resolutions/scalings returned will display as expected? There was never an issue with this on my last (Intel) Mac, so I don't know where the logic differs, or how the old process could be mimicked.
Thanks, and thanks for SFML!
