On May 21, 2014, at 6:25 PM, Matthias Dörfelt wrote:
Capturing the display does not make a difference.
Did you capture it before or after creating the pixel format object?
Anyways, your guess about the GPU switching was spot on! If I disable it, the
issue disappears. Is there any way to fix
Thanks for the detailed reply, that makes a lot of sense. I tried putting the
display capturing in multiple places, without any success.
My temporary work around really is to just call CGDisplaySetDisplayMode twice
(as that is the only „easy solution I found), as I don’t really wan’t to write
a
Hey,
I am experiencing some really weird behavior with CGDisplaySetDisplayMode
behavior on osx 10.9.3 on a late 2013 retina mbp.
if I call CGDisplaySetDisplayMode only once, it seems to end up in weird
display modes, that are not even listed through CGDisplayCopyAllDisplayModes
i.e.
Okay,
I just investigated this issue a little more. It only happens under one
condition for me, which is that I created an NSOpenGLPixelFormat before the
CGDisplay calls, i.e. this does not work as expected:
#import AppDelegate.h
#include CoreGraphics/CoreGraphics.h
@implementation
On May 21, 2014, at 5:45 PM, Matthias Dörfelt wrote:
I just investigated this issue a little more. It only happens under one
condition for me, which is that I created an NSOpenGLPixelFormat before the
CGDisplay calls, i.e. this does not work as expected:
while the same code without the
Hey Ken,
Capturing the display does not make a difference. Anyways, your guess about the
GPU switching was spot on! If I disable it, the issue disappears. Is there any
way to fix this in my code? I.e. an NSOpenGLPixelFormat flag that would take
that into account?
Thanks!
Matthias
Am
The more I think about this, the more I think this deserves a bug report. If
the automatic GPU switching gets triggered by switching the display mode in the
first place, and the newly active GPU supports the same display format,
shouldn’t it make sure it keeps the same format? I don’t see how
