# Trouble running PTB on my macbook pro 2019 16 inch

**URL:** https://psychtoolbox.discourse.group/t/trouble-running-ptb-on-my-macbook-pro-2019-16-inch/3939
**Category:** Bugs & Features
**Tags:** macos, gpu
**Created:** [July 29, 2021, 9:32am UTC](https://psychtoolbox.discourse.group/t/trouble-running-ptb-on-my-macbook-pro-2019-16-inch/3939 "2021-07-29T09:32:28Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)
#### Post date: [July 29, 2021, 1:56pm UTC](https://psychtoolbox.discourse.group/t/trouble-running-ptb-on-my-macbook-pro-2019-16-inch/3939/3 "2021-07-29T13:56:51Z")

</div>

You got a bit more lucky than the last person trying to get the 16" MBP 2019 working. On Catalina it failed completely. See here:

> <https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/644>
>
> Hello,
> 
> I meet exactly the same message as the one you described in your code …: 
> 
> PTB-ERROR \[Low-Level setup of window failed\]:The specified gpu + display + gfx-driver combo may not support some requested feature.
> 
> when I try to initialize the screen on a macOS Catalina.
> 
> Here is the code to initialize : 
> 
> \`function \[w, r\] = initializeScreen
> 
> screenNumber = 0; % 0 = main display
> 
> %PsychDebugWindowConfiguration(0, 0.5)
> \[w,r\] = Screen('OpenWindow',screenNumber, 127); % open the window
> 
> % Set fonts
> %Screen('TextFont',Window,'Times');
> Screen('TextSize',w,48);
> Screen('FillRect', w, 0); % 0 = black background
> 
> HideCursor; % Remember to type ShowCursor later
> \`
> 
> 
> and here are the error messages : 
> 
> \`PTB-INFO: Retina display. Enabling panel fitter for scaled Retina compatibility mode.
> 
> 
> PTB-INFO: This is Psychtoolbox-3 for Apple OS X, under Matlab 64-Bit (Version 3.0.16 - Build date: Dec 16 2019).
> PTB-INFO: OS support status: OSX version 10.15 is not officially supported or tested at all for this release.
> PTB-INFO: Type 'PsychtoolboxVersion' for more detailed version information.
> PTB-INFO: Most parts of the Psychtoolbox distribution are licensed to you under terms of the MIT License, with
> PTB-INFO: some restrictions. See file 'License.txt' in the Psychtoolbox root folder for the exact licensing conditions.
> 
> 
> PTB-ERROR\[CGLSetFullScreenOnDisplay failed: invalid drawable\]. Main Screen() context
> 
> 
> PTB-ERROR\[Low-Level setup of window failed\]:The specified gpu + display + gfx-driver combo may not support some requested feature.
> 
> Error using Screen
> See error message printed above.
> 
> Error in initializeScreen (line 6)
> \[w,r\] = Screen('OpenWindow',screenNumber, 127); % open the window
> 
> Error in FoodHealth (line 24)\`
> 
> What do you suggest ?
> 
> Thanks a lot

Apparently they fixed Big Sur at least to the point where you can make it to an onscreen window and then sync failure – so the machine is not utterly useless for all tasks and could run at least trivial tasks.

This machine uses the new AMD Navi graphics chips with DCN display engines. These are not supported at all by our PsychtoolboxKernelDriver, and most likely never will be, which means that all high precision visual timing and most of PTB’s diagnostics and workarounds for operating system bugs are dead. This makes the machine very untrustworthy for precise timing. You are essentially on your own here.

So you don’t need to bother with the PsychtoolboxKernelDriver, it won’t help.  
Seems we can rule out Retina display trouble as well, given you seem to run on an external display with 1920x1080@60Hz here.

What you observe could be really bad operating system timing, or more likely desktop compositor interference, no way to distinguish without use of external timing measurement equipment like photodiodes, VPixx devices or similar

As the text says already, if this happens on repeated runs, you can add `Screen(‘Preference’, ‘SkipSyncTests’, 2);` to disable sync tests and use the machine for tasks which do not require any trustworthy or accurate timing at all.

Or if this is a machine mostly used for serious data collection you could sell the machine and replace it by a much more suitable Linux laptop for less than half of the purchase price.

You could also consider trying all the things mentioned in this discussion thread, to contribute some data-point that may help fixing your machine sometime in the future. You can skip everything related to the PsychtoolboxKernelDriver ofc.:

> [@macOS PTB users: Petition Apple at WWDC?](https://psychtoolbox.discourse.group/t/macos-ptb-users-petition-apple-at-wwdc/3882/10):
>
> What anybody with access to macOS 11 or macOS 12 could do is to do a quick test / a rough assessment, if the problems persist on those OS’es with different hardware. Get and install the latest MoltenVK/Vulkan runtime: [https://sdk.lunarg.com/sdk/download/latest/mac/vulkan-sdk.dmg](https://sdk.lunarg.com/sdk/download/latest/mac/vulkan-sdk.dmg) This one now contains the bug fixes and improvements i contributed to this macOS Vulkan driver. On an IntelMac install the PsychtoolboxKernelDriver, and make sure it is actually working and used by PTB – The beamposi…

Good luck,  
-mario

---

_[View the full topic](https://psychtoolbox.discourse.group/t/trouble-running-ptb-on-my-macbook-pro-2019-16-inch/3939)._
