Greg96
7 discussion posts
Keith,
I have similar issues where Monitor Profiles are detected sometimes and not others. I have downloaded the tool you uploaded and capture before/after data like mentioned. I am using Win. 10 and DF v9.3. Do you prefer I stay in this thread or create a new one?
Thanks,
Greg
Dec 4, 2018 (modified Dec 4, 2018)
•
#1
Greg96
7 discussion posts
I will upload those on the next occurance. The last occurance was this morning but I didn't know about the tool then. I may capture one for now (after manually loading the profile) if that would be helpful also to compare with the next ones.
Sounds good! If you grab one now while the profile is working, then grab another one when it's not detected, that would be great.
Thanks!
Greg96
7 discussion posts
I have a before and after from the last incident plus an Auto Detected time from earlier.
Filenames are labeled with dates (yyyymmdd) and a description of detected or not.
If it helps I notice this most when the previous computer use was a different monitor profile... i.e. use at home, then use at work with different monitor profiles
Thanks,
Greg
• Attachment [protected]: BFCustomerTest 20181204-B after reboot - auto detected.txt [15,845 bytes]
• Attachment [protected]: BFCustomerTest 20181211-A - Not Detected.txt [15,883 bytes]
• Attachment [protected]: BFCustomerTest 20181211-B - After manual Load Profile.txt [15,921 bytes]
Thanks, I'll check these out!
So this is weird! The data is the same in all three files. Do you have Monitor Splits configured as part of your Monitor Profile as well?