BuildIng failed for native windows arm64 build

[CodeLikeCXK]

Seems the errors are related to wgpu versions. How to modify that?

[Patryk27]

Could you run cargo --version and show the results?

It seems like you don't have rustup and use a system-wide Cargo installation instead, which won't work in this case (for various technical reasons Strolle requires a specific toolchain version).

[CodeLikeCXK]

Could you run cargo --version and show the results?

It seems like you don't have rustup and use a system-wide Cargo installation instead, which won't work in this case (for various technical reasons Strolle requires a specific toolchain version).

I see. I just uninstalled the universal version and installed rustup.
It compiles now but would crash due to being unreachable for certain buffer.

[Patryk27]

Ah, that's interesting - it's probably because Strolle's toolchain is quite old (2023 [*]) and most likely just doesn't support this particular combination of Windows and arm64 (Windows + x86-64 seems to work, for instance).

I'll see if I can bump the toolchain over the weekend (if you want to play around, feel free to as well - thought it might be somewhat frustrating experience, since bumping toolchain requires switching from Embark's rust-gpu to the community-owned version, which might not necessarily be 100% compatible with the code here).

[CodeLikeCXK]

Ah, that's interesting - it's probably because Strolle's toolchain is quite old (2023 [*]) and most likely just doesn't support this particular combination of Windows and arm64 (Windows + x86-64 seems to work, for instance).

I'll see if I can bump the toolchain over the weekend (if you want to play around, feel free to as well - thought it might be somewhat frustrating experience, since bumping toolchain requires switching from Embark's rust-gpu to the community-owned version, which might not necessarily be 100% compatible with the code here).

That would be great. Thank you!

[Patryk27]

I've tried to upgrade the engine to Bevy 0.15 for the past four hours and I'm afraid I have to give up - there's too many moving parts; out of the bigger changes:

1. Newer wgpu validates that fragment shaders' targets don't exceed 32 bytes, so this shader (and in turn all other shaders as well):

strolle/strolle-shaders/src/prim_raster.rs

Line 59 in 69cbcdd

// Outputs

... would have to be redesigned to pack all of that information into 32 bytes instead of the 64 bytes the shader currently uses.

This shooould be doable (out_surface contains the same info as out_prim_gbuffer_d0 and out_prim_gbuffer_d1, just packed differently, and there's some spare space in out_prim_gbuffer_d* that should fit out_velocity), it's just a lot of work.

2. Bevy 0.15+ utilizes retained rendering world (Retain Rendering World bevyengine/bevy#14449), which requires adjusting a lot of logic within Strolle, e.g. around cameras:

strolle/bevy-strolle/src/stages/extract.rs

Line 366 in 69cbcdd

commands.get_or_spawn(entity).insert(ExtractedCamera {

I thought I've figured this one out, but on my development branch (https://github.com/Patryk27/strolle/tree/bevy-0.16) everything is still crashing with:

Attempting to create an EntityCommands for entity 12v1#4294967308, which doesn't exist.
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'Compute Task Pool (1)' panicked at /home/pwy/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_pbr-0.15.3/src/light_probe/mod.rs:445:18:
View entity wasn't synced.
thread 'Compute Task Pool (3)' panicked at /home/pwy/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_ui-0.15.3/src/render/mod.rs:582:18:
Camera entity wasn't synced.
thread 'Compute Task Pool (4)' panicked at /home/pwy/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_core_pipeline-0.15.3/src/core_3d/mod.rs:606:14:
Camera entity wasn't synced.
thread 'Compute Task Pool (6)' panicked at /home/pwy/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_pbr-0.15.3/src/cluster/mod.rs:540:14:
Clusters entity wasn't synced.
thread 'Compute Task Pool (2)' panicked at /home/pwy/.cargo/registry/src/index.crates.io-6f17d22bba15001f/bevy_pbr-0.15.3/src/light_probe/mod.rs:391:14:
/* ... */

... so there must be something I'm missing.

---

Overall I think most of the breaking changes made by upstream crates (notably wgpu and Bevy mentioned here) are actually for the better, that's how those things should work. At the same time, nowadays my focus has shifted towards https://github.com/Patryk27/kartoffels, so having to choose between sacrificing a couple of days bumping Bevy here and improving kartoffels, I choose the latter.

If you, or someone else, would like to pick up where I've left, feel free to - you can fork the repository and ping me if you need some help or guidance.