Latest version can not run on Windows 7 64bit #1300
Comments
|
The HRESULT is 0x887A0004, which is DXGI_ERROR_UNSUPPORTED. Is this Windows 7 with Platform Update, or just Windows 7? We don't support the latter. I just tested master on my Windows 7 (with Platform Update) compatibility test machine, and it's fine. Also, does druid 0.6 work? I made some changes in #1191, it's possible that regressed compatibility, though I was trying to be careful and did test. |
|
all example of 0.6 work properly on my win7. But git version(2020-10-11) can not run. This is the win7 sp1, but haven't update to the latest update. Host Name: ALAN-PC-VM |
|
Ok. Can you confirm that 30922d0 works but b631667 fails with the same error code? Can you try using D3D_DRIVER_TYPE_UNKNOWN or D3D_DRIVER_TYPE_SOFTWARE in dcomp.rs (around line 53)? Basically, we're not supporting anything earlier than Windows 7 with Platform Update, but the fact that it worked before means I am willing to consider a fix if it's not too complicated. Honestly I am a little surprised it worked before because I would have expected the downcast to ID2D1DeviceContext to fail. |
|
30922d0 can not compile here. 30922d0 compile error message: |
|
D3D_DRIVER_TYPE_SOFTWARE still wrong. INFO [druid_shell::platform::windows::util] No shcore.dll |
|
Yes, this is because of the very annoying fact that the 0.2.0-pre3 reference to piet breaks semver. Change the piet-common = "=0.2.0-pre3"
piet-direct2d = "=0.2.0-pre3"
piet = "=0.2.0-pre3" |
|
What about |
|
b631667 not work. |
|
version 2020-10-11, changed to D3D_DRIVER_TYPE_WARP work on my win7. |
|
Sweet! Let me prepare a PR that hopefully will fix this. |
|
Thank you! |
Use the WARP driver when creating a D3D11 device if the HARDWARE driver is not available. Fixes #1300
|
My win7 and windows server 2008 r2 are all virtual PC, so there's a possibility that maybe is caused by virtual PC? not caused windows version? |
|
It could be a combination of both. What's failing is selecting the hardware GPU driver, so the PR falls back to software in that case. In either case, let me know if it works, and if so, we don't need to worry too much about the exact factor. |
|
Now it works fine on the virtual machine win7 sp1 and windows server 2008 r2, so whether it is the problem of the virtual machine or the operating system, the problem has been solved. |
Latest git version(2020-10-11) can not run on Windows 7 64 bit ( in VirtualBox ).
for example widget_gallery.exe:
INFO [druid_shell::platform::windows::util] No shcore.dll
INFO [druid_shell::platform::windows::util] Could not load
GetDpiForSystem. Windows 10 or later is neededINFO [druid_shell::platform::windows::util] Could not load
GetDpiForWindow. Windows 10 or later is neededINFO [druid_shell::platform::windows::util] Could not load
SetProcessDpiAwarenessContext. Windows 10 or later is neededINFO [druid_shell::platform::windows::util] Could not load
GetSystemMetricsForDpi. Windows 10 or later is neededDEBUG [druid::localization] available locales [], current en-US
DEBUG [druid::localization] resolved: [en-US]
DEBUG [druid_shell::platform::windows::window] dxgi factory pointer = 0x3a39d0
DEBUG [druid_shell::platform::windows::window] 0x3b6bb0: desc = Some("VirtualBox Graphics Adapter (WDDM)"), vram = 147914752
DEBUG [druid_shell::platform::windows::window] adapter = 0x3b6bb0
ERROR [druid_shell::platform::windows::dcomp] D3D11CreateDevice: 0x887a0004
ERROR [druid_shell::platform::windows::window] Creating swapchain failed: Hr(-2005270524)
thread 'main' panicked at 'called
Option::unwrap()on aNonevalue', druid-shell\src\platform\windows\window.rs:812:55stack backtrace:
0: 0x13f93479e -
1: 0x13f94b57b -
2: 0x13f930b98 -
3: 0x13f937534 -
4: 0x13f937118 -
5: 0x13f937def -
6: 0x13f937955 -
7: 0x13f9350df -
8: 0x13f937909 -
9: 0x13f9492d0 -
10: 0x13f94921c -
11: 0x13f857d06 -
12: 0x13f85bf6d -
13: 0x77079bbd - TranslateMessageEx
14: 0x7707729b - SetWindowTextW
15: 0x770767e9 - IsDialogMessageW
16: 0x771cb5cf - KiUserCallbackDispatcher
17: 0x770718ea - ShowWindow
18: 0x13f84e70a -
19: 0x13f73386c -
20: 0x13f749dd8 -
21: 0x13f739d76 -
22: 0x13f739d8c -
23: 0x13f938133 -
24: 0x13f74fd07 -
25: 0x13f9aefc4 -
26: 0x76f5556d - BaseThreadInitThunk
27: 0x771b385d - RtlUserThreadStart
The text was updated successfully, but these errors were encountered: