Yes, I think so. I think that there is no way for a Titan Ridge device (which supports both Thunderbolt and non-Thunderbolt connection) can connect to a Thunderbolt host using non-Thunderbolt USB-C DisplayPort alt mode. There would need to be a hub or dock or Wacom Link Plus or VR2 cable or a bidirectional DisplayPort to USB-C cable in-between the host and the Titan Ridge device to eliminate the Thunderbolt connection possibility. For example, the HP Thunderbolt Dock G2 has a USB-C port with DisplayPort alt mode that is separate from Thunderbolt.Is that because the display (the 27MD5KL-B version) only looks for DisplayPort Alternate mode if Thunderbolt mode is not available?
Would using a USB-C cable (compatible for video) instead of the Thunderbolt cable force Alt mode? I'm just thinking of ways to make OpenCore visible on a cold boot (especially for FileVault)—the bootscreen is apparently available on a warm boot in Thunderbolt mode (although I'd really like further confirmation of this).
Do you have USB 2.0 connected to the GC-TITAN RIDGE? There could be a problem in the GC-TITAN RIDGE firmware or the firmware of the computer which doesn't know how to startup the GC-TITAN RIDGE. One could make an EFI driver that Open Core loads to setup the GC-TITAN RIDGE properly.On the other hand, even in Alt mode there is no guarantee. On my 4K display (LG 27UD88-W), I can get a bootscreen when connected to my MacBook (via USB-C), yet on my Mac Pro (via USB-C with the CG-TITAN RIDGE), the display turns on (when the boot picker should appear), but the screen stays black and then goes back to sleep. An image only appears once the display drivers load. Is this because of the CG-TITAN RIDGE (or maybe its firmware as @eksu has alluded to)? Perhaps someone could confirm that OpenCore is visible with the CG-TITAN RIDGE connected to the LG UltraFine 4K.
I think that's more modes than I'm used to seeing. My thought here is that there's no reason you should not be able to use any arbitrary timing. There should be a way to insert an arbitrary timing in EFI (EFI EDID override protocol?) like how SwitchResX does in macOS or CRU in Windows. In your case, you seem to have all the modes you could want (from 640x480 all the way up to 3840x2160), except you are missing 2560x1440 and only 3840x2160 has the correct 16:9 aspect ratio.In the case of OpenCore, the resolution as well as all available modes should be listed in the debug log. For example, this is what I get on my 4K display:
Code:06:893 00:011 OCC: Mode 0 - 3840x2160:1 06:905 00:011 OCC: Mode 1 - 640x480:1 06:916 00:011 OCC: Mode 2 - 800x600:1 06:928 00:011 OCC: Mode 3 - 1024x768:1 06:939 00:011 OCC: Mode 4 - 1280x1024:1 06:951 00:011 OCC: Mode 5 - 1400x1050:1 06:962 00:011 OCC: Mode 6 - 1600x1200:1 06:974 00:011 OCC: Mode 7 - 1280x960:1 06:985 00:011 OCC: Setting mode 0 with 3840x2160 resolution