Closed GoogleCodeExporter closed 9 years ago
Oh, interesting.
I can't test this myself, but when I do some updates again I will try adding
it, and send you back a version to test.
Original comment by paracel...@gmail.com
on 12 Jun 2013 at 12:47
Yep, thanks!
I managed to compile a build of Xee 2 with that fix and everything seems to
work properly without switching the GPU, so hopefully the fix will be the same
(or similar) in 3.
Original comment by miguelpontes
on 12 Jun 2013 at 1:03
Can you test http://wakaba.c3.cx/stuff/Xee3.0.7-test.zip ? There is an option
in the preferences to turn it on and off, try to see if that works too.
Original comment by paracel...@gmail.com
on 8 Jul 2013 at 9:19
Nope, checkbox makes no difference. It triggers the discrete GPU on both
states, unfortunately.
Original comment by miguelpontes
on 8 Jul 2013 at 9:27
Hmm, then I am a bit lost. Does the Info.plist look correct?
Original comment by paracel...@gmail.com
on 8 Jul 2013 at 9:30
Yeah, it looks fine. NSSupportsAutomaticGraphicsSwitching = YES and
NSOpenGLPFAAllowOfflineRenderers as the single attribute to NSOpenGLPixelFormat
was enough for it to not trigger the discrete GPU for me on Xee 2.
Perhaps I should add that with Xee 2, the discrete GPU only kicks in once an
image is loaded, while with Xee 3, the discrete GPU kicks in as soon as the app
launches, even without any visible window at all (strange!). So perhaps there's
something at the application's init that's causing the switch?
Original comment by miguelpontes
on 8 Jul 2013 at 9:36
Oh, that is a good clue. I think I am doing some testing for OpenGL context
features on startup that might trigger something. Let's see.
Original comment by paracel...@gmail.com
on 8 Jul 2013 at 10:05
Try http://wakaba.c3.cx/stuff/Xee3.0.7-test2.zip
Original comment by paracel...@gmail.com
on 8 Jul 2013 at 10:23
Yep, that does it! Checkbox does what it's supposed to do now.
Well, if you trigger the discrete GPU once, you need to quit and relaunch the
app in order to go back, but I think that's how OS X behaves in general. As
long as one starts the program with the box unticked, it seems like it won't
trigger the discrete GPU at all.
Thanks!
Original comment by miguelpontes
on 8 Jul 2013 at 10:38
Yes, that sounds about right. And thanks for the help getting this working!
Original comment by paracel...@gmail.com
on 8 Jul 2013 at 10:43
Seems like Mavericks breaks this.
I have "use discrete GPU if available" unchecked, but when loading certain
kinds of images, Xee uses the discrete GPU anyway. JPEG uses dedicated. GIF
does not.
I'm running Xee 3.3 on 10.9 Mavericks on a 2013 15" retina MacBook Pro.
Original comment by Aktariel
on 5 Dec 2013 at 6:35
No, it's 3.3 that breaks it. It uses the GPU more but I forgot to include code
to handle the discrete GPU stuff. Will be fixed next version.
Original comment by paracel...@gmail.com
on 5 Dec 2013 at 9:51
Any way to downgrade to 3.2 in the meantime?
Original comment by Aktariel
on 28 Feb 2014 at 8:01
There are old versions in http://wakaba.c3.cx/releases/mac/old/
If you bought it through the App Store, I'm not sure if there's a way. I recall
Apple adding something for that recently but haven't looked at it.
Original comment by paracel...@gmail.com
on 28 Feb 2014 at 10:46
Hopefully fixed now. Can't really test it, so report back and tell me if it's
not working once the next version is out.
Original comment by paracel...@gmail.com
on 6 Jul 2014 at 9:42
Original issue reported on code.google.com by
miguelpontes
on 12 Jun 2013 at 12:43