# VBL Sync not working for NVIDIA A6000 \[Paid Support\] **URL:** \ **Category:** Programming Help\ **Tags:** linux, timing\ **Created:** [April 26, 2023, 10:17pm UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962 "2023-04-26T22:17:09Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![PaulLinton](https://yyz2.discourse-cdn.com/free1/user_avatar/psychtoolbox.discourse.group/paullinton/32/518_2.png) [@PaulLinton](https://psychtoolbox.discourse.group/u/PaulLinton)\ **Post date:** [April 26, 2023, 10:17pm UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962/1 "2023-04-26T22:17:09Z")
Paid Support: WTPJMXZK-2023426175827:1b158fe5c842e3b4622ba79ae240a4bd70f03c6b41f839c85bad77f40e0396fe I’m trying to vsync my graphics card and display but get the following error (e.g. if run PerceptualVBLSyncTest): PTB-INFO: OpenGL-Renderer is NVIDIA Corporation :: NVIDIA RTX A6000/PCIe/SSE2 :: 4.6.0 NVIDIA 525.89.02 PTB-INFO: VBL startline = 1080 , VBL Endline = -1 PTB-INFO: Beamposition queries unsupported or defective on this system. Using basic timestamping asfallback. VBL Sync is necessary as trying to run shutter glasses on display. Solutions I’ve tried: 1. All the steps in “help SyncTrouble” and “help BeampositionQueries” 2. clear all; Screen(‘Preference’, ‘ScreenToHead’, 0, 0, n); for a n of 0, 1, 2, or 3 from: [Beamposition synch problems with Nvidia gpu and Ubuntu 18.04 LTS · Issue #645 · Psychtoolbox-3/Psychtoolbox-3 · GitHub](https://github.com/Psychtoolbox-3/Psychtoolbox-3/issues/645) I’ve also tried combinations of a 4th number for linux, but unclear what I should be doing 3. Checking G-SYNC not enabled (not present in NVIDIA control panel, and not a feature of this graphics card) 4. Drivers, Octave, and PsychToolbox should be up to date Forum discussions I’ve looked at: > > > Hello, > I used to use PTB-3 with MS Windows but now I am in need of high timing… precision, and as I read in the PTB documentation, Linux is the best option for that, so I'm transitioning to Ubuntu 18.04 LTS. > Matlab version R2019b and using Nvidia GeForce GTX 1070 Ti with proprietary driver. I installed PTB-3 via Neuro Debian. I successfully ran PsychLinuxConfiguration(). > However, the following WARNINGS and errors appear when I run PTB code (such as BeampositionTest.m). > > \`\`\` > PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under Matlab 64-Bit (Version 3.0.15 - Build date: Jul 17 2019). > PTB-INFO: Support status on this operating system release: Linux 5.3.0-28-generic Supported. > 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-INFO: NVIDIA Corporation - GP104 \[GeForce GTX 1070 Ti\] GPU found. Trying to establish low-level access... > PTB-INFO: Connected to NVidia GP104 \[GeForce GTX 1070 Ti\] GPU of NV-130 family with 4 display heads. > PTB-WARNING: Hang in beamposition query detected! Seems my mapping of screen numbers to GPU's and display outputs is wrong? > PTB-WARNING: In a single GPU system you can resolve this by plugging in your monitors in a different order, changing the > PTB-WARNING: display arrangement in the control panel, or using the Screen('Preference', 'ScreenToHead', ...); > PTB-WARNING: command at the top of your scripts to set the mapping manually. See 'help DisplayOutputMappings' for more info. > PTB-WARNING: > PTB-WARNING: I am not yet able to handle multi-GPU systems reliably at all. If you have such a system it may work if > PTB-WARNING: you plug your monitor(s) into one of the other GPU's output connectors, trying different combinations. > PTB-WARNING: Or you simply live without high precision stimulus onset timestamping for now. Or you use the free and open-source > PTB-WARNING: graphics drivers (intel, radeon, or nouveau) instead of the proprietary Catalyst or NVidia binary drivers. > PTB-WARNING: I've disabled high precision timestamping for this screen for the remainder of the session. > > WARNING: Measured a negative beam position value after VBL onset!?! Broken display driver!! > > PTB-WARNING: Couldn't determine end-line of vertical blanking interval for your display! Trouble with beamposition queries?!? > PTB-WARNING: Detected end-line is -1, which is either lower or more than 1.250000 times higher than vbl startline 1080 --\> Out of sane range! > > > PTB-INFO: OpenGL-Renderer is NVIDIA Corporation :: GeForce GTX 1070 Ti/PCIe/SSE2 :: 4.6.0 NVIDIA 435.21 > PTB-INFO: VBL startline = 1080 , VBL Endline = -1 > PTB-INFO: Beamposition queries unsupported or defective on this system. Using basic timestamping as fallback. > PTB-INFO: Timestamps returned by Screen('Flip') will be therefore less robust and accurate. > PTB-INFO: Measured monitor refresh interval from VBLsync = 4.182363 ms \[239.099310 Hz\]. (50 valid samples taken, stddev=0.075391 ms.) > PTB-INFO: Reported monitor refresh interval from operating system = 4.166667 ms \[240.000000 Hz\]. > PTB-INFO: Small deviations between reported values are normal and no reason to worry. > > > \----- ! PTB - WARNING: SYNCHRONIZATION TROUBLE ! ---- > > One or more internal checks (see Warnings above) indicate that > queries of rasterbeam position are not properly working for your setup. > > Psychtoolbox will work around this by using a different timing algorithm, > but it will cause Screen('Flip') to report less accurate/robust timestamps > for stimulus timing. > Read 'help BeampositionQueries' for more info and troubleshooting tips. > > > WARNING: Beamposition queries broken or disabled or unsupported on your setup! > \`\`\` > > > I went through the 'DisplayOutputMappings' and 'BeampositionQueries' help but I couldn't solve my problem. I am only using one display and a single GPU. Tried to replug the display into different video output connectors too. > > Thanks for your help. > > > I am using Psychtoolbox on MacOS HighSierra 10.13.4. I am having trouble with th…e VBL. I am getting the following error. I don't want to skip the sync test as I need the timings to be accurate. Can somebody help me with this? > \screen shot 2018-05-09 at 12 54 43 pm > [@Synch trouble on linux Ubuntu 18.04 with GeForce GTX 1650 nvidia GPU](https://psychtoolbox.discourse.group/t/synch-trouble-on-linux-ubuntu-18-04-with-geforce-gtx-1650-nvidia-gpu/3407/2): > > Hi Lilian, Your Psychtoolbox is way too old to recognize your graphics card. Updating to the latest 3.0.16 beta for Octave from NeuroDebian should solve that: I have the same GTX1650 is my most modern NVidia card, so i know that it works with current PTB at least on Ubuntu 20.04-LTS. Ie. timestamping is fine and accurate, timing is usually fine. Maybe the problem resolves itself after the PTB update. Otherwise, the proper mapping is probably one that only changes the index of the display … > [@Beamposition queries broken or disabled or unsupported on your setup!](https://psychtoolbox.discourse.group/t/beamposition-queries-broken-or-disabled-or-unsupported-on-your-setup/4096/2): > > That’s normal on Intel graphics. Beamposition queries are only supported on NVidia and on slightly older AMD (up to and including AMD Vega), not on Intel or on graphics chips like the RaspberryPi. No reason to worry, as the OS supported diagnostic and timestamping methods are at least as reliable and accurate as beamposition queries. Indeed, whenever you use an open-source (Mesa) graphics driver, beamposition queries are just another measure to verify and check, not the primary method of timing… Hardware / software: Linux version: Ubuntu 22.04.2 LTS Graphics card: RTX A6000 NVIDIA driver: 525.89.02 Octave version: 6.4.0 PsychToolbox version: 3.0.18 Thanks so much, I really appreciate it!! Paul ---
**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\ **Post date:** [April 27, 2023, 1:18am UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962/2 "2023-04-27T01:18:27Z")
Technically, you don’t need high precision timestamping to work just to driver stereo shutter glasses, it only enables some additional timing checks and more precise and robust stimulus onset timestamps. All you need is to connect your glasses/emitter to the graphics card and follow NVidia’s setup instructions to enable frame-sequential stereo mode. Then Psychtoolbox stereomode 1 for native OpenGL quad-buffered stereo should do the trick. We have `FrameSequentialStereoTest()` to exercise and test shutter glasses for proper sync and to demonstrate the use of the optional `param1` parameter in `Screen('SelectStereoDrawBuffer', windowPtr [, bufferid] [, param1]);` Ideally you’d not use a NVidia gpu, to avoid much hassle, but a recommended AMD or Intel gpu with open-source drivers, but given this very expensive gpu would be overkill for typical vision science, i assume the gpu is there for some machine learning or other gpu computing? This is a single X-Screen, single display setup, right? Your PTB is not the latest, the latest right now is PTB 3.0.19.2. Proper gpu detection support for your NVidia RTX A6000 Ampere family gpu was introduced in PTB 3.0.19.0. You can get the latest PTB from us via the usual UpdatePsychtoolbox, or from NeuroDebian. → Update PTB. I assume secure boot is disabled in your systems EFI firmware settings, as required for this to work on NVidia gpu’s? Apart from that, post full output with `Screen('Preference','Verbosity', 10); PerceptualVBLSyncTest`, a short run of a second is enough, we don’t need redundant output from every single flip inside that script. [18 out of 30 minutes of paid support used up] ---
**Author:** ![PaulLinton](https://yyz2.discourse-cdn.com/free1/user_avatar/psychtoolbox.discourse.group/paullinton/32/518_2.png) [@PaulLinton](https://psychtoolbox.discourse.group/u/PaulLinton)\ **Post date:** [April 28, 2023, 1:31am UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962/3 "2023-04-28T01:31:36Z")
Thanks so much Mario, that’s incredibly useful! We’re using the GPU for VR (recommended GPU by Varjo), but also in this context to drive Volfoni shutter glasses using 3-pin stereo directly from graphics card (as a Quadro card). System works incredibly well with LCD display (thanks to PsychToolbox!!), but breaks down with OLED, and hope is that with more accurate timing this might improve. Yes, it’s a single X-Screen, single display setup. And apologies, just recalibrated NeuroDebian and now gives me 3.0.19.2 rather than 3.0.18.4 it gave me yesterday. 3.0.19.2 doesn’t fix it, and I think the issue is the EFI firmware settings. I disabled Secure Boot, but just realised computer only launches in Legacy BIOS not UEFI, so fixing this now! Seems to make sense to fix that first, then dive into PerceptualVBLSyncTest if still unresolved. Thanks so much, I really appreciate all your help on this! ---
**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\ **Post date:** [April 28, 2023, 2:06am UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962/4 "2023-04-28T02:06:14Z")
> [@PaulLinton](#): > > Thanks so much Mario, that’s incredibly useful! > > We’re using the GPU for VR (recommended GPU by Varjo), but also in this context to Interesting. The high-end card makes sense, given the Varjo HMD’s are about as high-end and demanding as it gets. Maybe you want to give the latest Psychtoolbox 3.0.19.2 a spin with the Varjo? The big new feature of PTB 3.0.19 after a year of development is OpenXR support on Linux and Windows for OpenXR VR HMDs, so PTB for Windows should be able to use the Varjo’s. `help OpenXR` for setup and background info. Demos are e.g., VRHMDDemo, VRHMDDemo1, VRInputStuffTest, ImagingStereoDemo(103), a few others that use PsychVRHMD() functionality. I’d love to hear if it works as expected, although our demos will bore the Varjo to death. So far i’ve verified our driver works well with MonadoXR and SteamVR on Linux and OculusVR and SteamVR on Windows. Tested hardware so far was a Oculus Rift CV-1 + Oculus touch controllers and remot, and a HTC Vive Pro Eye + Vive Wand controllers. I wouldn’t have the funding to even rent a Varjo for testing, or any machine or graphics card powerful enough to drive it, for that matter. The Varjo’s come with their own OpenXR runtime afaik. Would love to see the PTB output when running on a Varjo. > [@](#): > > drive Volfoni shutter glasses using 3-pin stereo directly from graphics card (as a Quadro card). > > System works incredibly well with LCD display (thanks to PsychToolbox!!), but breaks down with OLED, and hope is that with more accurate timing this might improve. Hmm. How does the breakdown manifest itself? What would be the reasoning that more precise visual onset timestamps would help? > [@](#): > > Yes, it’s a single X-Screen, single display setup. And apologies, just recalibrated NeuroDebian and now gives me 3.0.19.2 rather than 3.0.18.4 it gave me yesterday. NeuroDebian: Did you manually run `PsychLinuxConfiguration` and reboot the machine once after installing PTB? This setup script is automatically run when using DownloadPsychtoolbox/UpdatePsychtoolbox/SetupPsychtoolbox on a PTB downloaded from us directly, but it needs to be manually run after a NeuroDebian install. Otherwise your system won’t be configured for PTB to be able to perform low-level access to the NVidia gpu. > [@](#): > > 3.0.19.2 doesn’t fix it, and I think the issue is the EFI firmware settings. I disabled Secure Boot, but just realised computer only launches in Legacy BIOS not UEFI, so fixing this now! > > Seems to make sense to fix that first, then dive into PerceptualVBLSyncTest if still unresolved. > > Thanks so much, I really appreciate all your help on this! Best to show me the full PTB output messages at high verbosity to narrow this down. -mario [20 out of 30 minutes of paid support used up] ---
**Author:** ![PaulLinton](https://yyz2.discourse-cdn.com/free1/user_avatar/psychtoolbox.discourse.group/paullinton/32/518_2.png) [@PaulLinton](https://psychtoolbox.discourse.group/u/PaulLinton)\ **Post date:** [April 29, 2023, 6:08pm UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962/5 "2023-04-29T18:08:02Z")
Hi Mario, Thanks so much, again, for all your help. I really appreciate it. [1]. “Maybe you want to give the latest Psychtoolbox 3.0.19.2 a spin with the Varjo?” Yes, very happy to help. Waiting on replacement headset at moment, but once that’s up and running will report back! [2]. On shutter glasses working with LCD but not OLED: “How does the breakdown manifest itself? What would be the reasoning that more precise visual onset timestamps would help?” Both views seem to be equally visible in the two eyes even though shutter glasses working at 120Hz. OLED should work with shutter glasses: > **[Perceptual Requirements for Eye-Tracked...](https://dl.acm.org/doi/abs/10.1145/3528233.3530699)** Which leads me to think display and shutter glasses out of sync. Ideally, I’d like to use G-Sync (via PsychtoolBox’s VRRSupport), but first trying VBLSync. [3]. Beamposition issue still present, but I’ve taken the following steps: Because my hard drive was partitioned between Linux and Windows, was booting in CSM mode: “some UEFI implementations immediately switch to the BIOS-based CSM booting upon detecting certain types of partition table on the boot disk, effectively preventing UEFI booting to be performed from EFI system partitions contained on MBR-partitioned disks.” > **[EFI system partition](https://en.wikipedia.org/wiki/EFI_system_partition)** > > The EFI (Extensible Firmware Interface) system partition or ESP is a partition on a data storage device (usually a hard disk drive or solid-state drive) that is used by computers having the Unified Extensible Firmware Interface (UEFI). When a computer is booted, UEFI firmware loads files stored on the ESP to start installing operating systems and various utilities. > An ESP contains the boot loaders or kernel images for all installed operating systems (which are contained in other partitions), de... Which meant “EFI variables are not supported on this system” (tested with “sudo efibootmgr”). This is now resolved by reformatting hard drive for just Ubuntu. So reinstalled Ubuntu (22.04.2 LTS), Octave (6.4.0), and PsychToolbox (3.0.19.2). G-Sync now present and disabled. Running PerceptualVBLSyncTest I now get a new error: PTB-INFO: Failed to enable realtime-scheduling [Operation not permitted]! PTB-INFO: You need to run the script PsychLinuxConfiguration once, then logout and login again for this to work. But I’ve run “sudo octave” then “PsychLinuxConfiguration” in the terminal and got: “Finished. Your system should now be ready for use with Psychtoolbox. If you encounter problems, try rebooting the machine. Some of the settings only become effective after a reboot.” And rebooted. [4]. This seems to be indicative of problem finding graphics card? Running “Screen(‘Preference’,‘Verbosity’, 10); PerceptualVBLSyncTest” (attached as txt) I get checks for graphics cards including: PTB-DEBUG: Checking PCI device [NVIDIA Corporation GA102GL [RTX A6000]] with class x00030000 … But it ultimately returns: PTB-INFO: No low-level controllable GPU on screenId 0. Beamposition timestamping and other special functions disabled. Thanks so much Mario, I really appreciate all your help on this!! And enjoy your break 🙂 Paul ---
**Author:** ![PaulLinton](https://yyz2.discourse-cdn.com/free1/user_avatar/psychtoolbox.discourse.group/paullinton/32/518_2.png) [@PaulLinton](https://psychtoolbox.discourse.group/u/PaulLinton)\ **Post date:** [April 29, 2023, 6:11pm UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962/6 "2023-04-29T18:11:38Z")
OUTPUT OF “Screen(‘Preference’,‘Verbosity’, 10); PerceptualVBLSyncTest”: PTB-INFO: This is Psychtoolbox-3 for GNU/Linux X11, under GNU/Octave 64-Bit (Version 3.0.19 - Build date: Apr 25 2023). PTB-INFO: OS support status: Linux 5.19.0-41-generic Supported. 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-INFO: For information about paid support, support memberships and other commercial services, please type PTB-INFO: ‘PsychPaidSupportAndServices’. PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E DMI3 Registers] with class x00060000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CBDMA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CBDMA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CBDMA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CBDMA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CBDMA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CBDMA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CBDMA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CBDMA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E MM/Vt-d Configuration Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E RAS] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E IOAPIC] with class x00080020 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Ubox Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Ubox Registers] with class x00110100 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Ubox Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller] with class x000c0330 … PTB-DEBUG: Checking PCI device [Intel Corporation 200 Series PCH Thermal Subsystem] with class x00118000 … PTB-DEBUG: Checking PCI device [Intel Corporation 200 Series PCH CSME HECI #1] with class x00078000 … PTB-DEBUG: Checking PCI device [Intel Corporation 200 Series PCH SATA controller [AHCI mode]] with class x00010601 … PTB-DEBUG: Checking PCI device [Intel Corporation 200 Series PCH PCI Express Root Port #17] with class x00060400 … PTB-DEBUG: Checking PCI device [Intel Corporation 200 Series PCH PCI Express Root Port #19] with class x00060400 … PTB-DEBUG: Checking PCI device [Intel Corporation 200 Series PCH PCI Express Root Port #1] with class x00060400 … PTB-DEBUG: Checking PCI device [Intel Corporation 200 Series PCH PCI Express Root Port #4] with class x00060400 … PTB-DEBUG: Checking PCI device [Intel Corporation 200 Series PCH PCI Express Root Port #5] with class x00060400 … PTB-DEBUG: Checking PCI device [Intel Corporation 200 Series PCH PCI Express Root Port #7] with class x00060400 … PTB-DEBUG: Checking PCI device [Intel Corporation X299 Chipset LPC/eSPI Controller] with class x00060100 … PTB-DEBUG: Checking PCI device [Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller] with class x00058000 … PTB-DEBUG: Checking PCI device [Intel Corporation 200 Series PCH HD Audio] with class x00040300 … PTB-DEBUG: Checking PCI device [Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller] with class x000c0500 … PTB-DEBUG: Checking PCI device [ASMedia Technology Inc. ASM2142 USB 3.1 Host Controller] with class x000c0330 … PTB-DEBUG: Checking PCI device [ASMedia Technology Inc. ASM2142 USB 3.1 Host Controller] with class x000c0330 … PTB-DEBUG: Checking PCI device [Aquantia Corp. AQC108 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion]] with class x00020000 … PTB-DEBUG: Checking PCI device [Intel Corporation I210 Gigabit Network Connection] with class x00020000 … PTB-DEBUG: Checking PCI device [ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge] with class x00060400 … PTB-DEBUG: Checking PCI device [ASPEED Technology, Inc. ASPEED Graphics Family] with class x00030000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E VT-d] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E RAS Configuration Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E IOxAPIC Configuration Registers] with class x00080020 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E CHA Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E PCU Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E PCU Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E PCU Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E PCU Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E PCU Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E PCU Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E PCU Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E PCI Express Root Port A] with class x00060400 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E VT-d] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E RAS Configuration Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E IOxAPIC Configuration Registers] with class x00080020 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Integrated Memory Controller] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Integrated Memory Controller] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Integrated Memory Controller] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Integrated Memory Controller] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Integrated Memory Controller] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Integrated Memory Controller] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Integrated Memory Controller] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E LM Channel 1] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E LMS Channel 1] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E LMDP Channel 1] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E DECS Channel 2] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E LM Channel 2] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E LMS Channel 2] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E LMDP Channel 2] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Integrated Memory Controller] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Integrated Memory Controller] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Integrated Memory Controller] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Integrated Memory Controller] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E Integrated Memory Controller] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E LM Channel 1] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E LMS Channel 1] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E LMDP Channel 1] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E DECS Channel 2] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E LM Channel 2] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E LMS Channel 2] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E LMDP Channel 2] with class x00088000 … PTB-DEBUG: Checking PCI device [NVIDIA Corporation GA102GL [RTX A6000]] with class x00030000 … PTB-DEBUG: Checking PCI device [NVIDIA Corporation GA102 High Definition Audio Controller] with class x00040300 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E VT-d] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E RAS Configuration Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E IOxAPIC Configuration Registers] with class x00080020 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E M3KTI Registers] with class x00110100 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E M3KTI Registers] with class x00110100 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E M3KTI Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E M2PCI Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E M2PCI Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E M2PCI Registers] with class x00088000 … PTB-DEBUG: Checking PCI device [Intel Corporation Sky Lake-E M2PCI Registers] with class x00088000 … PTB-INFO: No low-level controllable GPU on screenId 0. Beamposition timestamping and other special functions disabled. PTB-INFO: Using old-style override-redirect (=1) setup path for onscreen window creation. PTB-INFO: GLX Visual info depths is 24 bits PTB-INFO: Not running on Mesa graphics library. PTB-INFO: Using GLEW version 2.1.0 for automatic detection of OpenGL extensions… PTB-INFO: Window uses DRI3/Present for Optimus/Prime renderoffload visual stimulus presentation on display gpu. PTB-INFO: Fixed point precision integer framebuffer enabled. PTB-INFO: System Frame buffer provides 8 bits for red channel. PTB-INFO: System Frame buffer provides 8 bits for green channel. PTB-INFO: System Frame buffer provides 8 bits for blue channel. PTB-INFO: System frame buffer provides 8 bits for alpha channel, but effective alpha bits depends on imaging pipeline setup, if any. PTB-DEBUG: PPM file magic is P6 → Ok # Created by GIMP version 2.10.22 PNM plug-in PTB-DEBUG: Recognized splash image of 1000 x 750 pixels, maxlevel 255. Loading… OpenGL-Vendor / renderer / version are: NVIDIA Corporation - NVIDIA RTX A6000/PCIe/SSE2 - 4.6.0 NVIDIA 525.116.03 OpenGL-Extensions are: GL\_AMD\_multi\_draw\_indirect GL\_AMD\_seamless\_cubemap\_per\_texture GL\_AMD\_vertex\_shader\_viewport\_index GL\_AMD\_vertex\_shader\_layer GL\_ARB\_arrays\_of\_arrays GL\_ARB\_base\_instance GL\_ARB\_bindless\_texture GL\_ARB\_blend\_func\_extended GL\_ARB\_buffer\_storage GL\_ARB\_cl\_event GL\_ARB\_clear\_buffer\_object GL\_ARB\_clear\_texture GL\_ARB\_clip\_control GL\_ARB\_color\_buffer\_float GL\_ARB\_compatibility GL\_ARB\_compressed\_texture\_pixel\_storage GL\_ARB\_conservative\_depth GL\_ARB\_compute\_shader GL\_ARB\_compute\_variable\_group\_size GL\_ARB\_conditional\_render\_invertedGL\_ARB\_copy\_buffer GL\_ARB\_copy\_image GL\_ARB\_cull\_distance GL\_ARB\_debug\_output GL\_ARB\_depth\_buffer\_float GL\_ARB\_depth\_clamp GL\_ARB\_depth\_texture GL\_ARB\_derivative\_control GL\_ARB\_direct\_state\_access GL\_ARB\_draw\_buffers GL\_ARB\_draw\_buffers\_blend GL\_ARB\_draw\_indirect GL\_ARB\_draw\_elements\_base\_vertex GL\_ARB\_draw\_instanced GL\_ARB\_enhanced\_layouts GL\_ARB\_ES2\_compatibility GL\_ARB\_ES3\_compatibility GL\_ARB\_ES3\_1\_compatibility GL\_ARB\_ES3\_2\_compatibility GL\_ARB\_explicit\_attrib\_location GL\_ARB\_explicit\_uniform\_location GL\_ARB\_fragment\_coord\_conventions GL\_ARB\_fragment\_layer\_viewport GL\_ARB\_fragment\_program GL\_ARB\_fragment\_program\_shadow GL\_ARB\_fragment\_shader GL\_ARB\_fragment\_shader\_interlock GL\_ARB\_framebuffer\_no\_attachments GL\_ARB\_framebuffer\_object GL\_ARB\_framebuffer\_sRGB GL\_ARB\_geometry\_shader4 GL\_ARB\_get\_program\_binary GL\_ARB\_get\_texture\_sub\_image GL\_ARB\_gl\_spirv GL\_ARB\_gpu\_shader5 GL\_ARB\_gpu\_shader\_fp64 GL\_ARB\_gpu\_shader\_int64 GL\_ARB\_half\_float\_pixel GL\_ARB\_half\_float\_vertex GL\_ARB\_imaging GL\_ARB\_indirect\_parameters GL\_ARB\_instanced\_arrays GL\_ARB\_internalformat\_query GL\_ARB\_internalformat\_query2 GL\_ARB\_invalidate\_subdata GL\_ARB\_map\_buffer\_alignment GL\_ARB\_map\_buffer\_range GL\_ARB\_multi\_bind GL\_ARB\_multi\_draw\_indirect GL\_ARB\_multisample GL\_ARB\_multitexture GL\_ARB\_occlusion\_query GL\_ARB\_occlusion\_query2 GL\_ARB\_parallel\_shader\_compile GL\_ARB\_pipeline\_statistics\_query GL\_ARB\_pixel\_buffer\_object GL\_ARB\_point\_parameters GL\_ARB\_point\_sprite GL\_ARB\_polygon\_offset\_clamp GL\_ARB\_post\_depth\_coverage GL\_ARB\_program\_interface\_query GL\_ARB\_provoking\_vertex GL\_ARB\_query\_buffer\_object GL\_ARB\_robust\_buffer\_access\_behavior GL\_ARB\_robustness GL\_ARB\_sample\_locations GL\_ARB\_sample\_shading GL\_ARB\_sampler\_objects GL\_ARB\_seamless\_cube\_map GL\_ARB\_seamless\_cubemap\_per\_texture GL\_ARB\_separate\_shader\_objects GL\_ARB\_shader\_atomic\_counter\_ops GL\_ARB\_shader\_atomic\_counters GL\_ARB\_shader\_ballot GL\_ARB\_shader\_bit\_encoding GL\_ARB\_shader\_clock GL\_ARB\_shader\_draw\_parameters GL\_ARB\_shader\_group\_vote GL\_ARB\_shader\_image\_load\_store GL\_ARB\_shader\_image\_size GL\_ARB\_shader\_objects GL\_ARB\_shader\_precision GL\_ARB\_shader\_storage\_buffer\_object GL\_ARB\_shader\_subroutine GL\_ARB\_shader\_texture\_image\_samples GL\_ARB\_shader\_texture\_lod GL\_ARB\_shading\_language\_100 GL\_ARB\_shader\_viewport\_layer\_array GL\_ARB\_shading\_language\_420pack GL\_ARB\_shading\_language\_include GL\_ARB\_shading\_language\_packing GL\_ARB\_shadow GL\_ARB\_sparse\_buffer GL\_ARB\_sparse\_texture GL\_ARB\_sparse\_texture2 GL\_ARB\_sparse\_texture\_clamp GL\_ARB\_spirv\_extensions GL\_ARB\_stencil\_texturing GL\_ARB\_sync GL\_ARB\_tessellation\_shader GL\_ARB\_texture\_barrier GL\_ARB\_texture\_border\_clamp GL\_ARB\_texture\_buffer\_object GL\_ARB\_texture\_buffer\_object\_rgb32 GL\_ARB\_texture\_buffer\_range GL\_ARB\_texture\_compression GL\_ARB\_texture\_compression\_bptc GL\_ARB\_texture\_compression\_rgtc GL\_ARB\_texture\_cube\_map GL\_ARB\_texture\_cube\_map\_array GL\_ARB\_texture\_env\_add GL\_ARB\_texture\_env\_combine GL\_ARB\_texture\_env\_crossbar GL\_ARB\_texture\_env\_dot3 GL\_ARB\_texture\_filter\_anisotropic GL\_ARB\_texture\_filter\_minmax GL\_ARB\_texture\_float GL\_ARB\_texture\_gather GL\_ARB\_texture\_mirror\_clamp\_to\_edge GL\_ARB\_texture\_mirrored\_repeat GL\_ARB\_texture\_multisample GL\_ARB\_texture\_non\_power\_of\_two GL\_ARB\_texture\_query\_levels GL\_ARB\_texture\_query\_lod GL\_ARB\_texture\_rectangle GL\_ARB\_texture\_rg GL\_ARB\_texture\_rgb10\_a2ui GL\_ARB\_texture\_stencil8GL\_ARB\_texture\_storage GL\_ARB\_texture\_storage\_multisample GL\_ARB\_texture\_swizzle GL\_ARB\_texture\_view GL\_ARB\_timer\_query GL\_ARB\_transform\_feedback2 GL\_ARB\_transform\_feedback3 GL\_ARB\_transform\_feedback\_instanced GL\_ARB\_transform\_feedback\_overflow\_query GL\_ARB\_transpose\_matrix GL\_ARB\_uniform\_buffer\_object GL\_ARB\_vertex\_array\_bgra GL\_ARB\_vertex\_array\_object GL\_ARB\_vertex\_attrib\_64bit GL\_ARB\_vertex\_attrib\_binding GL\_ARB\_vertex\_buffer\_object GL\_ARB\_vertex\_program GL\_ARB\_vertex\_shader GL\_ARB\_vertex\_type\_10f\_11f\_11f\_rev GL\_ARB\_vertex\_type\_2\_10\_10\_10\_rev GL\_ARB\_viewport\_array GL\_ARB\_window\_pos GL\_ATI\_draw\_buffers GL\_ATI\_texture\_float GL\_ATI\_texture\_mirror\_once GL\_S3\_s3tc GL\_EXT\_texture\_env\_add GL\_EXT\_abgr GL\_EXT\_bgra GL\_EXT\_bindable\_uniform GL\_EXT\_blend\_color GL\_EXT\_blend\_equation\_separate GL\_EXT\_blend\_func\_separate GL\_EXT\_blend\_minmax GL\_EXT\_blend\_subtract GL\_EXT\_compiled\_vertex\_array GL\_EXT\_Cg\_shader GL\_EXT\_depth\_bounds\_test GL\_EXT\_direct\_state\_access GL\_EXT\_draw\_buffers2 GL\_EXT\_draw\_instanced GL\_EXT\_draw\_range\_elements GL\_EXT\_fog\_coord GL\_EXT\_framebuffer\_blit GL\_EXT\_framebuffer\_multisample GL\_EXTX\_framebuffer\_mixed\_formats GL\_EXT\_framebuffer\_multisample\_blit\_scaled GL\_EXT\_framebuffer\_object GL\_EXT\_framebuffer\_sRGB GL\_EXT\_geometry\_shader4 GL\_EXT\_gpu\_program\_parameters GL\_EXT\_gpu\_shader4 GL\_EXT\_multi\_draw\_arrays GL\_EXT\_multiview\_tessellation\_geometry\_shader GL\_EXT\_multiview\_texture\_multisample GL\_EXT\_multiview\_timer\_query GL\_EXT\_packed\_depth\_stencil GL\_EXT\_packed\_float GL\_EXT\_packed\_pixels GL\_EXT\_pixel\_buffer\_object GL\_EXT\_point\_parameters GL\_EXT\_polygon\_offset\_clamp GL\_EXT\_post\_depth\_coverage GL\_EXT\_provoking\_vertex GL\_EXT\_raster\_multisample GL\_EXT\_rescale\_normal GL\_EXT\_secondary\_color GL\_EXT\_separate\_shader\_objects GL\_EXT\_separate\_specular\_color GL\_EXT\_shader\_image\_load\_formatted GL\_EXT\_shader\_image\_load\_store GL\_EXT\_shader\_integer\_mix GL\_EXT\_shadow\_funcs GL\_EXT\_sparse\_texture2 GL\_EXT\_stencil\_two\_side GL\_EXT\_stencil\_wrap GL\_EXT\_texture3D GL\_EXT\_texture\_array GL\_EXT\_texture\_buffer\_object GL\_EXT\_texture\_compression\_dxt1 GL\_EXT\_texture\_compression\_latc GL\_EXT\_texture\_compression\_rgtc GL\_EXT\_texture\_compression\_s3tc GL\_EXT\_texture\_cube\_map GL\_EXT\_texture\_edge\_clamp GL\_EXT\_texture\_env\_combine GL\_EXT\_texture\_env\_dot3 GL\_EXT\_texture\_filter\_anisotropic GL\_EXT\_texture\_filter\_minmax GL\_EXT\_texture\_integer GL\_EXT\_texture\_lod GL\_EXT\_texture\_lod\_bias GL\_EXT\_texture\_mirror\_clamp GL\_EXT\_texture\_object GL\_EXT\_texture\_shadow\_lod GL\_EXT\_texture\_shared\_exponent GL\_EXT\_texture\_sRGB GL\_EXT\_texture\_sRGB\_R8 GL\_EXT\_texture\_sRGB\_decode GL\_EXT\_texture\_storage GL\_EXT\_texture\_swizzle GL\_EXT\_timer\_query GL\_EXT\_transform\_feedback2 GL\_EXT\_vertex\_array GL\_EXT\_vertex\_array\_bgra GL\_EXT\_vertex\_attrib\_64bit GL\_EXT\_window\_rectangles GL\_EXT\_x11\_sync\_object GL\_EXT\_import\_sync\_object GL\_NV\_robustness\_video\_memory\_purge GL\_NVX\_shared\_sync\_object GL\_IBM\_rasterpos\_clip GL\_IBM\_texture\_mirrored\_repeat GL\_KHR\_context\_flush\_control GL\_KHR\_debug GL\_EXT\_memory\_object GL\_EXT\_memory\_object\_fd GL\_NV\_memory\_object\_sparse GL\_KHR\_parallel\_shader\_compile GL\_KHR\_no\_error GL\_KHR\_robust\_buffer\_access\_behavior GL\_KHR\_robustness GL\_EXT\_semaphore GL\_EXT\_semaphore\_fd GL\_NV\_timeline\_semaphore GL\_KHR\_shader\_subgroup GL\_KTX\_buffer\_region GL\_NV\_alpha\_to\_coverage\_dither\_control GL\_NV\_bindless\_multi\_draw\_indirect GL\_NV\_bindless\_multi\_draw\_indirect\_count GL\_NV\_bindless\_texture GL\_NV\_blend\_equation\_advanced GL\_NV\_blend\_equation\_advanced\_coherent GL\_NVX\_blend\_equation\_advanced\_multi\_draw\_buffers GL\_NV\_blend\_minmax\_factor GL\_NV\_blend\_square GL\_NV\_clip\_space\_w\_scaling GL\_NV\_command\_list GL\_NV\_compute\_program5 GL\_NV\_compute\_shader\_derivatives GL\_NV\_conditional\_render GL\_NV\_conservative\_raster GL\_NV\_conservative\_raster\_dilate GL\_NV\_conservative\_raster\_pre\_snap GL\_NV\_conservative\_raster\_pre\_snap\_triangles GL\_NV\_conservative\_raster\_underestimation GL\_NV\_copy\_depth\_to\_color GL\_NV\_copy\_image GL\_NV\_deep\_texture3D GL\_NV\_depth\_buffer\_float GL\_NV\_depth\_clamp GL\_NV\_draw\_texture GL\_NV\_draw\_vulkan\_image GL\_NV\_ES1\_1\_compatibility GL\_NV\_ES3\_1\_compatibility GL\_NV\_explicit\_multisample GL\_NV\_feature\_query GL\_NV\_fence GL\_NV\_fill\_rectangle GL\_NV\_float\_buffer GL\_NV\_fog\_distance GL\_NV\_fragment\_coverage\_to\_color GL\_NV\_fragment\_program GL\_NV\_fragment\_program\_option GL\_NV\_fragment\_program2 GL\_NV\_fragment\_shader\_barycentric GL\_NV\_fragment\_shader\_interlock GL\_NV\_framebuffer\_mixed\_samples GL\_NV\_framebuffer\_multisample\_coverage GL\_NV\_geometry\_shader4 GL\_NV\_geometry\_shader\_passthrough GL\_NV\_gpu\_program4 GL\_NV\_internalformat\_sample\_query GL\_NV\_gpu\_program4\_1 GL\_NV\_gpu\_program5 GL\_NV\_gpu\_program5\_mem\_extended GL\_NV\_gpu\_program\_fp64 GL\_NV\_gpu\_shader5 GL\_NV\_half\_float GL\_NV\_light\_max\_exponent GL\_NV\_memory\_attachment GL\_NV\_mesh\_shader GL\_NV\_multisample\_coverage GL\_NV\_multisample\_filter\_hint GL\_NV\_occlusion\_query GL\_NV\_packed\_depth\_stencil GL\_NV\_parameter\_buffer\_object GL\_NV\_parameter\_buffer\_object2 GL\_NV\_path\_rendering GL\_NV\_path\_rendering\_shared\_edge GL\_NV\_pixel\_data\_range GL\_NV\_point\_sprite GL\_NV\_primitive\_restart GL\_NV\_primitive\_shading\_rate GL\_NV\_query\_resource GL\_NV\_query\_resource\_tag GL\_NV\_register\_combiners GL\_NV\_register\_combiners2 GL\_NV\_representative\_fragment\_test GL\_NV\_sample\_locations GL\_NV\_sample\_mask\_override\_coverage GL\_NV\_scissor\_exclusive GL\_NV\_shader\_atomic\_counters GL\_NV\_shader\_atomic\_float GL\_NV\_shader\_atomic\_float64 GL\_NV\_shader\_atomic\_fp16\_vector GL\_NV\_shader\_atomic\_int64 GL\_NV\_shader\_buffer\_load GL\_NV\_shader\_storage\_buffer\_object GL\_NV\_shader\_subgroup\_partitioned GL\_NV\_shader\_texture\_footprint GL\_NV\_shading\_rate\_image GL\_NV\_stereo\_view\_renderingGL\_NV\_texgen\_reflection GL\_NV\_texture\_barrier GL\_NV\_texture\_compression\_vtc GL\_NV\_texture\_dirty\_tile\_map GL\_NV\_texture\_env\_combine4 GL\_NV\_texture\_multisample GL\_NV\_texture\_rectangle GL\_NV\_texture\_rectangle\_compressed GL\_NV\_texture\_shader GL\_NV\_texture\_shader2 GL\_NV\_texture\_shader3 GL\_NV\_transform\_feedback GL\_NV\_transform\_feedback2 GL\_NV\_uniform\_buffer\_unified\_memory GL\_NV\_uniform\_buffer\_std430\_layout GL\_NV\_vdpau\_interop GL\_NV\_vdpau\_interop2 GL\_NV\_vertex\_array\_range GL\_NV\_vertex\_array\_range2 GL\_NV\_vertex\_attrib\_integer\_64bit GL\_NV\_vertex\_buffer\_unified\_memory GL\_NV\_vertex\_program GL\_NV\_vertex\_program1\_1 GL\_NV\_vertex\_program2 GL\_NV\_vertex\_program2\_option GL\_NV\_vertex\_program3 GL\_NV\_viewport\_array2 GL\_NV\_viewport\_swizzle GL\_NVX\_sysmem\_buffer GL\_NVX\_conditional\_render GL\_NV\_gpu\_multicast GL\_NVX\_progress\_fence GL\_NVX\_gpu\_memory\_info GL\_NVX\_nvenc\_interop GL\_NV\_shader\_thread\_group GL\_NV\_shader\_thread\_shuffle GL\_KHR\_blend\_equation\_advanced GL\_KHR\_blend\_equation\_advanced\_coherent GL\_OVR\_multiview GL\_OVR\_multiview2 GL\_SGIS\_generate\_mipmap GL\_SGIS\_texture\_lod GL\_SGIX\_depth\_texture GL\_SGIX\_shadow GL\_SUN\_slice\_accum PTB-DEBUG: Not running on Mesa graphics library. PTB-DEBUG: Interrogating Low-level renderer capabilities for onscreen window with handle 10: Indicator variables: FBO’s 1, ATI\_texture\_float 1, ARB\_texture\_float 1, Vendor NVIDIA Corporation, Renderer NVIDIA RTX A6000/PCIe/SSE2. Indicator variables: maxcolorattachments = 8, maxrectangletexturesize = 32768, maxnativealuinstructions = 65536. GPU supports non-power-of-two textures. Basic framebuffer objects with rectangle texture rendertargets supported → RGBA8 rendertargets with blending. Framebuffer objects support fast blitting between each other. Framebuffer objects support anti-aliasing via multisampling. Framebuffer objects support single-pass multisample resolve blits and image rescaling. Hardware supports floating point textures of 16bpc and 32bpc float format. Assuming NV30 core or later… Assuming NV40 core or later (maxcolattachments=8): Hardware supports floating point blending and filtering on 16bpc float format. Hardware also supports floating point framebuffers of 16bpc and 32bpc float format. Hardware supports full 32 bit floating point precision shading. Assuming G80 core or later (maxtexsize=32768): Hardware supports full floating point blending and filtering on 16bpc and 32bpc float format. Assuming hardware supports native OpenGL primitive smoothing (points, lines). Float color value 0.5 → fixed point reads back as 127 ==\> Truncates. PTB-Info: Running on ‘The [X.Org](http://X.Org) Foundation’ XServer, Vendor release 12101003. OML\_sync\_control indicators: glXGetSyncValuesOML=(nil) , glXWaitForMscOML=(nil), glXWaitForSbcOML=(nil), glXSwapBuffersMscOML=(nil) OML\_sync\_control indicators: glxewIsSupported() says 0. OML\_sync\_control indicators: glXQueryExtensionsString() says 0. No support for OpenML OML\_sync\_control extension. System supports backbuffer age queries. PTB-DEBUG: Interrogation done. RandR: 1920x1080 (0x225) 285.5MHz h: width 1920 start 1968 end 2000 total 2080 skew 0 v: height 1080 start 1083 end 1088 total 1144 RandR: 1920x1080 (0x225) 285.5MHz h: width 1920 start 1968 end 2000 total 2080 skew 0 v: height 1080 start 1083 end 1088 total 1144 PTB-DEBUG: glClear splash image top-left reference pixel: 90 0 90 PTB-INFO: Threshold Settings for successfull video refresh calibration are: maxStdDev = 0.200000 msecs, maxDeviation = 10.000000 %, minSamples = 50, maxDuration = 5.000000 secs. PTB-INFO: Failed to enable realtime-scheduling [Operation not permitted]! PTB-INFO: You need to run the script PsychLinuxConfiguration once, then logout and login again for this to work. ---
**Author:** ![PaulLinton](https://yyz2.discourse-cdn.com/free1/user_avatar/psychtoolbox.discourse.group/paullinton/32/518_2.png) [@PaulLinton](https://psychtoolbox.discourse.group/u/PaulLinton)\ **Post date:** [April 29, 2023, 6:12pm UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962/7 "2023-04-29T18:12:08Z")
PTB-DEBUG: Output of all acquired samples of calibration run follows: PTB-DEBUG: Sample 0: 0.000000 PTB-DEBUG: Sample 1: 0.008365 PTB-DEBUG: Sample 2: 0.007983 PTB-DEBUG: Sample 3: 0.009654 PTB-DEBUG: Sample 4: 0.007590 PTB-DEBUG: Sample 5: 0.007704 PTB-DEBUG: Sample 6: 0.008332 PTB-DEBUG: Sample 7: 0.009419 PTB-DEBUG: Sample 8: 0.007639 PTB-DEBUG: Sample 9: 0.008335 PTB-DEBUG: Sample 10: 0.008627 PTB-DEBUG: Sample 11: 0.008032 PTB-DEBUG: Sample 12: 0.007943 PTB-DEBUG: Sample 13: 0.008338 PTB-DEBUG: Sample 14: 0.008397 PTB-DEBUG: Sample 15: 0.008256 PTB-DEBUG: Sample 16: 0.008318 PTB-DEBUG: Sample 17: 0.008410 PTB-DEBUG: Sample 18: 0.008350 PTB-DEBUG: Sample 19: 0.008325 PTB-DEBUG: Sample 20: 0.008248 PTB-DEBUG: Sample 21: 0.008346 PTB-DEBUG: Sample 22: 0.008312 PTB-DEBUG: Sample 23: 0.008330 PTB-DEBUG: Sample 24: 0.008335 PTB-DEBUG: Sample 25: 0.008329 PTB-DEBUG: Sample 26: 0.008335 PTB-DEBUG: Sample 27: 0.008332 PTB-DEBUG: Sample 28: 0.008335 PTB-DEBUG: Sample 29: 0.008424 PTB-DEBUG: Sample 30: 0.008250 PTB-DEBUG: Sample 31: 0.008341 PTB-DEBUG: Sample 32: 0.008381 PTB-DEBUG: Sample 33: 0.008270 PTB-DEBUG: Sample 34: 0.008391 PTB-DEBUG: Sample 35: 0.008374 PTB-DEBUG: Sample 36: 0.009187 PTB-DEBUG: Sample 37: 0.007392 PTB-DEBUG: Sample 38: 0.008327 PTB-DEBUG: Sample 39: 0.008340 PTB-DEBUG: Sample 40: 0.008331 PTB-DEBUG: Sample 41: 0.008333 PTB-DEBUG: Sample 42: 0.008339 PTB-DEBUG: Sample 43: 0.008329 PTB-DEBUG: Sample 44: 0.008337 PTB-DEBUG: Sample 45: 0.008329 PTB-DEBUG: Sample 46: 0.008342 PTB-DEBUG: Sample 47: 0.008328 PTB-DEBUG: Sample 48: 0.008440 PTB-DEBUG: Sample 49: 0.008328 PTB-DEBUG: Sample 50: 0.008283 PTB-DEBUG: Sample 51: 0.008284 PTB-DEBUG: Sample 52: 0.008449 PTB-DEBUG: Sample 53: 0.008224 PTB-DEBUG: Sample 54: 0.008333 PTB-DEBUG: Sample 55: 0.008335 PTB-DEBUG: Sample 56: 0.008336 PTB-DEBUG: Sample 57: 0.008334 PTB-DEBUG: Sample 58: 0.008333 PTB-DEBUG: Sample 59: 0.008335 PTB-DEBUG: Sample 60: 0.008770 PTB-DEBUG: Sample 61: 0.007903 PTB-DEBUG: Sample 62: 0.008427 PTB-DEBUG: Sample 63: 0.008242 PTB-DEBUG: Sample 64: 0.008330 PTB-DEBUG: Sample 65: 0.008383 PTB-DEBUG: Sample 66: 0.008287 PTB-DEBUG: Sample 67: 0.008331 PTB-DEBUG: Sample 68: 0.008349 PTB-DEBUG: Sample 69: 0.008426 PTB-DEBUG: Sample 70: 0.008231 PTB-DEBUG: Sample 71: 0.008436 PTB-DEBUG: Sample 72: 0.008234 PTB-DEBUG: Sample 73: 0.008334 PTB-DEBUG: Sample 74: 0.008335 PTB-DEBUG: Sample 75: 0.008347 PTB-DEBUG: Sample 76: 0.008325 PTB-DEBUG: Sample 77: 0.008330 PTB-DEBUG: Sample 78: 0.008335 PTB-DEBUG: Sample 79: 0.008439 PTB-DEBUG: Sample 80: 0.008236 PTB-DEBUG: Sample 81: 0.008341 PTB-DEBUG: Sample 82: 0.008320 PTB-DEBUG: Sample 83: 0.008431 PTB-DEBUG: Sample 84: 0.008239 PTB-DEBUG: Sample 85: 0.008337 PTB-DEBUG: Sample 86: 0.008343 PTB-DEBUG: Sample 87: 0.008339 PTB-DEBUG: Sample 88: 0.008324 PTB-DEBUG: Sample 89: 0.008425 PTB-DEBUG: Sample 90: 0.008239 PTB-DEBUG: Sample 91: 0.008440 PTB-DEBUG: Sample 92: 0.008229 PTB-DEBUG: Sample 93: 0.008344 PTB-DEBUG: Sample 94: 0.008323 PTB-DEBUG: Sample 95: 0.008433 PTB-DEBUG: Sample 96: 0.008245 PTB-DEBUG: Sample 97: 0.008327 PTB-DEBUG: Sample 98: 0.008435 PTB-DEBUG: Sample 99: 0.008332 PTB-DEBUG: Sample 100: 0.008284 PTB-DEBUG: Sample 101: 0.008287 PTB-DEBUG: Sample 102: 0.008439 PTB-DEBUG: Sample 103: 0.008246 PTB-DEBUG: Sample 104: 0.008319 PTB-DEBUG: Sample 105: 0.008336 PTB-DEBUG: Sample 106: 0.008336 PTB-DEBUG: Sample 107: 0.008331 PTB-DEBUG: Sample 108: 0.008429 PTB-DEBUG: Sample 109: 0.008240 PTB-DEBUG: Sample 110: 0.008448 PTB-DEBUG: Sample 111: 0.008327 PTB-DEBUG: Sample 112: 0.008325 PTB-DEBUG: Sample 113: 0.008237 PTB-DEBUG: Sample 114: 0.008333 PTB-DEBUG: Sample 115: 0.008345 PTB-DEBUG: Sample 116: 0.008326 PTB-DEBUG: Sample 117: 0.008772 PTB-DEBUG: Sample 118: 0.007896 PTB-DEBUG: Sample 119: 0.008385 PTB-DEBUG: Sample 120: 0.008364 PTB-DEBUG: Sample 121: 0.008266 PTB-DEBUG: Sample 122: 0.008344 PTB-DEBUG: Sample 123: 0.008416 PTB-DEBUG: Sample 124: 0.008233 PTB-DEBUG: Sample 125: 0.008334 PTB-DEBUG: Sample 126: 0.008336 PTB-DEBUG: Sample 127: 0.008431 PTB-DEBUG: Sample 128: 0.008241 PTB-DEBUG: Sample 129: 0.008394 PTB-DEBUG: Sample 130: 0.008268 PTB-DEBUG: Sample 131: 0.008397 PTB-DEBUG: Sample 132: 0.008380 PTB-DEBUG: Sample 133: 0.008326 PTB-DEBUG: Sample 134: 0.008307 PTB-DEBUG: Sample 135: 0.008266 PTB-DEBUG: Sample 136: 0.008335 PTB-DEBUG: Sample 137: 0.008429 PTB-DEBUG: Sample 138: 0.008277 PTB-DEBUG: Sample 139: 0.008404 PTB-DEBUG: Sample 140: 0.008227 PTB-DEBUG: Sample 141: 0.008333 PTB-DEBUG: Sample 142: 0.008450 PTB-DEBUG: Sample 143: 0.008215 PTB-DEBUG: Sample 144: 0.008252 PTB-DEBUG: Sample 145: 0.008415 PTB-DEBUG: Sample 146: 0.008337 PTB-DEBUG: Sample 147: 0.008421 PTB-DEBUG: Sample 148: 0.008365 PTB-DEBUG: Sample 149: 0.008219 PTB-DEBUG: Sample 150: 0.008332 PTB-DEBUG: Sample 151: 0.008338 PTB-DEBUG: Sample 152: 0.008335 PTB-DEBUG: Sample 153: 0.008438 PTB-DEBUG: Sample 154: 0.008338 PTB-DEBUG: Sample 155: 0.008222 PTB-DEBUG: Sample 156: 0.008338 PTB-DEBUG: Sample 157: 0.008336 PTB-DEBUG: Sample 158: 0.008329 PTB-DEBUG: Sample 159: 0.008333 PTB-DEBUG: Sample 160: 0.008340 PTB-DEBUG: Sample 161: 0.008375 PTB-DEBUG: Sample 162: 0.008291 PTB-DEBUG: Sample 163: 0.008435 PTB-DEBUG: Sample 164: 0.008236 PTB-DEBUG: Sample 165: 0.008345 PTB-DEBUG: Sample 166: 0.008425 PTB-DEBUG: Sample 167: 0.008233 PTB-DEBUG: Sample 168: 0.008443 PTB-DEBUG: Sample 169: 0.008231 PTB-DEBUG: Sample 170: 0.008330 PTB-DEBUG: Sample 171: 0.008429 PTB-DEBUG: Sample 172: 0.008240 PTB-DEBUG: Sample 173: 0.008336 PTB-DEBUG: Sample 174: 0.008764 PTB-DEBUG: Sample 175: 0.007907 PTB-DEBUG: Sample 176: 0.008334 PTB-DEBUG: Sample 177: 0.008375 PTB-DEBUG: Sample 178: 0.008367 PTB-DEBUG: Sample 179: 0.008289 PTB-DEBUG: Sample 180: 0.008335 PTB-DEBUG: Sample 181: 0.008300 PTB-DEBUG: Sample 182: 0.008335 PTB-DEBUG: Sample 183: 0.008337 PTB-DEBUG: Sample 184: 0.008332 PTB-DEBUG: Sample 185: 0.008333 PTB-DEBUG: Sample 186: 0.008334 PTB-DEBUG: Sample 187: 0.008347 PTB-DEBUG: Sample 188: 0.008327 PTB-DEBUG: Sample 189: 0.008435 PTB-DEBUG: Sample 190: 0.008244 PTB-DEBUG: Sample 191: 0.008321 PTB-DEBUG: Sample 192: 0.008344 PTB-DEBUG: Sample 193: 0.008327 PTB-DEBUG: Sample 194: 0.008332 PTB-DEBUG: Sample 195: 0.008338 PTB-DEBUG: Sample 196: 0.008336 PTB-DEBUG: Sample 197: 0.008333 PTB-DEBUG: Sample 198: 0.008448 PTB-DEBUG: Sample 199: 0.008314 PTB-DEBUG: Sample 200: 0.008251 PTB-DEBUG: Sample 201: 0.008305 PTB-DEBUG: Sample 202: 0.008360 PTB-DEBUG: Sample 203: 0.008326 PTB-DEBUG: Sample 204: 0.008362 PTB-DEBUG: Sample 205: 0.008309 PTB-DEBUG: Sample 206: 0.008336 PTB-DEBUG: End of calibration data for this run… PTB-INFO: OpenGL-Renderer is NVIDIA Corporation :: NVIDIA RTX A6000/PCIe/SSE2 :: 4.6.0 NVIDIA 525.116.03 PTB-INFO: VBL startline = 1080 , VBL Endline = -1 PTB-INFO: Beamposition queries unsupported or defective on this system. Using basic timestamping as fallback. PTB-INFO: Timestamps returned by Screen(‘Flip’) will be therefore less robust and accurate. PTB-INFO: Measured monitor refresh interval from VBLsync = 8.332242 ms [120.015716 Hz]. (206 valid samples taken, stddev=0.199777 ms.) PTB-INFO: Reported monitor refresh interval from operating system = 8.334653 ms [119.981003 Hz]. PTB-INFO: Small deviations between reported values are normal and no reason to worry. PTB-INFO: Support for fast OffscreenWindows enabled. PTB-DEBUG: GLX\_BACK\_BUFFER\_AGE\_EXT == 2 after swap completion. PTB-DEBUG: Swaprequest too close to last swap vbl (0.000399 secs) or between forbidden scanline 1 and 50. Delaying… PTB-DEBUG: GLX\_BACK\_BUFFER\_AGE\_EXT == 2 after swap completion. PTB-DEBUG: Swaprequest too close to last swap vbl (0.000424 secs) or between forbidden scanline 1 and 50. Delaying… PTB-DEBUG: GLX\_BACK\_BUFFER\_AGE\_EXT == 2 after swap completion. RandR: 1920x1080 (0x225) 285.5MHz h: width 1920 start 1968 end 2000 total 2080 skew 0 v: height 1080 start 1083 end 1088 total 1144 PTB-DEBUG: Swaprequest too close to last swap vbl (0.001009 secs) or between forbidden scanline 1 and 50. Delaying… PTB-DEBUG: GLX\_BACK\_BUFFER\_AGE\_EXT == 2 after swap completion. PTB-DEBUG: GLX\_BACK\_BUFFER\_AGE\_EXT == 2 after swap completion. PTB-DEBUG: GLX\_BACK\_BUFFER\_AGE\_EXT == 2 after swap completion. [And continues like this until I exit] ---
**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\ **Post date:** [April 30, 2023, 1:11am UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962/8 "2023-04-30T01:11:34Z")
Many things here: First, try `PsychLinuxConfiguration` + logout + login again, launching octave from a terminal window ( **without sudo** ). The script will ask for your admin password at appropriate times, calling sudo as needed. Usually you don’t want to run octave or matlab with sudo, as it potentially screws up file ownerships, e.g., if it stores its own config files (e.g., the Octave/Matlab command history or settinga) with ownership “root” then, instead of your user name. Or what also might have happened is that because octave was launched `sudo` the PsychLinuxConfiguration script might have misidentified your user account as ‘root’ and created permissions for realtime priority and for membership in the “psychtoolbox” Unix user group for the ‘root’ user instead of your own user account name. If you type `id` in a terminal and don’t get “psychtoolbox” listed as one of the groups you are a member of, then that might be because of that. → The general PTB design is to make it not necessary to run matlab or octave with sudo if all the configuration steps completed successfully. I also think the booting in BIOS mode wasn’t necessarily a problem: The one thing that prevents low-level access by default is EFI secure boot, but if your machine booted with BIOS CSM, iow. no EFI, then there also wasn’t any EFI secure boot enabled. Anyhow, doesn’t hurt to use modern EFI boot now. Also, PTB never made it to the point where it could fail due to EFI secure boot or such, according to the output. The reason it doesn’t recognize your NVidia as low-level controllable is a peculiar one - I think we haven’t had this one yet: According to the following output … " PTB-DEBUG: Checking PCI device [ASPEED Technology, Inc. ASPEED Graphics Family] with class x00030000" …, there is a 2nd display controller in your machine, a very primitive and basic ASPEED chip, which is usually only found in server machines for remote maintenance or for a maintenance technician to connect a very simple display monitor in a server room. My suspicion is that that chip is not disabled on your machine and gets marked by the BIOS or EFI firmware as “VGA boot gpu” - the one used during machine powerup and initial boot for display. This throws off PTB’s gpu detection logic, as if no gpu is explicitely selected (via the `PsychTweak('UseGPUIndex', gpuindex);` command in a multi-gpu machine), PTB will choose the VGA boot gpu as the proper one. You could either execute PsychTweak(‘UseGPUIndex’, 0); first, to force use of the NVidia. This might fix the beamposition timestamping. Or if you don’t have any need for that primitive ASPEED display chip, there’s probably somewhere a EFI firmware setting to disable it completely, so it will disappear from the system. I assume your OLED monitor, and previously that LCD display, is connected to the NVidia, not to some other output connector on your machine - which would be that primitive ASPEED chip? What’s the output of `xrandr --listproviders` and the content of the ~/.local/share/xorg/Xorg.0.log` ? If the X-Server would also decide to choose the ASPEED as the primary gpu, that could cause quite lots of performance problems. Btw. for stereo shutter goggles you almost certainly **do not want** to use G-Sync or have it enabled → It should be off. That would likely screw up the stereo shutter timing for good, as such goggles need a very predictable and fixed frame duration and frame cycle, so they can sync up the phase of their own switching cycle to the switching cycle of the display. Btw. one thought wrt. the stereo goggles breaking down on OLED: I haven’t looked at how your specific model of stereo goggles works, and there are different working principles for such stereo shutters, but one non-computer related problem could be if your goggles depend on the presence of a polarizing light filter on the display monitor? A LCD display by design/by the way a LCD works, necessarily emits polarized light, but an OLED monitor doesn’t do that. So if the goggles somehow would depend on the photons from the monitor being polarized, they would possibly fail to do their shuttering job when pointed towards an OLED monitor? Also: we have `FrameSequentialStereoTest` as a test and demo on how to deal with different frame-sequential stereo setups and their quirks. Makes also sense to post PTB output when you use frame-sequential stereo mode 1, to make sure you are in fact using the right mode of operation. I may state the obvious here, but it does need setup in a custom xorg.conf setting afaiu, cfe. `Option "Stereo" "integer"` section in: [https://download.nvidia.com/XFree86/Linux-x86\_64/525.116.03/README/xconfigoptions.html](https://download.nvidia.com/XFree86/Linux-x86_64/525.116.03/README/xconfigoptions.html) I think mode `Option "Stereo" "3"` is what you’d want. -mario [60 minutes of out 30 minutes of paid-for support used → License used up.] ---
**Author:** ![PaulLinton](https://yyz2.discourse-cdn.com/free1/user_avatar/psychtoolbox.discourse.group/paullinton/32/518_2.png) [@PaulLinton](https://psychtoolbox.discourse.group/u/PaulLinton)\ **Post date:** [May 1, 2023, 5:23pm UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962/9 "2023-05-01T17:23:15Z")
Dear Mario, That’s absolutely amazing!!! I really appreciate all your help on this. [1]. ASPEED chip now disabled in BIOS, and Beamposition queries working perfectly, and “PsychLinuxConfiguration” rerun without problems (“id” returns “psychtoolbox”). Thanks so much, I would never have spotted, because everything looked perfect in my xorg.conf file (and nvidia-settings): Section “Device” Identifier “Device0” Driver “nvidia” VendorName “NVIDIA Corporation” BusID “PCI:101:0:0” EndSection Section “Screen” Identifier “Screen0” Device “Device0” Monitor “Monitor0” DefaultDepth 24 SubSection “Display” Depth 24 EndSubSection Option “metamodes” “1920x1080 { AllowGSYNC=Off }” Option “Stereo” “3” EndSection [2]. Checking “xrandr –listproviders” and Xorg.0.log now, after disabling Aspeed chip, and everything looks great. “xrandr –listproviders” output: Providers: number : 1 Provider 0: id: 0x37f cap: 0x1, Source Output crtcs: 4 outputs: 8 associated providers: 0 name:NVIDIA-0 And no mention of Aspeed chip in Xorg.0.log [3]. And thank you so much for the tips on sudo, GSYNC, and OLEDs, and stereo settings, they are invaluable 😊 Some manufacturers (LG) putting their own polarisers on their gaming monitor OLEDs causing further problems with shutter glasses. I wanted to get timing issue sorted, so I’d know that any remaining issues were hardware problems! Honestly, thanks so much Mario for this all, it’s all incredibly useful. I hope you have a well deserved break, and thank you so much for all your help, Paul ---
**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\ **Post date:** [May 1, 2023, 6:57pm UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962/10 "2023-05-01T18:57:10Z")
Great, all looking good. Case closed wrt. timing. I assume you tested the stereo goggles on exactly the same machine/graphics card/OS etc. successfully with the LCD monitor, and unsuccessfully with the OLED? In that case i’d expect it to be more of a hw or monitor ↔ stereo goggle interaction problem than a software problem, although it was good to rule out timing/timestamping problems. One thing to look at, as shown in the FrameSequentialStereoTest.m script, is if it makes sense to specify that extra argument to `Screen('SelectStereoDrawBuffer');` that selects if a ‘Flip’ should execute on even frames, odd frames or if it doesn’t matter. Different graphics cards and drivers vary in how they handle stimulus onset of a stereo pair in frame-sequential stereo mode. Ie. Does the flip to a new stereo image pair happen always when the present of a left-eye image is about to happen, or always on the right-eye, or even in the middle of a stereo cycle? If one flips at high rate that could cause weird artifacts if each stereo pair is not presented for a full cycle a la (L1R1, L2R2, …) but instead something like (L1R2L2R2 or L1R2L3R4…). Specifying that parameter will make ptb try to time flips itself so integrity of a stereo pair is preserved. Technically there is a hardware frame counter that increments each refresh cycle and it allows selection if a flip should happen on a even cycle count odd cycle count or whenever, the idea being that a stereo driver will always assign left eye to even cycles, and right eye on odd cycles - or vice versa. FrameSequentialStereoTest.m tries to help you figure out if that parameter is needed at all, or what the proper setting would be and how well/stable frame-seq stereo works, e.g., to prevent sudden inversion. Now with a gpu advertising native frame-sequential stereo support one would hope the driver takes care of reliable operation. But if the same PTB + OS + NVidia driver + graphics card + PC + video output port worked fine with a LCD connected, i’d assume some hw interaction problem between the OLED and goggles, all else the same. -mario ---
**Author:** ![PaulLinton](https://yyz2.discourse-cdn.com/free1/user_avatar/psychtoolbox.discourse.group/paullinton/32/518_2.png) [@PaulLinton](https://psychtoolbox.discourse.group/u/PaulLinton)\ **Post date:** [May 3, 2023, 12:51am UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962/11 "2023-05-03T00:51:22Z")
Thanks so much for this advice Mario, I really appreciate it. I had to return the OLED before I had a chance to run it with the updated timing (the polariser meant I couldn’t see anything through the glasses unless glasses / screen turned 90 agrees), but I share your concern that this is all pointing to a hardware problem. Reached out to some people who’ve seemed to get active shutter glasses and OLEDs working to see if they have hardware recommendations, and then will give it another shot. Will definitely keep you posted, and thanks so much again! ---
**Author:** ![PaulLinton](https://yyz2.discourse-cdn.com/free1/user_avatar/psychtoolbox.discourse.group/paullinton/32/518_2.png) [@PaulLinton](https://psychtoolbox.discourse.group/u/PaulLinton)\ **Post date:** [August 25, 2023, 3:51pm UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962/12 "2023-08-25T15:51:09Z")
Hi Mario, hope you had a good vacation! I switched motherboards on this computer and the VBL syncing problem arose again. I’ve checked that (1) Secure Boot not enabled, and (2) GSYNC not enabled, and (3) tried moving around ports on the GPU for the monitor as suggested in VBL Sync help. I’ve updated DigiStore receipt: 6L22MQA7/VW2TKNMQ Would it be a good idea to run “Screen(‘Preference’,‘Verbosity’, 10); PerceptualVBLSyncTest” to get your thoughts. Versions I’m currently using: GPU NVIDIA RTX A6000 Ubuntu version 22.04.2.LTS Octave version 6.4.0 Psychtoolbox version 3.0.19.2 Psychtoolbox seems to recognise GPU: "OpenGL-Renderer is NVIDIA Corporation : : NVIDIA RTX A6000/PCIe/SSE2 : : 4.6.0 NVIDIA 535.86.05 Thanks so much, I really appreciate it! ---
**Author:** ![mariokleiner](https://avatars.discourse-cdn.com/v4/letter/m/13edae/32.png) [@mariokleiner](https://psychtoolbox.discourse.group/u/mariokleiner)\ **Post date:** [August 25, 2023, 4:23pm UTC](https://psychtoolbox.discourse.group/t/vbl-sync-not-working-for-nvidia-a6000-paid-support/4962/13 "2023-08-25T16:23:52Z")
> [@PaulLinton](#): > > Hi Mario, hope you had a good vacation! Yes, indeed, thanks. First proper vacation in over 15 years. > [@](#): > > I switched motherboards on this computer and the VBL syncing problem arose again. > > I’ve checked that (1) Secure Boot not enabled, and (2) GSYNC not enabled, and (3) tried moving around ports on the GPU for the monitor as suggested in VBL Sync help. > > I’ve updated DigiStore receipt: 6L22MQA7/VW2TKNMQ Yep, one extra hour of paid support. > [@](#): > > Would it be a good idea to run “Screen(‘Preference’,‘Verbosity’, 10); PerceptualVBLSyncTest” to get your thoughts. Versions I’m currently using: Yes please. A short run of a second is enough to get the gist of it. As you switched the motherboard, did you also recreate the xorg conf file, so it adapts to the changed hardware, e.g., PCI bus ids of the NVidia card? > [@](#): > > GPU NVIDIA RTX A6000 > Ubuntu version 22.04.2.LTS > Octave version 6.4.0 > Psychtoolbox version 3.0.19.2 > > Psychtoolbox seems to recognise GPU: > "OpenGL-Renderer is NVIDIA Corporation : : NVIDIA RTX A6000/PCIe/SSE2 : : 4.6.0 NVIDIA 535.86.05 > > Thanks so much, I really appreciate it! Same config apart from the motherboard, only the NVidia driver seems to have received and upgrade. Single display setup? -mario