Some Feedback:
- SLI switched off -> no change, in any test scenario.
- Office reinstalled -> slight changes in the problem, but still a problem (see below).
so I continued to play some more and found two issues:
1. Issue:
I have a native screen res of 3840x2160 (4k Screen) and also using htis for OS desktop. In-game I set the resulution to 2560x1440 as the native res is to much for my outdated SLI cards.
In a borderless window the OS resulution remains, but the game (or the OS, or the GFX driver, I don't know) scales it up to a full screen window. So we have a logical in-game resolution of 2560x1440, but still a 4k fullscreen window for the OS. That has the effect, that the function "GetWindowRect" in the below code returns the OS window resultion (3840x2160), instead of the logical in-game resultion.
I'm not sure what is the real reason (saving a window which is smaller than the given rect, or if it is really out-of memory), but in any case it results in a "not enough memory" message from the function "stdole.SavePicture".
Code:If EDRun Then AppActivate ("Elite - Dangerous (CLIENT)") hWnd = FnFindWindowLike("Elite - Dangerous (CLIENT)") GetWindowRect hWnd, udtRect SetForegroundWindow hWnd End If If No_Cap = False Then stdole.SavePicture hDCToPicture(GetDC(0&), udtRect.Left, udtRect.Top, _ udtRect.Right - udtRect.Left, udtRect.Bottom - udtRect.Top), BMP_Target End If If EDRun Then AppActivate ("Elite - Dangerous (CLIENT)") End If
2. Issue:
Having OS desktop resulotion = in-game resultion makes the problem change:
Both Resolutions = 2560x1440 do work properly, OCR screen scan is perfect.
Both Resolutions = 3840x2160 does result in a black screenshot, but no out of memory message.
So I did myself a workaround for the moment, by adding using SETRES.EXE (freeware tool) and creating batch files, lowering the OS screen res priot to launch ED.
That makes it work, but switching to desktop in game doesn't look nice (but that's not a big issue).
Just came to my mind:
@eventure: I'll try to test, and hardcode my in-game res to the save picture function to see if problem persists.
OK! Maybe not my best idea, as I already failed to start it in debug mode or anything like this.
![]()
Thanks for your extensive testing. That is really interesting.
The out of memory is clear, because the big picture doesn't fit into the smaller range. But why UHD making such an issue, is unknown to me.
Your workaround is clever. I will add this to the FAQs.