Question Main monitor is not detected in Valorant when using DisplayPort ?

[cocotheunknownmutt]

Hey folks,

This is a pretty specific question but I'm at my wits end trying to debug this one ( Riot has been useless and I have gotten no answer on other forums).

This is my specs:

• Screen: ViewSonic XG270Q (1440p 165hz)
• Display port wire: *DisplayPort Cable 1.4 Displayport Cable (4K@144Hz 3840x2160)
• Radeon 6700 XT
• i5-12600k

So to summarize my problem, valorant doesn't detect my main monitor when plugged in with display port but it does detect it over HDMI. I would stick with HDMI but it caps out at 144hz. I wanted to use the 165hz but its just not working with hdmi. To highlight some things:

1. I tried other games. MW2, Diablo 4, and CSGO all were able to identify my screen and run at 165hz no problem.
2. The wire worked before on my Gigabyte screen (although it was 1080p at 144hz)
3. Drivers are all updated (checked both through AMD adrenaline and device manager)
4. I tried uninstalling and reinstalling the drivers
5. I saw floating around an idea of "Generic PNP" drivers that should be switched over. I don't see that driver in my device manager. All I see is the "ViewSonic XG27Q" driver
6. Tried reinstalling the game, nothing.

I just don't feel like switching the wire every time I decide to switch games. Its just driving me nuts. Here's what the valorant logs show:

[2023.06.20-02.46.05:712][564]LogPlatformSessionManager: Error: Attempting to parse unhandled loopstate string INVALID
 [2023.06.20-02.46.06:539][577]LogPlatformSessionManager: Error: Attempting to parse unhandled loopstate string INVALID
 [2023.06.20-02.46.06:647][578]LogShooterGameUserSettings: Monitor info changed:
 [2023.06.20-02.46.06:649][578]LogShooterGameUserSettings: Error: Monitor index 0 was not valid in UShooterGameUserSettings::GetAresMonitorInfo.
 [2023.06.20-02.46.06:649][578]LogShooterGameUserSettings: Error: Monitor index 0 was not valid in UShooterGameUserSettings::GetAresMonitorInfo.
 [2023.06.20-02.46.06:650][578]LogShooterGameUserSettings: Error: Resolution '2,560 x 1,440 16:9 (0Hz)' was not a supported option in UShooterGameUserSettings::GetCurrentResolutionInfo.
 [2023.06.20-02.46.06:652][578]LogShooterGameUserSettings: Error: Monitor index 0 was not valid in UShooterGameUserSettings::GetAresMonitorInfo.
 [2023.06.20-02.46.06:652][578]LogShooterGameUserSettings: Error: Resolution '2,560 x 1,440 16:9 (0Hz)' was not a supported option in UShooterGameUserSettings::GetCurrentResolutionInfo.

It seems to keep going in loop when I plug with display port.

This is what I get with the HDMI wire:

[2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings: Monitor info changed:
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:   [0] MONITOR\VSC3C3A\{4d36e96e-e325-11ce-bfc1-08002be10318}\0003 (2560x1440)
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:    - 3840 x 2160 (60 Hz)
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:    - 2560 x 1440 (144 Hz)
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:    - 1920 x 1200 (144 Hz)
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:    - 1920 x 1080 (144 Hz)
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:    - 1600 x 1200 (144 Hz)
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:    - 1680 x 1050 (144 Hz)
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:    - 1760 x 990 (144 Hz)
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:    - 1600 x 900 (144 Hz)
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:    - 1280 x 1024 (144 Hz)
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:    - 1366 x 768 (144 Hz)
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:    - 1152 x 870 (144 Hz)
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:    - 1280 x 720 (144 Hz)
 [2023.06.20-02.56.17:746][  0]LogShooterGameUserSettings:    - 1024 x 768 (144 Hz)

Any help would be appreciated.

Cheers!

 

[richardvday]

Seems like you tried a lot but neglected to change the most likely culprit. The DisplayPort wire would be the first thing to change IMO.

It could be not up to spec(Very common actually) or just be slightly damaged, very fine wires can be damaged easily sometimes depending on handling and quality of the cable. Like a thicker casing etc. tends to protect it more but tends to make it more expensive.

Some signal interference could make it work fine at lower resolution but fail signal integrity as more demands are placed on it.

You could also try another port if you have one. Wire is the most likely culprit though.