# Code check: Unusual reaction times (like less than 100 ms) for an AX-CPT task coded using PTB version 3.0.19

**URL:** <https://psychtoolbox.discourse.group/t/code-check-unusual-reaction-times-like-less-than-100-ms-for-an-ax-cpt-task-coded-using-ptb-version-3-0-19/5798>\
**Category:** Programming Help\
**Tags:** windows\
**Created:** [March 13, 2026, 6:39am UTC](https://psychtoolbox.discourse.group/t/code-check-unusual-reaction-times-like-less-than-100-ms-for-an-ax-cpt-task-coded-using-ptb-version-3-0-19/5798 "2026-03-13T06:39:58Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tylerdurden9591](https://yyz2.discourse-cdn.com/free1/user_avatar/psychtoolbox.discourse.group/tylerdurden9591/32/711_2.png) [@tylerdurden9591](https://psychtoolbox.discourse.group/u/tylerdurden9591)\
**Post date:** [March 13, 2026, 6:39am UTC](https://psychtoolbox.discourse.group/t/code-check-unusual-reaction-times-like-less-than-100-ms-for-an-ax-cpt-task-coded-using-ptb-version-3-0-19/5798/1 "2026-03-13T06:39:58Z")

</div>

I am coding an AX-CPT task using PTB in MATLAB and while doing pilot testing, I am getting **unusual RTs (Less than 100ms)** when the participant is trying to do the task fast. Below are the details of the environment I am using:

**PsychtoolBox version:** ‘3.0.19 - Flavor: Manual Install, 16-Jan-2026 16:17:44’

**Platform:** Windows 11

**Matlab Version:** Matlab R2025b

**Graphics detail:** Intel UHD graphics 730

**Code (Just the probe section where I am trying to record the RT):**

```auto
Target letter code snippet: 
%Probe letter
% Clear queue before probe

KbQueueStop;
KbQueueFlush;

% Wait until all keys are released

while KbCheck
end

Screen('TextSize',window,60);
DrawFormattedText(window,probeLetter,'center','center',magenta);

% Flip probe to screen and record TRUE onset time

tOnProbe = Screen('Flip',window,vbl+(waitframes-0.5)*ifi);

KbQueueFlush;

KbQueueStart;

while isnan(respProbe)

 [pressed, firstPress] = KbQueueCheck;

if pressed

% Accept response only if it occurred AFTER probe onset

if firstPress(numpad1) > tOnProbe

 respProbe = 1;

 rtProbe = firstPress(numpad1) - tOnProbe;

elseif firstPress(numpad2) > tOnProbe

 respProbe = 2;

 rtProbe = firstPress(numpad2) - tOnProbe;

end

end

end

KbQueueStop;

```

Can anyone tell me if it’s an issue with how I have set up the probe timing recording or is it anything else?

---

<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:** [March 13, 2026, 8:09am UTC](https://psychtoolbox.discourse.group/t/code-check-unusual-reaction-times-like-less-than-100-ms-for-an-ax-cpt-task-coded-using-ptb-version-3-0-19/5798/2 "2026-03-13T08:09:26Z")

</div>

As you are not using a paid version of Psychtoolbox, but an end of life version, I didn’t read far beyond the headline.

But what will obviously end badly if accurate visual stimulus timing matters, as explained on our websites System Requirements section, and numerous times here, is using Intel graphics on MS-Windows. This is true not only for PTB. Intel graphics under Linux is usually fine, at least with PTB, as opposed to other less advanced toolkits.