display setting not available Resolution error

[mortenrud]

Hi. 
 

when I try to set a displayport output resolution above 1920x1080 I get an error:

"Rendering error:5; Command: Activate; Display setting not available”

Can anyone point me in the right direction?

thanks

[jfk]

This is typically caused by a hardware shortcoming in the connection from the graphics card output to the display. 

I might add the most common cause that I have encountered for this issue is any adaptation away from DisplayPort. i.e. a DisplayPort to HDMI adaptor not capable of 4K resolution. Note, there are two kinds of DisplayPort to HDMI adaptors - active and passive.

A passive adaptor relies on the graphics card supporting a compatibility mode where the card internally switches from DisplayPort signal types to legacy HDMI signal types. This type of capability is often referred to as DisplayPort ++. The legacy compatibility mode often offers less possible resolutions when compared to native DisplayPort signals. So the graphics card recognizes the HDMI adaptation and switches to output legacy HDMI signals. Many graphics cards are unable to output 4K in the legacy compatibility mode required by passive adaptors.

An active adaptor on the other hand operates the graphics card in native DisplayPort mode. i.e. the graphics card only outputs native DisplayPort signals. An active adaptor isolates the graphics card from the adaptation, the card only sees native DisplayPort connection. The active adaptor then converts native DisplayPort to legacy signal types required by HDMI. Native DisplayPort often provides a much wider range of output resolutions when compared to legacy mode. And that is not just 4K. I once encountered this issue with an HDMI display operating at 1400x1050. This could not be accomplished with a passive adaptor, only with an active adaptor.

So if you are converting to HDMI, you may require an active adaptor rated at 4k60p to correct this error. 

Note, active and passive adaptors often look the same and active adaptors are only slightly more expensive, often as little as $5-$10 more. 

[TonyShamel]

1 hour ago, jfk said:

This is typically caused by a hardware shortcoming in the connection from the graphics card output to the display. 

I might add the most common cause that I have encountered for this issue is any adaptation away from DisplayPort. i.e. a DisplayPort to HDMI adaptor not capable of 4K resolution. Note, there are two kinds of DisplayPort to HDMI adaptors - active and passive.

A passive adaptor relies on the graphics card supporting a compatibility mode where the card internally switches from DisplayPort signal types to legacy HDMI signal types. This type of capability is often referred to as DisplayPort ++. The legacy compatibility mode often offers less possible resolutions when compared to native DisplayPort signals. So the graphics card recognizes the HDMI adaptation and switches to output legacy HDMI signals. Many graphics cards are unable to output 4K in the legacy compatibility mode required by passive adaptors.

An active adaptor on the other hand operates the graphics card in native DisplayPort mode. i.e. the graphics card only outputs native DisplayPort signals. An active adaptor isolates the graphics card from the adaptation, the card only sees native DisplayPort connection. The active adaptor then converts native DisplayPort to legacy signal types required by HDMI. Native DisplayPort often provides a much wider range of output resolutions when compared to legacy mode. And that is not just 4K. I once encountered this issue with an HDMI display operating at 1400x1050. This could not be accomplished with a passive adaptor, only with an active adaptor.

So if you are converting to HDMI, you may require an active adaptor rated at 4k60p to correct this error. 

Note, active and passive adaptors often look the same and active adaptors are only slightly more expensive, often as little as $5-$10 more. 

Is there a particular adapter you recommend?

[mortenrud]

Hi jfk

Thanks for your reply.

I was in fact trying to convert displayport to hdmi, but using an active cable.

Now I have placed a screen right next to the WatchPax 60 and running displayport to displayport and with the same error.

Everytime I try to set the resolution to more than 1920x1080 I will get the error.

[matkeane]

I've never had any problems with the Startech DP2HD4K60H DP-HDMI adapters. I recently used them for a project at 2160p50 when the client's no-name '4K' adapters wouldn't work past 2160p25.

[mortenrud]

And a side question.

Does anyone know hot to prevent the WatchPax from rearranging the displayport numbering when adding or removing outputs?

It seems to shuffle them around randomly, and when we have a monitor on port 1 for the sole purpose of monitoring it is quite annoying.

Any help is appreciated.

[jfk]

5 hours ago, mortenrud said:

Hi jfk

Thanks for your reply.

I was in fact trying to convert displayport to hdmi, but using an active cable.

Now I have placed a screen right next to the WatchPax 60 and running displayport to displayport and with the same error.

Everytime I try to set the resolution to more than 1920x1080 I will get the error.

Not all active adaptors are 4k60p capable. Anyway …

Forget WATCHOUT for a minute. Quit watchpoint on the display computer and using the graphic card’s control panel, can you set the desired resolution?

WATCHOUT is simply asking Windows its current resolution. . If the answer does match the numbers you have entered in the display specifications, it simply initiates DirectX 3D rendering mode. If the answer does not match the numbers you have entered in the display specifications, WATCHOUT will then ask Windows to set the resolution you have entered in display specifications. If Windows comes back and says it can not do that, the message you see is the result. BTW make sure there is no typo in the display specifications.

[Walter]

Hmmm... "Display Setting not available"  actually just sounds like there's a mismatch in FPS between show-setting and display-setting. (50 vs 60 )

[RBeddig]

On a WATCHPAX 60/62, you can open the remote control connection from the production software. WATCHPOINT then scales down to a window and in the menu you can find a link to the graphic card settings.

Check what the graphic card "sees" as the resolution of your display.

If you're sure that your DP-HDMI adaptors support HDMI 2.0, you can try to set the edid setting to the resolution you want to use. Do it one by one so that you can see how Windows reacts to it without loosing the image on the output.

The resorting of the outputs when adding or removing a display is something Windows initiates, not WATCHOUT. The only way to prevent this is to use some sort of edid management, either through the graphic card driver or using external edid minders.

[mortenrud]

This is still bugging me.

The WatchPax dosn't really see my display resolution as I connect to it through a Lightware MX2 HDMI matrix.

When I remote access to the WatchPax and create the custom resolution of 4224x1308 50hz then I have signal on my display.
When I take a HP Z4 with RTX4000 and do the same I have no issues using the same 10m Displayport to HDMI cable.

But whenever I try to go online with my show it fails with the "Display Setting not available".

[mortenrud]

On 6/29/2023 at 4:59 PM, Walter said:

Hmmm... "Display Setting not available"  actually just sounds like there's a mismatch in FPS between show-setting and display-setting. (50 vs 60 )

I run 50, both in show and display settings

[RBeddig]

Might be that the 3D mode of the graphic card (which WATCHPOINT uses for performance reasons) doesn't take the non-VESA resolution 4224x1308 50hz while the GDI mode of the graphic card does.

I seldom had save and reliable situations where I used very odd custom resolutions. I would definitely stay away from those.

[mortenrud]

22 hours ago, RBeddig said:

Might be that the 3D mode of the graphic card (which WATCHPOINT uses for performance reasons) doesn't take the non-VESA resolution 4224x1308 50hz while the GDI mode of the graphic card does.

I seldom had save and reliable situations where I used very odd custom resolutions. I would definitely stay away from those.

Hmm. I thought that is was one of the main features of Watchout to output non standard resolutions to non standard displays....

[jfk]

4 hours ago, mortenrud said:

Hmm. I thought that is was one of the main features of Watchout to output non standard resolutions to non standard displays....

The issue is not WATCHOUT, its the GPU and its software. I have used very odd nonstandard resolutions like a single WATCHOUT output of 7200x1080 without issues because the gpu was meticulously configured to support that resolution before WATCHOUT was even opened.

[mortenrud]

On 7/14/2023 at 5:54 PM, jfk said:

The issue is not WATCHOUT, its the GPU and its software. I have used very odd nonstandard resolutions like a single WATCHOUT output of 7200x1080 without issues because the gpu was meticulously configured to support that resolution before WATCHOUT was even opened.

But I am in fact able to output the resolution from the WatchPax alone and Watchout still fails.

[jfk]

56 minutes ago, mortenrud said:

But I am in fact able to output the resolution from the WatchPax alone …

How are you confirming that? using the gpu control panel in window mode? When watchpoint first starts up, before a show is loaded, the initial logo screen should choose a resolution determined by EDiD. 

[Walter]

On 7/13/2023 at 12:45 PM, mortenrud said:

This is still bugging me.

The WatchPax dosn't really see my display resolution as I connect to it through a Lightware MX2 HDMI matrix.

When I remote access to the WatchPax and create the custom resolution of 4224x1308 50hz then I have signal on my display.
When I take a HP Z4 with RTX4000 and do the same I have no issues using the same 10m Displayport to HDMI cable.

But whenever I try to go online with my show it fails with the "Display Setting not available".

Q = where do you create your custom resolution? I've had numerous issues with MX2 hardware and EDID's... always needed a lot of tweaking deep inside the EDID to resolve these issues. Not really sure as to why, just learned it as a trick to resolve issues... But I know for a fact that EDID's can harbour a bunch of issues inside, which aren't apparent since resolution seems fine...    But also recently on an AW Aquilon, drove the operators crazy, until they were provided with a different EDID, directly captured into the GPU and suddenly all played nice with eachother. 

[mortenrud]

On 8/2/2023 at 12:30 PM, Walter said:

Q = where do you create your custom resolution? I've had numerous issues with MX2 hardware and EDID's... always needed a lot of tweaking deep inside the EDID to resolve these issues. Not really sure as to why, just learned it as a trick to resolve issues... But I know for a fact that EDID's can harbour a bunch of issues inside, which aren't apparent since resolution seems fine...    But also recently on an AW Aquilon, drove the operators crazy, until they were provided with a different EDID, directly captured into the GPU and suddenly all played nice with eachother. 

Hi Walter. 

I create the custom resolution in the Nvidia Control panel on my WatchPax node.

[jfk]

4 hours ago, mortenrud said:

Hi Walter. 

I create the custom resolution in the Nvidia Control panel on my WatchPax node.

Note, only WATCHPAX models that run under Windows 10 offer the ability to manipulate EDID in the gpu. So WATCHPAX, WATCHPAX 2, WATCHPAX 4, and WATCHPAX 20 do not offer EDID editing. WATCHPAX 40, WATCHPAX 42, WATCHPAX 60 (all variants) and WATCHPAX 62 (all variants) provide access to EDID settings.

[mortenrud]

25 minutes ago, jfk said:

Note, only WATCHPAX models that run under Windows 10 offer the ability to manipulate EDID in the gpu. So WATCHPAX, WATCHPAX 2, WATCHPAX 4, and WATCHPAX 20 do not offer EDID editing. WATCHPAX 40, WATCHPAX 42, WATCHPAX 60 (all variants) and WATCHPAX 62 (all variants) provide access to EDID settings.

Hi jfk

It is a WatchPax 60, and the machine is able to output the correct resolution on the led screen.

But when I try to start the Watchout show, I get the error.

I don't know how I can find out what EDID settings to tweak....

[jfk]

57 minutes ago, mortenrud said:

Hi jfk

It is a WatchPax 60, and the machine is able to output the correct resolution on the led screen.

??? How are you determining that? Is the startup logo screen showing up? Keep in mind, before you load any show, the resolution used for the logo screen is determined by the EDID the output sees from the display / LED screen.

57 minutes ago, mortenrud said:

But when I try to start the Watchout show, I get the error.

Double check there is no typo in the resolutions specified in display settings.

Only when you load the show will WATCHOUT attempt to change resolution, and it only attempts to change resolution  if the logo screen resolution is different than the resolutions specified in your shows display settings.

 

[mortenrud]

19 hours ago, jfk said:

??? How are you determining that? Is the startup logo screen showing up? Keep in mind, before you load any show, the resolution used for the logo screen is determined by the EDID the output sees from the display / LED screen.

Double check there is no typo in the resolutions specified in display settings.

Only when you load the show will WATCHOUT attempt to change resolution, and it only attempts to change resolution  if the logo screen resolution is different than the resolutions specified in your shows display settings.

 

 

Hi jfk

I really appreciate your help. I have tried to make pics of my process. Let me know if this is unclear.

On the WatchPax 60 I create a custom resolution of 4224x1308 50hz.
See pic: 00 Nvidia Custom Resolution
And pic: 01 Nvidia Control Panel

My Display controller detects this resolution output correctly.
See pic: 02 Novastar Controller

My LED screen is able to output this resolution correctly
See pic: 03 Screen with Nvidia Info

The Watchout Node software is also able to output this resolution.
See pic: 04 Screen with WatchOut Logo

I then create an Display Output in my WatchOut show.
See pic: 05 WatchOut Show Output Configuration

But when I go Online my WatchOut show fails.
See pic: 06 WatchOut Show Error 

And pic: 07 WatchOut Node Error

 

 

[jfk]

One more screenshot please,

watchmaker - files - preferences - general

If you are at default output frame rate, it needs to be changed to 50

[mortenrud]

17 hours ago, jfk said:

One more screenshot please,

watchmaker - files - preferences - general

If you are at default output frame rate, it needs to be changed to 50

Yes, I have 50Hz in preferences. 
see screenshot. 
 

Btw, you write “Watchmaker”, my SW is called WatchOut. Is that different?

[RBeddig]

This looks correct. What you see is the software component watchmaker.exe   a.k.a. "watchout"

The software on the displays is watchpoint.exe.

Just out of curiosity: you're not trying to use a syncboard for your three outputs, are you?