Hyperion Entertainment Message Boards

Posted: **Tue Jan 04, 2022 1:57 pm**

@devs

Ok, i need help with this one.

I checked with Hans deRuiter and he assured me it's no driver issue.
It seems to be coming from graphics.library, so i ask you kindly to confirm or reject, please.

Take a look here for the full "thread" (since i don't know if one can look the items if not registered, i will do a summarize)
http://www.amiga.org/developer/bugrepor ... php?id=857

Summarize:
I have a UHD capable monitor (LG 43BN70-U) and a UHD capable graphics card (RadeonHD 7950), but HDMI refuses to display the UHD resolution (3840x2160), only 2560x1440 is possible (or at least seen and used by ScreenMode Prefs).

The monitor itself *can* do UHD, this was tested with a lend PC, gfx card was a IntelHD 4000 connected through DisplayPort.

Going on, i have tried DDC and manually adding the screenmodes to no avail.

These are my monitor tooltypes:

CMPLENGTH=21
BOARDNAME=Radeon HD 7900 series
VSYNCMIN=56
VSYNCMAX=61
HSYNCMIN=30000
HSYNCMAX=135000
MODE=640x480@60
MODE=640x512@60
MODE=720x480@60
MODE=800x600@60
MODE=1024x768@60
MODE=1152x864@60
MODE=1280x512@60
MODE=1280x720@60
MODE=1280x800@60
MODE=1280x1024@60
MODE=1600x900@60
MODE=1680x1050@60
MODE=1920x1080@60
MODE=2560x1440@60
MODE=3840x2160@56
MODE=3840x2160@57
MODE=3840x2160@58
MODE=3840x2160@59
MODE=3840x2160@60
MODE=3840x2160@61
MODE=3840x2160@27
MODE=3840x2160@28
MODE=3840x2160@29
MODE=3840x2160@30
DISABLEFAKENATIVE=Yes
INTERRUPT=No

btw, it doesn't matter if i set interrupt to on or off

and this is what i get in serial with the above tooltypes in place

Hidden Text - Click to Show :

and this is the answer of Hans deRuiter:

That's very weird behaviour from the graphics library. The 56-61 Hz modes are being rejected with a vague error that the frequency isn't right, and the 29-30Hz modes are being treated as out of range, because it says that the vsync must be in the range 55-62. Not sure where it got that idea from, since the modes are coming from the EDID data (which is visible in the debug log).

This isn't a driver issue. If you can't get it to work, then submit a bug report to Hyperion.

So, here i am, please help

grpahics.library is 54.248 (23.02.2020)

I can do NDA betatests if no dev got any UHD monitors available

edit: ...or letting a debug library run for more output, if that is not too much to ask?

Thank you

Posted: **Wed Jan 05, 2022 12:55 pm**

And while we are at it, could someone please lift this limitation in graphics library?

VSYNCMIN below 50hz not supported (using default 56hz)!

Thank you

Posted: **Wed Jan 12, 2022 6:26 am**

I think the minimum VSYNC value was created back in the old analogue days when a monitor's scan circuits could indeed overheat and be damaged if scan rates were too low. IIRC it's not graphics that imposes this limit, it's something else at boot time. I'll take a look.

(time passes)

OK, found it, it IS in graphics.lib. What value do you want? 25?

Posted: **Wed Jan 12, 2022 9:11 am**

@tonyw

Oh, nice.

Can I come back to you for that?
I'm not at home and would like to do another test with a DP to HDMI cable from a PC to see what VSYNC values are actually used.

25 sounds about as low as it could or should go (since the monitor seems to use 29/30Hz on the IHD resolution), but maybe some lower values would be even better, maybe 15 or even 14, to really support all kinds of new monitors?

I'll post here once I can confirm the needed values.

Thank you very much

Posted: **Wed Jan 12, 2022 10:23 am**

Sounds like it might be worth considering some form of warning about the risks related to old analogue monitors if the value is set below a certain level.

I realise it would be rare that someone actually uses one of those for OS4, but then again - you know those Amigans

.

Best regards,

Niels

Posted: **Thu Jan 13, 2022 11:21 am**

I don't know how you could warn them and have them take it seriously. Perhaps if gfx.lib raised a requester warning of the danger and the user had to click "I understand" to continue... but then, how do you display such a requester? In a basic 1024x768, before switching to what the user wanted?

Perhaps we could include a warning within the tooltypes?

Anyway, we've changed the hard-coded limit from 50 Hz down to 25 (and corrected the spelling of "Hz" from "hz").

Posted: **Thu Jan 13, 2022 1:09 pm**

It could also be a hint in the screenmode edit subwindow, whenever the frequency is set below some value.

Or it could even be a short text displayed in the GUI below the field when relevant.

I know, not everybody is using the hints, and a screenmode can also be created in the tooltypes of the monitor icon. But at least you'd catch the casual goofups.

Best regards,

Niels

Posted: **Thu Jan 13, 2022 9:06 pm**

tonyw wrote: Thu Jan 13, 2022 11:21 am I don't know how you could warn them and have them take it seriously. Perhaps if gfx.lib raised a requester warning of the danger and the user had to click "I understand" to continue... but then, how do you display such a requester? In a basic 1024x768, before switching to what the user wanted?

Perhaps we could include a warning within the tooltypes?

Anyway, we've changed the hard-coded limit from 50 Hz down to 25 (and corrected the spelling of "Hz" from "hz").

wrt warning
• You could make the color of the set Hz red once it's over or under a certain setting in screenmode prefs.
• You could make the *testing* of those settings mandatory and not skippable and display a warning on the test screen (though that could probably already damage the monitor)
• You could add a second warning when those settings get saved, one for the saving and rebooting part and one for the set Hz.

wrt the changes

First of all, thank you
Second I would like to know if there is any chance I could test it?
Maybe with a time-out after a week or so or a timer that counts the library open state and stops working after 50?

I'd like to see if that already fixes my monitor problems or if I maybe can provide more info and help fixing the issue?
Please

Thank you

Posted: **Thu Jan 13, 2022 11:04 pm**

WRT warnings: We are discussing what needs to be done for people with old analogue monitors. Thank you for the suggestions.

WRT testing:

I can't build the graphics library on my system, and it's not mine anyway, so I can't let you have a demo version, sorry. It will be released to betatesters in days and I should be able to test the VSync limits then.

Posted: **Fri Jan 14, 2022 3:22 pm**

@tonyw

Ok, thank you anyway.
Maybe one of the betatesters own a uhd screen?

Hyperion Entertainment Message Boards

Bug in graphics.library (UHD resolutions)

Bug in graphics.library (UHD resolutions)

Re: Bug in graphics.library (UHD resolutions)

Re: Bug in graphics.library (UHD resolutions)

Re: Bug in graphics.library (UHD resolutions)

Re: Bug in graphics.library (UHD resolutions)

Re: Bug in graphics.library (UHD resolutions)

Re: Bug in graphics.library (UHD resolutions)

Re: Bug in graphics.library (UHD resolutions)

Re: Bug in graphics.library (UHD resolutions)

Re: Bug in graphics.library (UHD resolutions)