- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
We used to render offscreen a 3D scene in WPF (render in a window not located in the screen) then copying it to a bitmap.
Everything works fine on i7 6700 (HD Graphics 530), i7 7700 (HD Graphics 630) but not on i7 8700 (UHD Graphics 630).
Has anything changed about offscreen rendering ?
Is there an option to enable/disable to make it works like before ?
Thanks in advance for your response.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After deeper researchs, it appears that the guilty is the 1809 update for Win10 that changed PrintWindow and not the chipset.
Regards
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Leo,
I can reproduce the issue on 3 differents computer of the same model : Dell Optiplex 7060 (i7 8700)
Before upgrading to Dell OptiPlex 7060, we had :
- Dell OptiPlex 7050 (i7 7700)
- Dell Precision 3620 (i7 6700)
- Dell OptiPlex 9020 (i7 4770)
- Dell OptiPlex 9010 (i7 3770)
- Dell OptiPlex 980 (i5 660)
All of those systems worked, but not the 3 new computers 7060.
We are a software editor and we use WPF to render 3D models.
We have a window with WPF controls and copied with PrintWindow (User32.dll).
If the window is partially located out of screen, the bitmap result is up to date only for the in-screen region of the WPF window. If the window is totally out of screen , the obtained bitmap is empty (or the last correct render if the window was on the screen before)
This is explained by the attached images (next message since I can attach only one file per post).
You will find attached the log of SSU executed on a 7060 computer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
After deeper researchs, it appears that the guilty is the 1809 update for Win10 that changed PrintWindow and not the chipset.
Regards
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page