Have had issues with stimuli timing. We run with mirrored monitors, one inside the booth and one outside for the experimenters. With the iGPU that comes built-in on the motherboard (CometLake-S GT2 [UHD Graphics 630]) if the booth monitor was a 240Hz Viewsonic and the outside booth was a generic 60Hz monitor, either the booth monitor was forced to run at 60Hz by Linux or it would for some reason allow it to run at 240Hz but then PTB would be unable to run. Once the outside monitor was also a 240Hz Viewsonic, then things ran fine, albeit with a 5% flip timing error rate. As the PTB website warns, using an NVIDIA video card (GeForce GTX 1660 SUPER) resulted in messages that the flipping system was failing. Switching to an AMD Radeon W5700, the monitors did not even display successfully. Dell support suggested that this video card might not work with the Optiplex computer. Apparently you have to call them up to confirm whether a given video card works with the computer you are using. We tried an AMD Radeon 550X, which has been reported on the forum to work with PTB, but although we found that it did indeed work with the Optiplex to drive the monitors, we get messages from PTB of total flip failure:
PTB-WARNING: Flip 1017 for window 10 didn't use pageflipping for flip. Visual presentation timing and timestamps are likely unreliable!
PTB-WARNING: Something is misconfigured on your system, otherwise pageflipping would have been used by the graphics driver for reliable timing.
PTB-WARNING: However, if you see this message only sporadically, this might be caused by onscreen popup messages a la "You have new mail!" or
PTB-WARNING: "New updates are ready to install" etc. Being low on free system memory can cause this as well, especially on integrated graphics chips.
PTB-WARNING: Read the Linux specific section of 'help SyncTrouble' for some other common causes and fixes for this problem.
PTB-WARNING: Couldn't even collect one single valid flip interval sample! Sanity range checks failed!
PTB-WARNING: Could be a system bug, or a temporary timing problem. Retrying the procedure might help if
PTB-WARNING: the latter is the culprit.
I have confirmed that we are running x11 and amdgpu. So for now, we're just using the iGPU. It would be nice to get the 550X working, if anyone has any ideas.