Pete Hayman

I'm getting this too, I guess its a bug because afik no other md or html elements trigger onchange when setting values via code. It would be very helpful to...

Here's a bevy example for a bundle where two kinematic colliders will trigger a collision event: ```rust use bevy::prelude::*; use bevy_rapier3d::prelude::*; #[derive(Bundle)] pub struct ColliderBundle { pub collider: Collider, pub...

Edit: here's a summary of bevy xr forks I've come across with my understanding of the difference in features: - [zarik5](https://github.com/zarik5/bevy) - Last updated: 11/21 - [pull request](https://github.com/bevyengine/bevy/pull/2319) - OpenXR...

On my old pixel 3 the scene isnt rendering, might be a different issue from the OP. I can confirm that this is an issue with the Standard Material only,...

Update: The Bevy 0.11 [WASM examples](https://bevyengine.org/examples/) are currently working fine on my old Pixel 3 Android. Edit: Lighting example still pixelated like OP.

Here's a one-liner that works for me: ```ts import { getApps, initializeApp, } from 'firebase-admin/app' export const app = getApps()[0] || initializeApp({}) ```

> Where do you put this one-liner? I just make a file called `firebase.ts`, for instance when running on the server: ```ts //firebase.ts import { getApps, initializeApp } from 'firebase-admin/app'...

Yes same got the error on an `esp-idf` project after updating rust nightly to ``` rustc 1.78.0-nightly (ee9c7c940 2024-02-14) ```

> @mrchantey Which rust nightly version doesn't have this error? Pretty sure I was on the previous version `1.77.0-nightly`

fyi in my case after removing `-C default-linker-libraries` I got all kinds of errors when trying to use `esp_idf_svc 0.47.3` features like wifi. All good after doing a full clean...