#asahi · 2026-05-12 06:34
playboicarti[m]I followed the guide linked in the docs but realised it only works if I bypass the TPM requirement or use a version that does not require TPM#asahi · 2026-05-12 06:33
playboicarti[m]Hey everyone, I seem to be having trouble setting up virtualised Win11 on Asahi#asahi · 2026-05-12 06:32
Leese[m]jbe: Joined just to ask about this lol.#asahi · 2026-05-11 07:45
Guest9171unless its a combination of what you said and the fact im using proton? not sure why that wouldnt affect vanilla though#asahi · 2026-05-11 07:44
Guest9171lacamar: cant say ive experienced that. using fex 2603. the problem i was takling about happens exclusively on valve's wine fork, vanilla wine works fine#asahi · 2026-05-11 07:43
jbethanks :)#asahi · 2026-05-11 07:42
chadmedit did yes#asahi · 2026-05-11 07:41
jbehmm, it seems the speakers are at full volume on login now regardless of my volume settings, did that pipewire bug regress or something?#asahi · 2026-05-11 07:21
barusuhas any of you tried the arm64 native steam beta?#asahi · 2026-05-11 07:04
lacamar[m]Guest9139: Yes, I know. I host all the rpm packages on my COPR. Arm64ec can run on 16k hosts, but when using FEX DLL versions newer than 2507.1 or 2508.1, it becomes rare to find any software that runs without crashing from stack overflows. This is because the FEX project removed hacks that let libarm64ecfex.dll and libwow64fex.dll work somewhat reliably with 16k systems #asahi · 2026-05-11 02:47
Guest9153proton wine doesnt seem to work with dxvk. not seeing any errors, but it just doesnt create a window#asahi · 2026-05-10 21:21
chaos_princessyou can just open the proton repo and see which wine it is using#asahi · 2026-05-10 21:20
chaos_princessin that case - yea#asahi · 2026-05-10 21:20
user_i already have dxvk dlls that im using with vanilla wine#asahi · 2026-05-10 21:20
chaos_princess"umu mess" gives you dxvk/vkd3d, which you want#asahi · 2026-05-10 21:18
user_does ValveSoftware/wine have the same patches as proton? avoiding the whole umu mess would be nice#asahi · 2026-05-10 21:18
JamesCalligeros[m]Thats the same for using power in general :p#asahi · 2026-05-10 21:18
chaos_princess64k is the largest realistic#asahi · 2026-05-10 21:18
chaos_princessteeeechnically, there is power that can do 256k pages, but even linux kconfig says "you probably shouldn't do this unless you have really good reason to"#asahi · 2026-05-10 21:17
JamesCalligeros[m]^#asahi · 2026-05-10 21:16
JamesCalligeros[m]If you use jemalloc, build it for 64K pages, and dont hard code page sizes in your allocations#asahi · 2026-05-10 21:16
chaos_princessor hardcode it to 64k#asahi · 2026-05-10 21:16
chaos_princessdon't hardcode PAGE_SIZE#asahi · 2026-05-10 21:16
linkmauveWhat do games do to make them incompatible, and what can I do as a game engine writer to avoid that?#asahi · 2026-05-10 21:15
JamesCalligeros[m]That way youll never be disappointed when it doesnt#asahi · 2026-05-10 21:15
JamesCalligeros[m]Just dont expect things to work isnall#asahi · 2026-05-10 21:14
JamesCalligeros[m]Most stuff outside of games and CEF and stuff that uses jemalloc should be fine#asahi · 2026-05-10 21:14
user_never ran into page size issues#asahi · 2026-05-10 21:13
user_interesting, guess ive just been lucky with the apps i've run#asahi · 2026-05-10 21:13
chaos_princessif you never use mmap/virtualAlloc, there is a high change that your thing is page size agnostic#asahi · 2026-05-10 21:13
JamesCalligeros[m]If you let windows allocate virtual pages as it pleases, it will allocate 64K pages#asahi · 2026-05-10 21:13
chaos_princessno. you can write apps that do not assume that pages are 4k. #asahi · 2026-05-10 21:13
JamesCalligeros[m]No but win32 has not always been x86 exclusive#asahi · 2026-05-10 21:12
user_doesnt every x86 app assume 4k pages? x86 processers dont have non 4k page sizes#asahi · 2026-05-10 21:11
chaos_princessnative arm64 apps will work fine#asahi · 2026-05-10 21:10
chaos_princessone example of an app that does this is windows version of adb#asahi · 2026-05-10 21:10
chaos_princessif a x86 app hardcodes that pages are 4k, it will usually break#asahi · 2026-05-10 21:10
Guest9139chaos_princess: like what? its worked about the same as wine on an x86 machine in my experience#asahi · 2026-05-10 21:09
chaos_princessyou can, but a lot of stuff will not work#asahi · 2026-05-10 21:08
Guest9139and same for the dlls, you can look at hangover on github for prebuilts#asahi · 2026-05-10 21:06
Guest9139lacamar: this is just wrong, you can build vanilla wine for arm64ec and run it without muvm#asahi · 2026-05-10 18:41
lacamar[m]Maybe in some exceptional cases, but the current FEX DLLs used by wine/proton arm64ec requires 4k pages to run almost anything#asahi · 2026-05-10 18:40
chaos_princessno#asahi · 2026-05-10 18:40
barusuwould compiling from source help avoid that chain? i know that muvm causes heavy memory usage#asahi · 2026-05-10 18:38
barusuAFAIR, muvm solves the 16k page size differences and fex translates x64 to arm#asahi · 2026-05-10 18:37
barusulacamar[m]: would this allow running proton outside muvm?#asahi · 2026-05-10 18:35
lacamar[m]Yes, it can be built using their container build process, however I couldn't manage to get it running anything but that's possibly a skill issue#asahi · 2026-05-10 18:11
user_anyone tried building proton natively? they seem to have added an arm64ec target as of a month ago#asahi · 2026-05-10 15:56
chaos_princessplayboicarti[m]: the demo works, fps is not great, but i could load into the level and run around a bit#asahi · 2026-05-10 15:51
MulchWell once, once, once again, thank you. Greatly appreciate the help.