-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ARM64][Windows 11]: Running Freshly Created Avalonia 11.0.0-preview4/5 application returns a transparent window #10405
Comments
@maxkatz6 avaloniarepro.mp4 |
Don't use preview4 just in case. |
I switched it to preview5 in the video after showing it not work out of the box with one targeting preview4 |
I actually suspect that it's only working within Parallels due to Parallels Tools drivers interacting with the Mac's video acceleration, etc. |
best would be to try it again with latest master / nightly build. This way, you have most fixes inside. If you target preview4 right now, some breaking changes are expected but they are easy to fix. Read breaking changes page for reference. |
Note that M1 doesn't have strict memory alignment rules like "normal" ARM CPUs. |
Tried the latest nightly, same result |
WAIT.... This is even more weird. So, it seems for anything to work with glES enabled, you HAVE to set Wgl on and Transparency unset |
@danwalmsley - Have you been able to repro this issue? :) |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Which device are you using to run this? |
@iksi4prs please try also latest nightly builds in a really simple App. If that does not work, please share the sample with us to double-check if anything obvious is missing. Thx. |
Nightly builds have the same issue. This is something that seems to be specific to the native Windows on Arm devices rather than Parallels specific VMs. |
Their reply
Is EXACTLY what I'm facing. It seems to only be reproducible on native Windows on Arm devices like the Pro X and Win Dev Kit 2023 for example. This isn't reproducible on WoA Parallels VMs. |
Created a new avalonia.app, switched the packages to the CI build, seems to load the black window with white text which means that it'll work out of the box. One thing I'm not seeing is the titlebar and transparency out of the box, but I assume that's to be expected if it's falling back to the Microsoft Basic Display Adapter. But you know what? This will do for now! I need to play around and try some more things, but the initial issue related to the window being fully transparent without showing any elements is good to go with that PR! I can create a separate issue for keeping an eye on the Adreno adapter since this gets us forward. \o/ Thanks @maxkatz6 and everyone!!! |
I can't find the packages from the PR build, which claims to have built 11.0.999-cibuild0041739-beta. This is the list of packages available from the https://nuget-feed-nightly.avaloniaui.net/v3/index.json feed. |
@AArnott
Use the 11.1.999* instead of 11.0.999*
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Andrew Arnott ***@***.***>
Sent: Wednesday, November 8, 2023 8:36:27 AM
To: AvaloniaUI/Avalonia ***@***.***>
Cc: Jeremy Sinclair ***@***.***>; Mention ***@***.***>
Subject: Re: [AvaloniaUI/Avalonia] [ARM64][Windows 11]: Running Freshly Created Avalonia 11.0.0-preview4/5 application returns a transparent window (Issue #10405)
I can't find the packages from the PR build, which claims to have built 11.0.999-cibuild0041739-beta.
[image]<https://user-images.githubusercontent.com/3548/281419413-d27e3caf-adef-43f6-b9e1-34453d9597b4.png>
This is the list of packages available from the https://nuget-feed-nightly.avaloniaui.net/v3/index.json feed.
—
Reply to this email directly, view it on GitHub<#10405 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AA6URJMT5OGSTG4HFGCV4YDYDODFXAVCNFSM6AAAAAAVBOBTIWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBRHEYDKOBZGQ>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I'm not sure why I'd look for a 11.1.999 version when the PR build says to use a 11.0.999 version. But I tried changing the 0 to 1 as you seemed to suggest. It still fails:
|
Apparently I need to combine the 0->1 change with a fix to the feed I was using. I should have been using https://nuget-feed-all.avaloniaui.net/v3/index.json rather than the nightly feed. With that, I no longer have a transparent window. But what is drawn looks butt-ugly. It's supposed to look like this (as seen on an x64 machine): |
@AArnott check RequestedThemeVariant in App.axaml. It should be Light in your case. |
It was I like your PR! |
Oof.. The lack of hardware acceleration is definitely visible. Recording.2023-11-10.101449.mp4 |
I strongly suggest using WGL for ARM64 instead of the software renderer. The user needs to have the OpenGL compatability app (available for free form the store https://apps.microsoft.com/detail/9NQPSL29BFFF) |
Hmmm yeah... I edited my local copy of WalletWasabi to use Wgl and 11.0.5 instead of the PR version and it's much smoother. I do wonder if the move is to force Wgl for any adreno gpu attempting Egl for the time being? Recording.2023-11-10.104639.mp4 |
I don’t think it’s a good idea. Wgl by itself has tons of issues, and half of them were reported here already. Microsoft basic renderer should provide stability that is missing on arm devices. And we can hope it will be better with next gen arm chips and new drivers. Although, ideally we should report it to adreno, so they could take a look and diagnose this problem from their side. Does anybody know the right tracker? |
Maybe raise the issue at https://linaro.atlassian.net/wiki/spaces/WOAR/overview? There are contacts with Qualcomm and Microsoft. |
Reopening per @snickler 's request |
I can confirm the issue is a driver issue and a fix is planned for the near future. I'll update once the new driver is available. |
@GrfxArik is there a way to programmatically detect a new driver? Will it have a different dx-adapter name, or maybe another dx/win32 api to know? Otherwise, we might stack with a current solution for a while. |
@maxkatz6 I found https://stackoverflow.com/questions/56935213/how-to-get-adapter-driver-version-in-directx12 that can be used, but completely understandable the need to have the workaround for a while |
Any updates on this? We have the same problem with Surface Pro 5 devices with Microsoft SQ1 ARM processors. The plain window appears and brings a mica effect, but there's no window content. |
|
I will second the workaround is pretty feasible. As far as the fix, it will be coming soon but for 8cx Gen 3 devices as of now (Surface Pro 9 5g, Win Dev Kit 2023, Lenovo ThinkPad X13s). @maxkatz6 , when the update becomes available I'll look to put in a PR that will exclude those devices from the workaround |
Is there a timeline for the updated graphics driver? It is still coming to 8cx Gen 3 devices, right? |
Just received word that the updated graphics driver is out! |
Latest driver is available form Qualcomm: https://www.qualcomm.com/products/mobile/snapdragon/laptops-and-tablets/snapdragon-mobile-compute-platforms/snapdragon-8cx-gen-3-compute-platform#Software |
@GrfxArik Will 8cx Gen 1/Gen 2 receive the same update? I know Qualcomm does not provide downloads for these platforms, so please provide a version number that fixes the issue. |
For reference: from the download linked above, on 8cx Gen 3 it would be 30.0.4035.6900. |
No. the fix was only done for 8cx Gen 3 and included in the X Series devices. Gen 1/2 aren't being offered the fix unfortunately. |
Describe the bug
Running Avalonia applications using 11.0.0-preview4,preview-5 and even nightly builds on native Windows on Arm devices (Surface Pro X / Windows Dev Kit 2023) fail to properly display window contents. By default, only the outer frame of the window is created while the inner contents are completely transparent.
To Reproduce
Steps to reproduce the behavior:
dotnet new avalonia.app -f net7.0 -av 11.0.0-preview4
from an Arm64 Windows 11 devicedotnet publish -c Release -r win10-arm64
Expected behavior
Creating a new application from the Avalonia.Templates should properly run without modification for Windows Arm64.
Screenshots

If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
The interesting thing is deleting
av_libglesv2.dll
from the output directory will cause the app to load properly. I'm assuming this is a composition issue related to #8776 ?The text was updated successfully, but these errors were encountered: