Hi i have a problem and wondering if anyone can help. I have an ASUS VG248QE GSYNC monitor which i am currently using with an AMD 295x2. I understand that ULMB may not work (it does not for me) however the strobelight utility does not work also - 'No compatible display found'. Any help would be appreciated. Thank you.
(02-07-2015 05:26 PM)Muezzin Wrote: [ -> ]Hi i have a problem and wondering if anyone can help. I have an ASUS VG248QE GSYNC monitor which i am currently using with an AMD 295x2. I understand that ULMB may not work (it does not for me) however the strobelight utility does not work also - 'No compatible display found'. Any help would be appreciated. Thank you.
On which Catalyst version?
(02-07-2015 05:26 PM)Muezzin Wrote: [ -> ]Hi i have a problem and wondering if anyone can help. I have an ASUS VG248QE GSYNC monitor which i am currently using with an AMD 295x2. I understand that ULMB may not work (it does not for me) however the strobelight utility does not work also - 'No compatible display found'. Any help would be appreciated. Thank you.
The G-SYNC version has completely different hardware, so I don't know if it's compatible. Renaming strobelight.exe to strobelight-debug.exe will leave a debug.txt file that should show you where it's failing.
"3D = ERROR" would mean LightBoost is not supported, or there's a problem communicating with the monitor.
"VENDOR = 0x## (unsupported)" would mean the monitor has a vendor code that isn't supported by Strobelight. If the code happens to be 0x6E, then there might be a communication problem.
(02-08-2015 05:40 PM)ToastyX Wrote: [ -> ] (02-07-2015 05:26 PM)Muezzin Wrote: [ -> ]Hi i have a problem and wondering if anyone can help. I have an ASUS VG248QE GSYNC monitor which i am currently using with an AMD 295x2. I understand that ULMB may not work (it does not for me) however the strobelight utility does not work also - 'No compatible display found'. Any help would be appreciated. Thank you.
The G-SYNC version has completely different hardware, so I don't know if it's compatible. Renaming strobelight.exe to strobelight-debug.exe will leave a debug.txt file that should show you where it's failing.
"3D = ERROR" would mean LightBoost is not supported, or there's a problem communicating with the monitor.
"VENDOR = 0x## (unsupported)" would mean the monitor has a vendor code that isn't supported by Strobelight. If the code happens to be 0x6E, then there might be a communication problem.
Thanks for the info. It seems that my error is none of the above, it is as follows;
[2015-02-08 18:36:10.198] LOAD(AMD): LoadLibrary("atiadlxx.dll") = SUCCESS
[2015-02-08 18:36:10.207] LOAD(AMD): ADL_Main_Control_Create() = SUCCESS
[2015-02-08 18:36:10.207] LOAD(NVIDIA): NvAPI_Initialize() = ERROR -2
[2015-02-08 18:36:10.338] INIT(AMD, 6): ADL_Display_DisplayInfo_Get() = ERROR -1
[2015-02-08 18:36:10.338] INIT: No compatible displays found.
I downloaded atiadlxx.dll from the first post as it was failing before that. Now it seems it fails on Nvidia which i presume does not concern me, however i am unsure how to remedy the last error; 'INIT(AMD, 6): ADL_Display_DisplayInfo_Get() = ERROR -1'?
(02-08-2015 06:41 PM)Muezzin Wrote: [ -> ]I downloaded atiadlxx.dll from the first post as it was failing before that. Now it seems it fails on Nvidia which i presume does not concern me, however i am unsure how to remedy the last error; 'INIT(AMD, 6): ADL_Display_DisplayInfo_Get() = ERROR -1'?
Why did you do that? You said you were using 14.12. The DLL was for working around a crash issue with 14.9/14.9.1. Are you using a 32-bit system? LoadLibrary("atiadlxx.dll") is supposed to fail on a 64-bit system. Was ADL_Display_DisplayInfo_Get() failing without the DLL?
(02-09-2015 02:27 PM)ToastyX Wrote: [ -> ] (02-08-2015 06:41 PM)Muezzin Wrote: [ -> ]I downloaded atiadlxx.dll from the first post as it was failing before that. Now it seems it fails on Nvidia which i presume does not concern me, however i am unsure how to remedy the last error; 'INIT(AMD, 6): ADL_Display_DisplayInfo_Get() = ERROR -1'?
Why did you do that? You said you were using 14.12. The DLL was for working around a crash issue with 14.9/14.9.1. Are you using a 32-bit system? LoadLibrary("atiadlxx.dll") is supposed to fail on a 64-bit system. Was ADL_Display_DisplayInfo_Get() failing without the DLL?
I was just trying my luck to be honest. Without the dll file atiadlxx.dll = 'ERROR 126', however ADL_Display_DisplayInfo_Get() fails regardless. I'm on Windows 8.1 64-bit.
UPDATE:
Without the DLL files the debug information is as follows,
[2015-02-09 19:03:59.829] LOAD(AMD): LoadLibrary("atiadlxx.dll") = ERROR 126
[2015-02-09 19:03:59.830] LOAD(AMD): LoadLibrary("atiadlxy.dll") = SUCCESS
[2015-02-09 19:03:59.838] LOAD(AMD): ADL_Main_Control_Create() = SUCCESS
[2015-02-09 19:03:59.838] LOAD(NVIDIA): NvAPI_Initialize() = ERROR -2
[2015-02-09 19:03:59.966] INIT: No compatible displays found.
(02-07-2015 07:47 AM)ToastyX Wrote: [ -> ] (02-04-2015 05:14 PM)LightLotus Wrote: [ -> ]Hey all, recently got a BenQ XL2411 connected via DVI-D.
Ran 144 hz and 120 hz and boy what a difference!
I've tried the 1350 tweak via Nvidia Control Panel; however I'm having a difficult time initializing strobelight.
I've installed 120 hz (strobed) and 121 hz (for on and off) via setup; however, upon restart it continues to intialize and never stops.
It's at 5000 passes as I post this but here's what it looked like:
Strobelight is not compatible with the BenQ Z-series monitors.
I had no idea, thank you Toasty for all the help and work you've spread.
(02-09-2015 03:20 PM)Muezzin Wrote: [ -> ]Without the DLL files the debug information is as follows,
[2015-02-09 19:03:59.829] LOAD(AMD): LoadLibrary("atiadlxx.dll") = ERROR 126
[2015-02-09 19:03:59.830] LOAD(AMD): LoadLibrary("atiadlxy.dll") = SUCCESS
[2015-02-09 19:03:59.838] LOAD(AMD): ADL_Main_Control_Create() = SUCCESS
[2015-02-09 19:03:59.838] LOAD(NVIDIA): NvAPI_Initialize() = ERROR -2
[2015-02-09 19:03:59.966] INIT: No compatible displays found.
I don't see any unusual errors. That means the monitor didn't respond when checking for 3D mode. The G-Sync module might have a different way of activating LightBoost that isn't compatible with Strobelight.
(02-09-2015 11:20 PM)LightLotus Wrote: [ -> ]I had no idea, thank you Toasty for all the help and work you've spread.
I just wish NVIDIA wouldn't put a vendor lock on such a useful monitor feature simply to protect their proprietary 3D Vision that hardly anyone cares about anyway.