You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The app is currently not supported on ARM64 devices, it currently runs on the prism emulation layer.
Even if it is realy well optimised, it would greately benefit from an ARM64 build especially as they are becoming more and more common (partly with the copilot plus pc's).
Describe the solution you'd like
Publish releases compiled for ARM64 windows computers.
Describe alternatives you've considered
Keep using the app under the emulation layer.
Additional context
The latest copilot pc's have the benefit of having a greater battery life than prior models mostly due to the adoption of the arm architecture by microsoft and other manufacturers. They will become more and more present and relevent as time goes on so providing an arm build would most certainly, in long term, benefit to the project.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The app is currently not supported on ARM64 devices, it currently runs on the prism emulation layer.
Even if it is realy well optimised, it would greately benefit from an ARM64 build especially as they are becoming more and more common (partly with the copilot plus pc's).
Describe the solution you'd like
Publish releases compiled for ARM64 windows computers.
Describe alternatives you've considered
Keep using the app under the emulation layer.
Additional context
The latest copilot pc's have the benefit of having a greater battery life than prior models mostly due to the adoption of the arm architecture by microsoft and other manufacturers. They will become more and more present and relevent as time goes on so providing an arm build would most certainly, in long term, benefit to the project.
The text was updated successfully, but these errors were encountered: