I have the DPU3000-D3 version and am able to get 2560x1600@72. Question is whats the absolute max resolution/refresh this monitor can do?
Proper quality assessment will come later though, as I can't manage to select the right resolutions through the adapter on that computer.
1920x1200 was a nighmare to get and is only displayed @60hz, CRU can't enforce higher refresh rates. Also with only the displayport connected color depth is stuck at 6 bpc while 8bpc can also be selected when there's another monitor connected on the DVI port, it's a total mess.
I suspect the issue comes from the shiny crappy Crimson interface. It worked with the older computer and the less shiny, but functionnal Catalyst center.
I was running 1920x1080@85 and it was working fine then noticed some random rippling effect after an hour or so of use. I then plugged the usb cable in for power and have not experienced this anymore. This was before upping the resolution any.
Nope, when plugged on the adapter the monitor isn't detected at all, in both single or dual monitor configuration. It only detects default resolutions from the adapter (1920x1080@60hz and 1280x1024@60hz if I remember correctly).Does the adapter correctly read the monitor EDID or you see "monitor non plug and play"?
Nope, when plugged on the adapter the monitor isn't detected at all, in both single or dual monitor configuration. It only detects default resolutions from the adapter (1920x1080@60hz and 1280x1024@60hz if I remember correctly).
I just tried with the 2nd computer (HD5850/ catalysts 14.12), hooking up on the adapter the GDM-5410 I'm investigating the electronics. It is detected properly. EDID is wrong but that's normal for that monitor.So the monitor is seen non plug and play?
This happen only with crimson driver?
Which monitors do you have?
I did the input lag test with SMTT 2.0, 2 FW900 at 1280x1024@85hz, V-sync off:
There is none or it is too low to be detected.
I moved the beast again ( ) and replugged it for the sake of accuracy.With my card if the monitor is not recognized (non plug and play),it is impossible to use CRU with crimson driver,black screen after load the sytem.
This not happen with previous catalyst driver and i have this problem only with Samsung monitors and only with adapters,on analog port it's all ok.
Custom resolution through crimson panel at least work when my secondary Samsung is seen non plug and play (50% of the time)
I remember problems in the past with Samsung monitors and their strange EDID
I have that slow boot problem every time the monitor is not recognized,when the edid is read correctly,the boot is normal,it happen only with crimson driver and up.
When you have time try with an updated or an old driver
I did try with 1280x800@120hz in the first place (funny enough the Crimsons accept 120hz refresh rates when they refuse 85hz), but had too much trouble reading the figures on pictures. The sweep was probably too narrow/too fast.This great news! And there'll be no point in me doing the test either since I'm also currently using the 380x (2 of them actually). But I still might try it with high refresh rates (say 640x480 160hz) and low refresh rates ( 2400x1800 @ 50hz) to see if there is any detectable differences at high and low refresh intervals.
But I do have a LaCie electron blue IV, which I believe has a higher max scan rate (140kHz) than the FW900. So let me know if you guys can think of any high resolution-related tests I should try.
I just tried with the 2nd computer (HD5850/ catalysts 14.12), hooking up on the adapter the GDM-5410 I'm investigating the electronics. It is detected properly. EDID is wrong but that's normal for that monitor.
The first computer (R9 380X / Crimson 16.4.2) normally has a FW900 on DVI port and I plugged another spare one on the adapter for the SMTT test. Whatever I do the FW900 plugged on the adapter is not recognized at all while the one on DVI is. It's a driver version I already know some problems about, for example the custom resolution function was broken maybe since 16.1.1, it required a dialog box to be checked to work but that dialog box did work only when having a display on HDMI or displayport. That means that anyone with only a display on analog output was stuck. It is currently impossible to set a custom resolution through the Crimsons.
I haven't tried to update the drivers since then because the next versions have a bug making Windows boot extremely slow and it was still not fixed 6 months later ...
Google the subject, problems are not specific to my computer or softwares, or whatever. It's just that AMD keeps breaking working things inside drivers everytime something new is added since the Crimsons. For example they managed to break DirectX9 support for some games in 17.12.x ...I was going to ask what OS, but I'm guessing Windows 7 from your later post. You do have a very old drivers which are basically over a year old now. I am guessing you tried the latest of 17.12.1 or even 18.1.1? Weird bug to have Windows boot extremely slowly, did you do a complete driver uninstall first? Maybe other software conflicting?
Google the subject, problems are not specific to my computer or softwares, or whatever. It's just that AMD keeps breaking working things inside drivers everytime something new is added since the Crimsons. For example they managed to break DirectX9 support for some games in 17.12.x ...
You'll certainly understand I'm reluctant to waste my time looking for one without too many issues when I have an old one that more or less does its job.
Can somebody with a Sunix adapter import my CRU profile and see what resolutions are available to you? Especially if you're on AMD. I'm not seeing any resolutions above 2176x1224.
I'm wondering if it's the cheap DP cable I'm using. I am using USB power with it.
I guess you got a Sunix adapter too? How is it for you?
Don't know yet, I'm running into the issue I stated above and it's really bugging me.
Any chance you could download that bin file and load it into CRU and see what you have available (you have to restart PC or use restart64.exe for changes to take effect)? I'm pretty sure it won't overwrite AMD's custom resolutions.
Alternatively, just make a custom resolution in Adrenalin that's higher than 1536 vertical. Say, 2304x1728@60hz progressive. I'm trying to figure out if this is a Sunix issue or just my cable.
I added that res in Adrenalin and it's select-able in Windows resolution change. I didn't actually apply it to my monitor, however.
Ok, so I guess my GPU is detecting my crappy cable and refusing to let me see higher resolutions? That's my best guess, since I've read that bad DP cables will prevent people from selecting 4k60 on DP 1.2.
My Sunix adapter is used but seems to be working fine at the resolutions I can send to it, so I doubt theres a problem with it. Could also be a driver issue, but I'm on 18.1.1 like you are, so that's doubtful.
Silly question since pretty sure you tried it, but did you try adding the resolution via Radeon Settings instead of CRU?Mine says that too, which is the confusing part. If it was limiting my pixel clock due to cable issues, you think it would say something different there
Silly question since pretty sure you tried it, but did you try adding the resolution via Radeon Settings instead of CRU?
Ok, well this took a turn for the strange. Yesterday, I was hooking the Sunix up to my Dell p992, which has a max horizontal scan of 107kHz.. Today, I tried it with my LaCie 22 blue IV, which tops out at 140kHz, and I was able to select WAY higher resolutions. Stuff like 2560x1920@70hz (495mHz pixel clock) or 2720x1530 @ 86Hz (520mHz) pixel clock, and they were all stable.
But I still eventually hit point where windows wasn't showing some resolutions. Like I couldn't select 2880x2160@60 on the Sunix, even though I could over VGA.
So now I'm starting to think the issue is not my cable. Could it be some weird limit the Sunix is creating based on the monitor's EDID? Could Radeon settings be limiting based on EDID, even though I'm supposed to overriding via CRU? This is all very strange and I can't figure out why I'm being limited here.
Yep, I get the "this isn't supported by your monitor" message, even though I can add the resolution over VGA.
Did you ever hit a point where Radeon settings wasn't letting you add stuff? Did it seem to be based on horizontal pixel count or overall pixel clock? And I'm talking about Adrenalin in Windows, of course. Seems like Ubuntu gives a lot more leeway
Also, I noticed my Sunix doesn't like interlaced resolutions, it blanks out even though my monitor is showing the correct timings on the OSD. Were any of the interlaced resolutions you tried actually visible?
Edit 2: For the heck of it, I tried 3200x2400 interlace at 30 Hz from Radeon Settings and I got a black screen. I believe this worked in Ubuntu Live CD, so I guess that's a driver limit.
Well I just tried 2848x1536@80 in Radeon Settings which works fine in Ubuntu Live CD, and no go. I got the error message "The custom resolution settings are not compatible with this display. Reconfigure your settings and try again." So safe to say it's AMD Windows driver limit?
Edit: 2648x1536@80 wouldn't add, but 2448x1536@80 added fine. It also shows picture.
Edit 2: I tried 1680x1260@68hz (67.5 wouldn't take) interlaced and while it added fine, I got a blank screen on choosing the resolution.
Yep, since it's not happening in Ubuntu, this sounds like another issue with AMD's Windows driver. Well, I remember interlaced working over HDMI>VGA on my Nano GX, so that could always be something to fall back on in those rare instances where I want inerlaced, even though pixel clock would be pretty restricted.