Millisecond Forums

+x

 

pinguin - 8/1/2025

+x

 

Dave - 7/31/2025

+x

 

pinguin - 7/31/2025

+x

 

Dave - 7/31/2025

+x

 

pinguin - 7/31/2025

+x

 

Dave - 7/31/2025

+x

 

pinguin - 7/31/2025

Dear all,

we have another question regarding Inquisit 7.

We are using an animation in a trial, which is followed by another trial that uses an animation of a picture.

Our problem is the following:

In Inquisit 6, when we clicked on the target stimulus (arrow_forward) within the first trial (intro1) before the animation of the hand (hand_blau picture) was finished, in the subsequent trial the stimulus p9_m3 was presented either way.

Since using Inquisit 7, we have to wait for the animation in the first trial (intro1) to finish; otherwise clicking on arrow_forward will lead to p9_m3 not being shown at all in the subsequent trial (Practice1_1).

Was there a change in the presentation modalities of Inquisit 7?

As soon as we comment the animation of hand_blau out, we can click on arrow_forward whenever we want and the stimulus p9_m3 will be shown in the subsequent trial. It seems as if the animation is the problem.

Is there a fix for this other than making duration_audio1_short longer?

Down below are the script snippets this problem relates to.

In case the full script would be necessary to understand what we mean, you can find it via the following link (but please note, it is very long): https://unitc-my.sharepoint.com/:u:/g/personal/benjamin_goecke_uni-tuebingen_online/EVnr8xO70vdJtwnptlyjR9cBB9vjTR9QcXRy3_LEGqPTOQ?e=aigNiv

Best,

pinguin

<values>
/duration_audio1_short=9000
</values>

<picture arrow_forward>
/ position = (90%, 80%)
/ items = ("arrow_forward.PNG")
/ size = (10%, 10%)
/ erase=false
</picture>

<picture hand_blau>
/ position = (75%, 50%)
/ items = ("hand.svg")
/ size = (15%, 15%)
/ rotation = 315
/ animation = circle(values.duration_animation, 4,1,100,93%,85%,3%) //dauer, anzahl an drehungen, von 1-100, position relativ, radius
/ erase=false
</picture>

<picture p9_m3>
/ items = ("m3.png")
/ position = (60%, 80%)
/ size = (20%, 20%)
/ animation = size(values.duration_animation, 1, 20%, 20%, 1, 0.8, 0.0001)
/ erase=false
</picture>

<trial intro1>
/ inputdevice = mouse
/ validresponse = (arrow_forward)
/ stimulustimes = [0= background_green,bush1, bush2, bush3, bush4, bush5, bush6, bush7, bush8, bush9, audio1_short, speaker; 9750 = bush1, bush2, bush3, bush4, bush5, bush6, bush7, bush8, bush9, hand_blau, arrow_forward, audio2_short, speaker]
/ beginresponsetime = values.duration_audio1_short
/ branch = [
    trial.Practice1_1
]
</trial>

<trial Practice1_1>
/ pretrialpause = values.duration_ISI
/ stimulustimes = [0=background_green, bush1, bush2, bush3, bush4, bush5, bush6, bush7, bush8, bush9, p9_m3, speaker,audio9_short; 4200 = no_speaker]
/ trialduration = 4200
/ branch = [
    trial.Practice1_1_Abruf
]
</trial>

Would you please, always, provide any necessary files required by code you want examined, so one may actually run it?

Thanks.

Yes - see my last reply. You can find the code and all necessary files here: The script is part of an experiment battery that we have also uploaded online. It is called binding_position_1_kids_short.iqx and is part of the upload of this web inquisit link: https://mili2nd.eu/qckc

The problem described in post 1 actually is the very start of the script once you click on "run".

Not reproducing either issue under 7.1.1.
- The p9_m3 animation is shown regardless of whether the blue forward arrow in the intro trial is clicked before the finger animation fineshes or after.
- Similarly, when running block learn_load2_2, both trials (load2_2_1 followed by load2_2_2) are run, and therefore both animations are shown.

Have you double-checked the version installed on whatever system you have observed this on? If it's 7.1.1 already, it might be an issue specific to the Apple Silicon build (I don't have a M-processor Mac with me right now and will have to ask a colleague to check if need be).

Dear Dave,

thank you for the quick response!

On my machine (as written, MacBook Pro, 14“, 2023, M2 Pro, 32GB RAM) I am running the latest version of Inquisit 7 (7.1.1).

After your response I’ve installed Inquisit 7 on a Windows computer and ran the script partly several times. It seems as if there was no issue on this computer.

This indeed makes me wonder whether this is an issue related to the Silicon chip. If this was the case, I am also wondering whether this would also affect iPad Pros using this kind of chips.

I can check whether the issue persists on another Mac tomorrow. Maybe you could also try to verify it.

Keep me updated?

Best,

pinguin

> Keep me updated?

Sure, will do. It's not reproducible under Android either, so that leaves (possibly only some) Apple devices.

Hi Dave,

here’s an update from our side. I think I managed to find the root of the problem.

1. On two other Windows computers the script works fine.

2. On a MacBook Air 24GB M3 it also worked fine.

Curiously, the issue persisted on my MacBook Pro. I first tried deinstalling and re-downloading Inquisit 7, but no luck.

Then I noticed the following:

Usually I am using the MacBook with 2 screens connected via two separate USB-C cords: a vertical 27“ Dell screen (HDMI to dock to USB-C); an a horizontal ultra-wide 34“ Philips 346B1C (USB-C directly) screen.

The failed presentation of the stimuli seems to be connected to the setup: As soon as I am plugging in the MacBook Air, the same presentation error occurs. When the MacBook Pro is unplugged, I cannot reproduce the error.

On the one hand this is somewhat reassuring, because it means that the issue lies not within the programming. On the other hand, it makes me wonder how dependable we are on using the „correct“ setup.

Hope this also somewhat helps to put the whole thread into context.

Best,

pinguin

+x

 

Erik - 8/15/2025

+x

 

pinguin - 8/1/2025

+x

 

Dave - 7/31/2025

+x

 

pinguin - 7/31/2025

+x

 

Dave - 7/31/2025

+x

 

pinguin - 7/31/2025

+x

 

Dave - 7/31/2025

+x

 

pinguin - 7/31/2025

Dear all,

we have another question regarding Inquisit 7.

We are using an animation in a trial, which is followed by another trial that uses an animation of a picture.

Our problem is the following:

In Inquisit 6, when we clicked on the target stimulus (arrow_forward) within the first trial (intro1) before the animation of the hand (hand_blau picture) was finished, in the subsequent trial the stimulus p9_m3 was presented either way.

Since using Inquisit 7, we have to wait for the animation in the first trial (intro1) to finish; otherwise clicking on arrow_forward will lead to p9_m3 not being shown at all in the subsequent trial (Practice1_1).

Was there a change in the presentation modalities of Inquisit 7?

As soon as we comment the animation of hand_blau out, we can click on arrow_forward whenever we want and the stimulus p9_m3 will be shown in the subsequent trial. It seems as if the animation is the problem.

Is there a fix for this other than making duration_audio1_short longer?

Down below are the script snippets this problem relates to.

In case the full script would be necessary to understand what we mean, you can find it via the following link (but please note, it is very long): https://unitc-my.sharepoint.com/:u:/g/personal/benjamin_goecke_uni-tuebingen_online/EVnr8xO70vdJtwnptlyjR9cBB9vjTR9QcXRy3_LEGqPTOQ?e=aigNiv

Best,

pinguin

<values>
/duration_audio1_short=9000
</values>

<picture arrow_forward>
/ position = (90%, 80%)
/ items = ("arrow_forward.PNG")
/ size = (10%, 10%)
/ erase=false
</picture>

<picture hand_blau>
/ position = (75%, 50%)
/ items = ("hand.svg")
/ size = (15%, 15%)
/ rotation = 315
/ animation = circle(values.duration_animation, 4,1,100,93%,85%,3%) //dauer, anzahl an drehungen, von 1-100, position relativ, radius
/ erase=false
</picture>

<picture p9_m3>
/ items = ("m3.png")
/ position = (60%, 80%)
/ size = (20%, 20%)
/ animation = size(values.duration_animation, 1, 20%, 20%, 1, 0.8, 0.0001)
/ erase=false
</picture>

<trial intro1>
/ inputdevice = mouse
/ validresponse = (arrow_forward)
/ stimulustimes = [0= background_green,bush1, bush2, bush3, bush4, bush5, bush6, bush7, bush8, bush9, audio1_short, speaker; 9750 = bush1, bush2, bush3, bush4, bush5, bush6, bush7, bush8, bush9, hand_blau, arrow_forward, audio2_short, speaker]
/ beginresponsetime = values.duration_audio1_short
/ branch = [
    trial.Practice1_1
]
</trial>

<trial Practice1_1>
/ pretrialpause = values.duration_ISI
/ stimulustimes = [0=background_green, bush1, bush2, bush3, bush4, bush5, bush6, bush7, bush8, bush9, p9_m3, speaker,audio9_short; 4200 = no_speaker]
/ trialduration = 4200
/ branch = [
    trial.Practice1_1_Abruf
]
</trial>

Would you please, always, provide any necessary files required by code you want examined, so one may actually run it?

Thanks.

Yes - see my last reply. You can find the code and all necessary files here: The script is part of an experiment battery that we have also uploaded online. It is called binding_position_1_kids_short.iqx and is part of the upload of this web inquisit link: https://mili2nd.eu/qckc

The problem described in post 1 actually is the very start of the script once you click on "run".

Not reproducing either issue under 7.1.1.
- The p9_m3 animation is shown regardless of whether the blue forward arrow in the intro trial is clicked before the finger animation fineshes or after.
- Similarly, when running block learn_load2_2, both trials (load2_2_1 followed by load2_2_2) are run, and therefore both animations are shown.

Have you double-checked the version installed on whatever system you have observed this on? If it's 7.1.1 already, it might be an issue specific to the Apple Silicon build (I don't have a M-processor Mac with me right now and will have to ask a colleague to check if need be).

Dear Dave,

thank you for the quick response!

On my machine (as written, MacBook Pro, 14“, 2023, M2 Pro, 32GB RAM) I am running the latest version of Inquisit 7 (7.1.1).

After your response I’ve installed Inquisit 7 on a Windows computer and ran the script partly several times. It seems as if there was no issue on this computer.

This indeed makes me wonder whether this is an issue related to the Silicon chip. If this was the case, I am also wondering whether this would also affect iPad Pros using this kind of chips.

I can check whether the issue persists on another Mac tomorrow. Maybe you could also try to verify it.

Keep me updated?

Best,

pinguin

> Keep me updated?

Sure, will do. It's not reproducible under Android either, so that leaves (possibly only some) Apple devices.

Hi Dave,

here’s an update from our side. I think I managed to find the root of the problem.

1. On two other Windows computers the script works fine.

2. On a MacBook Air 24GB M3 it also worked fine.

Curiously, the issue persisted on my MacBook Pro. I first tried deinstalling and re-downloading Inquisit 7, but no luck.

Then I noticed the following:

Usually I am using the MacBook with 2 screens connected via two separate USB-C cords: a vertical 27“ Dell screen (HDMI to dock to USB-C); an a horizontal ultra-wide 34“ Philips 346B1C (USB-C directly) screen.

The failed presentation of the stimuli seems to be connected to the setup: As soon as I am plugging in the MacBook Air, the same presentation error occurs. When the MacBook Pro is unplugged, I cannot reproduce the error.

On the one hand this is somewhat reassuring, because it means that the issue lies not within the programming. On the other hand, it makes me wonder how dependable we are on using the „correct“ setup.

Hope this also somewhat helps to put the whole thread into context.

Best,

pinguin

Hi pinguin,

I'm the developer trying to reproduce and fix the issue.  So far I've been unable to reproduce this on any of my Mac computers after testing with different combination of displays that I have (neither my M4 MacBook Pro nor M2 Ultra Mac Studio) .  On the setup where the issue occurs, which of the 3 displays is being considered the "Main display" by macOS?  Also, could you send me a copy of the contents of the "Tools" => "System Information" dialog when the computer is setup in the manner that is reproducing this issue. It may give me a hint as to what may be causing it. Also, could you private message me with the InquisitLab.log file from the relevant system.  Finally, can you describe how the displays are arranged (maybe a screenshot of the "System Settings" => "Displays" => "Arrange Displays" page).

Thanks and Enjoy,
Erik

+x

 

pinguin - 8/21/2025

+x

 

Erik - 8/15/2025

+x

 

pinguin - 8/1/2025

+x

 

Dave - 7/31/2025

+x

 

pinguin - 7/31/2025

+x

 

Dave - 7/31/2025

+x

 

pinguin - 7/31/2025

+x

 

Dave - 7/31/2025

+x

 

pinguin - 7/31/2025

Dear all,

we have another question regarding Inquisit 7.

We are using an animation in a trial, which is followed by another trial that uses an animation of a picture.

Our problem is the following:

In Inquisit 6, when we clicked on the target stimulus (arrow_forward) within the first trial (intro1) before the animation of the hand (hand_blau picture) was finished, in the subsequent trial the stimulus p9_m3 was presented either way.

Since using Inquisit 7, we have to wait for the animation in the first trial (intro1) to finish; otherwise clicking on arrow_forward will lead to p9_m3 not being shown at all in the subsequent trial (Practice1_1).

Was there a change in the presentation modalities of Inquisit 7?

As soon as we comment the animation of hand_blau out, we can click on arrow_forward whenever we want and the stimulus p9_m3 will be shown in the subsequent trial. It seems as if the animation is the problem.

Is there a fix for this other than making duration_audio1_short longer?

Down below are the script snippets this problem relates to.

In case the full script would be necessary to understand what we mean, you can find it via the following link (but please note, it is very long): https://unitc-my.sharepoint.com/:u:/g/personal/benjamin_goecke_uni-tuebingen_online/EVnr8xO70vdJtwnptlyjR9cBB9vjTR9QcXRy3_LEGqPTOQ?e=aigNiv

Best,

pinguin

<values>
/duration_audio1_short=9000
</values>

<picture arrow_forward>
/ position = (90%, 80%)
/ items = ("arrow_forward.PNG")
/ size = (10%, 10%)
/ erase=false
</picture>

<picture hand_blau>
/ position = (75%, 50%)
/ items = ("hand.svg")
/ size = (15%, 15%)
/ rotation = 315
/ animation = circle(values.duration_animation, 4,1,100,93%,85%,3%) //dauer, anzahl an drehungen, von 1-100, position relativ, radius
/ erase=false
</picture>

<picture p9_m3>
/ items = ("m3.png")
/ position = (60%, 80%)
/ size = (20%, 20%)
/ animation = size(values.duration_animation, 1, 20%, 20%, 1, 0.8, 0.0001)
/ erase=false
</picture>

<trial intro1>
/ inputdevice = mouse
/ validresponse = (arrow_forward)
/ stimulustimes = [0= background_green,bush1, bush2, bush3, bush4, bush5, bush6, bush7, bush8, bush9, audio1_short, speaker; 9750 = bush1, bush2, bush3, bush4, bush5, bush6, bush7, bush8, bush9, hand_blau, arrow_forward, audio2_short, speaker]
/ beginresponsetime = values.duration_audio1_short
/ branch = [
    trial.Practice1_1
]
</trial>

<trial Practice1_1>
/ pretrialpause = values.duration_ISI
/ stimulustimes = [0=background_green, bush1, bush2, bush3, bush4, bush5, bush6, bush7, bush8, bush9, p9_m3, speaker,audio9_short; 4200 = no_speaker]
/ trialduration = 4200
/ branch = [
    trial.Practice1_1_Abruf
]
</trial>

Would you please, always, provide any necessary files required by code you want examined, so one may actually run it?

Thanks.

Yes - see my last reply. You can find the code and all necessary files here: The script is part of an experiment battery that we have also uploaded online. It is called binding_position_1_kids_short.iqx and is part of the upload of this web inquisit link: https://mili2nd.eu/qckc

The problem described in post 1 actually is the very start of the script once you click on "run".

Not reproducing either issue under 7.1.1.
- The p9_m3 animation is shown regardless of whether the blue forward arrow in the intro trial is clicked before the finger animation fineshes or after.
- Similarly, when running block learn_load2_2, both trials (load2_2_1 followed by load2_2_2) are run, and therefore both animations are shown.

Have you double-checked the version installed on whatever system you have observed this on? If it's 7.1.1 already, it might be an issue specific to the Apple Silicon build (I don't have a M-processor Mac with me right now and will have to ask a colleague to check if need be).

Dear Dave,

thank you for the quick response!

On my machine (as written, MacBook Pro, 14“, 2023, M2 Pro, 32GB RAM) I am running the latest version of Inquisit 7 (7.1.1).

After your response I’ve installed Inquisit 7 on a Windows computer and ran the script partly several times. It seems as if there was no issue on this computer.

This indeed makes me wonder whether this is an issue related to the Silicon chip. If this was the case, I am also wondering whether this would also affect iPad Pros using this kind of chips.

I can check whether the issue persists on another Mac tomorrow. Maybe you could also try to verify it.

Keep me updated?

Best,

pinguin

> Keep me updated?

Sure, will do. It's not reproducible under Android either, so that leaves (possibly only some) Apple devices.

Hi Dave,

here’s an update from our side. I think I managed to find the root of the problem.

1. On two other Windows computers the script works fine.

2. On a MacBook Air 24GB M3 it also worked fine.

Curiously, the issue persisted on my MacBook Pro. I first tried deinstalling and re-downloading Inquisit 7, but no luck.

Then I noticed the following:

Usually I am using the MacBook with 2 screens connected via two separate USB-C cords: a vertical 27“ Dell screen (HDMI to dock to USB-C); an a horizontal ultra-wide 34“ Philips 346B1C (USB-C directly) screen.

The failed presentation of the stimuli seems to be connected to the setup: As soon as I am plugging in the MacBook Air, the same presentation error occurs. When the MacBook Pro is unplugged, I cannot reproduce the error.

On the one hand this is somewhat reassuring, because it means that the issue lies not within the programming. On the other hand, it makes me wonder how dependable we are on using the „correct“ setup.

Hope this also somewhat helps to put the whole thread into context.

Best,

pinguin

Hi pinguin,

I'm the developer trying to reproduce and fix the issue.  So far I've been unable to reproduce this on any of my Mac computers after testing with different combination of displays that I have (neither my M4 MacBook Pro nor M2 Ultra Mac Studio) .  On the setup where the issue occurs, which of the 3 displays is being considered the "Main display" by macOS?  Also, could you send me a copy of the contents of the "Tools" => "System Information" dialog when the computer is setup in the manner that is reproducing this issue. It may give me a hint as to what may be causing it. Also, could you private message me with the InquisitLab.log file from the relevant system.  Finally, can you describe how the displays are arranged (maybe a screenshot of the "System Settings" => "Displays" => "Arrange Displays" page).

Thanks and Enjoy,
Erik

Hi Erik,

sorry for the late response.

Hmm, that’s curious.

Here is the setup I am using:

MacBook Pro, 14“, 2023
M2 Pro
32GB
Sequoia 15.6

Modellname:    MacBook Pro
Modell-Identifizierung:    Mac14,9
Modellnummer:    Z17H000R7D/A
Chip:    Apple M2 Pro
Gesamtanzahl der Kerne:    12 (8 Leistung und 4 Effizienz)
Speicher:    32 GB
Systemfirmwareversion:    11881.140.96
OS-Ladeprogrammversion:    11881.140.96
Seriennummer (System):    LFFQW214L2

Screens:
Dell U2515H (vertically)
PHL 346B1C (ultra-wide, horizontally) —> this is the main screen.

Not sure where I can find the InquisitLab.log file.

Best,

pinguin

+x

 

pinguin - 8/21/2025

+x

 

Erik - 8/15/2025

+x

 

pinguin - 8/1/2025

+x

 

Dave - 7/31/2025

+x

 

pinguin - 7/31/2025

+x

 

Dave - 7/31/2025

+x

 

pinguin - 7/31/2025

+x

 

Dave - 7/31/2025

+x

 

pinguin - 7/31/2025

Dear all,

we have another question regarding Inquisit 7.

We are using an animation in a trial, which is followed by another trial that uses an animation of a picture.

Our problem is the following:

In Inquisit 6, when we clicked on the target stimulus (arrow_forward) within the first trial (intro1) before the animation of the hand (hand_blau picture) was finished, in the subsequent trial the stimulus p9_m3 was presented either way.

Since using Inquisit 7, we have to wait for the animation in the first trial (intro1) to finish; otherwise clicking on arrow_forward will lead to p9_m3 not being shown at all in the subsequent trial (Practice1_1).

Was there a change in the presentation modalities of Inquisit 7?

As soon as we comment the animation of hand_blau out, we can click on arrow_forward whenever we want and the stimulus p9_m3 will be shown in the subsequent trial. It seems as if the animation is the problem.

Is there a fix for this other than making duration_audio1_short longer?

Down below are the script snippets this problem relates to.

In case the full script would be necessary to understand what we mean, you can find it via the following link (but please note, it is very long): https://unitc-my.sharepoint.com/:u:/g/personal/benjamin_goecke_uni-tuebingen_online/EVnr8xO70vdJtwnptlyjR9cBB9vjTR9QcXRy3_LEGqPTOQ?e=aigNiv

Best,

pinguin

<values>
/duration_audio1_short=9000
</values>

<picture arrow_forward>
/ position = (90%, 80%)
/ items = ("arrow_forward.PNG")
/ size = (10%, 10%)
/ erase=false
</picture>

<picture hand_blau>
/ position = (75%, 50%)
/ items = ("hand.svg")
/ size = (15%, 15%)
/ rotation = 315
/ animation = circle(values.duration_animation, 4,1,100,93%,85%,3%) //dauer, anzahl an drehungen, von 1-100, position relativ, radius
/ erase=false
</picture>

<picture p9_m3>
/ items = ("m3.png")
/ position = (60%, 80%)
/ size = (20%, 20%)
/ animation = size(values.duration_animation, 1, 20%, 20%, 1, 0.8, 0.0001)
/ erase=false
</picture>

<trial intro1>
/ inputdevice = mouse
/ validresponse = (arrow_forward)
/ stimulustimes = [0= background_green,bush1, bush2, bush3, bush4, bush5, bush6, bush7, bush8, bush9, audio1_short, speaker; 9750 = bush1, bush2, bush3, bush4, bush5, bush6, bush7, bush8, bush9, hand_blau, arrow_forward, audio2_short, speaker]
/ beginresponsetime = values.duration_audio1_short
/ branch = [
    trial.Practice1_1
]
</trial>

<trial Practice1_1>
/ pretrialpause = values.duration_ISI
/ stimulustimes = [0=background_green, bush1, bush2, bush3, bush4, bush5, bush6, bush7, bush8, bush9, p9_m3, speaker,audio9_short; 4200 = no_speaker]
/ trialduration = 4200
/ branch = [
    trial.Practice1_1_Abruf
]
</trial>

Would you please, always, provide any necessary files required by code you want examined, so one may actually run it?

Thanks.

Yes - see my last reply. You can find the code and all necessary files here: The script is part of an experiment battery that we have also uploaded online. It is called binding_position_1_kids_short.iqx and is part of the upload of this web inquisit link: https://mili2nd.eu/qckc

The problem described in post 1 actually is the very start of the script once you click on "run".

Not reproducing either issue under 7.1.1.
- The p9_m3 animation is shown regardless of whether the blue forward arrow in the intro trial is clicked before the finger animation fineshes or after.
- Similarly, when running block learn_load2_2, both trials (load2_2_1 followed by load2_2_2) are run, and therefore both animations are shown.

Have you double-checked the version installed on whatever system you have observed this on? If it's 7.1.1 already, it might be an issue specific to the Apple Silicon build (I don't have a M-processor Mac with me right now and will have to ask a colleague to check if need be).

Dear Dave,

thank you for the quick response!

On my machine (as written, MacBook Pro, 14“, 2023, M2 Pro, 32GB RAM) I am running the latest version of Inquisit 7 (7.1.1).

After your response I’ve installed Inquisit 7 on a Windows computer and ran the script partly several times. It seems as if there was no issue on this computer.

This indeed makes me wonder whether this is an issue related to the Silicon chip. If this was the case, I am also wondering whether this would also affect iPad Pros using this kind of chips.

I can check whether the issue persists on another Mac tomorrow. Maybe you could also try to verify it.

Keep me updated?

Best,

pinguin

> Keep me updated?

Sure, will do. It's not reproducible under Android either, so that leaves (possibly only some) Apple devices.

Hi Dave,

here’s an update from our side. I think I managed to find the root of the problem.

1. On two other Windows computers the script works fine.

2. On a MacBook Air 24GB M3 it also worked fine.

Curiously, the issue persisted on my MacBook Pro. I first tried deinstalling and re-downloading Inquisit 7, but no luck.

Then I noticed the following:

Usually I am using the MacBook with 2 screens connected via two separate USB-C cords: a vertical 27“ Dell screen (HDMI to dock to USB-C); an a horizontal ultra-wide 34“ Philips 346B1C (USB-C directly) screen.

The failed presentation of the stimuli seems to be connected to the setup: As soon as I am plugging in the MacBook Air, the same presentation error occurs. When the MacBook Pro is unplugged, I cannot reproduce the error.

On the one hand this is somewhat reassuring, because it means that the issue lies not within the programming. On the other hand, it makes me wonder how dependable we are on using the „correct“ setup.

Hope this also somewhat helps to put the whole thread into context.

Best,

pinguin

Hi pinguin,

I'm the developer trying to reproduce and fix the issue.  So far I've been unable to reproduce this on any of my Mac computers after testing with different combination of displays that I have (neither my M4 MacBook Pro nor M2 Ultra Mac Studio) .  On the setup where the issue occurs, which of the 3 displays is being considered the "Main display" by macOS?  Also, could you send me a copy of the contents of the "Tools" => "System Information" dialog when the computer is setup in the manner that is reproducing this issue. It may give me a hint as to what may be causing it. Also, could you private message me with the InquisitLab.log file from the relevant system.  Finally, can you describe how the displays are arranged (maybe a screenshot of the "System Settings" => "Displays" => "Arrange Displays" page).

Thanks and Enjoy,
Erik

Hi Erik,

sorry for the late response.

Hmm, that’s curious.

Here is the setup I am using:

MacBook Pro, 14“, 2023
M2 Pro
32GB
Sequoia 15.6

Modellname:    MacBook Pro
Modell-Identifizierung:    Mac14,9
Modellnummer:    Z17H000R7D/A
Chip:    Apple M2 Pro
Gesamtanzahl der Kerne:    12 (8 Leistung und 4 Effizienz)
Speicher:    32 GB
Systemfirmwareversion:    11881.140.96
OS-Ladeprogrammversion:    11881.140.96
Seriennummer (System):    LFFQW214L2

Screens:
Dell U2515H (vertically)
PHL 346B1C (ultra-wide, horizontally) —> this is the main screen.

Not sure where I can find the InquisitLab.log file.

Best,

pinguin

+x

 

pinguin - 8/21/2025

Thanks! Will send it via DM asap

+x

 

pinguin - 8/29/2025

Hi Dave,will respond again once I have my setup available again - right now on the road with just the laptop.Best,pinguin