InconsolableCellist

That sounds like a good theory with the timing issue! I've disabled the Xorg conf file and I'm first trying with the master branch (a9b4a20) ``` $ sudo ./ddcutil detect...

I should note too that the same situation was occurring with that third monitor, the DELL P2214H, which is an old 1080p monitor, from 2015 (the Cintiq 2013). I suppose...

>Once the displays are detected, do getvcp and setvcp work? How about capabilities, which requires multiple write/read cycles? It appears that it doesn't: ``` $ sudo ./ddcutil -b 2 getvcp...

Sure. Here's the run without the 90-nvidia_i2c.conf: ``` ===========> IO STRATEGY 1: i2c_io_strategy: FILEIO i2c_read_bytewise: false EDID read uses I2C layer: false EDID read bytewise: false Display 1 I2C bus:...

Here it is after restoring the nvidia conf and rebooting: ``` ===========> IO STRATEGY 1: i2c_io_strategy: FILEIO i2c_read_bytewise: false EDID read uses I2C layer: false EDID read bytewise: false Display...

and environment --verbose: ``` Output level: Verbose Reporting DDC data errors: false Trace groups active: none Traced functions: none Traced files: none Force I2C slave address: false The following tests...

Have you tested these instructions on Ubuntu? Can you tell me what versions of tensorflow-gpu, CUDA/nvidia drivers, and the kernel you were running?

Is the IPD exposed via SteamVR or Sranipal? The Vive Pro Eye is aware of it and reports it when you adjust the knob on the headset. Is it possible...

I was thinking: https://github.com/sd-webui/stable-diffusion-webui Is that not the main one? I'm not familiar with InvokeAI

I mean, as it is now yours is using InvokeAI's SD fork, so if one of those WebUI forks added special features you'd have to merge it into this one...